Re: release-5 restorecd issue
Izumi Tsutsui <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.cobalt |
|---|---|
| Message-ID | <[email protected]> |
[email protected] wrote: > I got the first version of the restore cd and did a complete overwrite > to a new drive on my Qube2 tonight. > > When I tried to use chsh to change the shell, it complained that the > sticky bit wasn't set on /tmp. > > I think this is common when unpacking the sets without using the > "preserve" option. If using tar, it's the -p option. > > You can fix the problem by doing this: > > chmod 1777 /tmp Hmm, I wonder why no one else has noticed it for many years... I'll prepare fixed one in this weekend, but you could try the attached patch: --- restorecd-5.0_BETA/data/cobalt/install/scripts/install-core.sh.orig 2008-11-01 17:34:39.000000000 +0900 +++ restorecd-5.0_BETA/data/cobalt/install/scripts/install-core.sh 2008-11-27 22:23:30.000000000 +0900 @@ -290,7 +290,7 @@ # Fix permissions $CHMOD 755 /mnt/var - $CHMOD 4777 /mnt/tmp + $CHMOD 1777 /mnt/tmp $UMOUNT /mnt/tmp $UMOUNT /mnt/var > Is this worth a pr? No, the official installer (sysinst(8) in RAMDISK kernel) doesn't has this problem and restorecd isn't a part of official distribution (yet?), so it's enough to report a problem here. --- Izumi Tsutsui