hey guys, my server rebooted a few days ago, and while i was
looking around for possible reasons (none came up, which's
disconcerting in itself) i found this suspicious directory:
$ ls -l /tmp/download
total 44
drwxr-xr-x 4 root wheel512 Oct 23 16:28 Archive_Tar-1.3.1
drwxr-xr-x 3 root whe
In message: <[EMAIL PROTECTED]>
Ilya Vishnyakov <[EMAIL PROTECTED]> writes:
: -BEGIN PGP SIGNED MESSAGE-
: Hash: SHA1
:
: Hello, I'm in trouble with rsync. Some people think that this problem
: is freebsd related:
:
: I use rsync to synchronize 2 servers (rsync versions are s
In message: <[EMAIL PROTECTED]>
Freddie Cash <[EMAIL PROTECTED]> writes:
: On Friday 22 December 2006 08:09 am, [EMAIL PROTECTED] wrote:
: > Pete French <> wrote on Friday, December 22, 2006 2:44 PM:
: > Frankly, I can't follow the argument that 6.x is "unstable". After all,
: > it's na
On Fri, Dec 29, 2006 at 09:23:06AM +1100, Peter Jeremy wrote..
> On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
> >burncd had some nice advantages over cdrecord: it came from the BSD
> >tree, it had capabilities for burning DVD+RW images. Disadvantage was
> >the limitation to ATA interface.
On Wed, 2006-Dec-27 16:25:21 -0800, Doug Barton wrote:
>IOW, you're probably right, but "magical" hardware problems that
>develop during upgrade periods are more common than a lot of people
>realize.
I've had two hardware failures during upgrades: Once, when trying to
upgrade from 2.x to 3.x, my C
I need some help here, this is not a single case, I get this on a several
machines, this is releng_6 , recent, but old problem getting ugly
first I get this kind of events in messages, independent if it is client mode
or hostap or adhoc
Dec 28 16:50:53 ap1-cds kernel: ath0: discard oversize fr
On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
>burncd had some nice advantages over cdrecord: it came from the BSD
>tree, it had capabilities for burning DVD+RW images. Disadvantage was
>the limitation to ATA interface.
I see the latter as a disadvantage of cdrecord: It only works on SCSI
I got an error sending this message, so next try...
please excuse if its send to you twice.
* Forwarded message:
Date: Thu, 28 Dec 2006 18:12:42 +0100
From: Dirk Arlt <[EMAIL PROTECTED]>
To: freebsd-stable@freebsd.org
Subject: atapicam - System freeze with hw.ata.atapi_dma=1
Hi All,
I found t
Hi All,
I found that issue in older mailings and as bugreport, but its not
mentioned anymore.
Loading atapicam freezes my system, with or without dvdram. Only
solution is setting hw.ata.atapi_dma to 0.
I'd like to see that issue reanimated. Of course i'll give any
information necessary.
I am us
In response to Ilya Vishnyakov <[EMAIL PROTECTED]>:
>
> Hello, I'm in trouble with rsync. Some people think that this problem
> is freebsd related:
>
> I use rsync to synchronize 2 servers (rsync versions are same on both
> machines).
> Most of the directories are copied fine, however, some huge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, I'm in trouble with rsync. Some people think that this problem
is freebsd related:
I use rsync to synchronize 2 servers (rsync versions are same on both
machines).
Most of the directories are copied fine, however, some huge ones fail
and produ
Ken Smith wrote:
> On Thu, 2006-12-28 at 16:01 +0100, Thomas Herrlin wrote:
>> It still runs networking daemons into a frozen zoneli state on
>> heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is
>> no way to recover from it. (think frozen sshd and a very remote/headless
>> ser
On Thu, 2006-12-28 at 16:01 +0100, Thomas Herrlin wrote:
> It still runs networking daemons into a frozen zoneli state on
> heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is
> no way to recover from it. (think frozen sshd and a very remote/headless
> server).
> See the stress
Ken Smith wrote:
> All problems we felt needed to be addressed before 6.2 could be released
> have been taken care of.
It still runs networking daemons into a frozen zoneli state on
heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is
no way to recover from it. (think frozen
On Thu, 2006-12-28 at 01:26 -0800, Eric P. Scott wrote:
> (BTW, what's this "docs" ISO? That wasn't around in previous
> releases...)
For recent releases where recent is older than 6.1 there was a docs/
directory on disc2 that had all the documentation in a readable format
for all the supported l
On Wed, Dec 27, 2006 at 08:50:10PM -0800, Tom Samplonius wrote:
>
> I have a Soekris board, so I'm interested. What's the PR number for the
> bug? How frequently does it occur?
>
> It is good to log all of the details to the PR.
Right. I have hopened a PR for this, as well as a possibly r
On Thu, Dec 28, 2006 at 04:54:38AM -0800, Eric P. Scott wrote:
> You need to try to put yourself in an end user's frame of reference. It's
> easy to understand why even fairly experienced folks can find FreeBSD
> documentation baffling.
The FreeBSD Documentation Project is always in search of new
>http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-diff-media.html#AEN3220
Let me try to explain what's wrong here...
This URL corresponds to "Preparing Your Own Installation Media,"
which appears after "Advanced Installation Guide." That's sure
not the first place I'd look. Tit
* Oliver Fromme <[EMAIL PROTECTED]> [2006-12-28 12:34 +0100]:
> I'm afraid I don't know how to specify any mount options
> for the root file system when mounting it via the kernel's
> BOOTP options, but if you mount it read-only (or just treat
You can set some, but AFAIK not -L. :(
dhcpd.conf:
op
Robert Joosten wrote:
>
> > In that case you can savely mount with the -L option
> > (a.k.a. "-o nolockd"), an everything will just work.
> > No need for rpc.lockd at all.
>
> Hmm, yes. Fiddling in etc/fstab and /etc/rc.d/initdiskless didn't help.
> Where am I expected to fiddle to enable
On 2006.12.28 01:26:41 -0800, Eric P. Scott wrote:
> Would someone please please please publicly document what all the
> various 6.x ISO images are, which of them are (or might be)
> needed for a fresh installation (assuming poor or nonexistent
> network connectivity), and which have overlapping bi
On Thursday 28 December 2006 09:49, Marc G. Fournier wrote:
> How? I can break to DDB no problem, but 'panic' just gives me a
> backtrace and then the ddb> prompt again ... reset didn't dump core,
> just rebooted ... :(
You might have to type 'panic' twice these days. Alternatively, 'call
doadu
Would someone please please please publicly document what all the
various 6.x ISO images are, which of them are (or might be)
needed for a fresh installation (assuming poor or nonexistent
network connectivity), and which have overlapping bits. If this
is actually explained anywhere that's supposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How? I can break to DDB no problem, but 'panic' just gives me a backtrace and
then the ddb> prompt again ... reset didn't dump core, just rebooted ... :(
Had an 'out of swap' error tonight, and would have liked to have been able to
run a ps after
On 12/28/06, Jonathan Chen <[EMAIL PROTECTED]> wrote:
Hi,
I've just cvsup'd my Latitude D820 laptop with a Broadcom BCM5752
to the latest 6-STABLE, and I seem to experiencing some problems with
the dhcp client on the base system. The dhcp-client program fails to
request an IP address from the DH
25 matches
Mail list logo