Looked like a bourne shell to me. Default root shell is /bin/csh on
FreeBSD, but I believe /bin/sh is basically the same as ash.
Interestingly, MAKEDEV fails to work with bash but works fine with ash.
i'm not sure about freebsd, but netbsd has used ash in /bin/sh
for a Long Time. i even thought the debian one was based on the
netbsd sources but i could be wrong on that point.
>>Since bash is default /bin/sh, and
>>since what exactly is /bin/sh is subject to change by the user, this
>>must be patched in the source to use something other than /bin/sh.
>>Either that or fix the scripts so they will work with bash. I don't have
>>time to do the latter, and it'd be more work to maintain.
> Agreed, I just say that something other should be a Debianised shell
> like /bin/csh preferably to the /usr/bsd/bin/sh hierrachy.
sh is one of the tools it needs to build the source. There are several
others:
skaro:/# ls /usr/bsd/bin
byacc gcov kas kgdb kranlib make patch yacc
colldef gensetdefs kc++filt kld kreadelf mkdep sh
yyfix
compile_et install kcc knm ksize mknod tcsh
csh kaddr2line kcpp kobjcopy kstrings mktemp tsort
find kar kgasp kobjdump kstrip objformat xargs
And yes, all of these are things for which I can't presently substitute
the regular versions of these from Debian packages. :(
Several of the tools are there because they have incompatible options to
GNU versions. find and install for example. Others are apparently
BSD-specific, like gensetdefs or compile_et.
(dunno about gensetdefs, but compile_et is part of kerberos.)
FWIW, in netbsd-current, basically everything is cross buildable from
several platforms (netbsd-current, netbsd 1.5, freebsd, linux,
solaris, maybe more...) this is possible because we now build "native"
versions of all these tools before building the world. i heard a
whisper that freebsd is starting to be interested in cross compiling
(it was a reason to ditch perl as part of the base) so maybe they'll
get to that point eventually. in the netbsd source tree, see both
src/build.sh and src/tools... the former is a frontend script to building
stuff without having to know all the magic variables to set, etc., the
latter consists mainly of Makefile's to build native versions of tools,
eg, for lex we have:
# $NetBSD: Makefile,v 1.3 2001/11/14 22:13:40 tv Exp $
HOSTPROGNAME= nblex
HOST_SRCDIR= usr.bin/lex
.include "${.CURDIR}/../Makefile.host"
scan.c:
echo '#include <initscan.c>' >$@
(those ktools things scare me... i wonder why they need special
kernel wrappers/programs for all the toolchain bits...but i think i'd
be scared by the answer :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
