On 04-Feb-01 Steve Kargl wrote:
> lpt gives an instant panic with sources from this
> afternoon (3 Feb 01 pst). So far, I can boot the
> system if I disable lpd in /etc/rc.conf. If I start
> lpd from the command, I get
>
> %lpd
> stray irq 7
> stray irq 7
> stray irq 7
> stray irq 7
> kernel t
On Friday, 2 February 2001 at 20:10:10 -0800, Peter Wemm wrote:
> Robert Watson wrote:
>
>> crw-r--r-- 1 root wheel 78, 0 Dec 31 1969 pci
>
> This one may appear harmless, but it is not. It is trivially easy to create
> an alignment fault (fatal on an alpha) with the userland pcicon
> Also, I think that this isn't the right fix to a bigger problem.
> Instead, it shouldn't be hard to get a list of configured devices
> out of mdconfig via an ioctl on /dev/mdctl. This would be the right
> fix, as it would fix the general case problem you describe, not just
> one instance of it.
lpt gives an instant panic with sources from this
afternoon (3 Feb 01 pst). So far, I can boot the
system if I disable lpd in /etc/rc.conf. If I start
lpd from the command, I get
%lpd
stray irq 7
stray irq 7
stray irq 7
stray irq 7
kernel trap 26 with interrupts disabled
panic: mutex sched lock
Oops, sorry that From: address was different from the first email...
jhb> Instead, it shouldn't be hard to get a list of configured devices
jhb> out of mdconfig via an ioctl on /dev/mdctl. This would be the
jhb> right fix, as it would fix the general case problem you describe,
jhb> not just one
On Sat, Feb 03, 2001 at 12:32:50PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Peter Wemm writes:
> : As bizzare as it sounds, I like Julian's hack for populating this stuff...
> : ie: use a hard link to propagate nodes to the jailed /dev.
> :
> : eg: mount -t devfs -o empty /home/
On 04-Feb-01 Makoto MATSUSHITA wrote:
>
> jhb> The current method always finds an unused device to use, so the
> jhb> old VNDEVICE-style hack is no longer needed. There's no point to
> jhb> setting an explicit device to use.
>
> But I want to ensure that all used md(4) devices is unconfigured
jhb> The current method always finds an unused device to use, so the
jhb> old VNDEVICE-style hack is no longer needed. There's no point to
jhb> setting an explicit device to use.
But I want to ensure that all used md(4) devices is unconfigured after
it is used.
Imagine you run 'make release' f
On 03-Feb-01 Makoto MATSUSHITA wrote:
>
> src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable
> (formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to
> configure md -- trivial, add '-u' option if MDDEVICE is already defined.
But you shouldn't need this. The
src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable
(formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to
configure md -- trivial, add '-u' option if MDDEVICE is already defined.
-- -
Makoto `MAR' MATSUSHITA
Index: doFS.sh
On 03-Feb-01 Rasa Karapandza wrote:
> Has anyone see acpi S1 mode realy work?
Sort of. It works on my laptop if I'm in X with my wavelan plugged in. At a
console with no devices plugged in it will immediately resume after suspend.
> Rasa
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.Fr
Hi!
I got into a following problem with subj:
During boot process, the card can be in power down mode. This can be
cause MEMEN and PORTEN bits not set up correctly (set to 0) during boot.
This bits not set will cause no resources for this device, thus later a
bus_alloc_resource() call will fail.
Has anyone see acpi S1 mode realy work?
Rasa
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Why not the 'audit' list which is what audit is for I thought?
Other than if_wx which breaks cstyling, looks okay to me
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <14918.981230622@critter> Poul-Henning Kamp writes:
>: Doing straight symlinks would not work.
>
>OK.
>
>The other idea that I had was a cpdev. It would be like a templated
>mknod. It would stat the first argument and do a mknod wit
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
: At least for the USB devices this can be done with the
: 'usbd' daemon.
And pccardd can handle this for OLDCARD users. NEWCARD users will
need to cope until something comes alone :-(.
Warner
To Unsubscribe: send mail to [EMAIL P
In message <14918.981230622@critter> Poul-Henning Kamp writes:
: Doing straight symlinks would not work.
OK.
The other idea that I had was a cpdev. It would be like a templated
mknod. It would stat the first argument and do a mknod with the
st_rdev from the stat, eg:
#include
#include
#incl
From: "Poul-Henning Kamp" <[EMAIL PROTECTED]>
> I have created a patch which goes a long way to clean up the the
> usage of the API. The patch is generated
automatically
> and the objectfiles are identical if line numbers are preserved by
> breaking style(9).
>
> You can find the script and the
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <14760.981228917@critter> Poul-Henning Kamp writes:
>: In message <[EMAIL PROTECTED]>, Warner Losh writes:
>: >In message <[EMAIL PROTECTED]> Peter Wemm writes:
>: >: As bizzare as it sounds, I like Julian's hack for populating this s
In message <14760.981228917@critter> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, Warner Losh writes:
: >In message <[EMAIL PROTECTED]> Peter Wemm writes:
: >: As bizzare as it sounds, I like Julian's hack for populating this stuff...
: >: ie: use a hard link to propagate nodes to t
I have created a patch which goes a long way to clean up the the
usage of the API. The patch is generated automatically
and the objectfiles are identical if line numbers are preserved by
breaking style(9).
You can find the script and the patch here:
http://phk.freebsd.dk/patch
Please
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Peter Wemm writes:
>: As bizzare as it sounds, I like Julian's hack for populating this stuff...
>: ie: use a hard link to propagate nodes to the jailed /dev.
>:
>: eg: mount -t devfs -o empty /home/jail/dev
>: ln
In message <[EMAIL PROTECTED]> Peter Wemm writes:
: As bizzare as it sounds, I like Julian's hack for populating this stuff...
: ie: use a hard link to propagate nodes to the jailed /dev.
:
: eg: mount -t devfs -o empty /home/jail/dev
: ln /dev/null /home/jail/dev/null
: ln /dev/zero /home/jail/d
>> I have seriously been thinking about some way to say something like
>> mount -t devfs -o jailset /home/jail/dev
>> but an elegant implementation evades me at this moment.
>
>As bizzare as it sounds, I like Julian's hack for populating this stuff...
>ie: use a hard link to propagate nodes
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Warner Losh write
s:
> >In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
> >: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev"
> >: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It
> >:
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
>: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev"
>: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It
>: seems that "read my lips: no new devices
In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev"
: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It
: seems that "read my lips: no new devices" should be an option you can
: set from the very initia
>ok I understand now...
>I thought you were saying that the netgraph code was acting differently
>to how I belive it should act.
Nope that was the legacy bridge.
> > Exactly if there's just one interface when netgraph bridging is on. Why?
> > Why just one interface? Now that my kernel is patche
"Rogier R. Mulhuijzen" wrote:
>
[explanation]
ok I understand now...
I thought you were saying that the netgraph code was acting differently
to how I belive it should act.
>
>
>
>
> Exactly if there's just one interface when netgraph bridging is on. Why?
> Why just one interface? Now that m
I just installed cvsupped and installed a new world&kernel at 3feb2000.
Everything works fine, but reading /dev/dsp (cat /dev/dsp e.g.) gives
some thousands of bytes output, but then totally crashes the system;
it doesn't even break to the debugger when pressing Ctrl-Alt-Esc.
It worked fine on my
Hi
Please review the patch at http://people.freebsd.org/~markm/no_lock_h.diff.
the idea is to remove sys/*/include/lock.h.
I tested it with the usual i386 stuff, and it is known to break the cy
driver because of the COM_(UN)LOCK macros (which is another issue).
M
--
Mark Murray
Warning: this
In article <[EMAIL PROTECTED]> you wrote:
> With devfs "default" in -current, I have a question about permissions. I
> know that rc.devfs will set up custom permissions at boot... But what
> about a device that detaches? When you re-attach, it goes back to the
> default permissions. This is a bit
At 00:48 3-2-01 -0800, Julian Elischer wrote:
>"Rogier R. Mulhuijzen" wrote:
> >
> > I found this while experimenting with both "legacy" bridge and ng_bridge.
> > The bridging code doesn't check its activation everywhere so when I started
> > using an ng_bridge node I started getting weird errors.
In message <[EMAIL PROTECTED]>, Jordan Hubbard writes:
>> Once we have an extensible facility for mount options, you will be
>> able to say:
>>
>> mount -t devfs devfs /home/jail/dev
>> ( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails )
>> mount -u -o nonewdev /home/jail/d
> Once we have an extensible facility for mount options, you will be
> able to say:
>
> mount -t devfs devfs /home/jail/dev
> ( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails )
> mount -u -o nonewdev /home/jail/dev
Couldn't you also do "mount -t devfs -o nonewdev devfs
"Rogier R. Mulhuijzen" wrote:
>
> I found this while experimenting with both "legacy" bridge and ng_bridge.
> The bridging code doesn't check its activation everywhere so when I started
> using an ng_bridge node I started getting weird errors.
>
> Patch is rather simple, can someone submit this?
Hello,
Thank you for advices. Now I obtain same environment as of pre-devfs days.
From: Alex Kapranoff <[EMAIL PROTECTED]>
Date: Fri, 2 Feb 2001 15:29:09 +0300
> Yep. I have these in my /etc/rc.devfs:
> =
> ln -fs /dev/audio1.0 /dev/audio
> ln -fs /dev/dsp1.0 /dev/dsp
> ln -f
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <18334.980748975@critter> Poul-Henning Kamp writes:
>: >1. Say I want to use DEVFS, what should I change?
>:
>: Nothing. Just add DEVFS to your kernel config file.
>
>So it updates /dev all by itself? What if I want dev nodes else
In message <[EMAIL PROTECTED]>, Doug Barton
writes:
> I've been using devfs for a long time without problems. I had
>device vn in my kernel conf since the pre-devfs days, and today I needed
>to use a vn device to build picobsd. Lo and behold, I don't have any vn
>devices of any sort in /de
39 matches
Mail list logo