On Sun, 9 Apr 2006, Duane Whitty wrote:
Started doing a little reading on the UFS and UFS2 file systems. I'm just
wondering if all types of files have extended attribute blocks available
including named pipes, sockets, and device files?
Is it still the case that there are three unused
On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote:
Firewire would seem to be a lot like USB - hot pluggable and
chainable, though I'm not sure if something like a firewire hub. What
does it to do wire down device addresses?
FireWire devices have uuids, you can simply enumerate them
On Mon, 10 Apr 2006, Robert Watson wrote:
On Sun, 9 Apr 2006, Duane Whitty wrote:
Started doing a little reading on the UFS and UFS2 file systems. I'm just
wondering if all types of files have extended attribute blocks available
including named pipes, sockets, and device files?
A quick note to inform my fellow FreeBSD users and developers that my
new book Code Quality: The Open Source Perspective (Addison-Wesley,
2006) is now available. Almost all the 623 examples I use in the book
are drawn from actual code. NetBSD is the primary package I used for
source code
In [EMAIL PROTECTED], [EMAIL PROTECTED] typed:
On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote:
Firewire would seem to be a lot like USB - hot pluggable and
chainable, though I'm not sure if something like a firewire hub. What
does it to do wire down device addresses?
FireWire
Hello All!
I'm porting a CPI card driver from linux to FreeBSD.
Some initialization routines require much time (~1-2 seconds).
Initialization of hardware should be done during opening device
special file. So, I need to switch thread context.
I'm doing it in such way:
On Mon, Apr 10, 2006 at 09:47:41AM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], [EMAIL PROTECTED] typed:
On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote:
Firewire would seem to be a lot like USB - hot pluggable and
chainable, though I'm not sure if something like a firewire
Nickolas wrote:
Hello All!
I'm porting a CPI card driver from linux to FreeBSD.
Some initialization routines require much time (~1-2 seconds).
Initialization of hardware should be done during opening device
special file. So, I need to switch thread context.
I'm doing it in such way:
From: M. Warner Losh [EMAIL PROTECTED]
usb assigns addresses dynamically. Everyone else does it basically
statically. PCI slot/device numbers are static, but extreme
configurations can change the bus number.
Some USB devices (though not all of them) provide a unique
device ID. If this ID is
(This message started life on questions, but no responses :-( If
there's a better list to try, please point me! I have no clue how
rebooting actually works).
Setup: Dell 2850 running i386 FreeBSD 5.4-p5 (or so), ACPI enabled and
apparently working (shutdown -p or -r work fine).
After a
[EMAIL PROTECTED] wrote:
On Mon, Apr 10, 2006 at 09:47:41AM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], [EMAIL PROTECTED] typed:
On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote:
Firewire would seem to be a lot like USB - hot pluggable and
chainable, though I'm not sure if
I'm running Nagios 2.0 on FreeBSD 6 and I occasionally experience the
problem originally discussed
http://www.freebsd.org/cgi/getmsg.cgi?fetch=165398+171880+/usr/local/www/db/text/2005/freebsd-hackers/20050821.freebsd-hackers
(That is: a forked nagios process that consumes as much CPU time as it
On Sun, Apr 09, 2006 at 06:48:25PM -0600, M. Warner Losh wrote:
I though thtis was already supported. We export bus/slot/function
information devd, which can be used to configure the device.
If I've read the specs or code incorrectly please do let me know --
my reading here is based on the PCI
In message: [EMAIL PROTECTED]
Bruce M Simpson [EMAIL PROTECTED] writes:
: On Sun, Apr 09, 2006 at 06:48:25PM -0600, M. Warner Losh wrote:
: I though thtis was already supported. We export bus/slot/function
: information devd, which can be used to configure the device.
:
: If I've
I think at this point it's been pretty well established that:
- Device naming and unit numbering is not stable enough to avoid breakage
across hardware changes.
- There is a need for generic and/or descriptive interface naming
independent of driver- and probe-order-based naming.
- There are
On Apr 10, 2006, at 2:23 PM, Darren Pilgrim wrote:
I think at this point it's been pretty well established that:
- Device naming and unit numbering is not stable enough to avoid
breakage across hardware changes.
- There is a need for generic and/or descriptive interface naming
independent
Douglas K. Rand wrote:
I'm running Nagios 2.0 on FreeBSD 6 and I occasionally experience the
problem originally discussed
http://www.freebsd.org/cgi/getmsg.cgi?fetch=165398+171880+/usr/local/www/db/text/2005/freebsd-hackers/20050821.freebsd-hackers
(That is: a forked nagios process that
17 matches
Mail list logo
