Quoting Tim Kientzle [EMAIL PROTECTED]:
On Monday 04 June 2007 17:46, Robin Gruyters wrote:
This morning I have revert libarchive (src/lib/libarchive) and tar
(src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not)
it works fine now.
Maybe tar doesn't use the -b option when
all the problem of freebsd is that freebsd-team tries (mostly unsuccesfully)
to do EVERYTHING
freebsd team not just do freebsd, they doing freebsd5, freebsd6, freebsd7,
ports, etc ...
and nothing of this can work REALLY STABLE AND FUNCTIONAL
i don't like linux, but sometimes i have to choose it
i
On Wednesday 06 June 2007 16:14, Robin Gruyters wrote:
Then a tar the file (with or without blocksize set) to tape:
$ sudo tar -cf /dev/sa0 archive.dmp
$
After that I try to read/list the tar from tape with tar -t:
$ sudo mt -f /dev/sa0 rewind
$ sudo tar -tf /dev/sa0
archive.dmp
tar:
Quoting Daniel O'Connor [EMAIL PROTECTED]:
On Wednesday 06 June 2007 16:14, Robin Gruyters wrote:
Then a tar the file (with or without blocksize set) to tape:
$ sudo tar -cf /dev/sa0 archive.dmp
$
After that I try to read/list the tar from tape with tar -t:
$ sudo mt -f /dev/sa0 rewind
$ sudo
hi,
recently i tried to update my fresh install machine of 6.2RELEASE to
6.2STABLE,
but alway failed with these error msgs:
proxy2# /usr/local/bin/cvsup -g -L 2 /etc/stable-supfile
Parsing supfile /etc/stable-supfile
Connecting to cvsup.id.FreeBSD.org
Connected to cvsup.id.FreeBSD.org
Server
Niki Denev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
zen wrote:
hi,
recently i tried to update my fresh install machine of 6.2RELEASE to
6.2STABLE,
but alway failed with these error msgs:
proxy2# /usr/local/bin/cvsup -g -L 2 /etc/stable-supfile
Parsing supfile
zen wrote:
Niki Denev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
zen wrote:
hi,
recently i tried to update my fresh install machine of 6.2RELEASE to
6.2STABLE,
but alway failed with these error msgs:
proxy2# /usr/local/bin/cvsup -g -L 2 /etc/stable-supfile
Parsing supfile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
zen wrote:
hi,
recently i tried to update my fresh install machine of 6.2RELEASE to
6.2STABLE,
but alway failed with these error msgs:
proxy2# /usr/local/bin/cvsup -g -L 2 /etc/stable-supfile
Parsing supfile /etc/stable-supfile
Connecting to
On Wed, Jun 06, 2007 at 10:50:23AM +0400, Alexey Karagodov wrote:
all the problem of freebsd is that freebsd-team tries (mostly unsuccesfully)
to do EVERYTHING
freebsd team not just do freebsd, they doing freebsd5, freebsd6, freebsd7,
ports, etc ...
and nothing of this can work REALLY STABLE
On 10/25/06, Stefan Bethke [EMAIL PROTECTED] wrote:
Am 25.10.2006 um 10:57 schrieb Stefan Bethke:
I'm not sure that would be so easy. However, CONSPEED is/was the
setting to be used if the actual setting cannot be determined when
sio initializes.
The code is there to determine the currently
Hi all,
I'm in the last mile before crossing the beta-release line,
so I'd like to get some input, and update the list of targets it supports.
you can obtain the driver from:
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz
Cheers,
danny
and sorry for my english! :)
2007/6/6, Kris Kennaway [EMAIL PROTECTED]:
On Wed, Jun 06, 2007 at 10:50:23AM +0400, Alexey Karagodov wrote:
all the problem of freebsd is that freebsd-team tries (mostly
unsuccesfully)
to do EVERYTHING
freebsd team not just do freebsd, they doing freebsd5,
Dear colleagues,
on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP kernel I
got zillions of 'runtime went backwards' errors, both on i386 and amd64
kernels.
Upd: on GENERIC/amd64 kernel I got the same errors.
Any hints to eliminate this? Thanks in advance.
Sincerely,
I have this machine and I'm just trying to get it to boot from an SAS
drive that's all. I'm not trying to use the LSI 1068E for RAID.
See here if you're curious about specs:
http://www.supermicro.com/products/system/1U/6015/SYS-6015V-M3.cfm
Booting from the FreeBSD 6.2 install CD is not a
On Wed, Jun 06, 2007 at 03:33:52PM +0700, zen wrote:
Niki Denev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
zen wrote:
hi,
recently i tried to update my fresh install machine of 6.2RELEASE to
6.2STABLE,
but alway failed with these error msgs:
proxy2#
Hi,
Have you tried csup(1) ?
what is the different??
csup is a rewrite of cvsup in C instead of relying on Modula 3, that
seems to cause some troubles on your system.
Hth.
Kind regards,
Robert
PS: a happy csup user
pgpZ9DybmS5Wu.pgp
Description: PGP signature
On Wed, Jun 06, 2007 at 09:20:55AM -0400, T. Middleton wrote:
It seems the only way to get drives bootable from the BIOS that are plugged
into the LSI is to put them into a raid. Once a logical disk is configured in
the RAID bios one can see in the system bios PCI SCSI: Software Raid.
Quoting Danny Braniss [EMAIL PROTECTED]:
I'm in the last mile before crossing the beta-release line,
so I'd like to get some input, and update the list of targets it supports.
you can obtain the driver from:
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz
Looks
Quoting Danny Braniss [EMAIL PROTECTED]:
I'm in the last mile before crossing the beta-release line,
so I'd like to get some input, and update the list of targets it supports.
you can obtain the driver from:
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz
Looks
Quoting Danny Braniss [EMAIL PROTECTED]:
Quoting John Nielsen [EMAIL PROTECTED]:
Do you have any suggestions on startup integration (rc script, fstab
magic, etc)? I know you said once before that that was hopefully coming
soon..
this is an attempt:
A couple comments just from reading
I have a version of code ready to MFC, the big difference with CURRENT
is that TSO is #ifdef'd off until Andre is able to get that back.
I wanted a chance for any concerns to be aired before I did it, issues
that anyone has had with the driver in CURRENT?
Regards,
Jack
On Sat, May 19, 2007 at 04:35:49PM +0300, Stefan Lambrev wrote:
S Bruce M. Simpson wrote:
S Stefan Lambrev wrote:
S
S Are there any chances for this:
S
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/ip_carp.c.diff?r1=1.46;r2=1.47
S to be MFCed to RELENG_6 before 6.3-release ?
S
S
Wesley Shields wrote:
The difference is that csup is written in C and included in the base.
The only lacking feature in csup is that it doesn't work in checkout
mode, which shouldn't be a problem for your average use.
You have it backwards. csup _only_ works in checkout mode, what it
can't do
On Wed, Jun 06, 2007 at 10:20:11AM -0700, Doug Barton wrote:
Wesley Shields wrote:
The difference is that csup is written in C and included in the base.
The only lacking feature in csup is that it doesn't work in checkout
mode, which shouldn't be a problem for your average use.
You
On 6/6/07, David Christensen [EMAIL PROTECTED] wrote:
I have a version of code ready to MFC, the big difference with CURRENT
is that TSO is #ifdef'd off until Andre is able to get that back.
Is something broken with TSO? I just added TSO support to bce on
CURRENT
and was planning on MFC'ing
Dmitry Morozovsky wrote:
Dear colleagues,
on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP kernel I
got zillions of 'runtime went backwards' errors, both on i386 and amd64
kernels.
Upd: on GENERIC/amd64 kernel I got the same errors.
Do you perhaps run with TSC
I have a version of code ready to MFC, the big difference with CURRENT
is that TSO is #ifdef'd off until Andre is able to get that back.
Is something broken with TSO? I just added TSO support to bce on
CURRENT
and was planning on MFC'ing to RELENG_6 within the next week.
Dave
On 6/6/07, Jack Vogel [EMAIL PROTECTED] wrote:
I have a version of code ready to MFC, the big difference with CURRENT
is that TSO is #ifdef'd off until Andre is able to get that back.
I wanted a chance for any concerns to be aired before I did it, issues
that anyone has had with the driver in
On Wed, 6 Jun 2007, Ivan Voras wrote:
IV on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP kernel
IV I got zillions of 'runtime went backwards' errors, both on i386 and amd64
IV kernels.
IV
IV Upd: on GENERIC/amd64 kernel I got the same errors.
IV
IV Do you perhaps run
Quoting Ivan Voras [EMAIL PROTECTED]:
Danny Braniss wrote:
I'm in the last mile before crossing the beta-release line,
so I'd like to get some input, and update the list of targets it supports.
you can obtain the driver from:
:IV Upd: on GENERIC/amd64 kernel I got the same errors.
:IV
:IV Do you perhaps run with TSC timecounter? (that's the only cause I've notice
:IV that can generate this message).
:
:Nope:
:
:[EMAIL PROTECTED]:~ sysctl kern.timecounter
:kern.timecounter.tick: 1
:kern.timecounter.choice: TSC(-100)
Hiho! ;-)
I just bought a Western Digital MyBook 250GB external USB 2.0 drive and
I stumbled upon the problem mentioned in:
kern/107495: Fix long wait before WD My Book 250GB (USB) is recognized
There's a patch attached to that PR, which I applied, but it didn't
help.
FreeBSD version is
Hi all,
Sometime between the beginning of April and May 14(?) there appears to
have been a change in ACPI which is causing my IBM R51 to hang when
shutting down. I see syslog exit and then nothing. I need to do a hard
shutdown with the partitions still mounted for it to turn off. I booted
After that I try to read/list the tar from tape with tar -t:
$ sudo tar -tf /dev/sa0
archive.dmp
tar: Unrecognized archive format: Inappropriate file type or format
But when I extract the archive from tape, it works perfectly:
$ sudo tar -xvf /dev/sa0
Using dd to feed tar does work though. (I
This morning I have revert libarchive (src/lib/libarchive) and tar
(src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not)
it works fine now.
After that I try to read/list the tar from tape with tar -t:
$ sudo tar -tf /dev/sa0
archive.dmp
tar: Unrecognized archive format:
35 matches
Mail list logo
