Hi all,
I've been experimenting with upgrading 4.X to 5.3-STABLE. The challenge
I've been given is that the box to be upgraded is physically
inaccessible and so there's no console access. All I have to work with
is ssh and scp.
In our lab I built a box to 5.3-STABLE. I then used the /usr/obj
d
Hello,
I'm in charge of upgrading a number of boxes from 4.8-RELEASE from
4.10-RELEASE. My problem is this section of notes from the 4.9-RELEASE
errata:
(28 Oct 2003) Very late in the release cycle, a change was made to the
HyperThreading (HTT) support on Intel® processors. HTT support is now
Hi,
I'm wondering if this could possibly be related to a problem I was
having with my 4.9-RELEASE box. Twice in two days it hung on me
completely, and started spouting the following error messages:
ad0 WRITE command timeout tag=0 serv=0 -restting
ad0: trying fallback to PIO mode
ata0: resetting
Simon L. Nielsen wrote:
Do you use Privilege Separation? That can give interesting results with
DNS due to chroot into /var/empty... see the mailing lists archives.
Argh. This frustrates me. I did some searching on various mailing lists
before, and when they talked about switching into /var/emp
Ted Faber wrote:
On Fri, Sep 05, 2003 at 12:04:04PM -0400, Dwayne MacKinnon wrote:
That much I know. I was just wondering why the daemon is trying DNS
lookup when the IP in question is listed in /etc/hosts. I thought
listings in /etc/hosts would supercede the need for a DNS lookup. Of
course
Kris Kennaway wrote:
On Fri, Sep 05, 2003 at 10:32:52AM -0400, Dwayne MacKinnon wrote:
Anyone else see this type of thing before? I did some research on the
lists but all I ever saw was a problem with reading resolv.conf. That's
not the case here, because it's definitely pick
Hi,
I recently took one of our machines off the main network and set up a
crossover cable between it and my personal box. I was looking to scp
some large files over and I didn't want to swamp the network. (I use scp
from force of habit, even though ftp would probably be quicker in this
case.)
Arrgh. Forget what I just wrote about a @dstdir option. My brain
shortcircuited and I believed it actually existed.
Cheers,
DMK
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
Julian Elischer wrote:
Alternatively, the man page hints that
a 'srcdir' would stop a following 'cwd' from having effect in the create
phase.
Just wanted to mention that order is extremely important with package
creation. If you have @cwd /foo/bar; @srcdir /bar/foo your files will be
picked up f
Hi all,
Just wanted to chime in that I've encountered the exact same thing,
although it's a relatively recent thing... I think it happened when I
ported to 4.5 from 4.2.
The only solution I've found, pain in the neck that it is, is to create
the destination directories on the source box. That
10 matches
Mail list logo
