I don't agree with this change.
hostname != name-that-IP-address-resolves-to.
I can see how loggin the IP address (or some manifestation thereof) to
a central logger, but this is too strong.
Example: My laptop has a hostname set for my home network, and I connect
it to my work network and DHCP
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128 world
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote:
I don't agree with this change.
hostname != name-that-IP-address-resolves-to.
Dunno what you are talking about. That has nothing directly to do with
this. No one is talking about forcing you to change your hostname. The
patch just
On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote:
I don't agree with this change.
hostname != name-that-IP-address-resolves-to.
Dunno what you are talking about. That has nothing directly to do with
this. No one is talking about forcing you to change your hostname. The
Maxim Sobolev wrote:
Slightly OT, but could we have a flag to disable building sysinstall during make
world? It's hardly a tool that is required for day-to-day operation, so in most
cases it will only waste considerable amount of root partitition.
1) Now sysinstall is /usr/sbin, and it is
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128 world
Do you have an easy way to narrow it down to CCD by doing the same
thing but without ccd involvement?
M
--
Mark Murray
3) Most of what FreeBSD installs is not required for day-to-day for most
users. Since many users use sysinstall to some extent as a system
managing tool, sysinstall is actually quite more oftenly used than many.
It's currently the best way to install packages IMHO. With the automatic
"Rogier R. Mulhuijzen" wrote:
3) Most of what FreeBSD installs is not required for day-to-day for most
users. Since many users use sysinstall to some extent as a system
managing tool, sysinstall is actually quite more oftenly used than many.
It's currently the best way to install packages
What are you talking about? pkg_add -r pkgname, that's all it takes.
*hides head in shame*
OK so I'm a sucker for the graphical interface =)
DocWilco
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
This is directly traceable to entropy harvesting by /dev/*random.
I know it's not an option if you need to use ssh, but not loading
random.ko will fix the sound problems when moving the mouse or
typing. It doesn't fix the 'hwptr went backwards' messages, though.
On Fri, Jan 19, 2001 at
In message [EMAIL PROTECTED], Mark Murray writes:
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128 world
Do you have an easy way to narrow it down to CCD by doing the same
thing but
Mark Murray [EMAIL PROTECTED] types:
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128 world
Do you have an easy way to narrow it down to CCD by doing the same
thing but without ccd
This is directly traceable to entropy harvesting by /dev/*random.
I know it's not an option if you need to use ssh, but not loading
random.ko will fix the sound problems when moving the mouse or
typing. It doesn't fix the 'hwptr went backwards' messages, though.
Please tell me if
sysctl -w
If it helps at all, it's marginal. I still get skips.
On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark Murray wrote:
This is directly traceable to entropy harvesting by /dev/*random.
I know it's not an option if you need to use ssh, but not loading
random.ko will fix the sound problems when
OK, please try this, then; change the HARVEST_RING_SIZE in
sys/dev/random/yarrow.h to a smaller power-of-2 (256 or 128 would
be good), and let me know how that helps-or-not.
Thanks!
M
If it helps at all, it's marginal. I still get skips.
On Sat, Jan 20, 2001 at 05:36:08PM +0200, Mark
I have a recent -current that hangs in 'make -j36 world'.
I am now running a UP kernel of the same date:
# uname -a
FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \
Mon Jan 15 18:42:30 PST 2001 \
root@celebris:/usr/src/sys/compile/CELEBRIS i386
dmesg attached.
tomdean
dmesg
On Sat, 20 Jan 2001, Mark Murray wrote:
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128 world
Do you have an easy way to narrow it down to CCD by doing the same
thing but
On 20-Jan-01 The Hermit Hacker wrote:
On Sat, 20 Jan 2001, Mark Murray wrote:
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128 world
Do you have an easy way to narrow it down to
In message [EMAIL PROTECTED], John Baldwin writes:
On 20-Jan-01 The Hermit Hacker wrote:
On Sat, 20 Jan 2001, Mark Murray wrote:
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128
On Fri, Jan 19, 2001 at 11:09:24PM +0100, Dag-Erling Smorgrav wrote:
"Crist J. Clark" [EMAIL PROTECTED] writes:
On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote:
It should also log a message if the hostname changes.
Should that be a responsibility of syslogd(8) or
On Sat, 20 Jan 2001, John Baldwin wrote:
On 20-Jan-01 The Hermit Hacker wrote:
On Sat, 20 Jan 2001, Mark Murray wrote:
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128
I'll confirm a hang on both alpha i386 (both SCSI, qlogic ahc resp). The
i386 was SMP. The Qlogic wasn't. Both were hung with phk's make -j 256
foolery.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"Crist J. Clark" [EMAIL PROTECTED] writes:
How about just logging a sethostname(3) call?
Still doesn't help. There are (at least) two different ways of setting
the hostname, one being a syscall and the other being a sysctl. One
could of course have the kernel print a message to the console
Is it just me or does 'syslogd -s' exhibit just a little bit too
much paranoia about allowing socket connections? I was futzing
with a Perl script that needed to syslog(3) some stuff and after
much hair pulling I realized that 'syslogd -s' didn't even allow
connections from localhost.
Steve Price [EMAIL PROTECTED] writes:
Is it just me or does 'syslogd -s' exhibit just a little bit too
much paranoia about allowing socket connections? I was futzing
with a Perl script that needed to syslog(3) some stuff and after
much hair pulling I realized that 'syslogd -s' didn't even
On Sat, Jan 20, 2001 at 09:20:39PM -0800, Crist J. Clark wrote:
#
# You can write to the /dev/log (usually symlinked to /var/run/log)
# socket with '-s' set.
#
# If you want to or need to use network sockets,
#
# # syslogd -a localhost
#
# Should provide the behavior you want. As you noted
Steve Price [EMAIL PROTECTED] writes:
Aha! I must have read that manpage a dozen times and I didn't catch
on, but if I do this it works like I would expect even with '-s'.
...and even with -ss, which you might as well use unless you intend to
log *to* remote hosts, or are sufficiently
Hey all,
I've lately been trying to dig into why OpenPackages make(1) currently
doesn't compile on FreeBSD but does on OpenBSD. There is a (very
slight) difference between their sys/time.h headers.
The timespec* stuff is hidden behind the _KERNEL aura on FreeBSD, but
not on OpenBSD. This is
Hi,
After /boot/loader is moved to /boot/loader.old, the install of the new
/boot/loader can fail for whatever reason, leaving a computer that
cannot automatically bootup, since someone has to type in
/boot/loader.old at the boot prompt. I suggest that if the boot process
can't find /boot/loader
On Sat, Jan 20, 2001 at 11:39:37PM -0600, Steve Price wrote:
On Sat, Jan 20, 2001 at 09:20:39PM -0800, Crist J. Clark wrote:
#
# You can write to the /dev/log (usually symlinked to /var/run/log)
# socket with '-s' set.
#
# If you want to or need to use network sockets,
#
# # syslogd
How should I install XFree86 4.0.2 on a system running a -current snapshot
from January 20? I tried downloading the binaries from xfree86.org, but
Xinstall.sh complained that my extract file was bad (it wasn't), and when I
ran 'sh Xinstall.sh -check' it told me that "binaries are not
subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
32 matches
Mail list logo
