Atanas said the following on 12/12/05 18:57:
Peter Jeremy said the following on 12/12/05 13:40:
>> When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on
>> a serial console).
>>
> But if I have no keyboard response I won't be able to save it, right?
>
(replying to myself)
This
On Mon, 2005-Dec-12 18:57:24 -0800, Atanas wrote:
>When I plug a keyboard, there's no response at all - no LEDs, no VTYs,
>Ctrl-Alt-Esc, etc. You might think of "hint.atkbd.0.flags" not being set
>properly, but it's right (i.e. unchanged, it appears to default to that
>on i386 5.x+) and other mach
Hi all,
I'm setting up a UPS on one machine,
and the ups daemon (nut) works as user "upsd".
To make it work properly i have added in devfs.rules the
following :
permttyd0 0660
own ttyd0 upsd:upsd
But it still does not work because ttyd0.init and ttyd0.lock
are still owned by root.
I'
On Tue, 13 Dec 2005 20:47, Niki Denev wrote:
> permttyd0 0660
> own ttyd0 upsd:upsd
>
> But it still does not work because ttyd0.init and ttyd0.lock
> are still owned by root.
So?
> I'll try adding them too to the devfs.rules file,
> but i'm wondering if this is the expected behaviour
Hi,
we are hosting ftp8.fr.freebsd.org. The server is an HP DL360 G4 with an
HP msa20 attached for mirrors with FreeBSD 6, the msa20 is connected to
a smart array 642 card. Yesterday, due to bugs in the firmware of the
msa20 (like false detection of disk failures), we upgraded it with
version
Simon Barner wrote:
Philippe Pegon wrote:
Hi,
we are hosting ftp8.fr.freebsd.org. The server is an HP DL360 G4 with an
HP msa20 attached for mirrors with FreeBSD 6, the msa20 is connected to
a smart array 642 card. Yesterday, due to bugs in the firmware of the
msa20 (like false detection of
On Mon, Dec 12, 2005 at 09:21:29PM +0100, Ronald Klop wrote:
> On Mon, 12 Dec 2005 16:03:59 +0100, Pete French
> <[EMAIL PROTECTED]> wrote:
>
> >I'm about to start installing a whole new set of machines for production
> >use with 6.0 on them. Normally I would just use -RELEASE, but as this is
>
Graham Menhennitt <[EMAIL PROTECTED]> wrote:
> I got the following output from "ipfw show" in my daily security run output
> email.
>
> +++ /tmp/security.yri47lgA Mon Dec 12 03:01:45 2005
> +00522 3530 1204158 deny ip from 10.0.0.0/8 to any via sis1
> +0252218 784 deny tcp fro
David Taylor <[EMAIL PROTECTED]> wrote:
> I have a USB drive (SanDisk 1GB flash drive), which I have mounted
> on a windows PC using samba 3.0.
>
> I recently discovered the copy of my files on my USB device were
> corrupted (thankfully I had a backup), being filled entirely with
> 0's (that
On my FreeBSD 6-stable (the last build is less then 24hours ago) my
devfs doesn't apply permissions set in /etc/devfs.conf when I attach new
devices. I have to call:
/etc/rc.d/devfs restart
manually for the settings to be applied. This is rather uncomfortable in
some cases (especially with my PDA).
On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote:
> On my FreeBSD 6-stable (the last build is less then 24hours ago) my
> devfs doesn't apply permissions set in /etc/devfs.conf when I attach new
> devices. I have to call:
> /etc/rc.d/devfs restart
> manually for the settings to be appl
Sorry for the late reply ...
Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote:
> Highpoint RocketRAID 1640(4 ports)
> Promise FastTrak S150 SX4(4 ports)
> Promise FastTrak S150 SX4-M(4 ports)
> Highpoint RocketRAID 1810A(4 ports)
> Highpoint RocketRAID 1820A(8 ports)
> Intel R
On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote:
> On my FreeBSD 6-stable (the last build is less then 24hours ago) my
> devfs doesn't apply permissions set in /etc/devfs.conf when I attach new
> devices. I have to call:
> /etc/rc.d/devfs restart
> manually for the settings to be appl
It's a simple and working solution and I think it simply should be made
default for ALL attach events. To me it makes more sense than having 2
different systems for the same thing.
Anyway, now I'm going to set up a devfs.rules (and learn a new different
syntax for doing exactly the same thing). Th
Hi,
I have installed i386 6.0-RELEASE to two HP DL145G2-servers and they
crash soon after (1-2 minutes) booting up to login prompt. Sometimes
they boot up without crashing and sometimes with crashing.
I have now upgraded to RELENG_6 and crashing continues. What amazes
me is that these two machin
On Tuesday 13 December 2005 11:54 am, Marwan Burelle wrote:
> On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote:
> > On my FreeBSD 6-stable (the last build is less then 24hours ago)
> > my devfs doesn't apply permissions set in /etc/devfs.conf when I
> > attach new devices. I have to ca
> Date: Tue, 13 Dec 2005 08:49:47 -0800
> From: Brooks Davis <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote:
> > On my FreeBSD 6-stable (the last build is less then 24hours ago) my
> > devfs doesn't apply permissions set in /etc/de
On Tue, Dec 13, 2005 at 06:19:47PM +0100, [LoN]Kamikaze wrote:
> It's a simple and working solution and I think it simply should be made
> default for ALL attach events. To me it makes more sense than having 2
> different systems for the same thing.
>
> Anyway, now I'm going to set up a devfs.rule
On 12/13/05, fredthetree <[EMAIL PROTECTED]> wrote:
>
> On 12/12/05, Peter Jeremy <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 2005-Dec-12 22:21:52 -0400, fredthetree wrote:
> > >I just wanted to chime in and say I've had my 6.0-RELEASE #0 freeze up
> > twice
> > >in the past few days. never once had
On Tue, Dec 13, 2005 at 08:49:47AM -0800, Brooks Davis wrote:
> On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote:
> > On my FreeBSD 6-stable (the last build is less then 24hours ago) my
> > devfs doesn't apply permissions set in /etc/devfs.conf when I attach new
> > devices. I have to
On Tue, Dec 13, 2005 at 09:37:13AM -0800, Kevin Oberman wrote:
>
> You are being entirely too kind. The documentation for the practical use
> of devfs at all sucks! Nothing I could find in the handbook,
> either. It's a classic case of documentation written by programmers in
> that the author can'
On Tue, Dec 13, 2005 at 07:04:18PM +0100, Roland Smith wrote:
> On Tue, Dec 13, 2005 at 08:49:47AM -0800, Brooks Davis wrote:
> > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kamikaze wrote:
> > > On my FreeBSD 6-stable (the last build is less then 24hours ago) my
> > > devfs doesn't apply permis
> Date: Tue, 13 Dec 2005 11:21:43 -0800
> From: Brooks Davis <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> On Tue, Dec 13, 2005 at 07:04:18PM +0100, Roland Smith wrote:
> > On Tue, Dec 13, 2005 at 08:49:47AM -0800, Brooks Davis wrote:
> > > On Tue, Dec 13, 2005 at 05:37:09PM +0100, [LoN]Kami
Well, here are my conclusions.
1)
The manpage for devfs.rules should mention that you have to set
devfs_system_ruleset="yourruleset"
in /etc/rc.conf . I didn't see it anywhere.
2)
I have transferred all the rules in /etc/devfs.conf to /etc/devfs.rules,
because I don't like to have 2 solutions f
I'm running 5.4-STABLE (about two weeks old), and have just set up an
NFS server for the first time. Remote mounts sometimes work fine, and
sometimes fail.
The symptoms are that "showmount -e" sez
showmount: can't do exports rpc
and that "rpcinfo -u mountd" often works fine n times in a row,
Here is a small patch for /etc/rc.d/devfs which makes it behave the way
I suggested in my last mail.
--- devfs.old Tue Dec 13 20:58:52 2005
+++ devfs Tue Dec 13 21:00:57 2005
@@ -43,8 +43,8 @@
cd /dev
while read action device parameter; do
On Tue, 13 Dec 2005, Atanas wrote:
Atanas said the following on 12/12/05 18:57:
Peter Jeremy said the following on 12/12/05 13:40:
When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on
a serial console).
But if I have no keyboard response I won't be able to save it, right
On Tue, Dec 13, 2005 at 11:21:43AM -0800, Brooks Davis wrote:
> > > This is normal. devfs.conf is for boot only, you need devfs.rules for
> > > runtime. Unfortunatly, the documentation of this fact and the
> > > docuementation of devfs.rules sucks.
> >
> > Hmm, it's quite explicitly mentioned i
On Tue, Dec 13, 2005 at 08:44:50PM +0100, [LoN]Kamikaze wrote:
> Well, here are my conclusions.
>
> 1)
> The manpage for devfs.rules should mention that you have to set
>
> devfs_system_ruleset="yourruleset"
>
> in /etc/rc.conf . I didn't see it anywhere.
Agreed. I've posted a patch in this thr
I hacked together the current mess over two and a half years ago for one
simple reason, so that the functionality that used to be in the system prior
to rcNG would still be there. Since then, we've had roughly 18 rounds of
this same discussion, but no one has actually stepped up to do the work of
c
Hi,
On 13.12.2005, at 19.21, Räihä Marko wrote:
I have installed i386 6.0-RELEASE to two HP DL145G2-servers and they
crash soon after (1-2 minutes) booting up to login prompt. Sometimes
they boot up without crashing and sometimes with crashing.
I have now upgraded to RELENG_6 and crashing conti
On Tue, Dec 13, 2005 at 09:22:34PM +0100, Roland Smith wrote:
> On Tue, Dec 13, 2005 at 11:21:43AM -0800, Brooks Davis wrote:
>
> > > > This is normal. devfs.conf is for boot only, you need devfs.rules for
> > > > runtime. Unfortunatly, the documentation of this fact and the
> > > > docuementati
On Tue, Dec 13, 2005 at 12:55:39PM -0800, Brooks Davis wrote:
> > What's wrong with the EXAMPLES section in devfs(8)?
>
> It's fine. Referring to devfs(8) was poor word choice on my part. I
> meant the system as a whole including devfs.rules.
>
> > > any documentation of the rc.conf variables
hi.
i bought recently an usb keyboard. but when i connected it and started
up fbsd-6.0-stable(ukbd is in kernel).
when i tried to login, and enter my log/pass, it just did the ' '
(space character) instead of normal chars. my next step was editing
/boot/loader.conf and inserting:
hint.atkbd.0.flags
On Tue, Dec 13, 2005 at 12:23:26PM -0500, Anish Mistry wrote:
> > There maybe a better way, but "it works"© ;)
> You should be using /etc/devfs.rules
>
> Search the mailing list for examples and setup.
Yes, I know, some month ago I wrote a little documentation (in french
[1]) for using USB keys o
On Tue, 13 Dec 2005 17:51:02 +0100 (CET)
Oliver Fromme <[EMAIL PROTECTED]> wrote:
> There's no reason why you shouldn't be able to do that.
Noted. Good to know. :-)
> Note that the HPT 18x0A have an onboard processor which
> does the XOR (parity) calculations for RAID-5. For the
> non-A version
On 12/14/05 06:44, [LoN]Kamikaze wrote:
3)
There is one kind of thing I cannot do in /etc/devfs.rules, creating
links. So I am still doing this in /etc/devfs.conf (links don't cause
race conditions anyway, I hope).
One would think that "link ttyU0 pilot" would simply be translated to
"ln -s /dev
On Tue, Dec 13, 2005 at 10:31:21PM +0100, Roland Smith wrote:
> On Tue, Dec 13, 2005 at 12:55:39PM -0800, Brooks Davis wrote:
>
> > > What's wrong with the EXAMPLES section in devfs(8)?
> >
> > It's fine. Referring to devfs(8) was poor word choice on my part. I
> > meant the system as a whole i
I agree that a more flexible approach is generally better, but since
it's not necessary I don't want to create an extra entry in my
/etc/usbd.conf (one more file to worry about during mergemaster).
Thus I think the best solution would be to dump devfs.conf and
/etc/rc.d/devfs entirely (or leave it
On Wed, Dec 14, 2005 at 12:31:52AM +0100, [LoN]Kamikaze wrote:
> I agree that a more flexible approach is generally better, but since
> it's not necessary I don't want to create an extra entry in my
> /etc/usbd.conf (one more file to worry about during mergemaster).
IIRC, usbd is/will be deprecate
On Tuesday 13 December 2005 05:26 pm, Johny Mattsson wrote:
> On 12/14/05 06:44, [LoN]Kamikaze wrote:
> > 3)
> > There is one kind of thing I cannot do in /etc/devfs.rules,
> > creating links. So I am still doing this in /etc/devfs.conf
> > (links don't cause race conditions anyway, I hope).
> >
>
q
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Tue, 2005-Dec-13 13:43:13 -0400, fredthetree wrote:
>[/var/crash/vmcore.1]
>--
>Unread portion of the kernel message buffer:
>
>
>Fatal trap 12: page fault while in kernel mode
>fault virtual address = 0x10
That's a NULL pointer de-reference - it Shouldn't Happ
43 matches
Mail list logo
