Why the LS-120 Still Survives

I’ve written about the LS-120 on this blog before but I thought about it again today.  You see, yet another Micro Center sales paper showed up.  There were big sections for USB flash drives and SD cards, but nothing listed for organizers.  I paid a visit to eBay to find a bunch of SD travel cases aimed at family vacationers, but nothing for desktop storage and organization.  There was absolutely nothing for USB flash drives either for carrying or organizing.

Today’s product engineers are really a clueless lot.  None of them take into account existing practices and infrastructures when designing a new toy.  Yes, it is all well and good to make a USB flash drive key ring, but if you want your new media to sell in large quantities it needs to find a niche in the backup market.  Engineers of yesteryear knew these things.

First we had the 5 ¼ inch floppy which replaced the unwieldy 8 inch floppy.  Rather than replace it, most engineers found ways to double its capacity until it reached 1.2Meg.

IBM fought an up-hill battle when they introduced 720K 3.5 inch floppies.  We already had 1.2Meg floppy drives in our machines combined with a stack of disks and multi-drawer floppy organizers capable of holding a hundred or more floppies per drawer.  Yes the 3.5 inch had a hard case and could fit in most suit shirt pockets, but they didn’t hold as much.  Then IBM pushed the storage capacity to 1.44Meg.  The storage increase combined with the introduction of laptops pushed the 3.5 inch floppy into the world.  Floppy organizers and carrying cases appeared for the new media size.

Most people were neither patient enough nor rich enough to use tape as their primary backup.  The tape drives which could be purchased for under $400 were ice-melting-in-winter slow and typically only held 120Meg.  Later they boosted capacity to a claimed 250Meg, but, that was only if things being backed up weren’t already compressed.

The 5 ¼ floppy people were a bit pissed with all of this.  They went off and talked to the people who were designing the CD-ROM and guess what?  The media for the CD-ROM just happened to be designed so people could re-use all of those 5 ¼ media organizers and transport cases.  Early versions were read only, but provided software vendors with a method of shipping a single media unit instead of boxes of floppies.

Notebook users still wanted a convenient method of backing things up.  Low and behold the LS-120 appeared on the market and just happened to be the exact same size as the original 3.5 inch floppy.  In fact, you could read and write those 3.5 inch floppies in the same drive so it became the defacto standard drive in laptops.  Later models could store 240Meg on a single disk.  All of the same 3.5 inch floppy containers worked for these new disks so adoption was quick.

The CD crowd came out with both CD-R for the regular end user and CD-RW for those wanting to be just a bit kinder to the environment.  Yes, CD-R media sells in spindles of a hundred for $5 if you shop around, but landfills are only so deep.  Neither of these media really solved the “working backup” problem.  They were supposed to solve the long term backup problem until studies showed the media only retained its data for about five years unless you purchased the very expensive “archival quality” version of the disks.  Still, very few items last the 7-12 years which could be required either in court or by the IRS.

Rotating project backup really doesn’t have a better solution than the LS-120 today.  Yes, many people are just alternating between two USB hard drive enclosures and holding their breath, but, that’s not good.  Hard drives made today are not of the same quality they were during the peak of SCSI server drives.  Back then a 5 year MTBF (Mean Time Between Failures) could be trusted.  Today you find out IDE and SATA drives achieve their 5 year MTBF by putting in fine print the drive is to remain in power saver mode 70-80% of the time.  SAN administrators have to continually point this out to MBAs when explaining the cost of a 1TB SCSI based SAN vs. the sub $100 1TB SATA drive.

Many people work as writers, business analysts, technical architects, etc.  We all have one thing in common.  The bulk of what we create for each project can easily fit inside a 120Meg boundary.  Usually we can backup multiple projects onto these media and keep a rotating set of backup media on our desk with special copies stored at a friend’s house or some other off-site location.  The media is both cheap and durable.  It is fast enough for backup purposes and supported by most Linux and Windows versions.  To top it all off, most of us have something which looks quite nice to store the media in.

