tune2fs question

[James Miller <jamtat@mailsnare.net>]

I've recently succeeded in installing a Linux to a USB flash drive and, 
more importantly, booting to that drive using a floppy disk. A problem I 
have run into with tunefs needs addressing now. On the machine where I 
installed Linux, the drive was seen as /dev/sdb1. Apparently when I 
formatted the flash drive (ext2), some information regaridng the location 
of the drive was recorded for subsequent use. Now, when I reboot with the 
drive in a different system where it is actually /dev/sda1, e2fsck gives 
some error messages and wants to mount it read-only. I'm thinking that if 
I can change the system's understanding of the device file name, this 
problem might go away. Having looked over documentation (manpages) for 
e2fsck and tune2fs, I'm not finding how I could do this. Can anyone offer 
pointers on how I might get these ext2 filesystem utilities to be aware 
that the target device is not /dev/sdb1 but /dev/sda1?

On recovering a deleted file from reiserfs--the subject of my last post: I 
can confirm it is possible by rebuilding the directory tree. But I can 
also affirm that it is something you should NOT do on a root filesystem (a 
separate, data partition is the ideal target). It will corrupt important 
system files/modules if you do it on a root filesystem, necessitating a 
likely reinstall of the OS. On my system the kernel remains intact, but 
important modules are hosed, and maybe other key files. Think over 
carefully whether the file you want to recover is important enough to 
justify basically hosing the rest of your system.

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs