Joined: July 2004
||Posted: April 22 2008,12:41
/etc/init.d/dsl-config, line 267:
|Code Sample |
| 260 if [ -d "/mnt/$MYHOME$HOME" ]; then|
261 mount --bind "/mnt/$MYHOME$HOME" "$HOME/"
263 mkdir -p "/mnt/$MYHOME$HOME"
264 mount --bind "/mnt/$MYHOME$HOME" "$HOME/"
265 tar -C /KNOPPIX/etc/skel -cf - . | tar -C "$HOME" -xf -
266 printf 'wm: %s\nicons: %s\n' "$DESKTOP" "$ICONS" > "$HOME"/.desktop
267 chown -Rh "$USER".staff "$HOME"
To me this looks like chown occurs only if the home directory does not already exist, but for some reason it seems to happen every time I boot. I had a suspicion this was happening, but never actually looked into it until this morning. Everything in my home directory is dsl.staff, even though I know positively that yesterday it wasn't.
I keep all my work files, including mydsl extensions, in a persistent home. Every time I package an extension I have to chown the files even if I'd already done it last time i worked on that project. If I'm currently working on an extension and compress it to test, if I shut down, go to bed, and then decide I need to make a change the next day, I have to chown the files all over again.
It's not just the extensions, though. I also have a peculiar way of doing a partially persistent /root. Some of root's configuration files are linked to or copied from files in a subdirectory of /home/dsl, and they should belong to root. There are also a couple of system files that are copied from a subdirectory in home. This is done from bootlocal, so I can always chown them after the copy, but I shouldn't need to do this.
So....is this happening to anyone else with a persistent home?
My boot options:
root=/dev/hda3 vga=791 knoppix_name=KNOPPIX-4.2.3 dsl syslog legacy noswap noacpi noapm dma noscsi frugal home=hda4 mydsl=hda4/home/dsl/mydsl host=bungle
Perhaps there's a conflict with using mydsl inside home?
In any case, it doesn't seem like I'm doing anything technically wrong, so this might be considered a bug report, or at least a suggestion of something to look into.