If memory serves me right, "Steve O'Hara-Smith" wrote:
On Wed, 04 Apr 2001 23:49:40 -0500
"Brian D. Woodruff" [EMAIL PROTECTED] wrote:
BW I would rather be consistent across my servers than have some be one
BW release past the others.
Allow me to investigate this a little
On Wed, 4 Apr 2001, Brian D. Woodruff wrote:
At 10:35 PM 4/4/01 -0400, you wrote:
On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote:
Here are my questions:
1.) is there a way to specify 4.2-STABLE, which is what I have been using?
can anyone tell me how to get the
On 05-Apr-2001 Ken Bolingbroke wrote:
If you require absolute consistency across servers, you need to either
update all servers from the very same source, or specify an exact CVS tag
to get the same sources for all servers.
You can check out a branch at a specific time using -D which you
There may be some value in the multiple servers case, of running one as a
cvs server, and updating all the others off that one. Then all your servers
are reflections of the one that is cvsupping the - remote-cvs-server
just a thought.
Bob
On Wed, 4 Apr 2001, Brian D. Woodruff wrote:
At
I agree with you completely, Bob. The idea of keeping one "master
server" to push out updates to many is extremely useful when you are
maintaining a large number of similar systems. It is much less
work-intensive to maintain several hundred systems if they are running
on exactly the same
* fury [EMAIL PROTECTED] [010405 06:28]:
No it was NOT a hardware issue unlike many ppl stated, fact is, I have never
figured it out.
Then how do you know it wasn't hardware?
I'm not saying you're wrong, fury, and I can see you're more than a bit
pissed off, but in the vast majority of
Is there a decent walkthrough anywhere on the Net for using
disklabel, fdisk , etc - along with an explanation of what a,c etc all
mean?
man disklabel etc all assume you know what those letters mean.
I know c is the whole partition, but that's it.
I need to know because:
Brian D. Woodruff wrote:
At 10:35 PM 4/4/01 -0400, you wrote:
On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote:
Here are my questions:
1.) is there a way to specify 4.2-STABLE, which is what I have been using?
excellent answer to part 2
can anyone tell me how to get
Date: Wed, 04 Apr 2001 23:49:40 -0500
From: "Brian D. Woodruff" [EMAIL PROTECTED]
Subject: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
At 10:35 PM 4/4/01 -0400, you wrote:
On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote:
Here are my questions:
1.)
`id` is identical at both aterm, eterm, rxvt, and
console:
uid=1001(lipshitz) gid=1001(lipshitz)
groups=1001(lipshitz), 0(wheel)
--- Alfred Perlstein [EMAIL PROTECTED] wrote:
* Larry Librettez [EMAIL PROTECTED] [010405
09:42] wrote:
With 4.3-RC2, I cannot su to root in X using
either
Hello,
Fixed my problem. I was indeed not using a kernel that was built with the
updated source. I compiled my new kernel with 'make -kernel=sampson' and
installed with 'make install -kernel=sampson' but did not set up boot.conf to
boot that kernel =P. Thanks to all that replied.
Couple of
I am not having su problems, but perhaps our problems are related
somehow, since the "login" process is involved...
I am running Exceed under Win98 to access my FreeBSD with xterm,
to my now "4.3-RC2" box.
It now hangs waiting to login (using the rlogin method).
From my other FreeBSD machine
Bosko Milekic writes:
NMBUFS accordingly. Chances are, if you are explicitly declaring
`NMBCLUSTERS NO' in your kernel configuration file, that you are
actually lowering the number of clusters/mbufs that would otherwise be
allowed with your given `maxusers' value (unless you have an
In article [EMAIL PROTECTED],
Michael R. Wayne [EMAIL PROTECTED] wrote:
With the recent ntpd exploit, I wanted to update only the files
in /usr/src/contrib/ntp/ntpd. Based on the man page, I should
be able to use -i to do this. But cvsup seems pretty unhappy:
1162 /usr/local/bin/cvsup
Problem solved. Turns out my use of "nonstandard"
characters in my root password (like ^*(@$#) were the
cause of the problem. Specifically, use of the '('
character somehow was causing authentication problems
with rxvt in X, thus disallowing su to root and the
error "BAD SU to root on ttyp*".
On 06-Apr-2001 Larry Librettez wrote:
Problem solved. Turns out my use of "nonstandard"
characters in my root password (like ^*(@$#) were the
cause of the problem. Specifically, use of the '('
character somehow was causing authentication problems
with rxvt in X, thus disallowing su
i use 4.2 release,my display card is i810,4.2 release does not contain XFree86 4.0,
so i download source for XFree86 4.02,after compile and install,i use XF86Setup,but
failed.it told me can not start X.what's the matter?
i choose some X Server(VGA SVGA...) when i install my system,shall i remove
With FreeBSD 4.3RC1 I am also seeing quite a few silo overflow messages
sio0: 3 more silo overflows (total 61)
I've been seeing these as well, and I'm using 4.3-RC.
On a 550 MHz Athlon, I might add, at 38400 bps.
I applied the patch mentioned yesterday, it seems to have helped, however
I
18 matches
Mail list logo
