Date: Mon, 23 Sep 1996 18:12:49 +0100 (BST) From: Jeremy Prior <jez@netcraft.co.uk> To: freebsd-current@freebsd.org (FreeBSD's Current Mailing List) Subject: ncheck and a multi-lingual fsck Message-ID: <199609231712.SAA10123@server.netcraft.co.uk>
next in thread | raw e-mail | index | archive | help
All,
I've always missed the lack of ncheck(8) in FreeBSD - The 4.4BSD
manual page for it is wrong - its functionality is not obsoleted by
fsck(8)! Specifically, I miss ncheck's `-s' option (find / -perm ...
is no substitute).
My nostalgia turned into desperation when find started falling over
with an out-of-memory error in our news-spool partition during the
nightly /etc/security run. (Sorry, I don't have the error message to
hand - I can let people have it after tonight's run if they're
interested :-)
I was about to write an ncheck clone (using fsck as a starting
point), and had even got to the point of soliciting sample output for
other vendor's versions, when I discovered that one already exists!
OpenBSD has had ncheck (actually ncheck_ffs) since mid August.
So, I fetched, built, and installed their ncheck (no changes needed
other than the name :-), and it works fine! I'm currently in the process
of rewriting my /etc/security to use it.
Anyway, I'm now wondering whether I should with it. My options are:
1. keep it to myself and shut up :-)
2. submit it as-is, and let someone else decide what to do with it;
(I could also submit chkdsk(8) - aka fsck_msdos at the same time...)
or
3. go the whole way and submit it as part of a general `cleanup', where
each of the fs-dependent programs (fsck, ncheck, ...) are called by
an fs-independent parent (I'd use mount(8) as the template).
What do other people think? Do people want this? Am I treading on
anyone else's toes? by doing this :-) Opinions?
jez
--
Jeremy Prior <jez@netcraft.co.uk>
Netcraft, Rockfield House, Granville Road, Bath, BA1 9BQ, England
Tel: +44-1225-447500 Fax: +44-1225-448600
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609231712.SAA10123>