Bill Rugolsky Jr. wrote:
On Tue, Jan 21, 2003 at 09:44:11AM -0600, Thomas Dodd wrote:That one I didn't know :) Better than the problems of symlinks :)
I don't think so... If adding a new disk is not possible, use a file, the wonder of loop devices :) While people regularly use loop mounts for CD and floppy images or the initrd, they forget that almost any filesystem/mountpoint can be a loop device. I did this recently for /var/spool/up2date. The system is mainly a wi98 box, but it has a small linux install. So when I didn't have room for new updates, I tried a symlink. For various reasons it didn't work well, symlinking /var/spool/u2date to a FAT32 filesystem, so I created a new filesystem using the loop device and a file on the FAT32 filesystem. dd, losetup, and mke2fs where all it took.When you have free space on a filesystem with Linux semantics (e.g., /home),
bind mounts make more sense:
mkdir /home/up2date
mount --bind /home/up2date /var/spool/up2date
Still, that doesn't work for FAT16/FAT32/vfat, does it? While loop works there too.
Not sure if either work _well_ with NFS/SAMBA.
-Thomas
_______________________________________________
Redhat-devel-list mailing list
Redhat-devel-list@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
