On 10/25/2010 5:53 PM, Garrett Cooper wrote:
On Mon, Oct 25, 2010 at 2:15 PM, Doug Barton wrote:
On 10/25/2010 13:33, Ivan Voras wrote:
(except if the message is changed to say "please look at the kernel
syslog messages to find out the real reason for this failure")
Thinking about Garrett's
On Mon, Oct 25, 2010 at 6:06 PM, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 10/25/10 14:15, Doug Barton wrote:
>> On 10/25/2010 13:33, Ivan Voras wrote:
>>> (except if the message is changed to say "please look at the kernel
>>> syslog messages to find out the real re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/25/10 14:15, Doug Barton wrote:
> On 10/25/2010 13:33, Ivan Voras wrote:
>> (except if the message is changed to say "please look at the kernel
>> syslog messages to find out the real reason for this failure")
>
> Thinking about Garrett's resp
On Mon, Oct 25, 2010 at 2:15 PM, Doug Barton wrote:
> On 10/25/2010 13:33, Ivan Voras wrote:
>>
>> (except if the message is changed to say "please look at the kernel
>> syslog messages to find out the real reason for this failure")
>
> Thinking about Garrett's response as well, this may be the be
On Mon, Oct 25, 2010 at 5:42 PM, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> Here is a patch that makes top(1) to inverse its table header (PID
> USERNAME THR, etc).
Huh? I'm not quite sure what are you trying to achieve; a before and
after snapshot would help.
T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Here is a patch that makes top(1) to inverse its table header (PID
USERNAME THR, etc).
Cheers,
- --
Xin LI http://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16
On 10/25/2010 13:33, Ivan Voras wrote:
(except if the message is changed to say "please look at the kernel
syslog messages to find out the real reason for this failure")
Thinking about Garrett's response as well, this may be the best way to
go. At this point I'm also not concerned about waitin
On 10/25/10 22:13, Garrett Cooper wrote:
On Mon, Oct 25, 2010 at 12:26 PM, Doug Barton wrote:
On 10/25/2010 12:19, Xin LI wrote:
Here is a simple patch that adds more meaning messages when kldload hits
ENOEXEC.
+1 on anything that makes this (and related) error more clear. I know I've
stumb
On 10/25/10, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> Here is a simple patch that adds more meaning messages when kldload hits
> ENOEXEC.
>
> Before patch:
>
> kldload: can't load geom_eli.ko: Exec format error
>
> After patch:
>
> kldload: can't load geom_eli.
On Mon, Oct 25, 2010 at 12:26 PM, Doug Barton wrote:
> On 10/25/2010 12:19, Xin LI wrote:
>>
>> Here is a simple patch that adds more meaning messages when kldload hits
>> ENOEXEC.
>
> +1 on anything that makes this (and related) error more clear. I know I've
> stumbled over it numerous times.
On 10/25/2010 12:19, Xin LI wrote:
Here is a simple patch that adds more meaning messages when kldload hits
ENOEXEC.
+1 on anything that makes this (and related) error more clear. I know
I've stumbled over it numerous times.
Doug
--
Nothin' ever doesn't change, but nothin' changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Here is a simple patch that adds more meaning messages when kldload hits
ENOEXEC.
Before patch:
kldload: can't load geom_eli.ko: Exec format error
After patch:
kldload: can't load geom_eli.ko: Exec format error
kldload: Dependendent kernel m
On 22-10-2010 16:30, Ed Schouten wrote:
> Hello everyone,
>
> At EuroBSDCon I was talking with some committers active in the area of
> Clang (brooks, kwm, others) about replacing our libgcc shipped with GCC
> 4.2.1 with a BSD-licensed version. The LLVM folks have a BSD licensed
> implementation ca
Thomas E. Spanjaard wrote:
> On 10/24/2010 21:18, Alexander Motin wrote:
>> Thomas E. Spanjaard wrote:
>>> In an attempt to get more information about this issue, I'd like to ask
>>> people on freebsd-current if they're using any Sandforce-based SSDs with
>>> FreeBSD. So far, it appears not a lot o
On 10/24/2010 21:18, Alexander Motin wrote:
> Thomas E. Spanjaard wrote:
>> In an attempt to get more information about this issue, I'd like to ask
>> people on freebsd-current if they're using any Sandforce-based SSDs with
>> FreeBSD. So far, it appears not a lot of people do, making it hard to
>>
on 25/10/2010 14:23 vol...@vwsoft.com said the following:
> the Vaio P11Z does not boot at all with ACPI enabled so it's disabled in
> loader.conf. The panic messages are various if I try.
I would be interested to look at that problem (or those problems) too.
And now I think that see what the imm
On 10/25/10 13:03, Andriy Gapon wrote:
on 25/10/2010 13:35 vol...@vwsoft.com said the following:
Dear Andriy,
sorry for the delay.
On 10/22/10 11:29, Andriy Gapon wrote:
thanks a lot!
Perhaps, meanwhile you can provide a verbose boot dmesg?
Sure! Please find it at
http://people.freebsd.org/
on 25/10/2010 13:35 vol...@vwsoft.com said the following:
> Dear Andriy,
>
> sorry for the delay.
>
> On 10/22/10 11:29, Andriy Gapon wrote:
>> thanks a lot!
>> Perhaps, meanwhile you can provide a verbose boot dmesg?
>
> Sure! Please find it at
> http://people.freebsd.org/~vwe/misc/Vaio_p11z/dm
Dear Andriy,
sorry for the delay.
On 10/22/10 11:29, Andriy Gapon wrote:
on 22/10/2010 12:09 vol...@vwsoft.com said the following:
On 10/22/10 10:53, Andriy Gapon wrote:
[ping]
Sorry, Andriy!
I haven't found the time to hack yesterday. The Intel website doesn't provide
the 20091221 tarbal
Hello,
I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN
today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the
above chip is still not supported. I am wrong?
Any other idea how to get Wifi working on this mini laptop?
Thanks in advance
matthias
--
M
20 matches
Mail list logo