Subject: Re: bin/909: chown(1) and chflags(1) should be statically linked.
To: None <mrg@mame.mu.OZ.AU>
From: Chris G Demetriou <Chris_G_Demetriou@LAGAVULIN.PDL.CS.CMU.EDU>
List: netbsd-bugs
Date: 03/27/1995 03:21:32
> >Description:
>
> chown(1) and chflags(1) can be very useful in single usermode with
> out /usr. they should belong in /sbin/chown and /bin/chflags.
they're certainly not necessary (even in a wacked out case, as, say,
chmod would be) to get /usr mounted, and don't help to do so. I see
no reason to increase the size of / and further...
similarly:
diskpart
edquota
iostat
mtree <= VERY useful
nslookup <= VERY useful
pppd
pstat
pwd_mkdb
quot
rdate <= VERY useful
sysctl <= VERY useful
tcpdump <= VERY useful
update
vi <= VERY useful
vipw
vnconfig <= VERY useful
ar
as
awk <= VERY useful
bc
cc
cksum <= VERY useful
cpp
cpio
du
ex
false
true
find
fstat
ftp <= VERY useful
gprof
grep <= VERY useful
gzip <= VERY useful
hexdump <= VERY useful
ld <= VERY useful
make
[ OK, i got tired of looking... ]
are all very useful, and would be very useful to have in single-user
mode without /usr. In fact, i've wished to have most of them on /,
at some time or another.
For some of them (the ones that are marked 'very useful'), i think i'd
rather have them on / than chown or chflags, mostly because they allow
for reasonable system setup/debugging without mounting /usr (hey, if
you get /usr off of an NFS server, what if you can't figure out why
you can't mount it!).
The point is, / is for things that you _need_ to have in single-user
mode, before you mount /usr. (Actually, some of the things in / don't
really belong there, but that's traditionally where they've been, and
tradition has some meaning.)
Why can't you must mount /usr (even mount -o ro /usr) to usr chflags
and chown?
cgd