du -a tmp/ run/

[hiro]

What are these files/folders for?

tc@thinkpad:~/jo$ du -a tmp/ run/
0   tmp/aberr
4   tmp/98-tc.rules
4   tmp/
0   run/udev
0   run/

[Rich]

Hi hiro
A grep search for aberr on /usr returned   /usr/bin/tce-setup   and   /usr/bin/appsaudit   which probably use it for logging errors.

The file   /etc/init.d/tc-config   contains the line   mv /tmp/98-tc.rules /etc/udev/rules.d/. 2>/dev/null
It looks like the boot code   nofstab   bypasses that line leaving  98-tc.rules  in  /tmp/

[curaga]

See the FHS for tmp and run. Actually /run might not be in the latest FHS yet, but udev requires it. It used to be /var/run.

[hiro]

So 98-tc.rules gets moved later on because we need a different behavior on boot?

Ok I read something on Poetterings /run dir and from what I understand udev breaks down without it or something. Nevermind...

[Rich]

Hi hiro
Upon booting  98-tc.rules  is initially  under  /tmp  because that's how it was saved when  tinycore.gz  was made.
98-tc.rules  just calls  /usr/sbin/rebuildfstab  when a drive is added or removed from the system, like a USB thumb drive.
If you use the boot code   "nofstab"   then  /etc/fstab  is not created and  /tmp/98-tc.rules is simply left where it is.
If you do not use the boot code   "nofstab"   then  /etc/fstab  is created and  /tmp/98-tc.rules is moved to its proper
location (/etc/udev/rules.d/) and the system is told those rules exist.
Without  /etc/fstab  anyone not in the sudoers list can not mount a drive.