Re: Out of file descriptors ??
On Sat, 26 Jun 1999 09:21:59 GMT, Ben Rosengart wrote: > I am not fond of the new defaults/rc.conf system. Your objection is far too late, I'm afraid. The change makes staying STABLE and staying CURRENT much easier than it was before and has met with resounding approval, although it took a few die-hards a while to see the wisdom of it. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP! Inetd wrapping OFF by default
Hi folks, I've just committed a change to inetd that will effectively turn TCP Wrapping off for anyone who has an installed /etc/rc.conf that specifies an inetd_flags value, as well as anyone who makes world without running mergemaster to update /etc/defaults/rc.conf . This will not be a problem for most people. Inetd now takes command-line options to enable wrapping. This was a decision taken with the approval of our release engineer in an attempt to revert a backward-compatibility problem introduced in 3.2-RELEASE. The relevant changes to the manpage follow: " SYNOPSIS inetd [-d] [-l] [-w] [-c maximum] [-C rate] [-a address] [-p filename] [-R rate] [configuration file] [...] DESCRIPTION [...] -w Turn on TCP Wrapping. If this option is specified twice, internal services will also be wrapped. See the IMPLEMENTATION NOTES section for more information on TCP Wrappers support. [...] IMPLEMENTATION NOTES When given the -w option, inetd will wrap all services specified as ``stream tcp nowait'' except for ``internal'' services. If the -w option is given twice, such ``internal'' services will be wrapped as well. When wrapping is enabled, the tcpd daemon is not required, as that functionality is builtin. For more information on TCP Wrappers; see the relevant documentation ( hosts_access(5) ). " When this change is merged to STABLE, the release notes will be updated and a fat HEADS UP will be posted to the freebsd-stable mailing list. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: place of logfile for cron (PR 7682) - move it?
On Sat, 26 Jun 1999 11:57:17 -0400, Mikhail Teterin wrote: > I'd, probably, put a symlink from the old location to the new one... That's something you could do on your own machines, but I sincerely hope we _don't_ do that to installworld and future releases. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Ports problems
On Sat, 26 Jun 1999 22:50:31 +0200, FreeBSD mailing lists wrote: > Hi, I just wondered if it was a problem with my installation or in > general, but is anyone else here having problems with ports being > dependant on glib12.2 and ports installing glib12.3 instead? Try mailing [EMAIL PROTECTED] . When you do, be sure to give a few examples of "a LARGE number of the ports". Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! Inetd wrapping OFF by default
On Sun, 27 Jun 1999 18:37:51 MST, Doug wrote: > This is going to sound like I'm attacking sheldon, but I'm not > since he's already stated that the got approval for this change from > Jordan. Jordan will be the first to admit that he's been wrong before and I have a thick skin. > First, the setting in /etc/defaults/rc.conf should default to > off, as defaulting it to on violates POLA for the many many people who > haven't updated to 3.x from 2.2 yet. If we were integrating TCP Wrapper support into the base system for the very first time, I'd agree with you. However, we've already had a release go out with an inetd that wrapped by default. This is a situation in which we can't make _everyone_ happy. For the particular case you've provided, anyone who upgrades from 2.2 to 3.3 without reading the release notes will get what's coming to him. > Also, if the decision is made to leave it on by default, there should > be a hosts.allow file installed by default that has nothing but "ALL : > ALL" in it. We already have a hosts.allow that effectively allows everything. > Second, this command line switch is horrible UI design for > several reasons. First, any command line option that requires that > the same flag be applied twice is bad design, historical precedents > aside. That's an unfortunately timed revelation for me. I feel like I've seen it in a number of programs, although the only one I can remember is ftpd(8). I used that program as a reference, not knowing that it was bad design. :-( > Second, what if I want to wrap my internal services, but not wrap my > external ones? Then you want something that the guys working on the code, who use inetd quite a lot, didn't think of. They probably made the assumption that real-world scenarios like that don't exist. > I propose that the -w flag be changed to take parameters. To > start with, you would have [-w <[e] [i]>] to control wrapping for > external and internal services respectively. This makes my skin crawl, but that's probably just because I know what the code looks like. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is freebsd.org Down?
On Tue, 29 Jun 1999 08:59:10 MST, Thomas Dean wrote: > Is www.freebsd.org down? It was for a while, it isn't at the time of this posting and freebsd-current wasn't a good choice of mailing list. :-) Later, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! Inetd wrapping OFF by default
On Wed, 30 Jun 1999 00:41:54 MST, Doug wrote: > > This is a situation in which we can't make _everyone_ happy. For the > > particular case you've provided, anyone who upgrades from 2.2 to 3.3 > > without reading the release notes will get what's coming to him. > > That's always true, but traditionally it's been a primary goal of the > project to make these kinds of changes as minimal as possible. Okay, so let's say we've got Joe Bloggs upgrading from 2.2.8 to 3.3 . He doesn't read the release notes, so he doesn't notice that inetd now wraps by default. The impact on him is: 1) Inetd makes unnecessary calls to hosts_access(). 2) Previously unwrapped internal services are suddenly and mysteriously wrapped. The first is a performance issue and isn't a big deal, given that Joe didn't read the release notes. The second _is_ an issue. However, it's got to be an issue for _someone_; either for Joe or for the guy who's upgrading from 3.2-RELEASE to 3.3-RELEASE. To me, it just doesn't make sense to pander to the people who've lagged behind STABLE. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! Inetd wrapping OFF by default
On Wed, 30 Jun 1999 12:07:31 +0200, Sheldon Hearn wrote: > Okay, so let's say we've got Joe Bloggs upgrading from 2.2.8 to 3.3 . He > doesn't read the release notes, so he doesn't notice that inetd now > wraps by default. The impact on him is: Damnit! I forgot the most important part of my argument -- people upgrading from 2.2.8 and don't read the release notes are going to have an /etc/rc.conf that sets inetd_flags="", hence their systems won't wrap! Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HELP!!! -CURRENT libtool problem.
On Mon, 05 Jul 1999 13:42:39 MST, "Jordan K. Hubbard" wrote: > I also make this point now and with such force because various signs > and portents indicate that -current is about to become a dangerous > place again for awhile, and a lot of people who really don't have the > cojones to run -current are going to find this out rather abruptly and > painfully. :-) Haha! The secret to surviving CURRENT without big cojones is to watch cvs commit mail very closely. The stuff I've been seeing for the last couple of weeks has kept my hands off the trigger as far as rebuilding kernel or the world have been concerned. :-P Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/i386/linux linux_misc.c
I think you folks are in for a big surprise if you think that the proposed rtfm(1) tool will save you any heartache. Most of the times that people come to you for help, it's because they lack one or more of the time and inclination to help themselves. The proposed tool's inappropriate name reinforces that it will serve as nothing more than a BOFH plushie. Know that this has _not_ been met with unanimous acceptance. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: Inetd wrapping option syntax changed
Hi folks, About a week ago, we made inetd's TCP Wrapper support a command-line option instead of a compile-time option. While this was met with unanimous approval, a number of people objected to the limited -w option. I've just committed a change that allows wrapping for each of internal and external services to be enabled independantly of the other. If you have inetd_flags="-w -w" in /etc/rc.conf, you'll need to change it to: inetd_flags="-w -W" or remove the option altogether, since this is the defaults/rc.conf behaviour anyway. As with the previous change, folks who don't mergemaster after a make world are going to experience problems with subsequent reboots. :-) Thanks to everyone who put effort into persuading me against the original command-line syntax. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp passive mode
On Sun, 11 Jul 1999 22:27:04 PST, Adam Wight wrote: > Why was the FTP_PASS_MODE logic changed? This forces everyone who > uses active connections to alter their environment... Please let's not get into this again. This was discussed to death on the hackers mailing list last week and the week before. The change is not going to be reverted. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: zone: entry in free
On Thu, 15 Jul 1999 21:18:03 +0100, Dominic Mitchell wrote: > This of course begs the question, under what circumstances *should* one > use INVARIANTS? This has been explained to me before as "when you have the time and inclination to look into any problems that this might cause or highlight." Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: inetd looping (from cvs-all)
On Fri, 23 Jul 1999 14:33:43 -0400, "John W. DeBoskey" wrote: > PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND > 198 root 105 0 908K 584K RUN141.8H 95.70% 95.70% inetd [...] > There are NO messages in /var/log/messages. > > The -l option doesn't seem to work, and the -d option seems > to cause inetd to lock up. I can't comment on the -d option locking up, other than that it may have conspired with a bug to produce a far too busy inetd. :-) I introduced a bug in inetd.c rev 1.57, where code intended to serve dgram services was used for servicing stream services as well. I believe that DES fixed this problem a few hours ago. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PR 12634
On Sat, 24 Jul 1999 18:47:37 +0200, Nick Hibma wrote: > PR 12634 mentions the increase of MAXSYMLINKS (src/sys/sys/param.h) to > 64. There has to be a limit. Like so many limits, it has to increase as more and more people bump up against it, provided: 1) They're not bumping up against it just because they've done something silly. 2) They've all hiked the limit in question locally and haven't observed any problems for a while. I don't think we clear either of these two with this PR. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IDE_DELAY
On Sat, 24 Jul 1999 20:26:56 +0200, Thomas Schuerger wrote: > I've set the option > > IDE_DELAY=1500 Did you read the warning in LINT about this one? # Setting this below 1 violate the IDE specs, but may still work for # you (it will work for most people). _May_ still work for you implies may not. What happens when you set it to 1? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD-current and Netscape Java
[Hijacked from the freebsd-current mailing list] On Sat, 24 Jul 1999 19:46:52 -0400, Bill Pechter wrote: > Are there any tricks to getting Java in Netscape running with > FreeBSD --current. Just because CURRENT is the platform you use when you encounter a problem, doesn't mean that the freebsd-current mailing list is the right place to discuss it. I'd suggest the freebsd-ports, assuming good old freebsd-questions isn't good enough for you. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: whereis broken?
On Sun, 25 Jul 1999 14:12:53 -0400, Dan Moschuk wrote: > whereis anything yields.. > > Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Staleness. Unfortunately, the whereis(1) manpage doesn't tell you to look at the manpath(1) manpage. Do so now and you'll see that you should check your /etc/manpath.config and your $MANPATH environment variable. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: whereis broken?
On Sun, 25 Jul 1999 20:12:46 +0200, Sheldon Hearn wrote: > > Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! > > Staleness. It's been pointed out to me in private mail that current's manpath.config is broken. If nobody's looked at it by tomorrow, I'll do so then. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: whereis broken?
On Sun, 25 Jul 1999 21:33:55 +0200, Mark Murray wrote: > > It's been pointed out to me in private mail that current's > > manpath.config is broken. > > Fixed. Hi Dan, You'll need rev 1.11 of src/gnu/usr.bin/man/manpath/manpath.config, but you should be able to get away with commenting out those MANDATORY_MANPATH lines that reference /usr/local . Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: whereis broken?
On Mon, 26 Jul 1999 18:48:15 +0200, Jeroen Ruigrok/Asmodai wrote: > I got /usr/local ref's in my /etc/manpath.config, the MANDATORY_MANPATHs, > using man, whatis, whereis or other utilities that reference manpath.config > I got no problem whatsoever. This is -CURRENT from last night. You have perl5 packages or ports installed into /usr/local . :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sh still is not working for MAKEDEV
On Mon, 02 Aug 1999 22:34:19 +0300, Maxim Sobolev wrote: > Does anybody investigating what wrong with the sh in the -current? As I > reported earlier it still fails to correctly process MAKEDEV script. Perhaps someone should have come out and said this last time: I can't reproduce the problem. A buddy of mine in the office says this is exactly what he got a little while ago after compiling with -O2, but you've already stated that you're sure you didn't do this. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Fri, 13 Aug 1999 09:48:47 EST, "Matt Crawford" wrote: > load kernel > load -t splash_image_data daemon_640.bmp > load vesa > load splash_bmp > boot Why boot and not autoboot? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SUPFLAGS in /etc/make.conf
On Fri, 13 Aug 1999 15:17:47 -0400, Ben Rosengart wrote: > I submit that putting "-z" in here is silly, because the sample cvsup > config files turn on compression, and suggest commenting it out if you > have a fast link. It seems counterintuitive that one can comment out > the compression in the standard supfiles and then have it enabled by > default with "make update" anyway. This looks like PR material. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel hacker tasks seek interested hackers
On Sun, 15 Aug 1999 12:27:57 +0200, Poul-Henning Kamp wrote: > 4. [not quite easy] The CCD device ditto. > Earn brownie points: Make ccdconfig use sysctl instead of > libkvm to read back configuration. Anyone who decides to tackle this one is likely to have the wherewithall to test a PR which I can't right now -- PR 10077: PR: 10077 Class:kern Synopsis: dd'ing a ccd stripped partition sometimes hangs in physstr Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ccd bugs (was: Kernel hacker tasks seek interested hackers)
On Wed, 18 Aug 1999 08:39:35 +0930, Greg Lehey wrote: > Why did you take this one? Because I thought it was a simple problem with dd. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ccd bugs (was: Kernel hacker tasks seek interested hackers)
On Wed, 18 Aug 1999 09:19:20 -0400, "Mark J. Taylor" wrote: > There is a long as a parameter to ccdbuffer that needs to be a u_long. > Otherwise, you'll get panics (can't remember where). > Basically, bcount needs to be a u_long in all cases. Que? Are you sure? That means you want to change struct buf, where b_bcount is declared as long, as well? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: devtoname
On Wed, 18 Aug 1999 08:46:09 -0400, Bill Fumerola wrote: > As a result of a discussion between myself, Bruce Evans, and Poul-Henning > Kemp, there now exists a kernel function: > > char *devtoname (dev_t dev) Cool. This can be used to sort out the obscure message you get when you attempt a kernel dump to a bad partition. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
REQ: Test /etc/rc clean-up
Hi folks,
I have a diff for src/etc/rc that I'd like to have had used on a few
machines before I commit it. I'm pretty sure I haven't made any mistakes
with my changes, but you can never be too careful, right?
The diff homogenizes the manner in which variables are tested and is
more careful about using variables in a manner that avoids potential
problems that are unlikely to occur. I see it as a mostly cosmetic, but
healthy change.
Ciao,
Sheldon.
Index: rc
===
RCS file: /home/ncvs/src/etc/rc,v
retrieving revision 1.193
diff -u -d -r1.193 rc
--- rc 1999/08/06 06:22:43 1.193
+++ rc 1999/08/17 15:36:04
@@ -45,15 +45,15 @@
ccdconfig -C
fi
-if [ X$start_vinum = XYES ]; then
+if [ X"${start_vinum}" = X"YES" ]; then
vinum start
-elif [ -n "$vinum_drives" ]; then
- vinum read $vinum_drives
+elif [ -n "${vinum_drives}" ]; then
+ vinum read ${vinum_drives}
fi
swapon -a
-if [ $1x = autobootx ]; then
+if [ X"$1" = X"autoboot" ]; then
echo Automatic reboot in progress...
fsck -p
case $? in
@@ -95,7 +95,7 @@
# diskless boot it does not have to be.
#
-if [ "X$root_rw_mount" != "XNO" ]; then
+if [ X"${root_rw_mount}" != X"NO" ]; then
mount -u -o rw /
fi
@@ -106,7 +106,7 @@
umount -a >/dev/null 2>&1
-if [ "X$early_nfs_mounts" != "XYES" ]; then
+if [ X"${early_nfs_mounts}" != X"YES" ]; then
mount -a -t nonfs
else
mount -a
@@ -119,9 +119,9 @@
# Run custom disk mounting function here
#
-if [ "X$diskless_mount" != "X" ]; then
- if [ -f $diskless_mount ]; then
- sh $diskless_mount
+if [ X"${diskless_mount}" != X"" ]; then
+ if [ -f ${diskless_mount} ]; then
+ sh ${diskless_mount}
fi
fi
@@ -148,9 +148,9 @@
fi
# Add additional swapfile, if configured.
-if [ "x$swapfile" != "xNO" -a -w "$swapfile" -a -b /dev/vn0b ]; then
- echo "Adding $swapfile as additional swap."
- vnconfig /dev/vn0b $swapfile && swapon /dev/vn0b
+if [ X"${swapfile}" != X"NO" -a -w "${swapfile}" -a -b /dev/vn0b ]; then
+ echo "Adding ${swapfile} as additional swap."
+ vnconfig /dev/vn0b ${swapfile} && swapon /dev/vn0b
fi
# set sysctl variables early as we can
@@ -195,7 +195,7 @@
#
# See also the example of another cleanup policy in /etc/periodic/daily.
#
-if [ "X${clear_tmp_enable}" = X"YES" ]; then
+if [ X"${clear_tmp_enable}" = X"YES" ]; then
echo clearing /tmp
# prune quickly with one rm, then use find to clean up /tmp/[lq]*
@@ -217,7 +217,7 @@
# start system logging and name service (named needs to start before syslogd
# if you don't have a /etc/resolv.conf)
#
-if [ "X${syslogd_enable}" = X"YES" ]; then
+if [ X"${syslogd_enable}" = X"YES" ]; then
# Transitional symlink (for the next couple of years :) until all
# binaries had a chance to move towards /var/run/log.
if [ ! -h /dev/log ] ; then
@@ -233,21 +233,21 @@
# enable dumpdev so that savecore can see it
# /var/crash should be a directory or a symbolic link
# to the crash directory if core dumps are to be saved.
-if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then
+if [ X"${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then
dumpon ${dumpdev}
echo -n checking for core dump...
savecore /var/crash
fi
-if [ -n "$network_pass1_done" ]; then
+if [ -n "${network_pass1_done}" ]; then
network_pass2
fi
# Enable/Check the quotas (must be after ypbind if using NIS)
-if [ "X${enable_quotas}" = X"YES" ]; then
+if [ X"${enable_quotas}" = X"YES" ]; then
# Only check quotas if they have been previously enabled, and requested
-if [ "X${check_quotas}" = X"YES" ]; then
+if [ X"${check_quotas}" = X"YES" ]; then
echo -n 'checking quotas:'
quotacheck -a
echo ' done.'
@@ -258,7 +258,7 @@
echo ' done.'
fi
-if [ -n "$network_pass2_done" ]; then
+if [ -n "${network_pass2_done}" ]; then
network_pass3
fi
@@ -274,7 +274,7 @@
"password file may be incorrect -- /etc/ptmp exists"
fi
-if [ "X${accounting_enable}" = X"YES" -a -d /var/account ]; then
+if [ X"${accounting_enable}" = X"YES" -a -d /var/account ]; then
echo 'turning on accounting'
if [ ! -e /var/account/acct ]; then
touch /var/account/acct
@@ -287,7 +287,7 @@
if [ -x /sbin/ldconfig ]; then
if [ X"`/usr/bin/objformat`" = X"elf" ]; then
_LDC=/usr/lib
- for i in $ldconfig_paths; do
+ for i in ${ldconfig_paths}; do
if test -d $i; then
_LDC="${_LDC} $i"
fi
@@ -301,7 +301,7 @@
# Default the a.out ldconfig path.
: ${ldconfig_paths_aout=${ldconfig_paths}}
_LDC=/usr/lib/aout
- for i in $ldconfig_paths_aou
Re: "The Matrix" screensaver, v.0.2
On Fri, 20 Aug 1999 19:34:31 +0200, Andrzej Bialecki wrote: > Due to unexpected demand (I did it mostly as a distraction from real > work), I backported this screensaver to 3.2-RELEASE (don't know about > STABLE), and corrected some inconsistencies. I added also binary versions > to the archives. You really do get around, huh? From maintaining the bloat-free PicoBSD to contributing the ultrabloat candidate of the year. ;-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: REQ: Test /etc/rc clean-up
On Fri, 20 Aug 1999 11:59:05 MST, Doug wrote: > However I'd REALLY like to emphasize again that if we're going to do > this the proper fix is to use case wherever possible. > > I have offered several times to do the work if it has a chance of > being committed, that offer is still good. Hi Doug, The several times before, did folks come up with objections, or was it just a case of mass apathy? :-) I don't want to piss into the wind of wisdom from ages past, but I like the sound of what you're suggesting. I guess if there _are_ sensible objections, they'll crop up when you send a diff? Oh, and thanks for the offer. You no doubt understand that this is probably not something that'll get pumped straight into CURRENT without a goodly number of "works for me" messages in prviate mail from folks using lotsa weird setups. ;-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: REQ: Test /etc/rc clean-up
On Sat, 21 Aug 1999 16:59:38 MST, "Jordan K. Hubbard" wrote: > http://www.freebsd.org/~jkh/etc.diffs.fix-it-right > > Which I've sent to Sheldon for review but haven't heard anything > back from him yet. Universal Week-end Time. :-P Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird differences in rc5 behavior on -current vs. -stable
On Sat, 21 Aug 1999 19:11:33 MST, Doug wrote: > I have a 3.2-Stable and a 4.0-Current system at home, both > running rc5des. On both systems I set the priority in the rc5 options > menu to '0', indicating lowest possible priority. On the -Stable > system it's running at nice level '0', but it seems to be taking > advantage of the idprio stuff since in general my system seems much > "snappier," than when I was running 2.2.8 on the exact same machine. I think you'll find PR 12381 explains these results quite well. The fix bde applied to CURRENT and backported to STABLE were not backported to RELENG_2_2. If you look at the difference between RELENG_2_2 and RELENG_3, I think you'll see why. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: question about egcs
On Wed, 29 Dec 1999 14:47:12 GMT, Jonathon McKitrick wrote: > Will egcs affect the size of the kernel or any other compiledcode? Yes. Try it out for yourself and have a look, or hunt the -current mailing list archives. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: snapshot stability
On Wed, 29 Dec 1999 15:31:38 GMT, Jonathon McKitrick wrote: > As of right now, which would that be? The august CD snapshot release or > the one available on the cvs servers right now? If I were you, I'd hold out for 4.0-RELEASE, since it's just around the corner (January some time). Otherwise, just inhale and prepare to bleed. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lint still broken in -current (due to cpp).
On Fri, 07 Jan 2000 11:22:17 GMT, David Malone wrote: > I tried lint again since David O'Brien committed the new /usr/bin/cpp, > but it turns out that lint is hardwried to use /usr/libexec/cpp. > I changed it to use /usr/bin/cpp, and it works, but gives some > error messages. I submitted a patch on the cvs-all list yesterday. No feedback yet. Ciao, Sheldon. On Mon, 03 Jan 2000 19:48:09 PST, "David E. O'Brien" wrote: > Modified files: > usr.bin Makefile > gnu/usr.bin/cc Makefile > gnu/usr.bin/cc/cpp Makefile > Removed files: > usr.bin/cpp Makefile cpp.notraditional.sh cpp.sh > Log: > Turn on a new /usr/bin/cpp that is a true binary rather than a shell script > wrapper. /usr/bin/cpp knows about all the GCC predefined symbols and has > the functionality of the previous EGCS 1.1.2 /usr/libexec/cpp. I think lint(1) might work with this given the following small patch. Ciao, Sheldon. Index: xlint.c === RCS file: /home/ncvs/src/usr.bin/xlint/xlint/xlint.c,v retrieving revision 1.7 diff -u -d -r1.7 xlint.c --- xlint.c 1999/01/25 11:25:24 1.7 +++ xlint.c 2000/01/06 14:03:29 @@ -321,7 +321,6 @@ libsrchpath = xcalloc(1, sizeof (char *)); appcstrg(&cppflags, "-lang-c"); - appcstrg(&cppflags, "-undef"); appcstrg(&cppflags, "-$"); appcstrg(&cppflags, "-C"); appcstrg(&cppflags, "-Wcomment");
NTP4 manual pages committed
Hi folks, Those of you who whined about the absence of manual pages in the NTP4 package recently imported into the base system, please check your commit mail. Selected pages have been transcribed from the HTML documentation and committed to the base system. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** chown&chgrp moved again
On Tue, 11 Jan 2000 15:49:54 EST, Kelly Yancey wrote: > David, I just noticed that this note in 4.0's RELNOTES about the > relocation doesn't appear applicable anymore: You're right. I've removed the comment from the RELNOTES.TXT for the i386 and alpha. Thanks! Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Additional option to ls -l for large files
Folks, this is getting a little silly. Can't we cut all the esoteric mumbo-jumbo and agree to do it the same way that gnuls and our own existing df do it? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NTP4 manual pages committed
On Wed, 12 Jan 2000 22:10:07 +0100, Jean Louis Ntakpe wrote: > # Server is a Boeder DCF77 receiver > server 127.127.8.41 Does your server look like any of those listed in reflock.htm? Most of the documentation for your application has not been transcribed into manual page format. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lint not working on -current?
On Thu, 13 Jan 2000 13:52:50 EST, "Mr. K." wrote: > First of all, forgive me for being stupid, if that's what it turns out it > was, but I can't seem to get lint to work on -current (though it works > fine on -stable). > > > lint -V pvselect.c You'd want lint -i, since we don't install any .ln files into /usr/libdata/lint. But yes, lint is actually broken for the new cpp as well. I mailed publically a patch to fix this last week. Not a single follow-up since then, so I'll commit it now. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Making sure /var/tmp/vi.recover exists during reboot
On Tue, 11 Jan 2000 11:35:27 +0100, Trond Endrestol wrote: > This is something you might want to put in /etc/rc in both -stable > and -current. > > Scenario: > > /tmp is MFS, > /var/tmp, /usr/tmp and /usr/local/tmp are symlinks to /tmp, Not until someone can explain how making /var/tmp a symlink to /tmp is sensible, given that /var/tmp is documented as containing "temporary files that are kept between system reboots" (see hier(7)). So basically, no. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Making sure /var/tmp/vi.recover exists during reboot
Let's try not to cross-post this any more, eh? On Fri, 14 Jan 2000 11:55:55 +0200, Adrian Penisoara wrote: > Then let's get the other way around (change in /etc/rc): No, you're missing the point. /var/tmp is expected to survive reboots. That's its definition according to the hier(7) manual page. If you choose to break that functionality, don't expect anyone to make gratuitous changes to the FreeBSD startup scripts to support your oddball configuration. :-) > And let me notice that the original script assumes existence of this > directory whereas if I don't run vi I won't get one... It does so because of the definition of /var/tmp . > I use this small hack to get around the ugly error message I get every > time I boot with MFS mounted /var/tmp -- suited me well until now. You shouldn't be mounting /var/tmp in MFS, because a memory file system does not survive a reboot -- that's where you've gone wrong. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Making sure /var/tmp/vi.recover exists during reboot
On Fri, 14 Jan 2000 11:07:23 +0100, Trond Endrestol wrote: > If I want something preserved between reboots, I'll use /var/otmp > which is the original /var/tmp or my own ~/tmp directory. Do whatever grooves your plumes, just don't expect the startup scripts to be hacked around to support your disregard for the hier(7) manual page. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Making sure /var/tmp/vi.recover exists during reboot
On Fri, 14 Jan 2000 10:12:54 EST, Vivek Khera wrote: > If you don't like the warning, just delete the recovery procedure > rather than creating the directory. It does no good for you to try to > recover something that will never be there. Exactly. The only thing that comes out of this patch is we support an administrative mistake that leads naive users to believe that vi recovery on reboot is going to work as expected. This is a stupid idea. I wish the person who came up with it would just acknowledge that he's doing something inappropriate and move on, rather than insisting that the rest of us introduce a bad idea into our systems to support his bad practice. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world breaks in /usr/src/usr.bin/xlint
On Sat, 15 Jan 2000 12:02:09 +0100, Marcel Moolenaar wrote: > No. build-tools are those tiny little utilities that are part of the > sources and are only used to build the sources. Okay, so how do we boot-strap lint? Ultimately, the build of the lint libraries requires a working lint, which most people don't have at this stage. However, the lint binary itself doesn't require boot-strapping. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lint not working on -current?
On 15 Jan 2000 21:59:14 +0900, NAKAJI Hiroyuki wrote: > SH> I mailed publically a patch to fix this last week. Not a single > SH> follow-up since then, so I'll commit it now. :-) > > Related to this? Today's buildworld fails. Indeed. When I tested the change I made, I already had a working lint binary installed in /usr/bin, so I didn't notice this one. I backed out the offending change over the week-end. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU texinfo has been upgraded to 4.0
On Mon, 17 Jan 2000 14:22:39 +0200, Ruslan Ermilov wrote: > I've just upgraded our GNU texinfo to the latest available version 4.0. > Please see src/contrib/texinfo/NEWS for what has been changed since 3.12. Excellent! src/contrib/texinfo/NEWS: . New markup commands: @env (for environment variables), @command (for command names), @option (for command-line options). This should allow us to back out rev 1.22. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: installworld fails with setresuid.2.gz
On Tue, 18 Jan 2000 13:46:36 +0900, Munehiro Matsuda wrote: > /usr/share/man/man2/setresgid.2.gz -> /usr/share/man/man2/setresuid.2.gz > ln: /usr/share/man/man2/setresuid.2.gz: No such file or directory > *** Error code 1 My fault. It's fixed in rev 1.75 of src/lib/libc/sys/Makefile.inc . Sorry for the inconvenience. :-( Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
On Mon, 17 Jan 2000 21:53:10 PST, Kris Kennaway wrote:
> +.if defined(WITH_RSA) && ${WITH_RSA} == YES
> + /usr/bin/touch /etc/ssl/openssl_hasrsa
Um, are you sure you want that hard path, /etc/ssl ? Shouldn't there be
a ${DESTDIR} in there? What do you need this for?
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Is texinfo needed for buildworld with -DNOINFO ?
On Tue, 18 Jan 2000 19:14:19 +0900, Munehiro Matsuda wrote: > It seems that texinfo is compiled as cross-tools for buildworld. > But, is it really needed when -DNOINFO has been specified? It's arguable, so I'd go with the status quo -- always build and install the texinfo program, even if info files are not to be installed. > Following patch seems to work for me. Only because you have NOINFO defined. Try without it. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On 18 Jan 2000 03:03:09 PST, Satoshi - Ports Wraith - Asami wrote: > Maybe it's better to make it an error to not specify it (yes, killing > "make world" and stuff, that's what UPDATING is for). There's no better time for doing so than prior to 4.0-RELEASE. :-) Does sysinstall set this one? If not, it should. Then we can stop worrying about it. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: installworld fialed
On Wed, 19 Jan 2000 10:51:50 EST, "T. Hsiang" wrote: > Does anyone have the same problem? [...] > install-info: menu item `makeinfo' already exists, for file `makeinfo' > *** Error code 1 Are you getting this with rev 1.131 of src/Makefile.inc1? | revision 1.131 | date: 2000/01/18 11:00:24; author: ru; state: Exp; lines: +4 -4 | Finally resolve the texinfo issue by moving it | from the cross-tools to the bootstrap-tools. | | Requested by: bde, marcel I make and installed world successfully with this version about 15 hours ago. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current not compiling.
On Thu, 20 Jan 2000 18:53:12 CST, Raul Zighelboim wrote: > the last 3 days of current 'make buildworld' have ended with: > > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' So you haven't been reading your -current mail for 3 days? Bad pussycat. :-) As stated several times on this mailing list by the guy who knows it's a problem and is working on it, the openssl build in CURRENT is picking up libcrypto in /usr/local/lib. Either pkg_delete or move aside your openssl installation. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Tue, 25 Jan 2000 01:46:01 CST, Kevin Day wrote: > A more direct patch would have been: > > -# NOTE: The hosts.deny file is not longer used. Instead, put both 'allow' > +# NOTE: The hosts.deny file is no longer used. Instead, put both 'allow' I'm concerned about the authenticity of this comment. It looks to me like a comment on commonly accepted usage convention. It looks to me like hosts_access(3) still handles hosts.deny in the same way that it always has. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: This morning's make world.
On Wed, 26 Jan 2000 07:35:32 PST, Edwin Culp wrote: > This morning's make world What are you trying to achieve with these e-mail messages? If you're looking for confirmation that ``make world'' is broken, then "Yes, it is." :-) And then when you get past _that_, you'll break in the includes, for which Peter Wemm posted a tentative fix which doesn't work 100%. :-) Watch your cvs-all mail for a commit on src/include/Makefile (something more recent than rev 1.107) and try again once you've got that. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How can I use current release of FreeBSD?
On Tue, 25 Jan 2000 15:27:13 +0300, Grigory Kljuchnikov wrote: > How can I update 4.0-2110 directoty tree to 4.0-2124? > And how do these updates do properly? Where can I see more about this? The short answer is that you don't. Just wait for 4.0-RELEASE to come out in a few weeks. The long answer is contained in the FreeBSD Handbook, available online at: http://www.freebsd.org/handbook/ In particular, see the section titled The Cutting Edge: FreeBSD-current and FreeBSD-stable Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: y2k problem? naahhh...
On Tue, 25 Jan 2000 21:19:16 EST, John Baldwin wrote: > Ok then: > > 'egrep -v '^(---|+++|@@|[+-]#)', geez, am I the only one who knows regex? Are you the only person who doesn't know sed? ;-) My untested guess (since we all seem to be mouthing off the first thing that comes to mind) is sed 's/^\([^:#+@-][^:]*\):[^:]*:/\1:(password):/' This assumes that empty usernames and usernames which do not begin with an alphanumeric character won't appear. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Wed, 26 Jan 2000 02:02:36 +1100, Andy Farkas wrote: > > So you'll notice that this file is an example and *demands* your > > attention in configuring your system properly. > > Change it to hosts.allow.sample then? No hosts.allow file is essentially > the same as the ALL:ALL:allow rule, no? No. In the absence of a hosts.allow file, hosts_access(3) denies all. Can we please move onto something else now. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Thu, 27 Jan 2000 03:57:51 +1100, Andy Farkas wrote: > > No. In the absence of a hosts.allow file, hosts_access(3) denies all. > > Not according to what I read in 'man 5 hosts_access' - especially the > second paragraph titled "ACCESS CONTROL FILES". Wtf?! You're right. I'm frightened now. > But...but... ITS SUCH AN EYE-SORE IMHO. While this thread has been fun? C'mon, look around, there are bigger fish to fry. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sendmail on current
On Wed, 26 Jan 2000 11:47:04 MST, Matt Miller wrote: > Chastisment humbly accepted. *chastise* :-) > The only references to sendmail that I see in the UPDATING file is > about the move of the sendmail.cf, which doesn't seem relevant. It's sorta relevant. > Since starting this email, I have created an /etc/mailer.conf. Should be /etc/mail/mailer.conf. There are two things that would have saved you from this problem (and the chastisement above :-) : 1) Reading your cvs-all mail. 2) Using mergemaster(1). Have fun. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd
On Thu, 27 Jan 2000 00:23:23 PST, "David O'Brien" wrote: > I think what you really want is: > > sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' Eeek, I don't know why I sent you that. It should have been: sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/' Sorry about that. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd
On Thu, 27 Jan 2000 04:11:38 PST, "Rodney W. Grimes" wrote: > > sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/' > > IMNSO sed is the wrong tool here, No arguments from me, since my awk skills are limited. However, I'll point out that sed is doing a decent job without turning into an invocation mess. The awk program you sent is much longer. Oh, and it produces absolutely no output whatsoever over here. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sendmail on current
On 26 Jan 2000 20:33:31 +0100, Eric Jacoboni wrote: > in CURRENT, /usr/sbin/sendmail is a symlink to /usr/sbin/mailwrapper > (see man mailwrapper). No, it's a hard link. I only mention this because your explanation makes it sound like mailwrapper generates much more overhead than it really does: > In CURRENT, the command 'sendmail' runs the mailwrapper program which, > in turn, runs the correct ones according to /etc/mail/mailer.conf (there's > an exemple in 'man mailer.conf'). Anyway, this guy's problem is just the location of mailer.conf, which you got right, so he should be fine. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sendmail on current
On 27 Jan 2000 15:25:55 +0100, Eric Jacoboni wrote: > No, not on my box (as far as i believe 'ls' and 'file' ;-) : > > % ls -l /usr/sbin/sendmail > lrwxr-xr-x 1 root wheel 21 26 jan 23:54 /usr/sbin/sendmail -> > /usr/sbin/mailwrapper My humble apologies. No more drugs for me. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: src/include/Makefile,v 1.109 is broken
On Thu, 27 Jan 2000 17:00:58 +0200, Ruslan Ermilov wrote: > An attached patch seems to fix the problem. Does anybody actually understand what's really going on in this file? Everyone uses the words "seems to" and "I think" when they're proposing fixes in this file. I propose that we hold out for a fix which is accompanied by comments that explain what the hell all these oddball variables are used for and why SHARED is overridden (or used at all in the buildworld case). Ruslan, if I misunderstood your words, please don't take offense. It's just that this'll be the 5th commit in this regard without comment from Marcel, who was responsible for rewriting most of this Makefile recently. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current is still broken as of 2000/01/27
On Thu, 27 Jan 2000 18:35:33 PST, Jason Evans wrote: > This is the same kind of breakage I caused when moving some definitions > into unistd.h. I would call it bootstrapping breakage, but others who know > the build system better claim it's avoidable. I think it _is_ avoidable. One way to avoid it is to try to make world and report the brekage to -committers, asking for help. This works best when you do it _before_ committing the change you're testing. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
On Thu, 27 Jan 2000 13:46:47 +0900, Yoshinobu Inoue wrote: > I just added debug flag check instead of changing syslog > level. > Could you please try the following patch to > usr.sbin/inetd/inetd.c ? I would expect the messages to be sent to stderr in debug mode. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Tue, 01 Feb 2000 13:48:57 +0600, Max Khon wrote:
> 2129:
> {set,get}flags have been added to the tree for rather dubious
> reasons. An unintended side effect of this is that you must
> rebuild install before the rest of the world.
I'm surprised that this hasn't been resolved yet, but you're right;
the installworld target is still broken. Presumably, the reason for the
delay is that Joe is being very careful about testing the fix. :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Tue, 01 Feb 1900 13:18:21 +0100, I am not any sort of Fluffy wrote: > Just one problem, when I follow the instructions, in usr.bin/xinstall, > make depend all install clean ... > Then make installworld with my configuration dies in > install -c -o root -g wheel -m 444 install.1.gz /usr/share/man/man1 > install: install.1.gz: No such file or directory You're not following the instructions. :-) The instructions say you must "make depend all install clean before make world or buildworld" -- you're doing it _after_ buildworld. As a work-around, you could just do make depend all install and leave the clean out. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4->4.0 ... *almost* ...
On Wed, 02 Feb 2000 14:40:06 -0400, The Hermit Hacker wrote: > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development tools." --defentry="* >libcom_err: (com_err) If you fix this problem (by reading UPDATING) and run into another error in libcom_err, make sure you supped the src-crypto stuff as well. Using a CURRENT src-all and STABLE src-crypto will break world. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: update /etc (mergemaster) prior first boot after update (make world) ?
On Tue, 01 Feb 2000 22:29:58 +0100, Andreas Klemm wrote: > One additional question... What would be the best time to update > /etc after an update from 3.4-STABLE to 4.0-current ? > > - prior or > - after booting freshly compiled updated system ? Prior, obviously. Since much of /etc is used to get the system up and running, running mergemaster _before_ you boot that new world order will save you a reboot. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FTP_INTERNAL_LS
On Thu, 17 Feb 2000 00:24:00 +0800, Peter Wemm wrote: > You're 6 months late, this is already done: Hahaha! Suits me. I'm sure _someone_ will be unhappy that he can't offer an ftp service sans directory listings, but it certainly won't be me. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FTP_INTERNAL_LS
On Sat, 12 Feb 2000 10:52:22 +0100, "Patrick M. Hausen" wrote: > What about making FTP_INTERNAL_LS the default for 4.0? I'm very much in favour of this, but your second "BTW" suggestion did nothing for the cause. :-) Forget about changing any aspect of ftpd's chroot behaviour, but I'm very keen on having FTP_INTERNAL_LS the default for 4.0. It _does_ mean a change to the manual page... :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [PATCH]: Teach make.conf about FETCH_BEFORE_ARGS
On Sun, 20 Feb 2000 09:15:41 GMT, Nik Clayton wrote: > Here's another trivial patch that people might like to comment on before I > commit it. I'm doing more and more FreeBSD installs recently at various > client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.conf is just one of > those standard things you have to do if there's a firewall in place. I thought we'd all pretty much agreed that things like this don't belong in /etc/make.conf. I would have thought that this would be more at home in the system profile (as an environment variable) or in some ports-specific Makefile. I can remember discussions about such a Makefile, but I can't remember any resolution. Did we ever decide on a file to polute, other than /etc/make.conf? :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: quickie atapi dvd question
On Sun, 20 Feb 2000 14:31:43 PST, Kris Kennaway wrote: > I've not been able to play audio CDs ever since switching to the new ATA > drivers. Soren tells me there are two different ways to encode commands to > the drive, and no easy way to tell which one the drive expects :-( Welcome to it. This has been the case for me since the ata driver was first introduced. In my case, it's a cheap Creative labs piece of rubbish which says ATAPI on the casing but doesn't fully comply with the standard. Of course, this _is_ audio CD's we're talking about. Hardly mission-critical for the kind of person who buys cheap Creative Labs almost-ATAPI crap. ;-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installing linux_base 6.1
On Sun, 20 Feb 2000 21:55:22 PST, Matthew Dillon wrote:
> :As there becomes more ports around, this would simplify the job of
> :ports since we would now modify a ${PREFIX}-based file instead of
> :/etc/shells.
> I would be opposed to this for security reasons. The last thing I
> want to see are /usr/local versions of /etc/ files related to security.
Could you explain _why_? Is this just a matter of taste, or is there a
concrete security concern in play?
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: devices under 4.0
On Mon, 21 Feb 2000 01:16:49 MST, Warner Losh wrote: > MAKEDEV should be copied from src/etc/MAKEDEV to /dev before > starting the following: > > For N in the list of disks > MAKEDEV N # eg ad0 > for M in the list of slices > MAKEDEV NsMa# eg ad0s1a Why do we have to make slices ourselves? When this one bites you, it tears out quite a chunk. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't load if_xl module at startup
On Mon, 21 Feb 2000 18:47:48 +0100, [EMAIL PROTECTED] wrote: > When I load the if_xl module "by hand", all is well : the miibus is > also loaded and everything's fine (xl0 appears in ifconfig -a ...) > > When I try to load the if_xl and miibus modules via the loader, the > loader spins in : I'm answering because you don't seem to have gotten any other (public) answers, not because I'm sure of my facts. Quite a few people have reported problems loading modules from the loader (different modules, mind you). I'm pretty sure that I saw a clueful person suggest loading them out of /etc/rc.local for now. I can't check the archives to validate this, so you might want to think about it more than I have. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Mon, 06 Mar 2000 16:38:44 PST, R Joseph Wright wrote: > I just built a new world today and openssh does not appear to be > installed. I have the directories /etc/ssh and /etc/ssl but they are > empty. There is no /usr/bin/ssh. Last night's ``make world'' scored me a /usr/bin/ssh, but an empty /etc/ssh . I'm curious to know how /etc/ssh will be populated, since mergemaster won't pick up an sshd_config in src/etc . Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
On Mon, 06 Mar 2000 13:32:00 MST, Warner Losh wrote: > : This sounds bad. Are you referring to the -o syntax differences, or > : actual incompatabilities? > > I'm talking about the -o syntax difference specifically. How does the > following sound? What about the off-by-one hostkey length problem? Is it supposed to be possible to drop a "1024-bit" host key from the old ssh1 port into /etc/ssh ? We don't seem to be having much luck with that over here. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Tue, 07 Mar 2000 12:47:45 +0100, Anders Andersson wrote: > On Tis, Mar 07, 2000 at 11:09:12am +0200, Sheldon Hearn wrote: > > Last night's ``make world'' scored me a /usr/bin/ssh, but an empty > > /etc/ssh . I'm curious to know how /etc/ssh will be populated, since > > mergemaster won't pick up an sshd_config in src/etc . > > mergemaster sure did pick up ssh_config and sshd_config for me. ?!?! So it's been fiddled to know about the crypto directories? Wow, I'm impressed! *runs.off.to.mergemaster* Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Getty/Init weirdness
On Mon, 06 Mar 2000 21:35:31 PST, Christopher Nielsen wrote: > After booting, starting all services, and getting to the point where > init usually spawns the getty processes on ttyv[0-7], I get no login > prompts and no virtual terminal sessions. You should probably show us your /etc/ttys, not your kernel config. :-) Also, have a look in /var/log/messages for error messages from getty(8). Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Wed, 08 Mar 2000 09:56:56 PST, Doug Barton wrote: > mm only knows about what's in /usr/src/etc/Makefile. ssh_config and > sshd_config are in there, so if you run mm and you have those bits in > your tree it'll install them. Looks like mergemaster is much cleverer than I thought. Being called Mr Barton certainly _is_ a compliment! :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
tunefs -p doesn't work for read-write mounts
Hi folks, Shouldn't I be able to show the current tuneables for a given filesystem? # tunefs -p /usr tunefs: cannot work on read-write mounted file system This is on a recent CURRENT. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for usr.sbin/ntp/... (adds pcfclock)
On Sun, 27 Feb 2000 17:21:21 +0100, Alexander Leidinger wrote: > attached is a patch for usr.sbin/ntp/config.h and > usr.sbin/ntp/ntpd/Makefile. It adds reflock_pcf to the compiled in > drivers (current has support in the kernel for it). I think we should hold off on this until Sascha has fixed pcfclock for the Alpha. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: diskprep beta -- comments wanted.
On Fri, 03 Mar 2000 16:45:36 MST, Warner Losh wrote: > Please let me know how this works. I'd like to see this in FreeBSD in > the fullness of time. It will be a useful tool and end a lot of the > frustration I've seen in connection with the setting up of disks. As an aside, 4.0-RELEASE's sysinstall looks set to kick ass in this area. Of course, your solution will provide something more useful for folks who don't want to interact with anything after typing the command. Well, it will once it takes command-line options instead of / as well as parsing a config file. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Also... /etc/periodic/daily/200.backup-passwd and MD5 (fwd)
On Tue, 14 Mar 2000 11:27:34 CST, Visigoth wrote: > Did anybody get a chance to look at this and decide that it wasn't > the case or was? I was suprised because I didn't hear _anything_ and am > wondering if I was doing something wrong... Sorry, I read your original post, but somehow a reply like the one that follows didn't make it out of my MUA. :-) Please send me an example of what master.passwd lines look like with MD5 passwords look like and I'll have a look at 200.backup-passwd for you. For security's sake, I suggest you create a dummy user for this purpose and remove the user as soon as you've sent me the master.passwd line for it. Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
On Mon, 13 Mar 2000 02:13:30 GMT, Paul Richards wrote:
> I guess my next question is, are there any objections to
>
> #define UID_MAX ((uid_t)0-1)
If you decide to go the static macro definition (instead of Bruce's
maxof() / minof() idea), please consider using UID_T_{MAX,MIN} or, even
better, BSD_UID_T_{MAX,MIN}.
Thanks,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Also... /etc/periodic/daily/200.backup-passwd and MD5 (fwd)
On Wed, 15 Mar 2000 10:11:06 CST, Visigoth wrote: > Thanks for the security tips ;) here are 2 lines which (note to > the kiddies) have been removed from my server already. Thanks for taking the time. I tested these over here and the passwords are not disclosed by 200.backup-passwd. So what version do you have installed? You should have rev 1.6. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird differences in rc5 behavior on -current vs. -stable
On Mon, 23 Aug 1999 10:47:05 MST, Doug wrote: > How does that PR explain why rc5des with the same ini file is > running at nice 20 on -current, seemingly without idprio and running > at nice 0 on -stable, seemingly with it? Um, different nice levels. I didn't see that. Trigger happy. :-( Sorry, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
On Fri, 03 Sep 1999 10:41:12 -0400, Luoqi Chen wrote: > There have been discussions about the xdm entry /etc/ttys does not > guarantee the X server being started on the particular vty. So I wrote > a shell script to explicitly tell xdm to start X server on a specific > vty. It's been working great. I'd like to share it with you, maybe we > could include it in the base system. I think it'd make a lot more sense if it were part of the XFree86 port. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote: > Well, I got rid of the old Voxware drivers and went with the pnp drivers > and still nothing. Here is the dmesg: What does "still nothing" mean? I can't see anything in your e-mail message which indicates what you're doing to test the sound and what you see in the way of error messages. I do see this: > pcm0: at port 0x220-0x22f irq 5 drq 5 flags 0x15 > on isa0 That makes it look like your card's available. Are you sure you've created the appropriate devices and symlinks as follows: cd /dev ./MAKEDEV snd0 The pcm(4) manpage says snd1, but if your card's detected as pcm0, then that obviously doesn't apply. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
On Fri, 03 Sep 1999 14:03:11 -0400, Luoqi Chen wrote: > Do you know the appropriate channel to contact the XFree86 folks? In the > mean while, I can take Sheldon's advice, submit it to our XFree86 port. By the way, I've just thought of something you should consider. I think there's still a problem with xdm, where trying to change vty while it's starting up can lose you access to all your vtys. This is a problem if xdm starts up unexpectedly. This is why I'm in favour of it being part of XFree86 instead of FreeBSD. But even more important, it should only be installed if the person running the install is okay with it. For the port, that means asking another question. However, it's a little more tricky for the package and you'll probably have to warn that it has been installed, rather than ask whether it's okay to install. This is, of course, idealism. If the script becomes a part of life, people will learn. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386/isa/pnp.h is absent!
On Fri, 03 Sep 1999 17:03:24 GMT, FreeBSD mailing list wrote: > # The xl NIC controller also requires inclusion of the miibus > # controller. > > would clear this issue up for a lotta people. You may as well not introduce confusion on another issue, though; the xl driver provides a device, not a controller. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sb16 not found with newpcm
On Wed, 08 Sep 1999 16:53:37 +0300, Maxim Sobolev wrote: > Why you can't be happy with "device pcm0 at isa? port 0x220 irq 5 drq > 1 flags 0x15" if it works? I think Adam's just trying to make sure that he hasn't done something silly which is preventing him from using a more graceful configuration than he has to. He hasn't done anything silly, he does have to specify parameters, but it wasn't unreasonable to ask. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: optional 'make release' speed-up patch
On Sun, 12 Sep 1999 15:58:01 +0200, Oliver Fromme wrote:
>
> # The first command will fail on a handful of files that have their schg
> # flags set. But it greatly speeds up the next two commands.
> -rm -rf ${CHROOTDIR}
> -chflags -R noschg ${CHROOTDIR}/.
> -rm -rf ${CHROOTDIR}
>
Which sources are you looking at? That's not what I see in rev 1.85 of
Makefile.inc1 .
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
HEADS UP: Style changes in /etc/* scripts
Hi folks, Please be aware that some large deltas have been applied to most of the scripts in src/etc . While the submitter of the changes (Doug Barton), David O'Brien, some others and I have done our best to test these changes, there may be problems. The changes were discussed on the freebsd-hackers mailing list. The submitter addressed concerns raised, motivated the changes very well and has made several requests for review. Watch your startups closely after you mergemaster these changes, and please report any problems which you suspect are related ASAP. Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: optional 'make release' speed-up patch
On Mon, 13 Sep 1999 20:43:11 +0200, Oliver Fromme wrote: > > Makefile.inc1 . > > /usr/src/release/Makefile (This thread is about "make release", > or did I misunderstand the subject line?) Haha! Thanks! No wonder I haven't been understanding this thread. :-) *blush* Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make World Broken?
On Wed, 22 Sep 1999 23:52:54 MST, Thomas Dean wrote: > cvsup this evening. make world failed. /usr/src/crypto does not exist. Nope, no problem (well, apart from a few momentarily pending repo-copies which are resolved now). A lot of stuff moved from secure to crypto, so mebbe check which collections cvsup pulls down? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
