From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Martin Schlemmer <azarah@gentoo.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files
Date: 24 Apr 2003 13:03:05 +0100 [thread overview]
Message-ID: <1051185785.776.3.camel@gregs> (raw)
In-Reply-To: <1051184807.3604.2642.camel@workshop.saharact.lan>
On Thu, 2003-04-24 at 12:46, Martin Schlemmer wrote:
> On Thu, 2003-04-24 at 09:57, Grzegorz Jaskiewicz wrote:
>
> > Well, if you will read my post - i am trying to use _ONLY_ devfs,
> > without any demons.
>
> Ok, missed that.
>
> > Those demons are provided just to keep backward
> > compatbility (at least this is my opinion) and can be used without them.
> >
>
> Well, not really. Yes, it does support the compat symlinks, etc, but
> you can do much more with devfsd than just that. Setting the
> permissions/ownership on node registration, autoloading of modules
> if a node is accessed, etc is just a few.
Well, we don't need that - all we need is just file with settings cat-ed
to some /proc entry or script that sets up perms on boot/hotplug events.
>
> > i don't like personaly any ideas about udevfs and others. We should get
> > rid of min/maj nr of each device becouse each single program uses device
> > by name indeed ! Having just devfs solves many problems and is very good
> > thing. But, again - without any userspace demons.
> >
>
> See above.
>
> > Linus was always trying kernel as simple as it is possible, well - imho
> > devfs is just one step forward to make it even simpler but without
> > removing any of it functionality.
> >
>
> I guess you could see the management of devfs being done in userspace
> (devfsd) as keeping kernel side simple :P
Well, my point is - why i should install tons of userspace programs while everything can be/should be done internaly - becouse those demons are very close to kernel !
And it is pointles, kernel should be able to do everything required to be fully working by its self - not relay on some userspace shit.
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 Labs
next prev parent reply other threads:[~2003-04-24 11:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 17:49 [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files Pavel Roskin
2003-04-21 17:55 ` Christoph Hellwig
2003-04-21 17:58 ` Christoph Hellwig
2003-04-21 18:53 ` Pavel Roskin
2003-04-21 19:00 ` Christoph Hellwig
2003-04-21 19:44 ` Pavel Roskin
2003-04-21 19:56 ` Christoph Hellwig
2003-04-21 20:35 ` Pavel Roskin
2003-04-21 20:44 ` Grzegorz Jaskiewicz
2003-04-21 20:56 ` Pavel Roskin
2003-04-24 7:39 ` Martin Schlemmer
2003-04-24 7:57 ` Grzegorz Jaskiewicz
2003-04-24 11:46 ` Martin Schlemmer
2003-04-24 12:03 ` Grzegorz Jaskiewicz [this message]
2003-04-21 20:57 ` Christoph Hellwig
2003-04-21 21:15 ` Pavel Roskin
2003-04-21 21:23 ` Christoph Hellwig
2003-04-21 21:45 ` Pavel Roskin
2003-04-21 22:25 ` Christoph Hellwig
2003-04-21 22:37 ` Pavel Roskin
2003-04-22 10:12 Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1051185785.776.3.camel@gregs \
--to=gj@pointblue.com.pl \
--cc=azarah@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).