On Wed, 3 Dec 2003, Eric Anderson wrote:
...
> > Well, there are so many kinds of PERC cards. Some are just Mylex cards.
> >Others are MegaRAID. I think they use some Adaptec now.
> >
> My troubles were with the MegaRAID variant, I'm not sure about the others..
>
> > Either way, I tried booti
On Wed, 3 Dec 2003, Tom wrote:
>
> On Tue, 2 Dec 2003, Eric Anderson wrote:
>
> > Tom wrote:
> >
> > > Just to be complete, there are already a whole bunch of machines that
> > >will not boot 5.x, irregardless of the ACPI issues. I've never been able
> > >to boot 5.x with ACPI on or off, on any
Tom wrote:
On Tue, 2 Dec 2003, Eric Anderson wrote:
Tom wrote:
Just to be complete, there are already a whole bunch of machines that
will not boot 5.x, irregardless of the ACPI issues. I've never been able
to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350
servers I ha
On Tue, 2 Dec 2003, Eric Anderson wrote:
> Tom wrote:
>
> > Just to be complete, there are already a whole bunch of machines that
> >will not boot 5.x, irregardless of the ACPI issues. I've never been able
> >to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350
> >servers I have
:> This argument is exactly why I added the 'disable acpi' option in the boot
:> loader menu. Of course, we STILL need to get good debugging information
:> from you as to why you get a Trap 9 when ACPI is disabled. This is the
:> more important issue.
:
:This is actually a known issue on Intel m
Tom wrote:
Just to be complete, there are already a whole bunch of machines that
will not boot 5.x, irregardless of the ACPI issues. I've never been able
to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350
servers I have here, even though they run 4.9 perfectly. I have a PR ope
On Mon, 1 Dec 2003, Scott Long wrote:
> On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote:
> > On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
...
> >
> > I'm currently investigating ACPI problems on a dual processor Intel
> > motherboard (re@ knows about this). It looks as if th
On 02-Dec-2003 Scott Long wrote:
> On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote:
>> On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
>> > This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
>> >
>> > Show stopper defects for 5.2-RELEASE
>> >
>> > +-
On Monday, 1 December 2003 at 17:12:23 -0700, Scott Long wrote:
> On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote:
>> On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
>>> This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
>>>
>>> Show stopper defects for 5
On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote:
> On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
> > This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
> >
> > Show stopper defects for 5.2-RELEASE
> >
> > +---
On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
> This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
>
> Show stopper defects for 5.2-RELEASE
>
> ++
> | Issue | Status |Re
On Mon, 1 Dec 2003 10:01:23 -0500 (EST)
Robert Watson <[EMAIL PROTECTED]> wrote:
> This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues
> list. The live version of this list is available at:
>
> http://www.FreeBSD.org/releases/5.2R/todo.html
>
> Automated mailing of this lis
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
[NOTE: This is being resent due to a cvs update error that caused
an un-updated version of the TODO list to be sent out earlier]
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R
Sigh. Try three to follow. My script was checking out only the www tree,
and the checkout of the doc tree it depended on was gradually getting
stale. At some point, it picked up a new dependency in the doc tree and
the build broke. Hopefully third time will be the charm.
Robert N M Watson
[NOTE: This is being resent due to a cvs update error that caused
an un-updated version of the TODO list to be sent out earlier]
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
On Wed, Oct 29, 2003 at 10:00:22AM -0500, Robert Watson wrote:
> This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
> The live version of this list is available at:
>
> Desired features for 5.2-RELEASE
>
> +-
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
On Wed, 15 Oct 2003, Robert Watson wrote:
> Open Issues
>
> This is a list of open issues that need to be resolved for FreeBSD 5.2. If
> you have any updates for this list, please e-mail [EMAIL PROTECTED]
>
> |-+---+-
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
On Wed, Oct 01, 2003 at 10:00:18AM -0400, Robert Watson wrote:
> FreeBSD 5.2 Open Issues
> This is a list of open issues that need to be resolved for FreeBSD 5.2. If
> you have any updates for this list, please e-mail [EMAIL PROTECTED]
>
> Must Resolve Issues for 5.2-RE
Dan Nelson wrote:
> In the last episode (Sep 29), Wilko Bulte said:
> > On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote:
> > > I also mentioned recently (in the last couple of days) that we
> > > should worry more about sparc64 than alpha. Simply because I think
> > > alpha is on i
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
In message <[EMAIL PROTECTED]>, Dan Nelson writes:
>> In my book sparc64 is also with one foot in the grave. As is Sun
>> itself.
>
>Fujitsu makes sparc-compatible CPUs, too, so it'll be harder to kill
>the entire architecture like HP did with the Alpha.
Having at least on architecture with the o
In the last episode (Sep 29), Wilko Bulte said:
> On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote:
> > I also mentioned recently (in the last couple of days) that we
> > should worry more about sparc64 than alpha. Simply because I think
> > alpha is on it's way down and should alre
On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote:
> On Mon, Sep 29, 2003 at 08:07:32PM +0200, Wilko Bulte wrote:
> > >
> > > You should probably remove Marcel from this item. This task needs
> > > another volunteer.
> >
> > Recently Marcel noted to me he was planning to engage on
On Mon, Sep 29, 2003 at 08:07:32PM +0200, Wilko Bulte wrote:
> >
> > You should probably remove Marcel from this item. This task needs
> > another volunteer.
>
> Recently Marcel noted to me he was planning to engage on this one. I have
> offered him help for testing.
The deal is this (if you fi
On Mon, 29 Sep 2003, Wilko Bulte wrote:
> On Mon, Sep 29, 2003 at 02:05:16PM -0400, Daniel Eischen wrote:
> > On Mon, 29 Sep 2003, Robert Watson wrote:
> >
> > > |-+---+-+|
> > > | | |
On Mon, Sep 29, 2003 at 02:05:16PM -0400, Daniel Eischen wrote:
> On Mon, 29 Sep 2003, Robert Watson wrote:
>
> > |-+---+-+|
> > | | | | Userland bits |
> > | |
On Mon, 29 Sep 2003, Robert Watson wrote:
> |-+---+-+|
> | | | | Userland bits |
> | | | | implemented, |
> | KSE support for
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
On Wed, Sep 03, 2003 at 08:27:17PM -0700, Peter Wemm wrote:
> > Sorry, I missed this when I did my scrub yesterday. I'll fix it now.
> > Btw, does X work on it? Can I compile/install it without hassle?
>
> Yes. It installs Just Fine. You wont even notice the difference relative
> to an i386 ma
Scott Long wrote:
> David O'Brien wrote:
> > On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote:
> >
> >> |-+---+-+|
> >> | | | | Productionable |
> >> |
Scott Long wrote:
Btw, does X work on it? Can I compile/install it without hassle?
I've tried. "portinstall XFree86-Server" succeeded with no error.
But "XFree86 -configure" dumps core and exits abnormally.
In /var/log/messages:
kernel: pid 23797 (XFree86), uid 0: exited on signal 6 (core dumped
Scott Long wrote:
Doug Barton wrote:
On Mon, 1 Sep 2003, Nicole wrote:
In my 5.1 system I see this in my .hints file. So I assume I edit it
there or do I treat it like a defaults file and import and change in
in my config file?
I didn't say anything about your hints file. You need to edit your
Doug Barton wrote:
On Mon, 1 Sep 2003, Nicole wrote:
In my 5.1 system I see this in my .hints file. So I assume I edit it
there or do I treat it like a defaults file and import and change in
in my config file?
I didn't say anything about your hints file. You need to edit your
kernel config file,
On Mon, 1 Sep 2003, Nicole wrote:
> Sorry I didn't mean to be so "testy" I guess would discribe it. It's
> an old issue for me.
Not to put too fine a point on it, but I've seen numerous posts from
you, on several topics, all of them berating people for not giving you
what you want, when you want
On 02-Sep-03 Unnamed Administration sources reported Doug Barton said :
> On Mon, 1 Sep 2003, Nicole wrote:
>
>> It just drives me crazy when important things get broken and people
>> act like.. What the big deal. I don't need it why should you?
>
> You're certainly free to draw that conclusio
On Mon, 1 Sep 2003, Nicole wrote:
> It just drives me crazy when important things get broken and people
> act like.. What the big deal. I don't need it why should you?
You're certainly free to draw that conclusion, however you'd be
mistaken. There are times when adding new features means that t
On Mon, 1 Sep 2003, Scott Long wrote:
> Device flags are not specified in the kernel config anymore unless you
> try really, really hard. /etc/device.hints is the correct place to
> adjust this flag.
Yeah, I was looking at the kernel config on the wrong box. This flag did
used to be in GENERIC,
BTW - I do thank you Marc for your advice. I know you were trying to assist.
It just drives me crazy when important things get broken and people act like..
What the big deal. I don't need it why should you?
I still have not solved the going to comsonsole mode if there is no keyboard
detecte
On 01-Sep-03 Unnamed Administration sources reported Marc G. Fournier said :
>
>
> On Mon, 1 Sep 2003, Nicole wrote:
>
>>
>> So are you saying it Will work in single user mode perhaps? (drives in use)
>>
>> or are you saying gee we have this nice new version that if you need to
>> modify any
So are you saying it Will work in single user mode perhaps? (drives in use)
or are you saying gee we have this nice new version that if you need to modify
any disk slice you did after an install your screwed into going back to caveman
tools (which I admit I have NO IDEA how to use and I bet ma
In message <[EMAIL PROTECTED]>, Nicole writes:
>
> Is anyone going to be fixing the sysinstall problem of not being able to
>re-slice a drive? For those who are not technical whizes this IS a big problem.
>We do still care about them right?
If you are talking about using sysinstall to modify d
Is anyone going to be fixing the sysinstall problem of not being able to
re-slice a drive? For those who are not technical whizes this IS a big problem.
We do still care about them right?
Nicole
|\ __ /| (`\
| o_o |__ ) )
David O'Brien wrote:
On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote:
|-+---+-+|
| | | | Productionable |
| | | | support fo
David O'Brien wrote:
On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote:
|-+---+-+|
| | | | Productionable |
| | | | support fo
On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote:
> |-+---+-+|
> | | | | Productionable |
> | | | | support for the|
>
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
On Fri, 29 Aug 2003, Robert Watson wrote:
> |-+---+-+|
> | | | | Unsupported in |
> | | | | 5.1-RELEASE; |
> | KSE support for
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
On Mon, 30 Jun 2003, Tim Robbins wrote:
> This has already been fixed.
Great, I'll update the list, thanks!
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
___
[EMAIL PROTE
David Taylor wrote this message on Sun, Jun 29, 2003 at 17:04 +0100:
> Although it fits into an 80-column display in vim/cat/whatever, mutt ends
> up wrapping it, and making it very ugly, but removing a couple of the
> spaces would make it fit fine.
Reconfigure your mutt. It works fine over here
On Sun, 29 Jun 2003, David Taylor wrote:
> I don't suppose it would be possible to delete a couple of those leading
> spaces on each line?
>
Bah, ignore me, after deciding it was mutt's fault for wrapping it when it
shouldn't be, I found the 'wrapmargin' setting in my muttrc file...
Reducing that
On Sun, 29 Jun 2003, David Taylor wrote:
> On Sun, 29 Jun 2003, Robert Watson wrote:
> > ++
> > |Issue| Status | Responsible | Description |
> > |-+--+---
On Sun, 29 Jun 2003, Robert Watson wrote:
> ++
> |Issue| Status | Responsible | Description |
> |-+--+-+-|
^^^
I don't suppos
On Sun, Jun 29, 2003 at 10:00:15AM -0400, Robert Watson wrote:
>|+---++---| |
>|| || Kris Kennaway | |
>|| || reports |
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2
On Tue, Jun 03, 2003 at 05:32:35PM +0900, SUZUKI Shinsuke wrote:
> I discussed this issued within KAME.
>
> Here's our rough plan about this synchronization.
>
> If you have some opinion, please let me know.
> When I've finished each merge, I'll ask you how to proceed.
>
>
> - sync per feature;
> On Sun, 1 Jun 2003 10:00:14 -0400 (EDT)
> [EMAIL PROTECTED](Robert Watson) said:
>| | | | The FreeBSD KAME|
>| | | | IPv6 code is now|
>| | |
On Mon, 2 Jun 2003, Daniel C. Sobral wrote:
> Actually, I would think it a desirable feature mac support that won't
> panic within 24 hours. :-)
>
> I've given up on mac again. Can't have it if it panics on every daily.
> :-( What's the plans for dealing with that?
Right now I'm aware of one
Actually, I would think it a desirable feature mac support that won't
panic within 24 hours. :-)
I've given up on mac again. Can't have it if it panics on every daily.
:-( What's the plans for dealing with that?
Robert Watson wrote:
This is an automated bi-weekly mailing of the FreeBSD 5.2 open
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2
On Thu, May 29, 2003 at 10:00:13AM -0400, Robert Watson wrote:
>|-+--+-+-|
>| | | | Almost all process |
>| | | | debugging tools
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2
75 matches
Mail list logo