http://www.etsy.com/listing/92222446/tambour-teak-storage-box?ref=sr_gallery_2&sref=&ga_search_submit=&ga_search_query=roll+top+disk&ga_view_type=gallery&ga_ship_to=US&ga_search_type=all&ga_facet=

Until somebody comes up with something nice that will let you keep a rotating set of backups organized for the other forms of media trying to fill this niche, the LS-120 will continue to have an active market.

OpenSuSE When Home Isn’t /home Anymore

Over the last few days I’ve been building a new desktop machine.  I was going to hold off another year or so, but, I’m getting paid well for doing timely writing and I didn’t want to find myself suddenly reduced to my laptop.  I had replaced a few components in my other machine, but the CPU and motherboard were over 5 years old according to the dates they displayed when booting.  I had recently even had to replace the CPU fan due to noise the other one was making, thus, I bit the bullet and ordered enough pieces to assemble an AMD 3Ghz Quad Core desktop in an old Systemax case I had laying around.

This one needed to have a DOS boot partition as well as OpenSuSE because I might get back into doing some Zinc work later this year.  I dutifly obtained MS-DOS 7.10 GNU licensed DOS and FreeDOS 1.1.  After installing MS-DOS, then FreeDOS, I was horribly upset with FreeDOS.  It had way more problems than the previous version AND most of the boot software now displayed MS-DOS 7.1 logos.  The same appeared to be true with both the DRDOS enhancement project and NXDOS.

Of course, I made the grand assumption that my FAT-32 DRIVE_D partition would be accessible by either DOS.  Ever since I started using OS/2 over a decade ago I had the habit of keeping either a FAT-16 or FAT-32 DRIVE_D partition so I could exchange files with any other OS on my machine.  There was a time when I had (and needed) more than three operating systems on the machine due to the work I was doing at the time.  The FAT logical drive in an extended partition allowed me to quickly exchange data.  This was long before we had thumb drives.  You should also know that USB devices and DOS don’t have the magic they do with GUI systems.

Insult was added to injury when I booted MS-DOS 7.1.  (FreeDOS once again had issues booting under Grub.)  The “extended partition” created by the OpenSuSE installer has a type of 69 which is completely unrecognized by MS-DOS.  This lead me to delete the FreeDOS partition and manually move the DRIVE_D logical drive to a physical primary partition.  Of course I also decided to expand two other logical drives to utilize the space once consumed by DRIVE_D.  I used the Gnome Partition tool on Parted Magic 6.7 CD.  I knew I should have just backed things up, deleted, then restored, but, I was getting ready to leave so opted to let this run all night, which is exactly how long it took.

I was the good little soldier.  I booted recovery and dumped the information to manually edit fstab.

linux-pus9:/home/roland # fdisk -l

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00028bf5

Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63    40337407    20168672+   c  W95 FAT32 (LBA)
/dev/sda2        40337408    81981439    20822016    b  W95 FAT32
/dev/sda3   *    81981440  2930276351  1424147456    f  W95 Ext'd (LBA)
/dev/sda5        81983488    86188031     2102272   82  Linux swap / Solaris
/dev/sda6        86190080   128135167    20972544   83  Linux
/dev/sda7      1227030528  2695049215   734009344   83  Linux
/dev/sda8      2695051264  2930255871   117602304   83  Linux
/dev/sda9       128137216  1227028479   549445632   83  Linux

Partition table entries are not in disk order

I also completely ignored the last line in green.  Very carefully I changed all of the FSTAB entries to match this output.  When I rebooted my home was gone.  It was there under a different “home” location, just not the one the boot pointed to.

Much frustration and head scratching occurred, then I noticed this:

partitioner view

Yast expert partitioner

The output from fdisk has the partitions in the wrong order.  My books partition was being mounted as /home, and several other things were hosed.  Another careful edit session followed by a reboot made things all better.

 

1 2 3 4 5 ... 93 94