In message <[EMAIL PROTECTED]>, Munehiro Matsuda writ
es:
>Hi All,
>
>I just got following DEVFS related message with
>this mornings current.
>
>DEVFS Overflow table with 32768 entries allocated when 925 in use
>
>Anybody seen this?
This is mostly harmless.
When DEVFS initially was integrated the
In message <[EMAIL PROTECTED]>, Marc Olzheim writes:
>On Wed, Jun 04, 2003 at 03:44:28PM +0200, Harti Brandt wrote:
>> MO>( echo foo | tee /dev/fd/3 | tr f F ) 3>&1
>> MO>
>> MO>It should produce both "foo" and "Foo"
>>
>> mount -tfdescfs fdesc /dev/fd
>>
>> but your example doesn't work even the
On Wed, Jun 04, 2003 at 03:44:28PM +0200, Harti Brandt wrote:
> MO>( echo foo | tee /dev/fd/3 | tr f F ) 3>&1
> MO>
> MO>It should produce both "foo" and "Foo"
>
> mount -tfdescfs fdesc /dev/fd
>
> but your example doesn't work even then (although it gives no error).
> Don't know why.
Hmm, it do
In message <[EMAIL PROTECTED]>, Marc Olzheim writes:
>Hi.
>
>I've seen the question once before, but it was not answered (on-list ?),
>so now that I run in on it, I'd like to know what to do:
>
>On FreeBSD 4.x, without devfs, the following worked:
>( echo foo | tee /dev/fd/3 | tr f F ) 3>&1
>
>It s
On Wed, 4 Jun 2003, Marc Olzheim wrote:
MO>Hi.
MO>
MO>I've seen the question once before, but it was not answered (on-list ?),
MO>so now that I run in on it, I'd like to know what to do:
MO>
MO>On FreeBSD 4.x, without devfs, the following worked:
MO>( echo foo | tee /dev/fd/3 | tr f F ) 3>&1
MO>
M
On Wed, Jun 04, 2003 at 03:30:19PM +0200, Marc Olzheim wrote:
> Hi.
>
> I've seen the question once before, but it was not answered (on-list ?),
> so now that I run in on it, I'd like to know what to do:
>
> On FreeBSD 4.x, without devfs, the following worked:
> ( echo foo | tee /dev/fd/3 | tr f
Taavi Talvik <[EMAIL PROTECTED]> wrote:
> On Fri, 10 Jan 2003, Attila Nagy wrote:
>
> > Is there a recommended way to configure multiple devfs rules (massive jail
> > usage) in a standard manner? I don't see any traces of it.
> > Or is it up to the user how does he manage this question, for exampl
On Fri, 10 Jan 2003, Attila Nagy wrote:
> Is there a recommended way to configure multiple devfs rules (massive jail
> usage) in a standard manner? I don't see any traces of it.
> Or is it up to the user how does he manage this question, for example a
> shell script with the rules?
If you are usi
Attila Nagy <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Is there a recommended way to configure multiple devfs rules (massive jail
> usage) in a standard manner? I don't see any traces of it.
> Or is it up to the user how does he manage this question, for example a
> shell script with the rules?
Ther
On 26-Dec-2002 (23:11:27/GMT) Gernot A. Weber wrote:
> devfs rule add path uscanner0 mode 666
I used this way:
-8<-[ /etc/usbd.conf ]-8<-
[...]
device "Scanner Epson Perfection 1240U (photo)"
product 0x010b
vendor 0x04b8
release 0x0114
devname "uscanner[0-9]+"
Hello,
On Fri, Dec 27, 2002 at 12:11:27AM +0100, Gernot A. Weber wrote:
> Hi,
>
> I know how to change file permissions on devfs. But which file do I have
> to edit that these changes are no lost after a reboot? E.g. I altered my
> scanner dev:
You would need to edit /etc/rc.devfs.
> Another th
On Sat, Nov 16, 2002 at 10:15:53AM -0500, sven svenskar wrote:
> I have server i give people shell accounts each in chroot and they need some
>devices. How this work with DEVFS? Should I copy devices from DEVFS with dd or tar?
>Or I mount DEVFS in every chroots? Please help!
why not just use jai
In message <[EMAIL PROTECTED]>, Dima Dorfman writes:
>Taavi Talvik <[EMAIL PROTECTED]> wrote:
>>
>> I'i try to set up jail with following script, however
>> as result, urandom/stdin/stdout/stderr will not appear.
>>
>> They exist before applying devfs rules, but I cannot find
>> rules how to unhi
Taavi Talvik <[EMAIL PROTECTED]> wrote:
>
> I'i try to set up jail with following script, however
> as result, urandom/stdin/stdout/stderr will not appear.
>
> They exist before applying devfs rules, but I cannot find
> rules how to unhide those. Any ideas!?
Please try the attached patch, which
In message <[EMAIL PROTECTED]>, Kyle Martin writes:
>On Sat, Nov 16, 2002 at 10:15:53AM -0500, sven svenskar wrote:
>> I have server i give people shell accounts each in chroot and they need some
>devices. How this work with DEVFS? Should I copy devices from DEVFS with dd or tar?
>Or I mount DEVF
On Sat, Nov 16, 2002 at 10:15:53AM -0500, sven svenskar wrote:
> I have server i give people shell accounts each in chroot and they need some
>devices. How this work with DEVFS? Should I copy devices from DEVFS with dd or tar?
>Or I mount DEVFS in every chroots? Please help!
why not just use jai
In message <[EMAIL PROTECTED]>, "sven svenskar" writes:
>I have server i give people shell accounts each in chroot and they need some devices.
>How this work with DEVFS? Should I copy devices from DEVFS with dd or tar? Or I mount
>DEVFS in every chroots? Please help!
current or stable ?
--
Pou
< said:
> Has our CDROM driver ever supported multiple ISO filesystems per CD? Has
> it supported multi-session CDROMs? The notion of partitions on CDROMs is
> a little ambiguous. I'm hoping that GEOM can improve this.
Sort of, but it often gets things wrong for the more interesting
CD-ROM ty
> >> > In message <[EMAIL PROTECTED]>, Steve Kargl w
> >> > rites:
> >> > >root[208] cdcontrol play
> >> > >cdcontrol: no CD device name specified, defaulting to /dev/cd0c
> >> > >cdcontrol: /dev/cd0cc: No such file or directory
> >> > >
> >> > >Why is an extra "c" appended to cd0c?
> >
> >The fir
In message <[EMAIL PROTECTED]>, "Matthew N. Dodd" w
rites:
>On Sun, 6 Oct 2002, David O'Brien wrote:
>> Since when hasn't it been standard on BSD based systems? Other than
>> recently on FreeBSD, all other BSD systems I've used, the "c" partition
>> has been necessary when wanting to operate on t
On Sun, 6 Oct 2002, David O'Brien wrote:
> Since when hasn't it been standard on BSD based systems? Other than
> recently on FreeBSD, all other BSD systems I've used, the "c" partition
> has been necessary when wanting to operate on the entire disk.
Has our CDROM driver ever supported multiple I
On Sun, Oct 06, 2002 at 08:29:52AM +0200, Poul-Henning Kamp wrote:
> >The first "c" is part of the standard name for the whole of a (labelled)
> >disk device.
>
> It's not any "standard name". It is a convention used on a minority
> of UNIX platforms out there, and it is certainly not "standard"
On Sun, 6 Oct 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >On Sat, 5 Oct 2002, Steve Kargl wrote:
> >
> >> > In message <[EMAIL PROTECTED]>, Steve Kargl w
> >> > rites:
> >> > >root[208] cdcontrol play
> >> > >cdcontrol: no CD device name specified, defa
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Sat, 5 Oct 2002, Steve Kargl wrote:
>
>> > In message <[EMAIL PROTECTED]>, Steve Kargl w
>> > rites:
>> > >root[208] cdcontrol play
>> > >cdcontrol: no CD device name specified, defaulting to /dev/cd0c
>> > >cdcontrol: /dev/cd0cc: No such fil
On Sat, 5 Oct 2002, Steve Kargl wrote:
> > In message <[EMAIL PROTECTED]>, Steve Kargl w
> > rites:
> > >root[208] cdcontrol play
> > >cdcontrol: no CD device name specified, defaulting to /dev/cd0c
> > >cdcontrol: /dev/cd0cc: No such file or directory
> > >
> > >Why is an extra "c" appended to c
On Sat, Oct 05, 2002 at 03:39:47PM -0700, Steve Kargl wrote:
> On Sun, Oct 06, 2002 at 12:19:46AM +0200, Poul-Henning Kamp wrote:
> > In message <[EMAIL PROTECTED]>, Steve Kargl w
> > rites:
> > >root[208] cdcontrol play
> > >cdcontrol: no CD device name specified, defaulting to /dev/cd0c
> > >cdc
On Sun, Oct 06, 2002 at 12:19:46AM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Steve Kargl w
> rites:
> >root[208] cdcontrol play
> >cdcontrol: no CD device name specified, defaulting to /dev/cd0c
> >cdcontrol: /dev/cd0cc: No such file or directory
> >
> >Why is an extra "c"
In message <[EMAIL PROTECTED]>, Steve Kargl w
rites:
>root[208] cdcontrol play
>cdcontrol: no CD device name specified, defaulting to /dev/cd0c
>cdcontrol: /dev/cd0cc: No such file or directory
>
>Why is an extra "c" appended to cd0c?
That's not devfs, that's cdcontrol.
It should be fixed to use
In message <[EMAIL PROTECTED]>, Dima Dorfman writes:
>Sheldon Hearn <[EMAIL PROTECTED]> wrote:
>> On (2002/07/17 01:52), Dima Dorfman wrote:
>>
>> > The devfs(8) manual page is a pretty good reference of the existing
>> > features and semantics, but it lacks polish needed to be able to serve
>> >
Sheldon Hearn <[EMAIL PROTECTED]> wrote:
> On (2002/07/17 01:52), Dima Dorfman wrote:
>
> > The devfs(8) manual page is a pretty good reference of the existing
> > features and semantics, but it lacks polish needed to be able to serve
> > as an introduction.
>
> Actually, I think it's brilliant.
In message: <[EMAIL PROTECTED]>
Dima Dorfman <[EMAIL PROTECTED]> writes:
: Questions and comments are most welcome. In particular, if you use
: this with removable devices (e.g., USB), I'd like to hear about it. I
: haven't had much of an opportunity to test this with different
: rem
On (2002/07/17 01:52), Dima Dorfman wrote:
> The devfs(8) manual page is a pretty good reference of the existing
> features and semantics, but it lacks polish needed to be able to serve
> as an introduction.
Actually, I think it's brilliant.
The only nits are the weird sections, which made it h
In message <[EMAIL PROTECTED]>, David Malone writes:
>On Sun, Mar 03, 2002 at 09:26:11PM +0100, Poul-Henning Kamp wrote:
>> >I presume you'd push the rules in using sysclt or did you have
>> >something more filesystem like in mind?
>>
>> Nope, just a sysctl.
>
>I guess then you just need a sysctl
On Sun, Mar 03, 2002 at 09:26:11PM +0100, Poul-Henning Kamp wrote:
> >I presume you'd push the rules in using sysclt or did you have
> >something more filesystem like in mind?
>
> Nope, just a sysctl.
I guess then you just need a sysctl which lets you read the rules
for a given devfs mount point
I've often thought that owner, group, and mode should be
defaulted in the registration process for the device.
This would let defaults be set in the source code, so in
the worst case, you can rebuild the kernel to get them.
This would also allow low granularity persistance to be
handled in teh s
Poul-Henning Kamp wrote:
>
> In message <[EMAIL PROTECTED]>, David Malone writes:
> >On Sun, Mar 03, 2002 at 05:36:04PM +0100, Poul-Henning Kamp wrote:
> >> In message <[EMAIL PROTECTED]>, "Crist J. Clark" writes
> >> :
> >> >I've checked the manpages, the files in /etc, and Googled, and I can't
On Sun, Mar 03, 2002 at 09:26:11PM +0100, Poul-Henning Kamp wrote:
> >OK - I thought you had something much more complex in mind after
> >your example: "plugging the nuclear reactor into the serial port
> >where you had a a modem plugged in yesterday".
>
> No, that was to show why "persistence" i
In message <[EMAIL PROTECTED]>, David Malone writes:
>> Not really, the basic idea is just a linked list of rules:
>
>> name=="/dev/uscanner*" -> chmod 0644
>> driver=="bpf" -> chown user
>
>> It's not too much work, I just havn't had the time for it yet.
>> (Junior Kernel Hackers can a
> >Do you have any designs for this ruleset stuff? From what you said
> >at BSDconEurope it will have to be fairly complicated to achieve
> >the your aim of being better than a static permission for a given
> >device.
> Not really, the basic idea is just a linked list of rules:
> name=="/d
In message <[EMAIL PROTECTED]>, David Malone writes:
>On Sun, Mar 03, 2002 at 05:36:04PM +0100, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, "Crist J. Clark" writes
>> :
>> >I've checked the manpages, the files in /etc, and Googled, and I can't
>> >find the answer. I am begining to
On Sun, Mar 03, 2002 at 05:36:04PM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Crist J. Clark" writes
> :
> >I've checked the manpages, the files in /etc, and Googled, and I can't
> >find the answer. I am begining to worry there isn't one. How does one
> >change the permissi
On 03-Mar-2002 (17:02:35/GMT) Crist J. Clark wrote:
> I think some people missed the point of the earlier question.
I'm really sorry :( Next time I'll double read the messages.
Riccardo.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mes
On Sun, Mar 03, 2002 at 05:42:10PM +0100, Riccardo Torrini wrote:
> On 03-Mar-2002 (16:31:36/GMT) Crist J. Clark wrote:
>
> > How does one change the permissions on dynamically created
> > devices? That is, when the node comes into existence, it has
> > the permissions I want, and not necessarily
On 03-Mar-2002 (16:31:36/GMT) Crist J. Clark wrote:
> How does one change the permissions on dynamically created
> devices? That is, when the node comes into existence, it has
> the permissions I want, and not necessarily the defaults.
You can (must?) use /etc/rc.devfs
[...]
# Setup DEVFS, ie p
In message <[EMAIL PROTECTED]>, "Crist J. Clark" writes
:
>I've checked the manpages, the files in /etc, and Googled, and I can't
>find the answer. I am begining to worry there isn't one. How does one
>change the permissions on dynamically created devices? That is, when
>the node comes into existe
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>> In message <[EMAIL PROTECTED]>, Mike Silbersack
>writes:
>> > Oops, error on my part; /proc does need to exist. So, I guess the
>> > question is this: Can devfs's error handling in the c
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]>, Mike Silbersack writes:
> > Oops, error on my part; /proc does need to exist. So, I guess the
> > question is this: Can devfs's error handling in the case of /dev being
> > non-existant be improved?
> Barely, because
In message <[EMAIL PROTECTED]>, Garrett Wollman w
rites:
>< said:
>
>> Right, but the only way to get an error message is to let /sbin/init
>> die and have the kernel print the message. /sbin/init cannot
>> print the message when there is no "/dev/console" can it ?
>
>Yes, it can, if the kernel d
< said:
> Right, but the only way to get an error message is to let /sbin/init
> die and have the kernel print the message. /sbin/init cannot
> print the message when there is no "/dev/console" can it ?
Yes, it can, if the kernel does the right then when hand-crafting the
`init' process to ensu
On Sat, 27 Oct 2001, Poul-Henning Kamp wrote:
> >An error message would be sufficient; my concern was that someone
> >might run into this and spend hours trying to figure out which of X
> >variables was the problem.
>
> Right, but the only way to get an error message is to let /sbin/init
> die a
In message <[EMAIL PROTECTED]>, Mike Silbersack w
rites:
>
>On Sat, 27 Oct 2001, Poul-Henning Kamp wrote:
>
>> >Oops, error on my part; /proc does need to exist. So, I guess the
>> >question is this: Can devfs's error handling in the case of /dev being
>> >non-existant be improved?
>>
>> Barely,
On Sat, 27 Oct 2001, Poul-Henning Kamp wrote:
> >Oops, error on my part; /proc does need to exist. So, I guess the
> >question is this: Can devfs's error handling in the case of /dev being
> >non-existant be improved?
>
> Barely, because without /dev, how do you plan to open the console ?
>
> M
On Mon, Aug 20, 2001 at 08:02:44AM -0500, David W. Chapman Jr. wrote:
> On Mon, Aug 20, 2001 at 02:05:06AM -0400, Brandon D. Valentine wrote:
> > On Sun, 19 Aug 2001, Kris Kennaway wrote:
> >
> > >Devices are just inodes..you shouldn't have anything in /dev other
> > >than MAKEDEV, the fd/ subdir
Hmm- this is because init gets the 'd' argument if devfs is linked into the
kernel with the variable 'devfs_present' set.
Isn't there a way for the loader to dork with this?
On Mon, 20 Aug 2001, David W. Chapman Jr. wrote:
> On Mon, Aug 20, 2001 at 11:17:42AM -0400, Brandon D. Valentine wro
On Mon, Aug 20, 2001 at 11:17:42AM -0400, Brandon D. Valentine wrote:
> On Mon, 20 Aug 2001, David W. Chapman Jr. wrote:
>
> >The only problem is devfs is mounted and I can't seem to get around
> >that.
>
> I haven't had much time lately to fool with my -CURRENT box but
> it seems that booting s
At 11:17 AM 8/20/2001 -0400, Brandon D. Valentine wrote:
>On Mon, 20 Aug 2001, David W. Chapman Jr. wrote:
>
>>The only problem is devfs is mounted and I can't seem to get around
>>that.
>
>I haven't had much time lately to fool with my -CURRENT box but
>it seems that booting singleuser oughta hel
On Mon, 20 Aug 2001, David W. Chapman Jr. wrote:
>The only problem is devfs is mounted and I can't seem to get around
>that.
I haven't had much time lately to fool with my -CURRENT box but
it seems that booting singleuser oughta help?
--
"Never put off until tomorrow what you can do today. Th
On Mon, Aug 20, 2001 at 02:05:06AM -0400, Brandon D. Valentine wrote:
> On Sun, 19 Aug 2001, Kris Kennaway wrote:
>
> >Devices are just inodes..you shouldn't have anything in /dev other
> >than MAKEDEV, the fd/ subdirectory and a whole bunch of device nodes.
> >You probably have some other file i
On Sun, 19 Aug 2001, Kris Kennaway wrote:
>Devices are just inodes..you shouldn't have anything in /dev other
>than MAKEDEV, the fd/ subdirectory and a whole bunch of device nodes.
>You probably have some other file in there which was accidentally
>created by something like
>
># verbosecommand >
On Sun, Aug 19, 2001 at 10:11:35PM -0500, David W. Chapman Jr. wrote:
> On Sun, Aug 19, 2001 at 07:50:31PM -0400, Brandon D. Valentine wrote:
> > On Sat, 18 Aug 2001, David W. Chapman Jr. wrote:
> >
> > >If I'm using devfs on -current, can I erase the contents of my /dev
> > >before devfs is moun
In message <[EMAIL PROTECTED]> "David W. Chapman Jr."
writes:
: Hrm, mine said 5.5M. I did say this machine had been around since
: 2.2.8, right? I still had raw devices in there I believe.
That's at least 5.0M too big.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Sun, Aug 19, 2001 at 07:50:31PM -0400, Brandon D. Valentine wrote:
> On Sat, 18 Aug 2001, David W. Chapman Jr. wrote:
>
> >If I'm using devfs on -current, can I erase the contents of my /dev
> >before devfs is mounted to save space?
>
> What space are you planning to save? You might free up
On Sat, 18 Aug 2001, David W. Chapman Jr. wrote:
>If I'm using devfs on -current, can I erase the contents of my /dev
>before devfs is mounted to save space?
What space are you planning to save? You might free up some inodes but
according to my 4.4-PRERELEASE box:
[bandix@leto /dev]% du -sh .
Ohh, I think doing this unwise. You should always leave yourself something in
/dev...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, 18 Aug 2001, David W. Chapman Jr. wrote:
> If I'm using devfs on -current, can I erase the contents of my /dev
> before devfs is mounted to save space?
You could, but that would be, well, it'd really be a Darwin award winner.
>
> --
> David W. Chapman Jr.
> [EMAIL PROTECTED] Raintr
In message <[EMAIL PROTECTED]>, "David W. Chapman
Jr." writes:
>If I'm using devfs on -current, can I erase the contents of my /dev
>before devfs is mounted to save space?
Yes, the easiest way is:
boot singleuser
mount -o rw /
mv /dev /dev_
mkdir /dev
c
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>
>
>On Fri, 17 Aug 2001, Terry Lambert wrote:
>
>> Poul-Henning Kamp wrote:
>> > Julian Elischer writes:
>> >
>> > >Well you timed them out without askling the developer what he had in the
>> > >wings and that was more than impolite, it wa
On Fri, 17 Aug 2001, Terry Lambert wrote:
> Poul-Henning Kamp wrote:
> > Julian Elischer writes:
> >
> > >Well you timed them out without askling the developer what he had in the
> > >wings and that was more than impolite, it was stupid, because most of the
> > >shortcomings of devfs and SLICE
Poul-Henning Kamp wrote:
> Julian Elischer writes:
>
> >Well you timed them out without askling the developer what he had in the
> >wings and that was more than impolite, it was stupid, because most of the
> >shortcomings of devfs and SLICE had been solved and all I was waiting for
> >was the CAM
[Format recovered--see http://www.lemis.com/email/email-format.html]
Your MUA wraps incorrectly.
On Friday, 17 August 2001 at 9:16:59 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Julian
>Elischer writes:
>
>> Well you timed them out without askling the developer what he ha
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>Well you timed them out without askling the developer what he had in the
>wings and that was more than impolite, it was stupid, because most of the
>shortcomings of devfs and SLICE had been solved and all I was waiting for
>was the CAM sw
Julian Elischer wrote:
> > If it is to be counted as my only achivement on -core that I timed
> > out SLICE and DEVFS, I'll still be proud of what I did there.
>
> Well you timed them out without askling the developer what he had in the
> wings and that was more than impolite, it was stupid, beca
On Thu, 16 Aug 2001, Poul-Henning Kamp wrote:
> >Julian feels he has no avenue of recourse and gives up..--
>
> if (!strcmp("DEVFS", "SLICE"))
> return (ECONFUSED);
>
> Julian, you had four years, during which you didn't even manage to
> make half of the commits made to the
On Thu, 16 Aug 2001, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Ju
> lian Elischer writes:
>
> >> A quick script run on the cvs tree paints this picture of number
> >> of commits to src/sys/miscfs/devfs per year:
> >>
> >>julian phk other
> >>
On Thu, 16 Aug 2001, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Ju
> lian Elischer writes:
>
> >> A quick script run on the cvs tree paints this picture of number
> >> of commits to src/sys/miscfs/devfs per year:
> >>
> >>julian phk other
> >>
On 16-Aug-01 Michael Lucas wrote:
> [cc's trimmed]
>
> John,
>
> Thanks for the suggestion, I appreciate it. I did as you suggested
> (diff below).
>
> It paniced again, but this time savecore said "dump time is unreasonable."
>
> The short panic message was:
>
> panicstr: bremfree: bp 0xcc
[cc's trimmed]
John,
Thanks for the suggestion, I appreciate it. I did as you suggested
(diff below).
It paniced again, but this time savecore said "dump time is unreasonable."
The short panic message was:
panicstr: bremfree: bp 0xcc2a1ae4 not locked
Looks like the same thing to me, sorry.
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>> A quick script run on the cvs tree paints this picture of number
>> of commits to src/sys/miscfs/devfs per year:
>>
>> julian phk other
>> 199556 3 15
>> 1996
On Thu, 16 Aug 2001, Poul-Henning Kamp wrote:
> After 3 years I gave up on the hope that it would ever be fixed
> well enough to become politically acceptable.
>
> After 6 years I removed it.
>
> A quick script run on the cvs tree paints this picture of number
> of commits to src/sys/miscfs/d
On Thu, 16 Aug 2001, Greg Lehey wrote:
> On Thursday, 16 August 2001 at 6:36:45 +0200, Poul-Henning Kamp wrote:
> > In message <[EMAIL PROTECTED]>, Greg Lehey writes:
> >> In view of the fact that this thread is about deficiencies in your
> >> devfs, this is particularly uncalled for. One of th
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
ls -la /dev/fd
>>>
>>> What am I supposed to see there? I get three character devices, all
>>> mounted on /dev directly.
>>
>> Uhm, have you forgotten how ls(1) works ?
>
>No.
>
>> Try this then:
>>
>> ls -lad /dev/fd /dev/fd/[012]
On Thursday, 16 August 2001 at 6:36:45 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>> On Wednesday, 15 August 2001 at 19:17:47 +0200, Poul-Henning Kamp wrote:
>>> In message <[EMAIL PROTECTED]>, Ju
>>> lian Elischer writes:
>>>
the lack of subdirector
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>On Wednesday, 15 August 2001 at 19:17:47 +0200, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Ju
>> lian Elischer writes:
>>
>>> the lack of subdirectory support is a pitty.
>>
>> There is support for subdirectories:
>>
>> ls -
[snip]
> And in general, can we stop the high incidence of mud-slinging we've
> seen on the lists lately?
Here, here!
Brandon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 15-Aug-01 Michael Lucas wrote:
> On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
>> To help localize this problem, could you please try this same thing on
>> a kernel without devfs? The dump you sent me did not look like a
>> Vinum bug, as I said in my reply.
>
> Sorry, it happen
On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
> To help localize this problem, could you please try this same thing on
> a kernel without devfs? The dump you sent me did not look like a
> Vinum bug, as I said in my reply.
Sorry, it happens on a non-devfs kernel as well. Since it d
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>the lack of subdirectory support is a pitty.
There is support for subdirectories:
ls -la /dev/fd
>it was a primary design goal in the previous devfs and its
>disappearance caught me by surprise. (the support I mean)
The abilit
the lack of subdirectory support is a pitty.
it was a primary design goal in the previous devfs and its
disappearance caught me by surprise. (the support I mean)
On Wed, 15 Aug 2001, Andrew Kenneth Milton wrote:
> +---[ Poul-Henning Kamp ]--
> | In message <[EMAIL PROTECT
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
| >+---[ Poul-Henning Kamp ]--
| >| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| >| writes:
| >|
| >| >The problem turns up most violently wit
On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
> On Tuesday, 14 August 2001 at 19:26:09 -0400, Michael Lucas wrote:
> > Before I start generating crash dumps & etc., are there any gotchas
> > with Vinum & -current? I'm using devfs on a SMP system, upgraded 3
> > days ago. I get a pa
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>+---[ Poul-Henning Kamp ]--
>| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
>| writes:
>|
>| >The problem turns up most violently within the XFree86 DRI Module, since
>| >it now uses make_dev, and no
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
|
| >The problem turns up most violently within the XFree86 DRI Module, since
| >it now uses make_dev, and not mknod as it used to.
| >
| >The DRI Module first attempts to mkdir
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>The problem turns up most violently within the XFree86 DRI Module, since
>it now uses make_dev, and not mknod as it used to.
>
>The DRI Module first attempts to mkdir /dev/dri/, and then for each card
>it supports attempts to use mak
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
| >+---[ Greg Lehey ]--
| >|
| >
| >[snip]
| >
| >| whether it's been fixed. Basically, devfs as supplied in CURRENT had
| >| a 16 character limit on devi
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>> I'm working on the 16char limit problem as well, but I want to avoid
>> allocating memory in incovenient circumstances if at all possible.
>
>The problem is that I kept having problems with the devfs/vinum
>combination even after increasing th
On Wednesday, 15 August 2001 at 7:16:02 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
> writes:
>> +---[ Greg Lehey ]--
>>>
>>
>> [snip]
>>
>>> whether it's been fixed. Basically, devfs as supplied in CURRENT had
>>> a 16 charact
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>+---[ Greg Lehey ]--
>|
>
>[snip]
>
>| whether it's been fixed. Basically, devfs as supplied in CURRENT had
>| a 16 character limit on device names, and it didn't understand
>| subdirectories: it treated the /
+---[ Greg Lehey ]--
|
[snip]
| whether it's been fixed. Basically, devfs as supplied in CURRENT had
| a 16 character limit on device names, and it didn't understand
| subdirectories: it treated the / as a part of the device name.
The subdir part bit me about a week ag
On Thu, Jul 05, 2001 at 07:57:41AM +0200, Riccardo Torrini wrote:
> Maybe this is a stupid(?) question, but how DEVFS is supposed
> to work with softlink? How can I make them reboot-resistant?
>
See /etc/rc.devfs (which should probably be referenced in devfs(5)).
--
Chris D. Faulhaber - [EMAI
In message <[EMAIL PROTECTED]>, Robe
rt Watson writes:
>On Fri, 11 May 2001, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>, Bruce Evan
>> s writes:
>>
>> >> Blame the poor design of mount(2) (and ask Adrian when he fixes
>> >> it :-)
>> >
>> >It must be the excellent design of moun
1 - 100 of 200 matches
Mail list logo
