I'm attempting to take an fstab that looks something like this:
and write a script to loop through the "# Added by KNOPPIX" entries, then cut c1-9 off the next line and run mount $whatever-I-just-detected /mountpoint and also write that mountpoint to a file.
How would I write the condition to find "# Added by KNOPPIX" and then get it to look at the next line, first 9 characters, basically how can I get sed/awk/whatever to read something like this line by line and not go to the next line until it did something?
I install an external disk on my sun solaris 8
this went fine and I was able to access all filesystem on the disk. the new disk is mounted on /local
then 6 hours later
files under /local/files was 1 byte in size
at the same time I received the following
error message in... (4 Replies)
My site has a few sun solaris server including out NIS server and NFS server on solaris machines. we also have few suse linux and redhat linux machine.
All our home directory is on our NFS server(sun Solaris) and this is automounted through /etc/auto_master and /etc/auto_home this worked fine... (1 Reply)
Hello,
I have a SUN Solaris 9 machine (Sun-Fire-V490).
I put a DVD in the reader to install a software. The automount procedure did not work (vold is running) : I have nothing under /cdrom
When I try "eject" command I have the answer "No default media available"
When I try to mount manually the... (3 Replies)
Folks;
I'm mounting a directory on a different SUSE 10 server from my SUSE server fine. using this mount command:
# mount 192.168.132.11:/var/local/new /var/local/new
this command above works fine but when i added a new line to my "/etc/fstab" to be mounted automatically every time i... (2 Replies)
Hi friends
I'm a newbie trying to automount a nfs shared directory. Below is the configuration I'm using
FreeBSD machine as NFS server. IP Address - 192.168.1.60
# cat /etc/exports
/shared 192.168.1.50
Solaris 10 as NFS client. IP Address - 192.168.1.50
# cat... (1 Reply)
Hello experts,
On my RHEL box when i mount a nfs file system using autofs, the df -t shows the file system as nfs only. For which mounts does it report the filesystem as autofs. ?? I actually want to see the filesystem getting reported as autofs instead of nfs. Pls guide me
I... (1 Reply)
When i export the directory where the data really is, i can specify which hosts can mount it. On the remote server i create a mount point directory and then mount it to the source servers directory (that has the data).
I need to run my script on Server X , i would login there and type in the... (11 Replies)
Discussion started by: bkilaru
11 Replies
LEARN ABOUT NETBSD
vnduncompress
VNDCOMPRESS(1) BSD General Commands Manual VNDCOMPRESS(1)NAME
vndcompress, vnduncompress -- compress/uncompress file system images to/from cloop2 format
SYNOPSIS
vndcompress [-cd] disk/fs-image compressed-image [blocksize]
vnduncompress [-cd] compressed-image disk/fs-image
DESCRIPTION
The vndcompress program compresses an existing file system image into a cloop2 compatible compressed file system image. An optional block-
size can be given. If omitted, the default of 64kB is used.
The vnduncompress command decompress a cloop2-compressed file system image back into a regular image.
The file system images that can be handled are not limited to any specific file system, i.e. it is possible to handle images e.g. in ISO 9660
or UFS/FFS format. File system images in the cloop2 format are intended to be used with the vnd(4) driver in compressed mode as configured
by the -z option of the vnconfig(8) program, and later mounted with the appropriate -t option to mount(8).
OPTIONS
The following options are available:
-c Always compress, even if the program was started as vnduncompress.
-d Always uncompress (decompress), even if the program was started as vndcompress.
EXIT STATUS
The vndcompress and vnduncompress utilities exit with one of the following values:
0 The operation was performed successfully.
1 An error occurred.
EXAMPLES
To compress an existing CD-ROM file system image, run the following commands:
# vndcompress netbsd.iso netbsd.izo
Note that the resulting compressed image cannot be mounted directly via NetBSD's vnd(4) and mount_cd9660(8) commands any longer. Instead,
you will have to use the -z option of vnconfig(8).
The following example decompresses an existing CD-ROM file system image that was compressed in the cloop2 format into a regular file that can
then be mounted:
# vnconfig vnd0 KNOPPIX.iso
# mount -t cd9660 -o ro /dev/vnd0d /mnt
# vnduncompress /mnt/KNOPPIX/KNOPPIX /var/tmp/knoppix.iso
# umount /mnt
# vnconfig -u vnd0
#
# vnconfig vnd1 /var/tmp/knoppix.iso
# mount -t cd9660 -o ro /dev/vnd1d /mnt
# ls /mnt
.rr_moved cdrom floppy lib opt sbin usr
bin dev home mnt proc sys var
boot etc initrd none root tmp vmlinuz
# umount /mnt
# vnconfig -u vnd1
As an alternative, if your vnd(4) was compiled with VND_COMPRESSION, you can use vnconfig(8) to access the cloop-compressed image directly,
e.g.,
# vnconfig vnd0 KNOPPIX.iso
# mount -t cd9660 -o ro /dev/vnd0d /mnt
# vnconfig -z vnd1 /mnt/KNOPPIX/KNOPPIX
# mount -t cd9660 -o ro /dev/vnd1d /mnt2
# ls /mnt2
.rr_moved cdrom floppy lib opt sbin usr
bin dev home mnt proc sys var
boot etc initrd none root tmp vmlinuz
# df /mnt /mnt2
Filesystem Size Used Avail Capacity Mounted on
/dev/vnd0a 692M 692M 0B 100% /mnt
/dev/vnd1a 1.9G 1.9G 0B 100% /mnt2
# umount /mnt2
# vnconfig -u vnd1
# umount /mnt
# vnconfig -u vnd0
Note how the 1.9GB big filesystem on /mnt2 is mounted from the compressed file stored on the 692MB CD mounted on /mnt. To create a com-
pressed file system image of an existing directory and mount it, run:
# makefs -t ffs include.fs /usr/include
# vndcompress include.fs include.fs.cloop2
# vnconfig -z vnd0 include.fs.cloop2
# mount -o ro /dev/vnd0a /mnt
# ls /mnt
To undo the steps, run:
# umount /mnt
# vnconfig -u vnd0
# rm /tmp/include.fs.cloop2
# rm /tmp/include.fs
SEE ALSO gzip(1), vnd(4), mount(8), mount_cd9660(8), vnconfig(8)AUTHORS
The vndcompress utility was written by Florian Stoehr <netbsd@wolfnode.de>. The vndcompress manual page was written by Florian Stoehr
<netbsd@wolfnode.de> and Hubert Feyrer <hubertf@NetBSD.org>.
BSD December 12, 2005 BSD