>> i386 running 7.2 as of aug 29
>> twe, gmirrored boot partition, zfs universe
>> cvsupped 24 hours ago
>> new kernel world
>> will not boot. get beastie but stops at first twirly
>>
>> can boot old kernel -s, but not new kernel
>>
>> can not use old kernel with new world, hangs if i try to /et
Kevin Oberman wrote:
I just noticed that my dhclient.conf file seems to be ignored in
8.0. Worked fine in 7.2.
interface "ath0" {
send host-name "slan.XXX.YYY";
prepend domain-name "XXX.YYY ";
append domain-name-servers 198.128.W.ZZ;
}
Your interface is wrong, it should be wlanX not a
> Date: Mon, 19 Oct 2009 19:49:33 +
> From: Tom Judge
>
> Kevin Oberman wrote:
> > I just noticed that my dhclient.conf file seems to be ignored in
> > 8.0. Worked fine in 7.2.
> >
> > interface "ath0" {
> > send host-name "slan.XXX.YYY";
> > prepend domain-name "XXX.YYY ";
> > append d
I just noticed that my dhclient.conf file seems to be ignored in
8.0. Worked fine in 7.2.
interface "ath0" {
send host-name "slan.XXX.YYY";
prepend domain-name "XXX.YYY ";
append domain-name-servers 198.128.W.ZZ;
}
When I look at /etc/resolv.conf, neither the domain-name is added nor te
dns
On Sunday 18 October 2009 7:16:41 pm jhell wrote:
>
> I have just been setting up a release cycle for making some iso's of my
> own for a modified revision of the source that I am going to be using for
> offline use and run into a repetitive copy that I am hoping someone could
> shed some light
On Fri, 2009-10-16 at 21:13 -0400, Randy Bush wrote:
> i386 running 7.2 as of aug 29
> twe, gmirrored boot partition, zfs universe
> cvsupped 24 hours ago
> new kernel world
> will not boot. get beastie but stops at first twirly
>
> can boot old kernel -s, but not new kernel
>
> can not use old
Ivan Voras wrote:
Another data point - the OS in the VM in question hanged today sometime
after 5 AM in the following way:
* console nonresponsive (also to ctrl-alt-del)
* ssh login nonresponsive (timeout)
* ping works (!)
Judging by the last seen timestamp, the machine should hav
On Fri, 2 Oct 2009, kama wrote:
> > > Do you get this message in all cases? That is, every time you tried?
> > > Or only with ACPI_DEBUG defined?
> >
> > I cant recall. I have tried so many things lately. But I believe I get it
> > on a verbose boot without ACPI_DEBUG.
> >
> > Im currently rebui