On Tuesday 14 March 2006 15:27, Martin wrote:
David Xu wrote:
Can anyone add this to 6.1 todo list ? this definitely should be fixed
before
6.1R.
One of my friends also has found kern/94278:
http://www.freebsd.org/cgi/query-pr.cgi?pr=94278
There is no comment on it so far. This
Hello!
I won't reply to the overcommit part of your letter, since my concern
is rather local: I'm just not sure whether FreeBSD does it's best
during the DoS-attack in swapless environment.
On Mon, 13 Mar 2006, Jon Dama wrote:
Also, when the system is page-starved it kills the largest
On Mon, Mar 13, 2006 at 11:48:06AM -0800, Jon Dama wrote:
If you feel this situation is undesirable, the first thing to do is to put
together the patches necessary to allow the kernel to actually track how
much ram+swap might be needed to cover the address-space allocations
that have been
Eric Anderson wrote:
I get the above panic after nfs clients attach to this nfs server and
being read/write ops on it after an unclean shutdown. I've fsck'ed the
fs, and it marks it as clean, but I get this every time. It's an NFS
share of a GEOM stripe (about 2TB).
mode = 0100600, inum =
I have seen a lot of Thinkpad recommendations and I'd like to give you a
warning here. I'm owning an R40 and it works well driver-wise. But the
USB- and PCMCIA-controller have broken 3 times and the mainboard has
been replaced twice because of this. Now I am out of warranty and a
replacement board
On Tuesday 14 March 2006 05:37, Andrew Reilly wrote:
When I bumped into this error (I usually mergemaster after installworld,
in contravention of the UPDATING recommendation,) I went to run
Note that mergemaster should be ran twice during an upgrade; first as
'mergemaster -p' (pre-build
On Mon, Mar 13, 2006 at 09:32:24AM -0600, Alan Amesbury wrote:
Jorge Aldana wrote:
I'm on 6.1PreRelease and this works:
strings -n 3 /boot/kernel/kernel | grep -v | sed -n 's/^___//p'
There was a minor tweek in this line back in 5.X transition form 4.X but
my script works fine for
On Tue, Mar 14, 2006 at 04:41:32PM +0800, David Xu wrote:
On Tuesday 14 March 2006 15:27, Martin wrote:
David Xu wrote:
Can anyone add this to 6.1 todo list ? this definitely should be fixed
before
6.1R.
One of my friends also has found kern/94278:
I have an MSI K8D Master, wth an Opteron 242 installed, on which I have been
happily running 6.0-RELEASE. I did have one problem wuth the board, which was
that if I had ACPI enabled then the operating system would not boot, it froze
at the point where it waited for the SCSI devices to settle. I
Sorry for garbled patch. I do not know why mutt decided to encode
some = as =3D.
Index: compat/linux/linux_misc.c
===
RCS file: /usr/local/arch/ncvs/src/sys/compat/linux/linux_misc.c,v
retrieving revision 1.172
diff -u -r1.172
On Tuesday 14 March 2006 21:02, Kostik Belousov wrote:
Sorry for garbled patch. I do not know why mutt decided to encode
some = as =3D.
Index: compat/linux/linux_misc.c
===
RCS file:
Mike Tancsa wrote:
At 04:48 PM 13/03/2006, Eric Anderson wrote:
I get the above panic after nfs clients attach to this nfs server and
being
I do have dumps from two crashes so far.
This is FreeBSD-6.1-PRERELEASE from Friday-ish.
Dont know if it was fixed or not, but there were a lot of VM
On Tue, Mar 14, 2006 at 09:17:49PM +0800, David Xu wrote:
I know, someone will work out such a messy patch, but is it reasonable ?
why does not the fifi code suddenly work with well defined vnode interface ?
why did someone want to break the well defined FILE-vnode-fs-device
layers ? sigh.
Nikolas Britton [EMAIL PROTECTED] wrote:
M. Warner Losh [EMAIL PROTECTED] wrote:
I think we're going to see another BETA (BETA4) shortly. The hold up
is that there's still enough problems that need to be fixed that the
release isn't near enough to do the branch. [...]
Thanks for
On Mar 14, 2006, at 7:41 AM, Pete French wrote:
But FreeBSD will not boot SMP with the second processor installed.
It behaves
exactly as it did with a single processor and ACPI enabled - i.e.
it stops
at the 'Waiting for SCSI devices to settle point and does not get
beyond
this.
when
when you boot, at the FreeBSD menu, break to the command prompt and
type this:
debug.acpi.disabled=timer
boot
O.K., I will give this a try - that might fix theoriginal problem
with ACPI booting too I guess ?
Cant try this for a few hours though as the machine is remote,
thanks for the
TB --- 2006-03-14 15:04:30 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2006-03-14 15:04:30 - starting RELENG_6 tinderbox run for sparc64/sparc64
TB --- 2006-03-14 15:04:30 - cleaning the object tree
TB --- 2006-03-14 15:04:52 - checking out the source tree
TB --- 2006-03-14
Hi,
I'll be getting a few new machines for a customer soon.
They will be SMP (dual processor Pentium-IV) with 4 GB RAM,
and I plan to install FreeBSD/i386 6-stable on them.
What's the current status of running with that amount of
memory? I'm not completely up to date in that regard, and
Oliver Fromme wrote:
Hi,
I'll be getting a few new machines for a customer soon.
They will be SMP (dual processor Pentium-IV) with 4 GB RAM,
and I plan to install FreeBSD/i386 6-stable on them.
What's the current status of running with that amount of
memory? I'm not completely up to date in
Eric Anderson wrote:
The base install, running GENERIC will only use 3GB.
:[ ]. Why so?! How make FreeBSD to use 4GB? it is possible?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
Ivan Kolosovskiy wrote:
Eric Anderson wrote:
The base install, running GENERIC will only use 3GB.
:[ ]. Why so?! How make FreeBSD to use 4GB? it is possible?
Sure, as the rest of my email said. man pae
Eric
--
Oliver Fromme said the following on 03/14/06 08:30:
Will FreeBSD/i386 6-stable run on a 4 GB machine out of the
box? Do I have to apply special tuning (kernel config or
sysctl or whatever)? Using PAE shouldn't be necessary, I
assume.
All it depends is what size of memory address space the
That would mean that ipw is broken. I never had such problems when I was
using 5-stable with ipw from the ports.
Kris Kennaway wrote:
On Tue, Mar 14, 2006 at 10:13:31AM +0100, [LoN]Kamikaze wrote:
When using cvsup to update my sources over a wireless connection I often
get the error message:
On Tue, Mar 14, 2006 at 07:37:56PM +0100, [LoN]Kamikaze wrote:
That would mean that ipw is broken. I never had such problems when I was
using 5-stable with ipw from the ports.
OK.
Kris
pgpWcFJk4Mbcn.pgp
Description: PGP signature
Hi,
I'm starting to deploy 6.0-STABLE (from mid january) to progressively
replace all the 4.9 servers we have here and I'm seeing a curious thing :
On all 6.0 which get moderate to high network activity (ie webmail to inn),
I see that the 'calls to protocol drain routines' statistic given by
On Mar 13, 2006, at 2:31 PM, Chuck Swiger wrote:
Alban wrote:
For some reason I'm getting more or less random segfaults compiling
kernels, world or PHP5 on BETA-3 (Python and perl went ok). So far I
haven't succeeded building a fresh kernel or world. This system is an
Athlon XP with 1MB RAM
debug.acpi.disabled=timer
and see if it works. I have one system on which 5.4 works
flawlessly, but anything from 6.0-REL and up requires I disable the
ACPI timer.
Thanks - that does make it work with ACPI enabled, which is good. It
still won't boot SMP however - and despite the fcat it
Can anyone tell me if/when the Adaptec AIC9410 SAS/SATA controller
will be supported?
Michael Grant
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
In 4.x, I can make sshd not log this noise by using the Deny/Allow
Users/Groups options. In 6.x, the same configuration doesn't stop the
logging, so my logs get overrun with thousands of Failed password for
invalid user messages. What do I need to do to make sshd not log this
information?
Hello folks,
A while back (January) I posted to the list about a problem I had
booting 6.0-STABLE built with sources after about November 2005 on my
workstation.
Since that point, and including (I have now discovered) 6.1-PRERELEASE
(as my freshly built kernel identified itself just now), I
Just booted from a 6.1BETA4 CD and it does not recognize the Adaptec 1200A
raid card. Is there a work around for this?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
Henri Hennebert writes:
| Glenn Dawson wrote:
| At 12:06 PM 3/8/2006, you wrote:
| Does anyone know how to change the release version of the source
| code? I have some brain dead software (Plesk) that insists on
| FreeBSD 5.3, while it will work just fine on 5.5 and even 6. I am
|
Michael Grant wrote:
Can anyone tell me if/when the Adaptec AIC9410 SAS/SATA controller
will be supported?
Michael Grant
It's on my TODO list, but realistically I won't even be able to think
about starting it until this summer at the earliest. The MPT driver
has prototype support for SAS
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
availability of FreeBSD 6.1-BETA4 and FreeBSD 5.5-BETA4. Both FreeBSD
6.1 and FreeBSD 5.5 are meant to be a refinement of their respective
branches with few dramatic changes. A lot of bugfixes have been
Sorry, I accidentally sent out an incomplete draft. This announcement
is for BETA4, of course. Also, the note about VFS changes below should
stress that the changes were made for stability, not performance. Sorry
for the confusion.
Scott Long wrote:
Announcement
The FreeBSD
I just bought a Supermicro X6DH3-G2 with some Maxtor 500gig SATA
drives. The box sees the SATA drives in the bios but of course not in
Freebsd.
Do you think I can use the MPT driver from 7-current and use in
6-stable with these SATA drives?
Michael
On 3/15/06, Scott Long [EMAIL PROTECTED]
Sorry, I should have been more specific. The MPT driver has prototype
support for SAS enabled LSI Logic chips.
Scott
Michael Grant wrote:
I just bought a Supermicro X6DH3-G2 with some Maxtor 500gig SATA
drives. The box sees the SATA drives in the bios but of course not in
Freebsd.
Do you
Yesterday's kernel appears to be broken, in as much as my g_mirror
enabled machine boots, but g_mirror doesn't start mirroring!
This is after a crash; the machine reboots, kernel comes up, and
then instead of g_mirror starting to recover the degraded mirror
pair, nothing happens, and fsck sits
38 matches
Mail list logo
