Dylan Smith wrote:
> Marko Lerota wrote:
>> I see that 6.3 and 7.0 is comming. Now I'm using 6.2-RELEASE for my
>> servers. To what should I upgrade? Which of them will be stable or
>> production release?
>>
>>
>
> Both of them will be production stable at release, i'd say that unless
> you have r
I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor
machine. I kept having a lot of crashes at some point in the install, and I
believe I now have the cuprit: mysql-server-4.1.7 is doing it. Lately, when
mysql-server is running under no load, it caused lockups of the syst
Billy Newsom wrote:
I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor
machine. I kept having a lot of crashes at some point in the install,
and I believe I now have the cuprit: mysql-server-4.1.7 is doing it.
Lately, when mysql-server is running under no load, it
Alex Burke wrote:
Hi,
I wasnt quite sure what to call this problem.
I am running FreeBSD 5.3 STABLE on a quad Pentium Pro IBM Netfinity
7000 system, and since the GENERIC kernel does not come SMP enabled I
compiled a kernel with SMP support and drivers for networks card and
SCSI RAID adapter built
When a SMP machine does not have an AT keyboard controller, there needs
to be a way to reboot the machine under FreeBSD!
I have another system which fails to reboot under FreeBSD. This time it
is a bleeding-edge current system and FreeBSD 6.2-release. From what I
can tell, the code to reboot m
Kris Kennaway wrote:
On Tue, Feb 20, 2007 at 06:21:52PM -0600, Billy Newsom wrote:
When a SMP machine does not have an AT keyboard controller, there needs
to be a way to reboot the machine under FreeBSD!
Like the sysctl that was added in 6.2?
hw.acpi.handle_reboot=1
Kris
Well, what do you
Here's something pretty stupid about either the code in mount, df, or
both. I'm on the verge of a denial of service if this lasts much
longer. When I mount an nfs device more than once, I get this
ridiculous output from df and mount:
#df
Filesystem 1K-blocksUsed Avail Capacity Mounted
Jonathan Noack wrote:
> On 05/09/05 23:14, Billy Newsom wrote:
>
> From the fstab(5) man page:
> "The fourth field, (fs_mntops), describes the mount options associated
> with the file system. It is formatted as a comma separated list of
> options. It contains at least
Jonathan Noack wrote:
>> Anyone tried that sort of stuff in fstab? I'm a little skeptical.
>
> I use "that sort of stuff" and have for a long time. Here's one of my
> fstab lines:
>
> optimator:/usr/home /usr/home nfs rw,-3,-T,-r=32768,-w=32768 0 0
>
> It's obvious you don't believe me but w
Erik Trulsson wrote:
> Note that mount(8) (as well as mount_nfs(8)) says about the -o flag
> that "Options are specified with a -o flag followed by a comma
> separated string of options."
>
> If you try writing it as the manpage says, i.e. like
>
> mount -o -s,-x=2,-T dell:/nfs /dellbak
>
> it shou
Is there some reason why ipnat wouldn't automatically startup?
I just upgraded from a 5-stable in February to a 5-stable in May, so I
could essentially get 5.4 on this firewall machine. I simultaneously
was upgrading some ports, etc., but nothing too severe. When I rebooted
the machine, ever
comments in it, because a lot of the generic kernel fluff has
been removed for sake of speed.
I removed them with:
cat mykernel | sed -e 's;#.*;;' -e '/^[ ]*$/d' >mykernel.1
Billy
~>-----Original Message-
~>From: [EMAIL PROTECTED]
~>[mailto:[EMAIL PROTECTED]
Billy Newsom wrote:
Okay, I'm going to dig up someone who might be responsible or might be
able to fix it. Two strikes while doing the same upgrade... While I'm
thinking about it, would you see if it happens on the next reboot? I
haven't tried, because my system is a firewall
I posted previously that ipnat failed to start after I upgraded to
FreeBSD 5.4. On the same machine, I am having additional ipnat failures.
I reported the first time that ipnat failed to start on the first boot.
I am now reporting that on the second boot, ipnat loaded and installed
its tables
Steve Roome wrote:
> We're using mostly:
>
> 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Jun 6 12:22:18 BST 2005
>
> This is on a Dell PowerEdge 2850. (2 * 2.8 GHz Xeons, 4GB ram, disks),
> we've been keeping up with stable because supposedly all these new
> fixes to threading will help us out here.
>
Colin Percival wrote:
> It sounds like the SMP kernel I provided for FreeBSD 5.3 was quite
> popular, so I've started building an SMP kernel for FreeBSD 5.4 as
> well, in addition to the usual GENERIC kernel. To take advantage
I'm curious how popular. Would you like to report some statistics h
Here's a neat little script you can run from cron or commandline. I use
it to update the ports tree and the source tree for 5-STABLE. Feel free
to change the cvsup logging to suit (I don't log the ports, but I do log
important STABLE src stuff). Also, use the correct country for mirrors.
Yo
Does anyone have FreeBSD 5.3 installed (preferably a version compiled
before March 2005) and you can help? I am still trying to help diagnose
a problem I have in which something may be started before something
else. In my case, ipnat. When I upgraded to 5.4 (or a late 5-stable),
I started ha
Hans Lambermont wrote:
Billy Newsom wrote:
Does anyone have FreeBSD 5.3 installed (preferably a version compiled
before March 2005)
FreeBSD 5.3-RELEASE #3: Sun Dec 19 14:54:18 CET 2004
What is the output for this command under FreeBSD 5.3?
sh -c "cd /etc/rc.d ; rcorder -s nostar
Is there a sysctl variable, or a quick method to determine if ipv6 is
enabled in the kernel? e.g. How do I test for the prescence of ipv6 in
a script or at the commandline?
Thanks,
Billy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebs
I am wondering if I should file a PR on /sbin/rcorder dumping core?
This is a reproducible core dump. I am using FreeBSD 5-Stable dated
July 2, I think. SMP, i386, custom kernel.
First, try this. Make a file that looks like this:
#!/bin/sh
#
# PROVIDE: hello_world
# REQUIRE: hello_world
No
Does anyone know exactly what to do about an interrupt storm, or if it
really is a problem? I have an old system acting as a router/firewall.
It is a dual processor, so I use SMP. But since going to 5.3 and 5.4, it
would seem that this system runs a bit worse than under 4.7. It could be
based o
I have a usable kernel that I built from 5-Stable sources on July 4th,
2005. But the last two days, I tried to compile and install the lastest
5-Stable, and neither one would boot.
During the boot, the entire normal dmesg is output (the part which is in
"bold" on the CRT), except the last line
Okay, Tim, I just reported the same bug in a previous post. So did
Julian C. Dunn. I think this is an issue with some recent code changes
in CVS...
See these threads:
critical BOOT failure updating to latest 5-Stable (5.4)
9/23/2005 12:07 AM
ATA lockup with 5.4-STABLE
9/21/2005 10:19 PM
I ha
Michael L. Squires wrote:
This may be a similar problem to the one discussed in the Intel ICH2
thread.
System is a Toshiba 8100. System boots from a 5.4-STABLE kernel
compiled 5/3/2005 but locks up on boot with kernels compiled in the past
few days.
I re-cvsup'd after the first lockup and
Tim Howe wrote:
Tim Howe <[EMAIL PROTECTED]> writes:
ata0-master: stat=0xd0 err=0xd0 lsb=0xd0 msb=0xd0
This turned out to be the key.
Version 1.51 of ata-lowlevel.c added a check for stat0/1, err, lsb, and
msb being identical. If they are, it aborts the probe. The attached
patch creates
Tim Howe wrote:
Tim Howe <[EMAIL PROTECTED]> writes:
ata0-master: stat=0xd0 err=0xd0 lsb=0xd0 msb=0xd0
This turned out to be the key.
Version 1.51 of ata-lowlevel.c added a check for stat0/1, err, lsb, and
I am just wondering about this. As far as I can tell, I have the
ata-lowlevel.c f
See my posts and others on these topics:
critical BOOT failure updating to latest 5-Stable (5.4)
5.3 -> 5.4 breaks ATA (Intel ICH2)
[PATCH] option to re-enable aggressive ATA probing
Those are from September 2005, when I and others started having problems
with the latest (poor) edits to the 5
28 matches
Mail list logo
