baslinux AT lists.ibiblio.org
Subject: Baslinux mailing list
List archive
- From: Day Brown <daybrown AT hypertech.net>
- To: baslinux AT lists.ibiblio.org
- Subject: Re: [BL] e2fsck, finally, now "init not found"
- Date: Thu, 08 Jan 2004 12:55:34 -0800
I would copy the data. I can see where laptops would have a frequent
problem with power loss, and there is no way of knowing what else has
been screwed up on the drive. Tracking down all the lost dependancies,
or making sure that whatever they are, they are compatable with the next
distro, seems like a much more iffy project and take a longer time than
just reformating the drive. Letting c/fdisk check all the sectors during
the partitioning seems a reasonably safer course.
And of course, since it may loose power again, do what BSD recommends,
install a small dos partition. You can park LTOOLS on it to access your
data if it ever crashes again. I can see that having a dos boot that
goes to loadlin and running your surfing browser in a ramdisk, would
mean that while your bookmarks and downloads can be copied from the
ramdisk cache to the hard drive, sabotage or other problems with the
kernel would be lost, or gotten rid of, just by shutting down the
system.
Would sabotage software realize it is running in a ramdisk?
-
[BL] e2fsck, finally, now "init not found",
James Miller, 01/08/2004
-
Re: [BL] e2fsck, finally, now "init not found",
3aoo-cvfd, 01/08/2004
- [BL] Lucent winmodems in linux - ltmodem.o, Sindi Keesan, 01/08/2004
- Re: [BL] e2fsck, finally, now "init not found", Day Brown, 01/08/2004
-
Re: [BL] e2fsck, finally, now "init not found",
3aoo-cvfd, 01/08/2004
Archive powered by MHonArc 2.6.24.