On Tue, Nov 08, 2011 at 08:02:13PM +0100, Sebastian Chmielewski wrote:
> I've got following error after upgrading my 9.0-RC1 to RC2 using source and
> got this error at loader prompt:
>
> ZFS: invalid zap_type=134218628
>
> when I tried zfsboottest from 9.0-STABLE it failed
> ./zfsboottest /boot/
Am 10.11.2011 11:32, schrieb Attilio Rao:
2011/11/10 Stefan Esser:
I can produce further debug output on demand, but I do not have a serial or
firewire console setup for debugging.
Is anybody else affected by this boot problem?
Can you setup a videocamera or a simple serial console?
Did you t
Can you try rebuilding your kernel and modules from scratch and see if
it fixes your problem?
Attilio
2011/11/11 Stefan Esser :
> Am 10.11.2011 11:32, schrieb Attilio Rao:
>>
>> 2011/11/10 Stefan Esser:
>>>
>>> I can produce further debug output on demand, but I do not have a serial
>>> or
>>> fi
Dear all ,
Instead of using Current and then renaming everything for a new version
number ,
is it not possible to use the newest version number in place of Current
when it is branched .
Such a change will prevent unnecessary renaming problems .
For everyone , it i very easy to understand that
On Friday, November 11, 2011 07:29:46 AM Mehmet Erol Sanliturk wrote:
-(snipped stuff)-
> This is preventing testing and / or using efforts .
>
>
> I know , it is possible to rename local link names , but
> everyone is not so much knowledgeable .
>
>
>
> Thank you very much .
>
> Mehmet Erol
On Fri, Nov 11, 2011 at 8:04 AM, Chuck Burns wrote:
> On Friday, November 11, 2011 07:29:46 AM Mehmet Erol Sanliturk wrote:
> -(snipped stuff)-
>
> > This is preventing testing and / or using efforts .
> >
> >
> > I know , it is possible to rename local link names , but
> > everyone is not so muc
On Friday, November 11, 2011 08:17:52 AM you wrote:
-snip-
> My sentence is NOT about "Current" , but 9.0 RC1 .
> Perhaps , you will NOT say , if a person is NOT knowledgeable , he should
> NOT use 9.0 RC1 .
>
If you use a proper RC, then pkg_add will work until a new RC, and since there
is no b
Chuck Burns wrote:
On Friday, November 11, 2011 08:17:52 AM you wrote:
-snip-
My sentence is NOT about "Current" , but 9.0 RC1 .
Perhaps , you will NOT say , if a person is NOT knowledgeable , he should
NOT use 9.0 RC1 .
If you use a proper RC, then pkg_add will work until a new RC, and since
Hello all.
Before I begin, I appreciate any help/comments/criticism. Please, don't
hesitate to support this topic.
Some time ago I've announced new project - of creating rolling images of
FreeBSD from SVN.
Along with plain standard ones (plain world+kernel install of bare system)
I'm working on cr
On Fri, Nov 11, 2011 at 4:39 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
> Chuck Burns wrote:
>>
>> On Friday, November 11, 2011 08:17:52 AM you wrote:
>> -snip-
>>>
>>> My sentence is NOT about "Current" , but 9.0 RC1 .
>>> Perhaps , you will NOT say , if a person is NOT knowledgeable , he shou
George Kontostanos schreef:
On Fri, Nov 11, 2011 at 4:39 PM, Miroslav Lachman<000.f...@quip.cz> wrote:
Chuck Burns wrote:
On Friday, November 11, 2011 08:17:52 AM you wrote:
-snip-
My sentence is NOT about "Current" , but 9.0 RC1 .
Perhaps , you will NOT say , if a person is NOT knowledgeable
Hi!
I'm having troubles booting today's 9.0-RC2 from zfsroot, I'm getting 'unknown
filesystem' error.
But 9.0-RC1 from Tue Nov 8 2011 boots fine.
Here is output with 9.0-RC1 kernel:
# zpool list
NAMESIZE ALLOC FREECAP DEDUP HEALTH ALTROOT
zroot 5.97G 2.85G 3.11G47% 1.00x
> If FreeBSD starts using numbers for HEAD/CURRENT, i think a lot of users
> would find them selves in a situation
> that they download version 10 in this case and that they are using a
> develepment version instead of a real release version.
>
Assuming there will be link from main page - probably
On Fri, 11 Nov 2011, Mehmet Erol Sanliturk wrote:
Dear all ,
Instead of using Current and then renaming everything for a new version
number ,
is it not possible to use the newest version number in place of Current
when it is branched .
Such a change will prevent unnecessary renaming problems
> Along with plain standard ones (plain world+kernel install of bare system)
> I'm working on creating specific images.
> Like with preset installed packages (kde-set, gnome-set, etc.), like with
> some patches (area51/kde-wip/kms) etc.
> So, I did not fully automated (yet) creating of this one ima
On Fri, Nov 11, 2011 at 12:29 PM, Benjamin Kaduk wrote:
> On Fri, 11 Nov 2011, Mehmet Erol Sanliturk wrote:
>
> Dear all ,
>>
>> Instead of using Current and then renaming everything for a new version
>> number ,
>> is it not possible to use the newest version number in place of Current
>> when
On 11/11/2011 20:33, Mehmet Erol Sanliturk wrote:
> On Fri, Nov 11, 2011 at 12:29 PM, Benjamin Kaduk wrote:
>
>> On Fri, 11 Nov 2011, Mehmet Erol Sanliturk wrote:
>>
>> Dear all ,
>>>
>>> Instead of using Current and then renaming everything for a new version
>>> number ,
>>> is it not possible
On 11/11/2011 21:07, Luchesar V. ILIEV wrote:
> On 11/11/2011 20:33, Mehmet Erol Sanliturk wrote:
>> On Fri, Nov 11, 2011 at 12:29 PM, Benjamin Kaduk wrote:
>>
>>> On Fri, 11 Nov 2011, Mehmet Erol Sanliturk wrote:
>>>
>>> Dear all ,
Instead of using Current and then renaming everything
Hello all,
i try to unmute a box with a mcp79 ane alc-889.
the sound is working on another os, and playback
and recording are treated separately by os x, (10.7).
i tried different combinations according to the snd_hda man page,
but i cannot find a good one.
Pleease, have you some hints?
here
On Thu, Sep 29, 2011 at 12:22:54AM +0200, Baptiste Daroussin wrote:
> On Sun, Sep 11, 2011 at 10:39:38PM +0200, Baptiste Daroussin wrote:
> > > > the result is:
> > > > db> show intrcnt
> > > > cpu0: timer4510
> > > > irq256: hdac0 1
> > > > cpu3: timer 29
> > > > cpu1: timer 3036
> >
On 11/11/2011 04:29, Mehmet Erol Sanliturk wrote:
> pkg_add -r *
>
> is giving error about directory not found .
>
>
> This is preventing testing and / or using efforts .
I see your perspective on this, but package support for HEAD (N-current)
is always done on a "best effort" basis, and is in
On Fri, Nov 11, 2011 at 7:29 PM, Benjamin Kaduk wrote:
> On Fri, 11 Nov 2011, Mehmet Erol Sanliturk wrote:
>
>> Dear all ,
>>
>> Instead of using Current and then renaming everything for a new version
>> number ,
>> is it not possible to use the newest version number in place of Current
>> when i
On 11/11/2011 14:23, George Kontostanos wrote:
> BTW I follow both stable and current lists. I have noticed that people
> still ask questions in current regarding 9-RC(*) problems.
> Maybe if it was clear that current is now 10 this would not happen.
Actually up until the actual release we encoura
On Fri, Nov 11, 2011 at 11:10:58PM +0100, Baptiste Daroussin wrote:
> On Thu, Sep 29, 2011 at 12:22:54AM +0200, Baptiste Daroussin wrote:
> > On Sun, Sep 11, 2011 at 10:39:38PM +0200, Baptiste Daroussin wrote:
> > > > > the result is:
> > > > > db> show intrcnt
> > > > > cpu0: timer4510
> > > >
When upgrading a FreeBSD 8.2 (amd64) to today's csup (tag=RELENG_9,
i.e. 9.0-RC2), the standard procedure got itself into trouble:
rm -rf /usr/obj
make buildworld
make buildkernel KERNCONF=xxx
make installkernel KERNCONF=xxx
(the xxx is mostly a plain vanilla 'include GENERIC'
with pf alt
25 matches
Mail list logo
