Well once this is done, the disk environments will be highly similar. The
devices and the order they appear will be the same. So I suppose a manual
copy and minor tailoring of an existing fstab would be acceptable. It's
just not automatic and dynamic. I'm trying to be elegant here of course.
Elegance is always hard.
"Post, Mark K"
<[EMAIL PROTECTED]
m> To
Sent by: Linux on [email protected]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: Generating and fstab from list
of mounted file systems
10/21/2005 11:48
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
How many times are you going to do this? If it's once, or the output
will be identical for subsequent times, it would be easier just to do it
manually, based on what _you_ know about the various file systems. If
you want to know what each file system type is, the -T switch to the df
command will show you that. I find that easier to read than trying to
extract info from /proc/mounts or the mount command with no options.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
James Melin
Sent: Friday, October 21, 2005 10:58 AM
To: [email protected]
Subject: Generating and fstab from list of mounted file systems
Is thre a utility that can examine file systems that are mounted and
generate a new fstab?
Obviously after I do that single disk copy to the multiple HFS struture
I need to create a new fstab
If there's no utility that anyone knows, how does one get an fstab that
looks something like this:
pepin:~ # cat /etc/fstab
/dev/dasda1 / ext3 acl,user_xattr
1 1
/dev/dasdb1 /boot ext3 acl,user_xattr
1 2
/dev/dasdd1 /home ext3 acl,user_xattr
1 2
/dev/dasde1 /opt ext3 acl,user_xattr
1 2
/dev/dasdf1 /opt/IBM/WebSphere ext2 ro,acl
1 2
/dev/dasdc1 /root ext3 acl,user_xattr
1 2
/dev/dasdg1 /tmp ext3 acl,user_xattr
1 2
/dev/dasdh1 /usr ext3 acl,user_xattr
1 2
/dev/dasdi1 /var ext3 acl,user_xattr
1 2
/dev/dasdj1 /work ext3 acl,user_xattr
1 2
/dev/dasdk1 swap swap pri=42
0 0
devpts /dev/pts devpts mode=0620,gid=5
0 0
proc /proc proc defaults
0 0
sysfs /sys sysfs noauto
0 0
from this:
vadnais:/etc # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/dasdb1 2125924 1927060 90872 96% /
tmpfs 510532 0 510532 0% /dev/shm
/dev/dasdc1 209120 141756 56572 72% /mnt
/dev/dasdd1 52200 8948 40560 19% /mnt/boot
/dev/dasde1 34764 460 32512 2% /mnt/root
/dev/dasdf1 191680 90384 91404 50% /mnt/home
/dev/dasdk1 418344 65364 331388 17% /mnt/var
/dev/dasdi1 850292 20 807080 1% /mnt/tmp
/dev/dasda1 850292 20 807080 1% /mnt/work
/dev/dasdg1 2763768 141052 2482324 6% /mnt/opt
/dev/dasdj1 2976336 1446328 1378816 52% /mnt/usr
/dev/dasdh1 237720 4 225448 1%
/mnt/opt/IBM/WebSphere
The existing fstab for the single disk system that gets copied from the
single volume system looks like:
vadnais:/etc # cat fstab
/dev/dasdb1 / ext3 acl,user_xattr
1 1
/dev/dasdl1 swap swap pri=42
0 0
devpts /dev/pts devpts mode=0620,gid=5
0 0
proc /proc proc defaults
0 0
sysfs /sys sysfs noauto
0 0
Specifically I'm interested in figuring out how to examine a file
system, determine if it's ext3, ext2, reiser, etc,and what the
attributes should be (like acl,usr_xattr and the 1 1 or 1 2 stuff) The
fstab example was generated by a manual install of the sles 9 system I
am now trying to re-create via the single disk clone and copy to final
destination method.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
