and copied the file
GENERIC.hints to /boot/device.hints and installed the new kernel. I ve
updated all files in /etc and remade all devices. Now a bootup hangs:
a) The kernel is loading
b) acpi.ko is loading
c) Pentium Pro MTRR support enable
d) WARNING: Driver mistake: destroy_dev on 154/0
next
On Wed, Oct 31, 2001 at 12:10:14AM +, Nick Hibma wrote:
Yes. I have no idea why phk has not done this.
As this is a purposeful panicing of systems that worked fine before, I
presume that someone is keeping track of the problems that are occurring
and going to do something about it? Or
[EMAIL PROTECTED] (Jan Stocker) writes:
So whats on?
Please refer to the Handbook, section 19.2.1.4, first paragraph.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
tl == Terry Lambert wrote:
tl FWIW: tail-call optimization is when I have a function
tl that, as it's last thing (perhaps after reordering by
tl the compiler, as well) calls another function, such
tl that the return value of the other function is its
tl return value.
See also:
Debunking
Terry Lambert([EMAIL PROTECTED])@2001.06.22 20:38:45 +:
Karsten W. Rohrbach wrote:
btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved
instrumentation of the new compiler kit, is there someone working on
getting gcc-3.0 into -current?
...yes *sigh* i know,
Karsten W. Rohrbach wrote:
refer to http://www.gnu.org/software/gcc/gcc-3.0/features.html
---
General Optimizer Improvements:
- Basic block reordering pass.
- New if-conversion pass with support for conditional (predicated)
execution.
- New tail call and sibling call
btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved
instrumentation of the new compiler kit, is there someone working on
getting gcc-3.0 into -current?
...yes *sigh* i know, 3.0 is _not_ stable, neither is -current ;-)
/k
Dag-Erling Smorgrav([EMAIL PROTECTED])@2001.06.21
On Fri, Jun 22, 2001 at 07:22:32PM +0200, Karsten W. Rohrbach wrote:
btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved
instrumentation of the new compiler kit, is there someone working on
getting gcc-3.0 into -current?
It will come with time.
To Unsubscribe: send mail to
Karsten W. Rohrbach wrote:
btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved
instrumentation of the new compiler kit, is there someone working on
getting gcc-3.0 into -current?
...yes *sigh* i know, 3.0 is _not_ stable, neither is -current ;-)
Does it do tail-call
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
June 5th doesn't work (dumps core when it gets to crt1.c). Today's
won't build anything at all.
I think I've found the problem - what doesn't work is:
- building crt1.c with -fno-builtin
- building anything with gcc compiled with -fno-builtin
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
I think I've found the problem - what doesn't work is:
- building crt1.c with -fno-builtin
- building anything with gcc compiled with -fno-builtin
Ah, no, I understand now: crt1 is the first item to be built in the
libraries stage of
In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2
will dump core when compiling specific source files (crt1.c at least),
and in the very latest -CURRENT, when compiling anything at all. So
far, gcc built with CPUTYPE set to i586 seem to work fine.
DES
--
Dag-Erling Smorgrav -
On Thu, Jun 21, 2001 at 12:37:00AM +0200, Dag-Erling Smorgrav wrote:
In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2
will dump core when compiling specific source files (crt1.c at least),
and in the very latest -CURRENT, when compiling anything at all. So
far, gcc built
David O'Brien [EMAIL PROTECTED] writes:
On Thu, Jun 21, 2001 at 12:37:00AM +0200, Dag-Erling Smorgrav wrote:
In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2
will dump core when compiling specific source files (crt1.c at least),
and in the very latest -CURRENT, when
I hope I don't offend anyones intelligence...
This is a typical Nigerian 4-1-9 scam.
To read more, just do a search on google:
http://www.google.com/search?q=nigeria+scam+4+1+9
Leif
- Original Message -
From: "jega uba" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 16,
I have uncovered some odd behavior on my machine here using netgraph
since the last changes..
I'm trying to find the problem but I need sleep...
If you have used he latest netgraph code, let me know what modules
you are using and how so I can try narrow my search..
thanks..
Julian
--
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:34 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT = (http://WWW.26
To: Peter Wagner
Cc: FreeBSD List
Subject: VIRUS WARNING
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner [EMAIL PROTECTED] at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject &qu
This mail message was not automatically generated by our Stupid2000 release
of Dumbscan which did not find any virus infected files in the (0) or more
attached file(s) in this message(s) in this/these posting(s). As such it seems
to be an exceptional condition and we are choosing to respond to
[EMAIL PROTECTED] wrote:
WARNING!
Mail robots uproar... :-)
--
With Best Regards.
Rashid N. Achilov (RNA1-RIPE), Brainbench ID: 28514
Granch Ltd. system administrator, e-mail: [EMAIL PROTECTED]
tel/fax (383-2) 24-2363
To Unsubscribe: send mail to [EMAIL PROTECTED
joke
Nice product... where can I download this?? ;)
Perhaps you should put this in the ports tree?? *chuckle*
/joke
Cheers,
Marc
On Thu, Nov 02, 2000 at 01:14:49AM -0800, Dragos Ruiu wrote:
This mail message was not automatically generated by our Stupid2000 release
of Dumbscan which did
[EMAIL PROTECTED] wrote:
I get it as well. IIRC, it simply means that the bpf pseudo device needs
to be updated, but is otherwise harmless. I forgot the details, but it's
all in the mailinglist archives. Somewhere... :-)
Anybody handling this, or anybody can give pointers as to what
On 02-Nov-00 Marcel Moolenaar wrote:
[EMAIL PROTECTED] wrote:
I get it as well. IIRC, it simply means that the bpf pseudo device needs
to be updated, but is otherwise harmless. I forgot the details, but it's
all in the mailinglist archives. Somewhere... :-)
Anybody handling this, or
On 02-Nov-00 John Baldwin wrote:
On 02-Nov-00 Marcel Moolenaar wrote:
[EMAIL PROTECTED] wrote:
I get it as well. IIRC, it simply means that the bpf pseudo device needs
to be updated, but is otherwise harmless. I forgot the details, but it's
all in the mailinglist archives.
John Baldwin wrote:
Quick question: Is this a problem for people _without_ DEVFS?
That's a yes for me.
non-DEVFS case. Try this hackish patch:
Index: bpf.c
===
RCS file: /usr/cvs/src/sys/net/bpf.c,v
retrieving revision
Quick question: Is this a problem for people _without_ DEVFS? Poul
may have accidentally broke calling make_dev for the bpf device in the
non-DEVFS case. Try this hackish patch:
Personally, I surely get it with DEVFS and I think I also got it when running
without it. I will try the patch
On 02-Nov-00 Marcel Moolenaar wrote:
John Baldwin wrote:
Quick question: Is this a problem for people _without_ DEVFS?
That's a yes for me.
non-DEVFS case. Try this hackish patch:
Index: bpf.c
===
RCS file:
John Baldwin wrote:
I already managed to test it locally here and commit the proper fix.
It was an order of operations bug due to the fact that ! is
evaluated before .
Ok, thanks!
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe:
Subject says it all. I get:
WARNING: driver bpf should register devices with make_dev() (dev_t = "#bpf/0")
probably at first usage. Card is an xe PC Card.
I know I will probably get flamed for not RTF*, but I couldn't find a clue
anywhere...
Bye,
Andrea
--
[EMAIL PROTECTED] wrote:
WARNING: driver bpf should register devices with make_dev() (dev_t = "#bpf/0")
probably at first usage. Card is an xe PC Card.
I know I will probably get flamed for not RTF*, but I couldn't find a clue
anywhere...
I get it as well. IIRC, it si
Hi,
I'm seeing lots of:
ed0: warning - receiver ring buffer overrun
This box is building the world with sources via NFS. What gives?
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]fax (0118) 989 4254
To Unsubscribe: send mail to [EMAIL
On Tue, Oct 10, 2000 at 01:35:57PM +0100, Bob Bishop wrote:
Hi,
I'm seeing lots of:
ed0: warning - receiver ring buffer overrun
This box is building the world with sources via NFS. What gives?
Something not servicing the ed0 card fast enough? FWIW: my -current build
on a PPro 200 took
At 20:08 +0200 10/10/00, Wilko Bulte wrote:
On Tue, Oct 10, 2000 at 01:35:57PM +0100, Bob Bishop wrote:
Hi,
I'm seeing lots of:
ed0: warning - receiver ring buffer overrun
This box is building the world with sources via NFS. What gives?
Something not servicing the ed0 card fast enough
Hi,
ed0: warning - receiver ring buffer overrun
One more datapoint: I have two boxes doing this, both with ed but one is
ISA, the other is PCI.
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]fax (0118) 989 4254
To Unsubscribe: send mail
At 10 Oct 2000 22:36:15 GMT,
Bob Bishop [EMAIL PROTECTED] wrote:
One more datapoint: I have two boxes doing this, both with ed but one is
ISA, the other is PCI.
I don't have statistics, but I feel very slow on my SMP box with
recent -current (with NFS, fxp0).
--
Jun Kuriyama [EMAIL
Warning:
Do not use IBM Microdrives in any USB based CF II readers, like the
SmartMedia ImageMate until further notice. I've had reports of 2 drives
breaking in a SmartMedia ImageMedia. They are PHYSICALLY broken and will
no longer work.
Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED
In message [EMAIL PROTECTED], "Daniel O'Connor" write
s:
On 15-Jun-00 Poul-Henning Kamp wrote:
Remove the "wd" compatibility name from the "ad" driver.
WARNING: If you have not updated to use /dev/wd* in your /etc/fstab
You mean 'If you have not update
will
need this RSN.
Remove a pointless warning in the root device locating code.
Remove the "wd" compatibility name from the "ad" driver.
WARNING: If you have not updated to use /dev/wd* in your /etc/fstab
and modern bootblocks, it would be a very good idea to do so
On 15-Jun-00 Poul-Henning Kamp wrote:
Remove the "wd" compatibility name from the "ad" driver.
WARNING: If you have not updated to use /dev/wd* in your /etc/fstab
You mean 'If you have not updated to use /dev/ad* in your /etc/fstab...' right?
---
Dani
Hi,
I just up'd my sources to -current to try sblive support out. Did make world
and new kernel but now I get a warning at boot.
Device char-major=116 minor=196608 opened in block mode, convert to char
mode with /dev/MAKEDEV before 2000-07-01
I'm sure it just a simple command to fix, but I
"Andrew Tulloch" [EMAIL PROTECTED] writes:
Device char-major=116 minor=196608 opened in block mode, convert to char
mode with /dev/MAKEDEV before 2000-07-01
It has been fixed in sys/kern/vfs_subr.c:1.255. cvsup or grab the
patch and apply.
/assar
To Unsubscribe: send mail to [EMAIL
.
Could you try to update your bootblocks with the disklabel
program and see if that stops the warning Manfred ?
I did a disklabel -B da0 and it still happens
Another thing is this is a RAID 1 disk 2 disk mirror on a DPT RAID controller
I don't know if that make a difference.
Which is the dev I'm
program and see if that stops the warning Manfred ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
I get this in boot mesgs and I don't know how to fix it.
Device char-major=13 minor=0 opened in block mode, convert to char mode with
/dev/MAKEDEV before 2000-07-01
I've run MAKEDEV all
I have a simple fstab:
# DeviceMountpoint FStype Options DumpPass#
-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
I get this in boot mesgs and I don't know how to fix it.
Device char-major=13 minor=0 opened in block mode, convert to char mode
with /dev/MAKEDEV before 2000-07-01
There is a bug somewhere in the rootmount code.
I just lack the
At 09:54 PM 5/13/2000 +0200, Assar Westerlund wrote:
Jeroen Ruigrok van der Werven [EMAIL PROTECTED] writes:
-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
I get this in boot mesgs and I don't know how to fix it.
Device char-major=13 minor=0 opened in block mode, convert to
In message [EMAIL PROTECTED], Manfred Antar writes:
--- vfs_subr.c~ Sat May 6 00:08:38 2000
+++ vfs_subr.c Sat May 13 21:47:08 2000
@@ -1296,7 +1296,7 @@
return (error);
}
vp = nvp;
- vp-v_type = VBLK;
+ vp-v_type = VCHR;
addalias(vp,
At 10:28 PM 5/13/2000 +0200, Jeroen Ruigrok van der Werven wrote:
-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote:
Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use
rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ?
The
The following patch fixed the problem for me. For extra points,
rename the function.
That fixed the problem for the me too. Thanks!
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Actually I think this is an indication of really old boot blocks.
The old bootblocks passed in a Bmajor number for the root device.
Could you try to update your bootblocks with the disklabel
program and see if that stops the warning Manfred ?
I can't speak for this case, but the one I
Jeroen Ruigrok van der Werven [EMAIL PROTECTED] writes:
-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
I get this in boot mesgs and I don't know how to fix it.
Device char-major=13 minor=0 opened in block mode, convert to char mode
with /dev/MAKEDEV before 2000-07-01
There
-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote:
Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use
rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ?
The /dev/da0s1a would be the correct one to use, example:
# Device
I get this in boot mesgs and I don't know how to fix it.
Device char-major=13 minor=0 opened in block mode, convert to char mode
with /dev/MAKEDEV before 2000-07-01
There is a bug somewhere in the rootmount code.
It's the following VFS_MOUNT call at line 215 of vfs_mountroot_try()
No, I havn't tracked down the last couple of causes of this, but I
will try to reproduce it as you describe it with some debugging added.
How hard would it be to print the filename (or the device/inode) that
triggers the warning?
Not at all (warning: cutpasted patch, tabs are screwed
On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
I ran MAKEDEV all, but the message still appear. The messages I found
about this on the archives says to do a 'ls -l /dev | grep ^b', and
to remake all devices listed, but there's no device listed when I'm
doing the 'ls -l /dev | grep
On Tue, 9 May 2000, Sheldon Hearn wrote:
On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
I ran MAKEDEV all, but the message still appear. The messages I found
about this on the archives says to do a 'ls -l /dev | grep ^b', and
to remake all devices listed, but there's no
I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
when I first launch /stand/sysinstall after the system has start, the
following message appears :
... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
block devices
I searched the list archives and find
On Mon, May 08, 2000 at 03:41:55PM -0500, Erik de Zeeuw wrote:
I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
when I first launch /stand/sysinstall after the system has start, the
following message appears :
... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01
In message [EMAIL PROTECTED], Erik de Zeeuw writes:
I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
when I first launch /stand/sysinstall after the system has start, the
following message appears :
... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid
: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
block devices
I searched the list archives and find some informations about this, but
nothing that helps me understand why I get this message.
Any idea about what could cause this message to come up ?
No, I havn't tracked down
, the
following message appears :
... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
block devices
I searched the list archives and find some informations about this, but
nothing that helps me understand why I get this message.
Any idea about what could cause
:
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all and the message still persists.
I get this message too whenever I mount
I've got an mfs /tmp too :-]
Hi,
On 0, Ted Sikora [EMAIL PROTECTED] wrote:
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all
a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all and the message still persists.
I get this message too whenever I mount a mfs filesystem.
The line in /etc/fstab is:
/dev
The warning mentions the date 2000-06-01. What are you planning to
happen on that date? Whatever it is, please make it tolerant. I
don't care whether I can _use_ the old block devices, but I would
like to be able to ls them, dump them, restore them, etc., without
terrible consequences. (I
In message [EMAIL PROTECTED], John Polstra writes:
The warning mentions the date 2000-06-01. What are you planning to
happen on that date? Whatever it is, please make it tolerant.
My intention is to make the system whine even louder starting around
2000-05-01 and then I lean towards a sysctl
rator 13, 0x00020001 Dec 12 21:09 /dev/da0s1b
crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/rda0s1b
Regards
Dirk
I also get the same warning when I mount /tmp on an MFS filesystem. I
don't get the warning when I pass the "nodev" option to mount.
/etc/fstab:
/dev/da0s2b /t
Warner Losh wrote:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: Almost none. I don't actually mount nfs partitions until I type mount
: foo:/bar /bar. There's no network card active at that time anyway...
:
: But does the nfs filesystems you mount have any bdevs on them ?
, 3077343 free (60807 frags, 377067 blocks, 0.8% fragmentation
)
WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices
net.inet.tcp.slowstart_flightsize: 1 - 3
Doing initial network setup: hostname.
---snip---
and:
---snip---
(24) root@ttyp2# ls -l /dev/ad0s2[abe]
crw-r- 1 root
Warner Losh wrote:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: Almost none. I don't actually mount nfs partitions until I type mount
: foo:/bar /bar. There's no network card active at that time anyway...
:
: But does the nfs filesystems you mount have any bdevs on them
Hi,
On Wed, 19 Apr 2000 12:33:44 +0100
Brian Somers [EMAIL PROTECTED] said:
brian I did the find, removed the bdevs in /compat/linux/dev and rebooted -
brian no luck, the message is still there.
brian thinks
brian I wonder if whatever's done on 2000-06-01 will leave the emulators
brian
Hi,
On 0, Ted Sikora [EMAIL PROTECTED] wrote:
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all and the message still persists.
I get
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all and the message still persists.
Regards,
--
Ted Sikora
Jtl Development Group
[EMAIL
the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all and the message still persists.
Regards,
--
Ted Sikora
Jtl Development Group
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
On Tue, 18 Apr 2000, Ted Sikora wrote:
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all and the message still persists.
ls -l /dev
"Chris D. Faulhaber" wrote:
On Tue, 18 Apr 2000, Ted Sikora wrote:
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a M
In message [EMAIL PROTECTED] Ted Sikora writes:
: Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
: 2000-06-01 to get rid of block devices
: I did a MAKEDEV all and the message still persists.
I get this message when the output of ls -l | egrep ^b is empty.
Warner
On Tue, Apr 18, 2000 at 01:34:11PM -0600, Warner Losh wrote:
I get this message when the output of ls -l | egrep ^b is empty.
\begin{AOL mode}
M To
\end{AOL mode}
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
In message [EMAIL PROTECTED], "David O'Brien" writes:
On Tue, Apr 18, 2000 at 01:34:11PM -0600, Warner Losh wrote:
I get this message when the output of ls -l | egrep ^b is empty.
\begin{AOL mode}
M To
\end{AOL mode}
Hmm, that sounds weird...
At what time does
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: At what time does the message come relative to the mounting of the
: root filesystem ? Before or after ?
I get mine when nfs starts up.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: At what time does the message come relative to the mounting of the
: root filesystem ? Before or after ?
I get mine when nfs starts up.
Any chance you have a bdev on one of the nfs fs's ?
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: In message [EMAIL PROTECTED], Warner Losh writes:
: In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: : At what time does the message come relative to the mounting of the
: : root filesystem ? Before or after ?
:
: I get mine when
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: In message [EMAIL PROTECTED], Warner Losh writes:
: In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: : At what time does the message come relative to the mounting of the
: : root
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: Almost none. I don't actually mount nfs partitions until I type mount
: foo:/bar /bar. There's no network card active at that time anyway...
:
: But does the nfs filesystems you mount have any bdevs on them ?
I've not mounted any
16006410 : OK
start_init: trying /sbin/init
WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices
Linux-ELF exec handler installed
--
Christopher Nielsen
(enkhyl|cnielsen)@pobox.com
Enkhyl on IRC
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
On Tue, 18 Apr 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Ted Sikora writes:
: Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
: 2000-06-01 to get rid of block devices
: I did a MAKEDEV all and the message still persists.
I get this message when the output
On Mon, 24 Jan 2000, Lars Eggert wrote:
Ilya,
thanks for the quick response.
Signals and Perl do not mix. Please do not use signals if a segfault
is not a desirable form of output.
Never? After reading perlipc I was under the impression that using signals
was okay if you keep your
On Tue, Jan 25, 2000 at 02:44:05PM -0500, Chuck Robey wrote:
On Mon, 24 Jan 2000, Lars Eggert wrote:
Ilya,
thanks for the quick response.
Signals and Perl do not mix. Please do not use signals if a segfault
is not a desirable form of output.
Never? After reading perlipc I
On Tue, 25 Jan 2000, Ilya Zakharevich wrote:
On Tue, Jan 25, 2000 at 02:44:05PM -0500, Chuck Robey wrote:
On Mon, 24 Jan 2000, Lars Eggert wrote:
Ilya,
thanks for the quick response.
Signals and Perl do not mix. Please do not use signals if a segfault
is not a
e a chunk to a random position
@data[$pos..$pos+CHUNK_SIZE] = (1) x CHUNK_SIZE;
}
}
Execution of this script results in the following output:
[sub: ~/thesis/bin] short
......perl in malloc(): warning: recursive call.
Out of memory!
perl in malloc(): warning: recursive cal
Lars Eggert writes:
Running the following test script causes perl to crash. You may need
to run the script several times before seeing the problem. (The script
spawns a child process that does nothing but write to an array. The
parent signals the child periodically.)
Signals and Perl do not
Ilya,
thanks for the quick response.
Signals and Perl do not mix. Please do not use signals if a segfault
is not a desirable form of output.
Never? After reading perlipc I was under the impression that using signals
was okay if you keep your handlers simple. I may have to use to another
On Mon, Jan 24, 2000 at 09:53:27PM -0800, Lars Eggert wrote:
Signals and Perl do not mix. Please do not use signals if a segfault
is not a desirable form of output.
Never?
Never. Well, I did not try XSUB signal handlers, but if it is a Perl
subroutine, then the harm may be already done
401 - 500 of 516 matches
Mail list logo
