Puppy seems to override fstab changes

Using applications, configuring, problems
Post Reply
Message
Author
User avatar
HedonismBot
Posts: 1
Joined: Tue 25 Oct 2011, 17:05

Puppy seems to override fstab changes

#1 Post by HedonismBot »

Hi all,
I'm trying to do some optimizations on fstab but changes seem to be ignored.
I've added: noatime,data=writeback,commit=30 and tmpfs for /tmp and /var/lock-log-run
Here my fstab:

Code: Select all

/dev/sda2 / ext4 noatime,data=writeback,commit=30 0 1
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
none /dev/pts devpts gid=2,mode=620 0 0
tmpfs /tmp tmpfs noatime 0 0
tmpfs /var/lock tmpfs noatime 0 0
tmpfs /var/run tmpfs noatime 0 0
tmpfs /var/log tmpfs noatime 0 0
/dev/fd0 /mnt/floppy auto noauto,rw 0 0
This is mtab when Puppy is running:

Code: Select all

rootfs / rootfs rw 0 0
/dev/root / ext4 rw,relatime,barrier=1,data=writeback 0 0
none /proc proc rw,relatime 0 0
none /dev/pts devpts rw,relatime,gid=2,mode=620 0 0
none /sys sysfs rw,relatime 0 0
shmfs /dev/shm tmpfs rw,relatime,size=255916k 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
I think data=writeback was already enabled before i made changes

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#2 Post by Karl Godt »

For frugal puppy installation you would have to adjust or implement fstab into the initrd.gz

Fstab mounting would work if only one parameter is given like
mount /dev/sda2 , afaik .

The scripts mostly use more than one parameter
like
busybox mount -o remount,rw /
in the /etc/rc.d/rc.sysinit file , which would be most relevant for full installations .

The entry /dev/sda2 may not be correct , maybe it really should be /dev/root , but I dont know this exactly .

To mount everything other than that you would need to call
mount -a
which should mount all the other tmpfs stuff in your fstab .

Post Reply