AJ>On Saturday 04 October 2003 18.42, Anders Johansson AJ>wrote: AJ>> I don't think you can use /dev/root from the rescue AJ>though, you have to AJ>> find out which partition it really is (hda1, hdb2 or AJ>whatever). Try ls -l AJ>> /dev/ root and see what it is AJ>Sorry, this was silly, you obviously know which AJ>partition it is since you can AJ>mount it and look at the fstab. What bothers me is that I have to rewrite the fstab because it is practically empty. It gives a /dev/root as an ext2 partition. But I know that I only had one 23.5Mb ext2 partition as /boot, a 258.8M as swap, further only reiserfs partitions. Above two partitions are with a 1.7 GB as /usr together with my drdos partition on my first harddisc. My second hd is 4 GB mounted as / and the third hd of 1,1 Gb as my /home Just write this in the fstab? And what about the mtab? -- ! Not on your life ! NTReader v0.36w(P)/Beta (Registered) in conjunction with Net-Tamer.
On Saturday 04 October 2003 20.11, Constant Brouerius van Nidek wrote:
What bothers me is that I have to rewrite the fstab because it is practically empty. It gives a /dev/root as an ext2 partition. But I know that I only had one 23.5Mb ext2 partition as /boot, a 258.8M as swap, further only reiserfs partitions. Above two partitions are with a 1.7 GB as /usr together with my drdos partition on my first harddisc. My second hd is 4 GB mounted as / and the third hd of 1,1 Gb as my /home
Just write this in the fstab? And what about the mtab?
The mtab file shouldn't be edited by humans. It is maintained by the kernel as and when things are mounted If YaST2 messed up your fstab you may just get lucky with a file like fstab.YaSTsave or something like it. Look for a backup file named like that before you start editing If you can't find a backup, then yes, you'll have to edit the fstab and put the correct entries in there
-----Original Message-----
From: Constant Brouerius van Nidek
AJ>On Saturday 04 October 2003 18.42, Anders Johansson AJ>wrote: AJ>> I don't think you can use /dev/root from the rescue AJ>though, you have to AJ>> find out which partition it really is (hda1, hdb2 or AJ>whatever). Try ls -l AJ>> /dev/ root and see what it is
AJ>Sorry, this was silly, you obviously know which AJ>partition it is since you can AJ>mount it and look at the fstab.
What bothers me is that I have to rewrite the fstab because it is practically empty. It gives a /dev/root as an ext2 partition. But I know that I only had one 23.5Mb ext2 partition as /boot, a 258.8M as swap, further only reiserfs partitions. Above two partitions are with a 1.7 GB as /usr together with my drdos partition on my first harddisc. My second hd is 4 GB mounted as / and the third hd of 1,1 Gb as my /home
Just write this in the fstab? And what about the mtab?
Never touch the mtab file, it is created automatically by the system and contains the current state of all mounted filesystems. Ken
The 03.10.05 at 01:11, Constant Brouerius van Nidek wrote:
What bothers me is that I have to rewrite the fstab because it is practically empty.
That's a file you should keep a printed copy on paper, together with the partition list and exact sizes.
And what about the mtab?
Nothing :-) -- Cheers, Carlos Robinson
Carlos, Mad as it seems I have to agree with this one. If it's a single system (not networked) then yes, print to paper. Better would be to write a config finder which emails the system config to another machine (your email adress), periodically. Sorry to jump in after the event but other list members might stop and think about this one ... Damian
What bothers me is that I have to rewrite the fstab because it is practically empty.
That's a file you should keep a printed copy on paper, together with the partition list and exact sizes.
And what about the mtab?
Nothing :-)
The 03.10.05 at 20:46, Damian O'Hara wrote:
Better would be to write a config finder which emails the system config to another machine (your email adress), periodically.
Nice idea... it could be in cron.daily, and email certain files only if they change. But, after all, this should be done for any setup by scheduled backups. What I meant is that we need to have an emergency recovery procedure. The minimum is the SuSE CD, plus a backup. A HD image is nice. And somewhere safe, a printout of the partition table and fstab, without which some HD recoveries become hard indeed. -- Cheers, Carlos Robinson
participants (5)
-
Anders Johansson
-
Carlos E. R.
-
Constant Brouerius van Nidek
-
Damian O'Hara
-
Ken Schneider