Date: Tue, 04 May 2004 09:11:58 +0300 From: Danny Braniss <danny@cs.huji.ac.il> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: kenv enhancement Message-ID: <20040504061200.9713643D46@mx1.FreeBSD.org> In-Reply-To: Your message of Mon, 3 May 2004 14:59:36 -0400 .
next in thread | raw e-mail | index | archive | help
> On Saturday 01 May 2004 08:22 am, Danny Braniss wrote: > > Hi, > > I propose to bring back some lost options to kenv, -c and -s > > ie, > > kenv -c class [-s] > > so that > > kenv -h is equivalent to kenv -c hint. > > and > > kenv -c boot.nfsroot. -s > > gives: > > nfshandle="X9ca48b3f5b77454e0c00000002000000bfa3063100000000000000000000000 > >0X" path="/d/6" > > server="132.65.16.100" > > > > the 'enhanced' kenv is in > > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/kenv/ > > > > danny > > I rototilled this a bit to make it use the existing style. I also renamed > 'class' to prefix since you can do things like 'kenv -p kern -s' to get > interesting output like: > > el="kernel" > el_options="" > elname="/boot/kernel/kernel" > > :-P > > One thing to note is that 'kenv -p foo' is basically the same as > 'kenv | grep ^foo', and that 'kenv -p foo -s' is basically the same as > 'kenv | sed -ne '/^foo/{s///;p;}'. Generally new options aren't added to > programs if they can be easily duplicated via a simple pipeline. Is there a > reason that you need kenv to do this explicitly rather than using sed or > grep? We use it very early in the boot process - rc.d/initdiskless, and /usr might not be mounted - not true in my particular case though. BTW, the flags I used are the same that once were in kenv and somewhere down the road were removed. danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040504061200.9713643D46>