Language Selection

English French German Italian Portuguese Spanish

I been Buffalo'd

Filed under
Reviews

Buffalo Linux 1.7.3 was released on May 10 and it sounded quite interesting. I'd visted their website a couple times in the past but never installed this oddly named distro. Now with the site up and running I thought the time was right.

The boot up of the new livecd format seems to go well detecting most hardware, loading up necessary modules, and configurations. I could tell almost immediately this distro must be based on slackware, then the interactive configuration dialogues confirmed this.

All seemed to be going fine until it tried to autologin into an X environment. All I got was a big tan screen of nothing else. The mouse responded, but nothing else would. I couldn't kill X or ctrl+alt+Fx to terminal. After seeing all my partitions mounted during boot all I could do was hit reset. Bad bad Buffalo mounting all partitions without asking. Luckily no perceivable damage detected as of yet after fsck. Time will tell for sure tho.

I had one other distro just boot to a blank X screen like that, but I can't remember which one it was now. I wanted to blame it on my video card at first, then remembered that damn small and even pcbsd had no trouble with it. So, I don't know what's up with Buffalo, but I'm gonna be a little shy about wanting to test future releases unless the author turns off that mounting all partitions thing.

Buffalo ain't the only livecd that mounts all the partitions automagically. I think this is a very dangerous trend. Oh I see the reason for it, user-friendliness. But I think somewhere the line needs to be drawn. Why not place an icon on the desktop to a script that mounts them after boot? I'd be making a bigger stink about all this had I lost some important data. Down with auto-mount! Big Grin Down with auto-mount. Come on, protest with me...

If anyone else would like to review and post screenshots of Buffalo, they'd be most welcome to submit. Another distro that I wanted to review but was not able to boot was flonix. If you have a review of flonix, please submit. Smile

More in Tux Machines

OpenBSD Gets Mitigated For Meltdown CPU Vulnerability

  • OpenBSD Gets Mitigated For Meltdown CPU Vulnerability
    A few days back FreeBSD 11 stable was mitigated for Meltdown (and Spectre vulnerabilities), which came more than one month after these nasty CPU vulnerabilities were disclosed while DragonFlyBSD was quickly mitigated and the first of the BSDs to do so. While OpenBSD is known for its security features and focus, only today did it land its initial Meltdown mitigation.
  • Meltdown fix committed by guenther@

    Meltdown mitigation is coming to OpenBSD. Philip Guenther (guenther@) has just committed a diff that implements a new mitigation technique to OpenBSD: Separation of page tables for kernel and userland. This fixes the Meltdown problems that affect most CPUs from Intel. Both Philip and Mike Larkin (mlarkin@) spent a lot of time implementing this solution, talking to various people from other projects on best approaches.

    In the commit message, Philip briefly describes the implementation [...]

France Proposes Software Security Liability For Manufacturers, Open Source As Support Ends

It sometimes seems as though barely a week can go by without yet another major software-related hardware vulnerability story. As manufacturers grapple with the demands of no longer building simple appliances but instead supplying them containing software that may expose itself to the world over the Internet, we see devices shipped with insecure firmware and little care for its support or updating after the sale. The French government have a proposal to address this problem that may be of interest to our community, to make manufacturers liable for the security of a product while it is on the market, and with the possibility of requiring its software to be made open-source at end-of-life. In the first instance it can only be a good thing for device security to be put at the top of a manufacturer’s agenda, and in the second the ready availability of source code would present reverse engineers with a bonanza. Read more

today's howtos

Security: Updates, Word and More