Hi all,
I'm running cone on 8.0-STABLE.
When I run the program for the first time it works like a charm!
Cone then creates a configuration directory and conerc.
When I run cone the second time it crashed with a segmentation fault.
Then after removing the "OPTIONS" node from the config file cone
On 19/06/2010 11:06, Mark Stapper wrote:
> On 06/18/10 12:20, Alfred Bartsch wrote:
>
>> Mark Stapper schrieb:
>>
>>
>>> Hello,
>>>
>>> Since updating to 8.X I noticed that network services were started
>>> before the netw
On 06/18/10 12:20, Alfred Bartsch wrote:
> Mark Stapper schrieb:
>
>> Hello,
>>
>> Since updating to 8.X I noticed that network services were started
>> before the network was up!
>> I use lagg failover configuration on both my FreeBSD boxes.
>> F
On 18/06/2010 10:26, Jeremy Chadwick wrote:
> On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote:
>
>> Hello,
>>
>> Since updating to 8.X I noticed that network services were started
>> before the network was up!
>>
> This is common/norm
Hello,
Since updating to 8.X I noticed that network services were started
before the network was up!
I use lagg failover configuration on both my FreeBSD boxes.
First, boot fails on mounting my nfs-shares.
After entering and exiting the "rescue" shell, the system boots as normal.
uname -a
FreeBSD
On 05/30/10 08:31, Garrett Cooper wrote:
>
> Everything I saw there appeared sane (it would have been nice to grab
> the -v output from kldstat, but that's ok...). Let's try doing the
> following:
>
> 1. Add `options EMU_MTX_DEBUG' to your kernconf.
> 2. Add set the sysctl: dev.emu10kx.0.debug=1 .
On 30/05/2010 08:31, Garrett Cooper wrote:
>
> Everything I saw there appeared sane (it would have been nice to grab
> the -v output from kldstat, but that's ok...). Let's try doing the
> following:
>
> 1. Add `options EMU_MTX_DEBUG' to your kernconf.
> 2. Add set the sysctl: dev.emu10kx.0.debug=1
On 30/05/2010 08:31, Garrett Cooper wrote:
> On Wed, May 26, 2010 at 12:05 PM, Mark Stapper wrote:
>
>> On 25/05/2010 20:05, Garrett Cooper wrote:
>>
>>> On Tue, May 25, 2010 at 3:06 AM, Mark Stapper wrote:
>>>
>>>
On 25/05/2010 20:05, Garrett Cooper wrote:
> On Tue, May 25, 2010 at 3:06 AM, Mark Stapper wrote:
>
>> On 18/05/2010 08:14, Mark Stapper wrote:
>>
>>> On 18/05/2010 00:22, Garrett Cooper wrote:
>>>
>>>
>>>&
On 25/05/2010 20:05, Garrett Cooper wrote:
> On Tue, May 25, 2010 at 3:06 AM, Mark Stapper wrote:
>
>> On 18/05/2010 08:14, Mark Stapper wrote:
>>
>>> On 18/05/2010 00:22, Garrett Cooper wrote:
>>>
>>>
>>>&
On 18/05/2010 08:14, Mark Stapper wrote:
> On 18/05/2010 00:22, Garrett Cooper wrote:
>
>> On Mon, May 17, 2010 at 11:21 AM, Mark Stapper wrote:
>>
>>
>>> On 12/04/2010 16:29, Garrett Cooper wrote:
>>>
>>>
>>
On 05/19/10 12:44, Jeremy Chadwick wrote:
> On Wed, May 19, 2010 at 12:34:17PM +0200, Mark Stapper wrote:
>
>> I have two machines running FreeBSD amd64 8.0-Stable with custom kernels.
>> My newer box has had troubles with ssh from day one.
>> I hoped a kernel upgrade w
On 19/05/2010 12:44, Jeremy Chadwick wrote:
> On Wed, May 19, 2010 at 12:34:17PM +0200, Mark Stapper wrote:
>
>> I have two machines running FreeBSD amd64 8.0-Stable with custom kernels.
>> My newer box has had troubles with ssh from day one.
>> I hoped a kernel up
Hi,
I have two machines running FreeBSD amd64 8.0-Stable with custom kernels.
My newer box has had troubles with ssh from day one.
I hoped a kernel upgrade would help, but it didn't.
When I'd ssh into the box ssh would exit with errors:
Bad packet length xx
Disconnecting: Packet corrupt.
afte
Jeffrey Goldberg wrote:
> On Aug 31, 2009, at 1:33 PM, Szára György wrote:
>
>> I had some nuisance when after implementation booting 7.2 release. It
>> denied me to boot the once installed release.
>
> I don't understand what you are saying. Are you saying that once you
> installed 7.2 the syste
Thomas Backman wrote:
> On Sep 2, 2009, at 10:27 AM, Mark Stapper wrote:
>
>>
> Nothing a LiveCD or something to that regard can't handle. Obviously
> this doesn't work for everyone, but it should for many.
Actually it won't because updating zfs comes with updati
Emil Mikulic wrote:
> On Wed, Sep 02, 2009 at 09:20:21AM +0200, Mark Stapper wrote:
>
>> updating a zfs filesystem which you are running from is next to
>> impossible.
>>
>
> [citation needed] :)
>
Well, to update your zfs filesystem version, the fi
Miroslav Lachman wrote:
> Maciej Jan Broniarz wrote:
>> 2009/9/1 Thomas Backman :
>>
>>> On Sep 1, 2009, at 4:04 PM, Maciej Jan Broniarz wrote:
>>>
>>>
>>> I'm not familiar with gmirror, but it'd be a way better idea to
>>> mirror it
>>> using ZFS if possible - that way you get self-healing and stu
Arnaud Houdelette wrote:
> Mark Stapper wrote:
>> Arnaud Houdelette wrote:
>>
>>> Mark Stapper a écrit :
>>>
>>>> Ivan Voras wrote:
>>>>
>>>>
>>>>> 2009/7/21 Mark Stapper :
>>>
Christian Walther wrote:
> 2009/7/29 grarpamp :
>
>> One week old build...
>>
>> # df -i .
>> Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted
>> on
>> ram01/mnt1 239465344 239465344 0 100% 13163 0 100% /mnt1
>> # ls -aliT zero
>> 20797 -rw-r--r-- 1 us
Arnaud Houdelette wrote:
> Mark Stapper wrote:
>> Arnaud Houdelette wrote:
>>
>>> Mark Stapper a écrit :
>>>
>>>> Ivan Voras wrote:
>>>>
>>>>
>>>>> 2009/7/21 Mark Stapper :
>>>
Arnaud Houdelette wrote:
> Mark Stapper a écrit :
>> Ivan Voras wrote:
>>
>>> 2009/7/21 Mark Stapper :
>>>
>>>> Ivan Voras wrote:
>>>>
>>>>> Mark Stapper wrote:
>>>>>
&
Ivan Voras wrote:
> 2009/7/21 Mark Stapper :
>
>> Ivan Voras wrote:
>>
>>> Mark Stapper wrote:
>>>
>>>> Good day,
>>>>
>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other
>>>
Good day,
I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other
things, a data server.
My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system
disc, and has a zfs RAIDZ array with 4 discs for bulky data.
As it is a home server, and I work during the day, these four
24 matches
Mail list logo
