Re: cruft : great program ! everyone should use it !
On Sat, Apr 25, 1998 at 01:06:35PM +0200, Andreas Jellinghaus wrote:
i realy like cruft a lot ! i strongly suggest to all developers to check
their systems, and improve the packages.
Thanks :)
suggestion to the craft autor :
with MAKEDEV -I you can create device files in the local directory,
even within fakeroot. what about adding a list of the normal devices to cruft,
and report obsolete devices, strange permissions, etc. this would require
some cooperation with the makedev maintainer, but would be realy good.
I've already mentioned this to Andreas on irc, but I've got a first draft
of this implemented -- it currently checks that you have exactly those
devices listed in MAKEDEV's generic batch. Andreas also suggested that
it should allow, but not require, *any* device file MAKEDEV knows about,
which will require a little reworking of cruft, so I've left that until
I have a little time to think about it.
What I'm using at the moment is a new version of /usr/lib/cruft/explain/dev,
which looks something like:
---
#!/bin/sh
if [ -x /dev/MAKEDEV ]; then
/dev/MAKEDEV -In generic | grep -v '^l' | awk '{ print /dev/ $8 }'
/dev/MAKEDEV -In generic | grep'^l' | awk '{ print /dev/ $2 }'
fi
---
If you copy that into /etc/cruft/explain/dev, it will override the dev
explanation thingy that's distributed with cruft, without messing with
.deb'ed files, btw.
Just FYI.
Cheers,
aj
--
Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/
I don't speak for anyone save myself. PGP encrypted mail preferred.
``It's not a vision, or a fear. It's just a thought.''
pgpE2SGMMNL2t.pgp
Description: PGP signature
Re: cruft : great program ! everyone should use it !
In article [EMAIL PROTECTED] you wrote: : with MAKEDEV -I you can create device files in the local directory, : even within fakeroot. what about adding a list of the normal devices to cruft, : and report obsolete devices, strange permissions, etc. this would require : some cooperation with the makedev maintainer, but would be realy good. WARNING WARNING WARNING The makedev maintainer (that's me) intends to change upstream code bases in a significant way for slink. Any work on device file consistency in cruft would be well-advised to wait a month or three, until this gets done. I'd hate to see a lot of work go into whacking around with the current MAKEDEV since I can't guarantee that the options will all be the same, etc... Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cruft : great program ! everyone should use it !
Bdale Garbee [EMAIL PROTECTED] wrote: a significant way for slink. Any work on device file consistency in cruft would be well-advised to wait a month or three, until this gets done. I'd hate to see a lot of work go into whacking around with the current MAKEDEV since I can't guarantee that the options will all be the same, etc... That should just be a configuration detail, though. No? -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cruft : great program ! everyone should use it !
On Sun 26 Apr 1998, Joey Hess wrote: Andreas Jellinghaus wrote: with MAKEDEV -I you can create device files in the local directory, even within fakeroot. No you can't. Making such files requires root permissions. Fakeroot emulates making them, but from outside fakeroot, they look like normal 0 byte files. you are right. but the idea was to get a list of all devices and their security informations, and for this fakeroot is sufficient. andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cruft : great program ! everyone should use it !
Andreas Jellinghaus wrote: with MAKEDEV -I you can create device files in the local directory, even within fakeroot. No you can't. Making such files requires root permissions. Fakeroot emulates making them, but from outside fakeroot, they look like normal 0 byte files. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
