In message <[EMAIL PROTECTED]>, Mike Tancsa wr
ites:
>
>It only happens when periodic runs, but it on occasion skips a day. Eg.
>yesterday it did not do it. It only started happening post Jan28th. I can
>brutalize the server with repeated buildworlds (-j2 through 8) and it is
>always successf
Vaclav Haisman wrote:
> > If you want this to not happen, you should explicitly uninstall the
> > handler, or you should call abort(3) (or _exit(2), if you don't want
> > to leave a core dump).
>
> Even though this is probably about my misunderstanding of things I post here
> the test I used.
[ .
Mooneer Salem wrote:
> Hello,
>
> I've been looking at the kernel source, in particular the scheduler
> in the past few weeks. I found a place in kern_switch.c where per-jail
> CPU controls could be added (in particular, in the kse_reassign() function).
> >From looking at that function, I could lo
> Because POSIX mandates that it do so?
>
> man 3 signal tells us:
>
> The handled signal is unblocked when the function returns and the process
> continues from where it left off when the signal occurred. Unlike previ-
> ous signal facilities, the handler func() remains installed a
[ Originally crossposted to -hackers and -fs. This reply Bcc'd to
-hackers, followups to -fs. ]
On Wed, Feb 19, 2003 at 10:20:12PM +0100, Michael Ranner wrote:
> Scan_ffs is a system tool from OpenBSD to recover erased disklabels
> from your hard drive.
Forgive me if I'm being dense, but what fe
Vaclav Haisman wrote:
> > man 2 abort
> >
> > -- Terry
>
> logout ~/tmp>man 2 abort
> No entry for abort in section 2 of the manual
>
> Besides, this doesn't explain anything. I see I haven't asked any question in
> my previous post. So, why does FreeBSD behave different?
Because POSIX mandates
> McKusick wrote:
> The potentially slow, but utterly effective way to fix this race
> is to only allow one rename at a time per filesystem.
Can we serialize unprivileged renames per mount as an alternate work around?
Later
Mark Hittinger
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL P
The potentially slow, but utterly effective way to fix this race
is to only allow one rename at a time per filesystem. It is
implemented by adding a flag in the mount structure and using
it to serialize calls to rename. When only one rename can happen
at a time, the race cannot occur.
If this prov
On Wed, 19 Feb 2003, Paul Robinson wrote:
> Seriosuly Terry, I can't tell if you were joking or not, but nobody is going
> to play with opengis stuff, just because it would be a "neat" way of showing
> where user groups are. :-)
No, but there are active OSS GIS packages - GRASS comes to mind, and
My searches for information on webcam have not found much, except for some
sites which say FreeBSD does not support USB web cameras.
Is anyone currently working on support for this? Does anyone have any
ideas about where one could go to get information about where to start
if one was to start wri
Just reminder that this problem is local kernel panic DoS (which can do
filesystem corruption) with very simple trigger code and it still exists.
And it's been almost 2 years since i wrote about it.
Workaround (commenting out panic call) doesnt fix the problem.
Server still crashes (not so ofte
Am Mittwoch, 19. Februar 2003 22:20 schrieb Michael Ranner:
> Hello!
>
> I am trying to learn scan_ffs (original from OpenBSD, ported to FreeBSD
> by Robert Watson) about UFS2 on 5-CURRENT, but it will not find the
> Superblock and I dont understand exactly both for loops, especially
> that 512 byt
Hello!
I am trying to learn scan_ffs (original from OpenBSD, ported to FreeBSD
by Robert Watson) about UFS2 on 5-CURRENT, but it will not find the
Superblock and I dont understand exactly both for loops, especially
that 512 byte increment.
Scan_ffs is a system tool from OpenBSD to recover erased
It only happens when periodic runs, but it on occasion skips a day. Eg.
yesterday it did not do it. It only started happening post Jan28th. I can
brutalize the server with repeated buildworlds (-j2 through 8) and it is
always successful. Its only on periodic that it dies and find is always
Mike Tancsa <[EMAIL PROTECTED]> writes:
> Fatal trap 12: page fault while in kernel mode
> mp_lock = 0002; cpuid = 0; lapic.id = 0100
> fault virtual address = 0xc6efa8e8
Hmm, different fault address this time.
> (kgdb) up 6
> #6 0xc0174830 in makedev (x=28, y=160) at /usr/src/sys/kern
On Wednesday 19 February 2003 10:20 am, IAccounts wrote:
> 1: What is the best FBSD list for finding out who (if anyone) is also
> working on IPFW and what new features are planned, and;
The IPFW list could help ([EMAIL PROTECTED]). To see who is working on
it, look at the commit logs (e.g.
http
On Wed, 19 Feb 2003 19:45:52 +0100
Pawel Jakub Dawidek <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 19, 2003 at 07:43:19PM +0100, Pawel Jakub Dawidek wrote:
> +> Patches are attached.
>
> Now!:)
>
Please resubmit your patch as PR to ensure it will not get lost.
--
Alexander Kabaev
To Unsubscribe:
On Wed, Feb 19, 2003 at 07:43:19PM +0100, Pawel Jakub Dawidek wrote:
+> Patches are attached.
Now!:)
--
Pawel Jakub Dawidek
UNIX Systems Administrator
http://garage.freebsd.pl
Am I Evil? Yes, I Am.
diff -ru /sys/compat/linux/linux_ipc.c sys/compat/linux/linux_ipc.c
--- /sys/compat/linux/linux_i
Sure,
send PRs over :)
On Wed, 19 Feb 2003 19:43:19 +0100
Pawel Jakub Dawidek <[EMAIL PROTECTED]> wrote:
> Hello hackers...
>
> I prepared patches against 4.7-STABLE for secure IPC in jail.
> Main host and every jail has separated IPC memory zones, etc.
> I have added some sysctls and set-gid o
Hello hackers...
I prepared patches against 4.7-STABLE for secure IPC in jail.
Main host and every jail has separated IPC memory zones, etc.
I have added some sysctls and set-gid on group kmem for ipcs(1)
is nomore needed.
I could port those patches against 5.x if someone will review and
commit i
Thus spake Wes Peters <[EMAIL PROTECTED]>:
> What would you like to see, a sigaction flag of SA_CRASHON2NDSIG that
> is set by default? (Ah, Wes, that software comedian.)
Sure, but let's call it SA_RESETHAND. ;-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers"
On Wed, Feb 19, 2003 at 11:38:23AM -, Paul Robinson wrote:
> Terry Lambert wrote:
>
> > None of those maps are clickable. They're actually just *tiny*
> > PNGs of maps-with-pins-in-them, with no obvious correlation to
> > real location data associated with PERL (e.g. number of pins is
> > not
Audsin wrote:
Sir / Madam
I am doing my research on fragmentation avoidance technique for mip6. I
am using FreeBSD4.4 with kame snap and ethereal to capture packets
I have a query regarding the packet length
If i am correct ,
packet length = IPHdr +extHdr+TCPHdr+TCPOpt+Data
Hi,
At 17:27 19/2/03, Tim Kientzle wrote:
Dag-Erling Smorgrav wrote:
[EMAIL PROTECTED] writes:
Well, I'm right in principle but wrong in current practice, at
the very least make it:
#define arc4random31() (arc4random() & RAND_MAX)
or rather
#define arc4random31() (arc4random() % (RAND_M
> "phk" == phk <[EMAIL PROTECTED]> writes:
phk> /dev/da2 is always writable unless you have any of the partitions
phk> open.
The error was that /dev/da2 didn't exist. I was confused too.
fdisk da2 # worked, displyed one slice (3) that was NetBSD
fdisk -I da2 # error, /dev/
On Tuesday 18 February 2003 22:36, Peter Jeremy wrote:
>
> I see this as a major advantage of arc4random() - if I want 32-bit
> random numbers I don't have to call random() twice and merge the
> results. I've never understood why random() was specified to return
> a '0' in the MSB.
It probably ha
In message <[EMAIL PROTECTED]>, David Gilbert writes:
>I ran into an interesting problem last night ... that was very
>frustrating. I was recycling SCSI drives from some NetBSD machines
>(that were client boxes) to add to a RAID server running
>FreeBSD-5.0-RELEASE.
>
>It's simply impossible to for
Dag-Erling Smorgrav wrote:
[EMAIL PROTECTED] writes:
Well, I'm right in principle but wrong in current practice, at
the very least make it:
#define arc4random31() (arc4random() & RAND_MAX)
or rather
#define arc4random31() (arc4random() % (RAND_MAX + 1))
to avoid relying on RAND_MAX be
On Wednesday 19 February 2003 04:43, Vaclav Haisman wrote:
> > man 2 abort
> >
> > -- Terry
>
> logout ~/tmp>man 2 abort
> No entry for abort in section 2 of the manual
Yeah, it's in (3). try _exit(2).
> Besides, this doesn't explain anything. I see I haven't asked any
> question in my previous
I would like to make some changes to IPFW, specifically, I would like to
add a function that would simulate fwd, but also change the destination
address. I know this can be done with natd, but would like to have it
native, so I can manipulate the packets in certain ways. My questions are
this:
1:
I ran into an interesting problem last night ... that was very
frustrating. I was recycling SCSI drives from some NetBSD machines
(that were client boxes) to add to a RAID server running
FreeBSD-5.0-RELEASE.
It's simply impossible to format NetBSD drives under current.
Let me expand on that. /d
Brian Buchanan wrote:
I'm having problems getting SMP to work on a Tyan S4520 Thunder GCHE
motherboard with 4x 1.9GHz Xeon processors:
Programming 16 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
Programming 16 pins in IOAPIC #1
Programming 16 pins in IOAPIC #2
AP #1 (PHY# 2) failed!
panic y/n?
At 08:39 PM 17/02/2003 +0100, Dag-Erling Smorgrav wrote:
Mike Tancsa <[EMAIL PROTECTED]> writes:
> ns4# nm /kernel | grep \^c0174 | sort
> [...]
> c01747d4 T makedev
> c01748f4 T freedev
This is it (makedev)
> Does this actually show the location ?
> ns4# gdb -k kernel.debug
> [...]
> (kgdb) lis
Sir / Madam
I am doing my research on fragmentation avoidance technique for mip6. I am
using FreeBSD4.4 with kame snap and ethereal to capture packets
I have a query regarding the packet length
If i am correct ,
packet length = IPHdr +extHdr+TCPHdr+TCPOpt+Data
=IPHdr+Rout
Respected Sir
I have made some changes to the
/usr/kame/kame/kame/sys/netinet6/tcp6_input.c and
/usr/kame/kame/kame/netinet6/sys/tcp6_output.c in FreeBSD 4.4 and iam
using Kame snap. I have some queries regarding making the changes active.
Can anyone please tell me the procedure to recompile o
> man 2 abort
>
> -- Terry
logout ~/tmp>man 2 abort
No entry for abort in section 2 of the manual
Besides, this doesn't explain anything. I see I haven't asked any question in
my previous post. So, why does FreeBSD behave different?
Vaclav Haisman
To Unsubscribe: send mail to [EMAIL PROTECTED
Vaclav Haisman wrote:
> I have been playing with signals handling and I've found one thing where
> FreeBSD differes from other unix systems that I have access to. This test loops
> endlessly in FreeBSD but terminates in SunOS 9 and GNU/Linux. It is as test for
> what happens when a program raises S
Hi,
I have been playing with signals handling and I've found one thing where
FreeBSD differes from other unix systems that I have access to. This test loops
endlessly in FreeBSD but terminates in SunOS 9 and GNU/Linux. It is as test for
what happens when a program raises SIGSEGV in SIGSEGV handle
Paul Robinson wrote:
> Terry Lambert wrote:
> > None of those maps are clickable. They're actually just *tiny*
> > PNGs of maps-with-pins-in-them, with no obvious correlation to
> > real location data associated with PERL (e.g. number of pins is
> > not equal to number of page entries, in most cas
Terry Lambert wrote:
> None of those maps are clickable. They're actually just *tiny*
> PNGs of maps-with-pins-in-them, with no obvious correlation to
> real location data associated with PERL (e.g. number of pins is
> not equal to number of page entries, in most cases, and the pins
> for Columbs
Peter Jeremy <[EMAIL PROTECTED]> writes:
> In any case, doesn't the name imply that it's 31-bits...
Yes, it's a bad name.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
[EMAIL PROTECTED] writes:
> Well, I'm right in principle but wrong in current practice, at
> the very least make it:
>
> #define arc4random31() (arc4random() & RAND_MAX)
or rather
#define arc4random31() (arc4random() % (RAND_MAX + 1))
to avoid relying on RAND_MAX being one less than a power
Thus spake Paul Herman <[EMAIL PROTECTED]>:
> On Wed, 19 Feb 2003 [EMAIL PROTECTED] wrote:
>
> > In message <[EMAIL PROTECTED]>, Paul Herma
> > n writes:
> >
> > > arc4random() returns random numbers in the range of 0 to
> > > (2**32)-1, and therefore has twice the range of RAND_MAX.
> >
> > Goo
In message <[EMAIL PROTECTED]>, Paul Herma
n writes:
>>
>> > EXAMPLES
>> > The following produces a drop-in replacement for the traditional
>> > random() and rand() functions using arc4random():
>> > #define arc4random31() (arc4random() & 0x7FFF)
>>
>> Not good. Only true on 32 bit a
On Wed, 19 Feb 2003 [EMAIL PROTECTED] wrote:
> In message <[EMAIL PROTECTED]>, Paul Herma
> n writes:
>
> > arc4random() returns random numbers in the range of 0 to
> > (2**32)-1, and therefore has twice the range of RAND_MAX.
>
> Good.
>
> > EXAMPLES
> > The following produces a drop-in repla
In message <[EMAIL PROTECTED]>, Paul Herma
n writes:
> arc4random() returns random numbers in the range of 0 to
> (2**32)-1, and therefore has twice the range of RAND_MAX.
Good.
> EXAMPLES
> The following produces a drop-in replacement for the traditional
> random() and rand() functions usi
On Wed, 19 Feb 2003, Peter Jeremy wrote:
> On Tue, Feb 18, 2003 at 06:22:37PM -0800, Paul Herman wrote:
> >
> > [...range of arc4random() is twice that of random()...]
>
> I see this as a major advantage of arc4random()
I see this as an advantage, too. It's also produces random numbers
with a ver
47 matches
Mail list logo
