Hi Ruslan,
On the 26th you made changes to the Makefiles with this log message:
##
Do not build (and install) both secure/ and standard versions
of libtelnet, telnetd, and telnet. This only worked because
secure/ was listed late in SUBDIR in Makefile.inc1.
##
Did you
I have put up a patch which sanitizes the fsck passno handling,
you will find it at http://phk.freebsd.dk/patch/
Apologies to Kirk if this conflics with any of his work on
delayed fsck...
20010328fsck.patch
This patch sanitizes the way fsck deals with pass numbers
Hi!
I don't see how my changes to non-secure Makefiles might affect this.
What I did is disabled building of non-secure, standard libtelnet,
telnet and telnetd if we are also building the secure versions.
I did not touch the secure/ versions in this commit. Moreover, the
standard versions are
On Tue, Mar 27, 2001 at 02:14:38PM -0500, Robert Watson wrote:
After the EA backing files are initialized, you can manually start the
EA's on the file system, or if UFS_EXTATTR_AUTOSTART is enabled, simply
remount the file systems, or reboot the system. To manually start and
enable the
Run the 4.3 mountd on it.
Boom! Kernel memory allocation way to large; unrecoverable!
Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.
On 28-Mar-01 John Baldwin wrote:
On 28-Mar-01 John Baldwin wrote:
That's right, more SMPng breakage is on the way. Well, hopefully not bad
breakage. On a more serious note, I've just spammed sys/alpha/alpha with
parts
of the critical_enter/exit change which I meant to commit anyways, so
On Wed, 28 Mar 2001, Poul-Henning Kamp wrote:
There is no way to tell it that ccd0c overlaps ad0 and ad1.
With the patch, it will do it this way:
pass 2:
One process doing ad0s1e
One process doing ad1s1e and ad1s1f
and when they are
In message [EMAIL PROTECTED], Chr
is Dillon writes:
On Wed, 28 Mar 2001, Poul-Henning Kamp wrote:
There is no way to tell it that ccd0c overlaps ad0 and ad1.
With the patch, it will do it this way:
pass 2:
One process doing ad0s1e
One process doing
I just rebooted my machine with the cvupped-and-compiled world
and kernel, I logged on and did the following:
(stephanb@enigma|ttyp4)~ w
w: /dev/null: Permission denied
Checking out /dev/null gave me this:
crw--- 1 root wheel2, 2 Mar 28 20:00 /dev/null
I had to chmod it to 666
Ouch .. ok this was meant to go to -stable.
I don't know what made me sent this to -current.. damn.
I'll cc this reply to -stable. My apologies.
Anyway, I forgot to mention some into.. I do not have DEVFS in my
kernel and this is my kernel:
FreeBSD enigma.whacky.net 4.3-RC FreeBSD 4.3-RC #0:
Stephan van Beerschoten wrote:
I just rebooted my machine with the cvupped-and-compiled world
and kernel, I logged on and did the following:
(stephanb@enigma|ttyp4)~ w
w: /dev/null: Permission denied
Checking out /dev/null gave me this:
crw--- 1 root wheel2, 2 Mar 28 20:00
Peter Wemm([EMAIL PROTECTED])@2001.03.28/06:24:34(epoch+985757074s):
FYI:
SYNOPSIS
portmap [-d] [-v]
SYNOPSIS
rpcbind [-dilLs]
yup, so i think it makes sense, to have the daemon called rpcbind, since
it would probably break other people's configuration after making world.
/k
On Wed, Mar 28, 2001 at 10:09:28PM +0200, Jesper Skriver wrote:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev
On Wed, Mar 28, 2001 at 10:15:21PM +0200, Niels Chr. Bank-Pedersen wrote:
On Wed, Mar 28, 2001 at 10:09:28PM +0200, Jesper Skriver wrote:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
I do not. -v could easily be added to what is now rpcbind (even if it
was ignored). -d mean the same thing for both. there's then no reason
to change its name.
Well, my feeling on the matter, since everyone gets to have an opinion
today, is that we should stick with rpcbind: it's what
I've been notified that one of the ports I'm responsible for, xswallow, will no
longer build under -current. Here's a snip from the build log:
=== Building for xswallow-1.0.18
cd /tmp/a/ports/www/xswallow/work/xswallow/xswallow cc -O -pipe -o
xswallow.so -aout -shared -nostdlib -DXP_UNIX
On Wed, Mar 28, 2001 at 10:20:33PM -0600, Conrad Sabatier wrote:
I've been notified that one of the ports I'm responsible for, xswallow, will no
longer build under -current. Here's a snip from the build log:
a.out support is entirely optional thesedays for ports, so it's up to
you whether or
On 29-Mar-2001 Kris Kennaway wrote:
On Wed, Mar 28, 2001 at 10:20:33PM -0600, Conrad Sabatier wrote:
I've been notified that one of the ports I'm responsible for, xswallow, will
no longer build under -current. Here's a snip from the build log:
a.out support is entirely optional these days
18 matches
Mail list logo
