On 10/31/05, Scott Long <[EMAIL PROTECTED]> wrote:
> The future direction is that FreeBSD will continue to be friendly to
> novice users while still affording power users the control that they
> seek. This feature is not going to be a dumping ground of dubious
> and secret options that are impossi
Hi!
On Tue, Nov 01, 2005 at 06:40:42AM +0600, Max Khon wrote:
> > > Everyone is still welcome to update their sources on the RELENG_6_0
> > > branch and provide feedback for the next 48 hours or so. The release
> > > will likely be announced by the end of the weekend or early next
> > > week
Pete Slagle wrote:
i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that
class. Why was a 5ton hammer used to fix non existing problem?
a small comment like 'you better keep these lines to make X happy'
would have sufficed.
You've clearly never spent much time on the FreeBSD
Hi!
On Mon, Oct 31, 2005 at 04:18:09PM +0100, Marc Olzheim wrote:
> > Everyone is still welcome to update their sources on the RELENG_6_0
> > branch and provide feedback for the next 48 hours or so. The release
> > will likely be announced by the end of the weekend or early next
> > week, at
On Mon, Oct 31, 2005 at 03:46:56PM -0800, Pete Slagle wrote:
> >>i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that
> >>class. Why was a 5ton hammer used to fix non existing problem?
> >>a small comment like 'you better keep these lines to make X happy'
> >>would have sufficed.
On Mon, 31 Oct 2005, Marc Olzheim wrote:
On Thu, Oct 27, 2005 at 12:05:07PM -0600, Scott Long wrote:
Everyone is still welcome to update their sources on the RELENG_6_0
branch and provide feedback for the next 48 hours or so. The release
will likely be announced by the end of the weekend o
i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that
class. Why was a 5ton hammer used to fix non existing problem?
a small comment like 'you better keep these lines to make X happy'
would have sufficed.
You've clearly never spent much time on the FreeBSD support forums,
where
On Tue, Nov 01, 2005 at 09:31:37AM +1000, Joel Hatton wrote:
> > Ah, that's they key. aliases don't work with dhclient at the moment for
> > most interfaces because the interfaces generate bogus link events when
> > aliases are modified. We hope to fix this, but it's going to take some
> > time.
>
> Ah, that's they key. aliases don't work with dhclient at the moment for
> most interfaces because the interfaces generate bogus link events when
> aliases are modified. We hope to fix this, but it's going to take some
> time.
Ok - thanks. I'm fortunate at the moment that I've stopped using the
From: Scott <[EMAIL PROTECTED]>
Subject: Re: HEADS UP! 6.0-RELEASE coming
Date: Mon, 31 Oct 2005 12:48:49 -0700 (MST)
> On Mon, 31 Oct 2005, Warner Losh wrote:
> > From: Scott Long <[EMAIL PROTECTED]>
> > Subject: Re: HEADS UP! 6.0-RELEASE coming
> > Date: Mon, 31 Oct 2005 10:42:32 -0700
> >
> >>
On Mon, 31 Oct 2005, Warner Losh wrote:
From: Scott Long <[EMAIL PROTECTED]>
Subject: Re: HEADS UP! 6.0-RELEASE coming
Date: Mon, 31 Oct 2005 10:42:32 -0700
Warner Losh wrote:
The ACPI+sio problem is known. I have a motherboard with a similar
problem, though a different brand than yours. I s
On Mon, Oct 31, 2005 at 10:50:38AM +1000, Joel Hatton wrote:
> I said:
> >
> > DHCP configuration - for some reason my machine didn't acquire a
> > default route on boot, but rerunning the dhclient script after
> > boot caused the interface to be set up again successfully. I
> > ha
Marc Olzheim wrote:
On Mon, Oct 31, 2005 at 08:36:42AM -0700, Scott Long wrote:
Anyone having updates for my showstopper page, please, notify me...
http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html
The pty problem is likely a side effect of known locking problems with
ttys and ptys in
From: Scott Long <[EMAIL PROTECTED]>
Subject: Re: HEADS UP! 6.0-RELEASE coming
Date: Mon, 31 Oct 2005 10:42:32 -0700
> Warner Losh wrote:
> >>>The ACPI+sio problem is known. I have a motherboard with a similar
> >>>problem, though a different brand than yours. I solved it by removing
> >>>the A
Warner Losh wrote:
The ACPI+sio problem is known. I have a motherboard with a similar
problem, though a different brand than yours. I solved it by removing
the ACPI attachment from the sio code. The better solution is to allow
loader hints to override ACPI hints. I tried talking to John Bald
> > The ACPI+sio problem is known. I have a motherboard with a similar
> > problem, though a different brand than yours. I solved it by removing
> > the ACPI attachment from the sio code. The better solution is to allow
> > loader hints to override ACPI hints. I tried talking to John Baldwin
>
On Mon, Oct 31, 2005 at 08:36:42AM -0700, Scott Long wrote:
> >Anyone having updates for my showstopper page, please, notify me...
> >
> >http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html
>
> The pty problem is likely a side effect of known locking problems with
> ttys and ptys in general.
Marc Olzheim wrote:
On Thu, Oct 27, 2005 at 12:05:07PM -0600, Scott Long wrote:
Everyone is still welcome to update their sources on the RELENG_6_0
branch and provide feedback for the next 48 hours or so. The release
will likely be announced by the end of the weekend or early next
week, at the
On Thu, Oct 27, 2005 at 12:05:07PM -0600, Scott Long wrote:
> Everyone is still welcome to update their sources on the RELENG_6_0
> branch and provide feedback for the next 48 hours or so. The release
> will likely be announced by the end of the weekend or early next
> week, at the latest.
An
At 12:01 PM +0200 2005-10-31, Danny Braniss wrote:
> you probably know many scenarios that i - thankfully - am no
> aware of, but by creating the magic DEFAULTS file the problem
> still exits! What will prevent from Joe Shootmyfoot to comment out
> the lines in DEFAULTS?
chflags
> At 11:18 AM +0200 2005-10-31, Danny Braniss wrote:
>
> > you probably know many scenarios that i - thankfully - am no
> > aware of, but by creating the magic DEFAULTS file the problem
> > still exits! What will prevent from Joe Shootmyfoot to comment out
> > the lines in DEFAULTS?
>
>
On Mon, 24 Oct 2005, Scot Hetzel wrote:
On 10/24/05, Neil Hoggarth <[EMAIL PROTECTED]> wrote:
I tried a source-upgrade from RELENG_5 to RELENG_6 over the weekend
(cvsuped RELENG_6 at around 10am Sunday morning, UK time). I was using a
GENERIC kernel. The procedure from UPDATING was working fine
At 11:18 AM +0200 2005-10-31, Danny Braniss wrote:
you probably know many scenarios that i - thankfully - am no
aware of, but by creating the magic DEFAULTS file the problem
still exits! What will prevent from Joe Shootmyfoot to comment out
the lines in DEFAULTS?
chflags schg DEFAU
[...]
> Many users who build custom kernels do not build modules, since they
> want to compile everything they (think they) need into the kernel
> statically.
you probably know many scenarios that i - thankfully - am no
aware of, but by creating the magic DEFAULTS file the problem
still exits! What
On Mon, Oct 31, 2005 at 10:46:37AM +0200, Danny Braniss wrote:
>
> > You've clearly never spent much time on the FreeBSD support forums,
> > where every few days someone posts for help
> >
> > 1) with an error caused by removing one of those "Do not remove this!"
> > lines, and
> >
> > 2) for he
> You've clearly never spent much time on the FreeBSD support forums,
> where every few days someone posts for help
>
> 1) with an error caused by removing one of those "Do not remove this!"
> lines, and
>
> 2) for help on getting X working when they forgot to add /dev/io and
> /dev/mem to their
On Mon, Oct 31, 2005 at 10:12:01AM +0200, Danny Braniss wrote:
> i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that
> class. Why was a 5ton hammer used to fix non existing problem?
> a small comment like 'you better keep these lines to make X happy'
> would have sufficed.
You'
> >> I've seen that 'GENERIC' file has been modified, moving some lines to
> >> 'DEFAULTS':
> >>
> >> device isa
> >>
> >> device mem # Memory and kernel memory devices
> >> device io # I/O device
> >>
> >> Why?
> >> What does it mean? Should
28 matches
Mail list logo
