Hello everybody,
Carsten Aulbert wrote:
Hi all,
Ubuntu uses tmpfs for both /var/run as well as /var/lock:
$ mount | grep var
(rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
So that might be the reason for this. I had to manually alter a few
(Debian) start scripts to do a "mkdir -p /var/run/something/" when
porting Debian packages to Ubuntu.
I added /var/run/network and /var/lock in my base image and that problem
is now gone. However FAI sets up the /etc/fstab without varrun and
varlock as tmpfs.
I also have a problem that my installation sets up my fstab with
/dev/hdaX, but when rebooting ubuntu sees /dev/sda.
From feisty on my experience is that everything is used as /dev/sd? and
/dev/hd? is not used anymore. A machine with a SATA and a PATA disk
looks like this:
$ mount |egrep '(sd|hd)'
/dev/sda2 on / type xfs (rw)
/dev/mapper/sda1 on /boot type ext3 (rw)
/dev/mapper/sda4 on /home type xfs (rw)
/dev/sdb1 on /mnt/backup type xfs (rw)
Here sda is the SATA disk and sdb is PATA. Since Ubuntu uses disk-uuids
for mounting partitions it simply does not care anymore where the
partitions are located, even if you move them offline. That's something
I would like to see more ;)
Ah I didn't know that. The ftab that gets put on the ubuntu installed
machine is a default FAI fstab, thus without the disk uuids.
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office
Groep Systemen Systems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
