On Thu, Sep 13, 2001 at 04:09:57PM -0700, Mike Smith wrote:
Is there a single blessed way to define packed structures
for use in drivers? I suspect that using #pragma pack(1)
will lead to alignment errors in non-Intel architectures.
Any form of packing is going to cause problems for
Josef Karthauser wrote:
Hi!
I just wonder if all freebsd developers are ok, due the wtc attack?
We believe so.
Has anyone talked to Loqui Chen since the the event?
Loqui was a financial person in New York at one time,
and made significant contributions in the VM system, the
Soft
Mike Smith wrote:
Having said that, I recommend using __attribute__ ((packed))
to explicitly request that a structure be packed.
Is there a problem with #pragma pack(1)? I see it in a
lot of header files... do they need changing?
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
From: Brian Somers [EMAIL PROTECTED]
Subject: Re: Checking changes to listening ports in /etc/security
Date: Thu, Sep 13, 2001 at 10:25:02PM +0100
I like this idea. I think It would be worth making it diff against
/dev/null when netstat.today doesn't exist, so that the first time
Does it make sense at all to stripe primary slave,
secondary master and slave together?
I would imagine it is a waste of time , just looking for thoughts
on this vs just a single primary master IDE.
--
Dan
+--+
| BRAVENET WEB
Terry Lambert wrote:
Mike Smith wrote:
Having said that, I recommend using __attribute__ ((packed))
to explicitly request that a structure be packed.
Is there a problem with #pragma pack(1)? I see it in a
lot of header files... do they need changing?
Yes, but it should be:
#define
iJust a quickie - sorry if it's OT, but I know a few
people on this list use Orinoco wireless NICs.
I'm finally implementing my wireless gateway
BSD box.
Is there any difference between Gold and Silver cards from
a compatibility standpoint (with the usual Apple Airport cards)?
Thanks!
--
One
On Fri, Sep 14, 2001 at 03:02:03PM +0100, Rasputin wrote:
Is there any difference between Gold and Silver cards from
a compatibility standpoint (with the usual Apple Airport cards)?
With WEP encryption turned off they both work together fine. I've
seen many used in mixed enviornments. With
Peter Wemm writes:
The same goes for __format_arg(n) in stdio.h. And so on. We've been pretty
clean about it so far, but a few have slipped through.
That __format_arg, btw, breaks the Compaq CCC compiler causes us to
have to override stdio.h because of just that one line.
Does your
Hi,
A quote from the end of the boot_i386.8 manual page..
IMPORTANT NOTE: Because of limitations imposed by the conventional disk
interface provided by the BIOS, all boot-related files and structures
(including the kernel) that need to be accessed during the boot phase
must reside on
Thanks! It turns out the bug is caused by the following reason:
I use bp=malloc() to allocate a buffer structure and issue an I/O with
BUF_STRATEGY(). Then I use free() to free bp even before the I/O is
completed. Really stupid. Memory trespass seems to be the most common
source of panics I
On Fri, Sep 14, 2001 at 06:06:22PM +0300, Peter Pentchev wrote:
Hi,
A quote from the end of the boot_i386.8 manual page..
IMPORTANT NOTE: Because of limitations imposed by the conventional disk
interface provided by the BIOS, all boot-related files and structures
(including the
On Thu, Sep 13, 2001 at 04:09:57PM -0700, Mike Smith wrote:
Is there a single blessed way to define packed structures
for use in drivers? I suspect that using #pragma pack(1)
will lead to alignment errors in non-Intel architectures.
Any form of packing is going to cause
A quote from the end of the boot_i386.8 manual page..
IMPORTANT NOTE: Because of limitations imposed by the conventional disk
interface provided by the BIOS, all boot-related files and structures
(including the kernel) that need to be accessed during the boot phase
must reside on
From: Brian Somers [EMAIL PROTECTED]
Subject: Re: Checking changes to listening ports in /etc/security
Date: Fri, Sep 14, 2001 at 12:18:43PM +0100
I think the attached patch makes things slightly better. We only run
sockstat once, and remove the trailing whitespace that sockstat emits
On Fri, Sep 14, 2001 at 09:50:23AM -0700, Mike Smith wrote:
A quote from the end of the boot_i386.8 manual page..
IMPORTANT NOTE: Because of limitations imposed by the conventional disk
interface provided by the BIOS, all boot-related files and structures
(including the kernel)
So.. if I read you right, booting correctly for 1024 cylinders works
if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd
slice? Does this mean that boot1 and boot2 should work just fine if they
are loaded by another kind of MBR loader (say, Grub), and they find out
On Fri, Sep 14, 2001 at 10:30:37AM -0400, Leo Bicknell wrote:
On Fri, Sep 14, 2001 at 03:02:03PM +0100, Rasputin wrote:
Is there any difference between Gold and Silver cards from
a compatibility standpoint (with the usual Apple Airport cards)?
With WEP encryption turned off they both work
Brooks Davis wrote:
On Fri, Sep 14, 2001 at 10:30:37AM -0400, Leo Bicknell wrote:
On Fri, Sep 14, 2001 at 03:02:03PM +0100, Rasputin wrote:
Is there any difference between Gold and Silver cards from
a compatibility standpoint (with the usual Apple Airport cards)?
With WEP
Is there a way to increase the memory size that is allocated by the kernel
to a certain kernel memory pool (is that the correct word?):
I mean, I have
options VM_KMEM_SIZE=(64*1024*1024)
in my kernel config file, and it appears that I'm only allowed to use half
of that memory for a
On 14-Sep-01 Mike Smith wrote:
A quote from the end of the boot_i386.8 manual page..
IMPORTANT NOTE: Because of limitations imposed by the conventional disk
interface provided by the BIOS, all boot-related files and structures
(including the kernel) that need to be accessed during
Peter Pentchev wrote:
A quote from the end of the boot_i386.8 manual page..
IMPORTANT NOTE: Because of limitations imposed by the conventional disk
interface provided by the BIOS, all boot-related files and structures
(including the kernel) that need to be accessed during the boot
Kent Stewart wrote:
Mike Smith wrote:
So.. if I read you right, booting correctly for 1024 cylinders works
if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd
slice? Does this mean that boot1 and boot2 should work just fine if they
are loaded by another
On Fri, Sep 14, 2001 at 10:15:48AM -0700, Brooks Davis wrote:
Unless Apple is mangling the firmware or someone screwed up the driver,
this is false. Gold Lucent cards are capable of 40-bit crypto.
How do you set this? I have been unable to set a 40 bit key, or
set a card into '40 bit mode'
any success in using an Airport AP with non airport cards?
danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
From: Igor Podlesny [EMAIL PROTECTED]
Subject: Re[2]: Checking changes to listening ports in /etc/security
Date: Fri, Sep 14, 2001 at 11:11:10AM +0800
Hello!
I've done similar thing by myself also, cause I have been working with
some Linux distros, where it is an usual thing (I mean
On Fri, Sep 14, 2001 at 09:46:08PM +0300, Danny Braniss wrote:
any success in using an Airport AP with non airport cards?
It works with Lucent gold cards at least. If you open it the card
inside is a standard lucent silver card, not even relabeled.
The guts are also a 'karlbridge', and the
On Fri, Sep 14, 2001 at 09:46:08PM +0300, Danny Braniss wrote:
any success in using an Airport AP with non airport cards?
We have not had any problems using many different manufactures with
the Airport AP. The only gotcha is if you using WEP. Different
drivers using different methods of
On Fri, Sep 14, 2001 at 03:10:48PM -0400, Leo Bicknell wrote:
On Fri, Sep 14, 2001 at 10:15:48AM -0700, Brooks Davis wrote:
Unless Apple is mangling the firmware or someone screwed up the driver,
this is false. Gold Lucent cards are capable of 40-bit crypto.
How do you set this? I have
[EMAIL PROTECTED] wrote:
Kent Stewart wrote:
Mike Smith wrote:
So.. if I read you right, booting correctly for 1024 cylinders works
if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd
slice? Does this mean that boot1 and boot2 should work just fine
[EMAIL PROTECTED] writes:
| Kent Stewart wrote:
|
| Mike Smith wrote:
|
|So.. if I read you right, booting correctly for 1024 cylinders works
|if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd
|slice? Does this mean that boot1 and boot2 should work just
On 14-Sep-01 Doug Ambrisko wrote:
[EMAIL PROTECTED] writes:
| Kent Stewart wrote:
|
| Mike Smith wrote:
|
|So.. if I read you right, booting correctly for 1024 cylinders works
|if boot0 knows about it. Isn't boot0 the one in the MBR, not in the
|fbsd
|slice? Does this
John Baldwin writes:
| This is for boot0. Nothing should be touching boot1 flags.
| My guess is that someone has somehow mixed an old boot2 with the new boot1
| which is jumping to the wrong place to call xread. The code at cs:eip looks
| a lot like the BPB in boot1 now.
Okay that basically
John Baldwin wrote:
On 14-Sep-01 Kent Stewart wrote:
[EMAIL PROTECTED] wrote:
Kent Stewart wrote:
Mike Smith wrote:
So.. if I read you right, booting correctly for 1024 cylinders works
if boot0 knows about it. Isn't boot0 the one in the MBR, not in the
On 14-Sep-01 Kent Stewart wrote:
John Baldwin wrote:
On 14-Sep-01 Kent Stewart wrote:
[EMAIL PROTECTED] wrote:
Kent Stewart wrote:
Mike Smith wrote:
So.. if I read you right, booting correctly for 1024 cylinders
works
if boot0 knows about it. Isn't
In message [EMAIL PROTECTED] Mike Smith writes:
: Any form of packing is going to cause problems for items that are
: located in illegal fashions.
It is almost more appropriate to use bus_space_{read,write} than using
memory mapped structures. The bus macros will work for otherwise
unaligned
John Baldwin wrote:
On 14-Sep-01 Kent Stewart wrote:
John Baldwin wrote:
On 14-Sep-01 Kent Stewart wrote:
[EMAIL PROTECTED] wrote:
Kent Stewart wrote:
Mike Smith wrote:
So.. if I read you right, booting correctly for 1024 cylinders
works
Umm, ok. Did you do 'disklabel -B' to update the boot blocks on the disk
(the
boot blocks do _not_ live in the /boot files, they are part of the
disklabel)
when you updated the boot1 in bootsect.bsd?
That I didn't do. What do I need to do? I'm reading the man page and
this is foreign
In message [EMAIL PROTECTED] Mike Smith writes:
: Any form of packing is going to cause problems for items that are
: located in illegal fashions.
It is almost more appropriate to use bus_space_{read,write} than using
memory mapped structures. The bus macros will work for otherwise
In message [EMAIL PROTECTED], dphoenix@braven
et.com writes:
Does it make sense at all to stripe primary slave,
secondary master and slave together?
I would imagine it is a waste of time , just looking for thoughts
on this vs just a single primary master IDE.
On a normal system, random access
Hello,
I am running FreeBSD Current and having a problem with my Memorx CRW-1662
CD-Writer and trying to use it with 'burncd'. I tried to write a small
test 'iso' Image that I made using mkisofa and got the following error
message MODE_SELECT_BIG - Illegal Request'...when trying to write to
ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3
sn 2) retrying
ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3
sn 2) retrying
ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3
sn 2) retrying
ad0s1a: UDMA ICRC error
On 14-Sep-2001 Peter Pentchev wrote:
So.. if I read you right, booting correctly for 1024 cylinders works
if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd
slice? Does this mean that boot1 and boot2 should work just fine if they
are loaded by another kind of MBR
ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3
sn 2) retrying
ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3
sn 2) retrying
ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn 3
sn 2) retrying
ad0s1a: UDMA ICRC
44 matches
Mail list logo
