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

Florida is back on the Map for Linux and Open Source conventions with FOSSETCON 2

In summary the event was a good investment in time and booth expenses spent. We were able to distribute and promote Fedora in a very positive manner. More importantly getting more information on the various spins offered on our website pointed out to many individuals that there are more available on the Fedora Project website.. As the event ended on the 13th, I had had a conversation with the event coordinator with the plus side and the down side of what was going on. Read more

Linux 3.17-rc6

It's been quiet - enough so that coupled with my upcoming travel, this might just be the last -rc, and final 3.17 might be next weekend. Of course, that still depends on what happens - if we have something scary coming up next week, I may have to delay things. But as it looks right now, we're all good to go. The shortlog is appended, but the view from ten thousand feet is pretty normal: a bit more than half is drivers (gpu, sound, iio, media, usb), just under a third is arch updates (arm, mips, x86), and the rest is mainly filesystem updates (gfs2, cifs, btrfs, nfs). Nothing particular stands out, and I'm not aware of any big pending issues either. So please go out and test, because this *should* all be pretty close to release. Read more

today's leftovers

F2FS Tools Gain FSCK Support

The F2FS Tools v1.4.0 release introduces fsck.f2fs for fixing corrupted images/partitions for Samsung's Flash-Friendly File-System. There's also now dump.f2fs for retrieving a specific file. Additionally, the f2fs-tools 1.4 update also has bug-fixes for the stat and fibmap utilities. Last but not least is some code refactoring for the Android build. The release was mentioned today on the kernel mailing list by Samsung's Jaegeuk Kim. Read more