On Fri, 18 Mar 2005 12:06:12 +1030
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
On Thursday, 17 March 2005 at 19:33:50 +0300, Roman Kurakin wrote:
Hi,
I was unable to refrain from posting this :-)
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o,
On Thu, 17 Mar 2005, John-Mark Gurney wrote:
but that causes a page fault in kernel mode (ie. Kernel panic :-)
Any help is appreciated, thanks.
Take a look at psignal(9)... You'll need to look up the struct proc for
psignal with pfind(9)... and then PROC_UNLOCK the struct proc after
On Thu, 17 Mar 2005, Pietro Cerutti wrote:
Hi Hackers,
I posted this on freebsd-questions, but couldn't find a solution...
Maybe here
Thank you!
Please: don't Cc me, I'm on the list!
-- Forwarded message --
From: Pietro Cerutti [EMAIL PROTECTED]
Date: Thu, 17
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Pietro Cerutti
Sent: Thursday, March 17, 2005 7:42 AM
To: FreeBSD; freebsd-hackers@freebsd.org
Subject: Re: problem due to hostname change
Well I double check once more on my system!
Unless your
Hey,
I'm busy writing a Ziatech 5503 watchdog driver for FreeBSD (and
porting all the watchdog stuff to DragonFly BSD) and Plan 9. For my
driver, I have no way to identify that the system has the driver, so
I wanted to make it conditional on
options ZT5503
existing in the kernel configuration
im writing an iSCSI initiator, which is 'almost' beta, but now im
getting into trouble.
to exercise the system im doing:
cd /to the iscsi device
rsh some-host -n dump 0f - /somefilesystem | restore rf -
this
o- works fine with no tags on UP/SMP hosts
o- works fine
Hi daniel,
Josseph in this mailing list responded that I can do
ifconfig em1 alias inet 205.229.165.8 netmask 255.255.255.255
Can I?
I need the other NIC for some internal operations.
On Fri, 18 Mar 2005 06:47, Amandeep Pannu wrote:
Now the em0 nic is up with 205.229.165.4 netmask
Greetings,
I'm trying to test for the possibility of interleaved data when two more
more processes are writing to a pipe and more than PIPE_BUF bytes need
to be written. How can I make a situation where this scenario can be
caused reliably so I can make my test case, then apply my patch and make
I'm busy writing a Ziatech 5503 watchdog driver for FreeBSD (and
porting all the watchdog stuff to DragonFly BSD) and Plan 9. For my
driver, I have no way to identify that the system has the driver, so
I wanted to make it conditional on
options ZT5503
That's not a good enough reason to
On Sat, 19 Mar 2005 04:04, Amandeep Pannu wrote:
ifconfig em1 alias inet 205.229.165.8 netmask 255.255.255.255
Can I?
Not sure, I would expect you'd get complaints from ARP because both NIC's are
on the same segment.
I need the other NIC for some internal operations.
Errm.. Why do they
On Sat, 19 Mar 2005 09:25, Warner Losh wrote:
That's not a good enough reason to make it an option, it should really
be a device. Users that want it can add it to their kernel config.
In fact, they'd have to add it either way, so why make it weird for
them.
Put this device on the ISA bus,
11 matches
Mail list logo
