I've been trying out 9.0-BETA1: it's a lot easier to install than
previous releases with bsdinstall, but I spotted a few issues:
Typo - "Resovler Configuration".
If I leave the resolver window for a while it gets corrupted with:
Aug 2 10:31:23 dhclient[973]: Bogus domain search list 15: lan, ..
On Aug 1, 2011, at 9:36 PM, Patrick Lamaiziere wrote:
> Hello,
>
> Will pflow(4) be available on 9.0 ?
>
> There is a "if_pflow.h" in pf's code but no manual page.
No; the header file is only there to ease compiling of the rest of the code.
/bz
--
Bjoern A. Zeeb
9.0 Beta1 Panic
Hi guys,
I just downloaded and install 9.0 BETA1 but it panics on ACPI. Please view
attached screenshot for the error. If you need more information, do let us know.
Thanks.
___
freebsd-current@freebsd.org mailing list
http://lists.fre
Hi!
It seems, I've found a bug in the ZFS v28 on the latest stable:
if we have a snapshot with some files having an extended attributes,
then attempt to read an extended attributes's value leads to a well
reproducible kernel panic.
The part of backtrace follows:
#6 0x804bbe44 in calltra
On Tuesday, August 02, 2011 12:41:29 am Martin Wilke wrote:
> 9.0 Beta1 Panic
>
> Hi guys,
>
> I just downloaded and install 9.0 BETA1 but it panics on ACPI. Please view
attached screenshot for the error. If you need more information, do let us
know.
>
> Thanks.
Unfortunately the attachment
On Aug 2, 2011, at 6:58 PM, Lystopad Olexandr wrote:
> Hello, Martin Wilke!
>
> On Tue, Aug 02, 2011 at 12:41:29PM +0800
> m...@freebsd.org wrote about "9.0 B1 Panic":
>> 9.0 Beta1 Panic
>>
>> Hi guys,
>>
>> I just downloaded and install 9.0 BETA1 but it panics on ACPI. Please view
>> attach
On 08/02/11 04:41, Bruce Cran wrote:
I've been trying out 9.0-BETA1: it's a lot easier to install than
previous releases with bsdinstall, but I spotted a few issues:
Good! Thanks for checking.
Typo - "Resovler Configuration".
If I leave the resolver window for a while it gets corrupted with:
On Aug 1, 2011, at 4:24 PM, Test Rat wrote:
> Anyone else? I can still reproduce with trunk r136607.
> boot and gptboot seem to be unaffected.
>
> IIRC, with previous clang import it just stuck during boot
> without any error messages.
I have the same behavior. GCC build of gptzfsboot works fine
On 02/08/2011 14:36, Nathan Whitehorn wrote:
The spelling fixes are easy to fix. The documentation issue is more
confusing. It should begin running pkg_add, after you press OK,
assuming you selected something. Do you have the installer log handy?
It will be in /tmp.
I selected both English
On Tuesday, August 02, 2011 8:58:10 am Martin Wilke wrote:
>
> On Aug 2, 2011, at 6:58 PM, Lystopad Olexandr wrote:
>
> > Hello, Martin Wilke!
> >
> > On Tue, Aug 02, 2011 at 12:41:29PM +0800
> > m...@freebsd.org wrote about "9.0 B1 Panic":
> >> 9.0 Beta1 Panic
> >>
> >> Hi guys,
> >>
> >> I j
On Aug 3, 2011, at 12:56 AM, John Baldwin wrote:
> On Tuesday, August 02, 2011 8:58:10 am Martin Wilke wrote:
>>
>> On Aug 2, 2011, at 6:58 PM, Lystopad Olexandr wrote:
>>
>>> Hello, Martin Wilke!
>>>
>>> On Tue, Aug 02, 2011 at 12:41:29PM +0800
>>> m...@freebsd.org wrote about "9.0 B1 Panic":
TB --- 2011-08-02 19:26:51 - tinderbox 2.7 running on freebsd-current.sentex.ca
TB --- 2011-08-02 19:26:51 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2011-08-02 19:26:51 - cleaning the object tree
TB --- 2011-08-02 19:27:10 - cvsupping the source tree
TB --- 2011-08-02 19:27:10 - /usr
On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
> on 19/07/2011 18:16 John Baldwin said the following:
> > Hmm, can you get devinfo -r output from a working kernel with ichwd loaded?
> >
> > You might be able to just build the kernel with 'nooptions NEW_PCIB'.
>
> I believe that I've
Hello,
Looks like I've broke my soekris net5501 while doing installworld (built
with clang)
===> libexec/rtld-elf (install)
chflags noschg /usr/libexec/ld-elf.so.1
install -s -o root -g wheel -m 555 -C -b -fschg -S ld-elf.so.1 /libexec
install -o root -g wheel -m 444 rtld.1.gz /usr/share/man/ma
Hello,
I think that devfs is sure to have the bug.
I found that I couldn't open "/dev/XXX" though the kernel detected XXX
device.
"dm->dm_generation" is updated with "devfs_generation" in
devfs_populate(), and the context holds only "dm->dm_lock" in
devfs_populate().
On the other hand, "devfs_g
Hello,
> Hello,
>
> I think that devfs is sure to have the bug.
> I found that I couldn't open "/dev/XXX" though the kernel detected XXX
> device.
>
>
> "dm->dm_generation" is updated with "devfs_generation" in
> devfs_populate(), and the context holds only "dm->dm_lock" in
> devfs_populate().
16 matches
Mail list logo