On Wed, May 24, 2006 at 12:29:28PM -0500, Eric Anderson wrote, and it was
proclaimed:
> Eric Anderson wrote:
> >Coleman Kane wrote:
> >>On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote:
> >>>On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote:
> Brooks Davis wrote:
>
В сообщении от Среда 24 мая 2006 21:14 Cesar написал(a):
> Hi,
>
> Anyone know if FreeBSD 6.x have problems with usb flash disks?
> I have a mini-freebsd build running on some flash disks with FreeBSD
> 5.3, last week I changed to FreeBSD 6.0 and my flash disks started to show
> a lot of er
2006/5/24, R. Tyler Ballance <[EMAIL PROTECTED]>:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've started the uphill battle to port FreeBSD's kernel to run
"paravirtualized" (<--note the smart sounding vocabulary) on top of
the L4/Iguana OS (Iguana is a very barebones OS developed by NICTA:
h
On Sun, May 21, 2006 at 02:28:29PM -0300, Ricardo A. Reis wrote:
>
> First about exit codes, when program is executed without options,
> how this must return ?
> kldunload and kldload not return the same exit codes,
>
>[EMAIL PROTECTED]:~/kldfind] # kldload
> usage: kldload [-v]
Eric Anderson wrote:
Coleman Kane wrote:
On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote:
On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote:
Brooks Davis wrote:
On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote:
Brooks Davis wrote:
On Sun, Apr 30, 2006 a
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
william wallace wrote this message on Wed, May 24, 2006 at 21:13 +0800:
> roger really good tips :)
> and so far as i know ,
> the PCI configure space is accessed by pci_read_config,and so on
> the PCI IO space is accessed by
bus_space_read_1 and friends...
> the PCI memory space is ac
> the PCI configure space is accessed by pci_read_config,and so on
> the PCI IO space is accessed by
> the PCI memory space is accessed by bus_space_read_1 and so on
> am i right sir?
Yes.
Warner
___
freebsd-hackers@freebsd.org mailing lis
On Wednesday 24 May 2006 03:05, R. Tyler Ballance wrote:
> I've started the uphill battle to port FreeBSD's kernel to run
> "paravirtualized" (<--note the smart sounding vocabulary) on top of
> the L4/Iguana OS (Iguana is a very barebones OS developed by NICTA:
> http://www.ertos.nicta.com.au/softw
Hi,
Anyone know if FreeBSD 6.x have problems with usb flash disks?
I have a mini-freebsd build running on some flash disks with FreeBSD
5.3, last week I changed to FreeBSD 6.0 and my flash disks started to show a
lot of errors. I tried the 6.1 STABLE too, but no lucky.
Flash Disk Info:
roger really good tips :)
and so far as i know ,
the PCI configure space is accessed by pci_read_config,and so on
the PCI IO space is accessed by
the PCI memory space is accessed by bus_space_read_1 and so on
am i right sir?
On 5/24/06, John-Mark Gurney <[EMAIL PROTECTED]> wrote:
wi
Artem Kazakov wrote at 20:00 +0900 on May 24, 2006:
> I don't know if this should go here, point me to the right place.
> But it looks like a problem (bug?) in tcsh.
That report and the link to the PR should be plenty of information to
ship off to:
[EMAIL PROTECTED]
(see also http://mx.gw.co
On Wed, May 24, 2006 at 01:21:59AM +, [EMAIL PROTECTED] wrote:
> I tried the 'ln -s' command in bothe 4.3 & 4.7 in a situation
> where it should fail and it did, but it still had a return/exit
> code of 0 , I think it should have been nonzero. I tried 'ln -s
> a b' where the file b exis
Dear All,
I don't know if this should go here, point me to the right place.
But it looks like a problem (bug?) in tcsh.
The story started from this pr:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/77574
While debugging I realized that the problem is because of the way tcsh
manages descri
"Artem Kazakov" <[EMAIL PROTECTED]> writes:
> The problem is that at some point a socket() function is called. And
> it returns descriptor = 1, which is a standart ouput.
socket() will not return 1 unless you previously closed descriptor 1,
either directly with close(1) or indirectly with fclose(s
william wallace wrote this message on Wed, May 24, 2006 at 15:48 +0800:
> IN static device_method_t pci_methods[] = {
> what is the freeBSD's magic to connect pci_read_config_methodwtih
> PCI_READ_CONFIG? awk script?and so on?
> which
> DEVMETHOD(pci_read_config,pci_read_config_method), in
IN static device_method_t pci_methods[] = {
what is the freeBSD's magic to connect pci_read_config_methodwtih
PCI_READ_CONFIG? awk script?and so on?
which
DEVMETHOD(pci_read_config, pci_read_config_method), in pci.c
command = PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2); in
pci_enable_io_
what is a process descriptor table?
process FILE descriptor table?
process table?
process file descriptor table I suppose.
The problem is that at some point a socket() function is called. And
it returns descriptor = 1, which is a standart ouput.
So when write() is done, everything goes to termin
Artem Kazakov wrote:
Dear All,
please give me a hint, how to see process descriptor table?
I'm debugging in gdb.
what is a process descriptor table?
process FILE descriptor table?
process table?
Tyoma.
___
freebsd-hackers@freebsd.org mailin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've started the uphill battle to port FreeBSD's kernel to run
"paravirtualized" (<--note the smart sounding vocabulary) on top of
the L4/Iguana OS (Iguana is a very barebones OS developed by NICTA:
http://www.ertos.nicta.com.au/software/kenge/i
20 matches
Mail list logo
