i386 -current make release available for testing

Hi, I have built a i386 specific install for -current. It is available as: ftp://releng4.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20030228-CURRENT Floppies are in the typical place. It was built using the patch below passed in as LOCAL_PATCH to the make release process. I'll leave

Re: config files and includes.

- Julian Elischer's Original Message - I have just gone through the process of upgrading or installing several hundred machines, and Thst includes altering or editing many config files in /etc. I like the way that rc.conf is handled, in that defaults/rc.comf can be updated and only

UFS2 regression tests?

Hi Folks, I've just put together a 1.7TB filesystem and was looking for some regression tests to run against it. Looking through the mailing lists doesn't turn up anything, nor does a websearch (at least for the keywords I tried). So, does anyone have any comments/ideas on a good way to

Re: UFS2 regression tests?

- Brad Knowles's Original Message - Yeah, especially if it's UFS2, you're doing softupdates with background fsck, and you've used vinum to build the large logical volume. ;-) Actually, I didn't say how the volume was put together :-) It is currently a Raid50 consisting of

src/sbin/mount/mount.c argv[0] cleanup

Hi, I've built and installed a complete system with the patch below. Amoung other things, this allows the individual mount_$vfstype executables to not have to differentiate how they were invoked. They can then have their XXX sections removed along with a small amount of code (and this will

cron/crontab openlog() cleanup

Hi, While debugging a problem recently I had all.log enabled in syslog.conf. One of the things I noted was the messages coming from cron where the ident string was the fully qualified pathname: Dec 29 21:00:00 xxx4 /usr/sbin/cron[7409]: (root) CMD (newsyslog) Dec 29 21:00:00 xxx4

Re: Run two copies of named from rc.conf?

- Terry Lambert's Original Message - Brad Knowles wrote: Sorry, I wasn't think of transient networks. Indeed, that does make things a lot uglier. I'll have to think some more about all the various implications, however. One of the draft RFC's in the FTP directory I

ccd disklabel (what should work?)

In trying to setup a ccd on a -current system I seem to have run into a few issues: /etc/ccd.conf: # ccd ileave flags component devices ccd0 64 none/dev/ad1s1a /dev/ad2s1a # ccdconfig -g ccd064 0 /dev/ad1s1a /dev/ad2s1a # ls -al /dev/ccd*

Run two copies of named from rc.conf?

It would be nice if rc.conf could start a 2nd copy of named (split dns). Comments on the following simplistic patch? -John cvs diff: Diffing src/etc Index: src/etc/rc.network === RCS file: /home/ncvs/src/etc/rc.network,v retrieving

Re: Kernel not booting....Immediate crash

- Nate Lawson's Original Message - On Thu, 7 Nov 2002, David Rhodu wrote: Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after

5.0-20021101-CURRENT snap iso

For all you weekend install warriors out there... There is a new 5.0 snap iso available via anonymous ftp at: usw2.FreeBSD.Org /pub/FreeBSD/snapshots/i386/5.0-20021101-CURRENT and the iso: /pub/FreeBSD/snapshots/i386/5.0-20021101-CURRENT.iso I have verified that this iso boots and can

Poor 5.0/nfs performance

Hi, I have a 5.0 system from 10/27. In an attempt to improve performance I commented out the INVARIANTS/WITNESS options: #optionsINVARIANTS #Enable calls of extra sanity checking #optionsINVARIANT_SUPPORT #Extra sanity checks of internal structures,

5.0-20021027-CURRENT.iso cdrom will not mount

Hi, The last three 5.x install iso cdroms that I have created will not mount. The iso(s) boot correctly and sysinstall works fine. The disks are formated and newfs'd correctly. However, when sysinstall tries to mount the cdrom, the following error is received: Error mounting /dev/acd0c on

Large 'label'ing defaults for sysinstall

Hi, In this day of larger disk drives, I've modified the code in sysinstall to automatically create a /home partition and increase the rest of the sizes if the size of the disk (or slice) exceeds a given size (currently 58gig in my patch). For example, using A(uto in the label editor on a

Re: 5.0-20021025-CURRENT snapshot

- Daniel Flickinger's Original Message - Sent: Sun, 27 Oct 2002 01:03:43 +0900 by MAR + jwd A new 5.0-20021025-CURRENT snapshot is available + jwd via anonymous ftp at usw2.freebsd.org: + + Wonderful! Is it a time to switch back 'current.FreeBSD.org' name to + that machine?

Local DNS lookup by sshd?

Hi, When logging into a current 5.0 system via ssh, I see the following written to the system console (the 'xxx's are my whiteout): ... kernel: Connection attempt to UDP xxx.58.184.35:53 from xxx.58.184.35:49253 ... kernel: Connection attempt to UDP xxx.58.184.35:53 from xxx.58.184.35:49254

5.0 disklabel warnings against 4.7 disk

Hi, I've (re)scanned my -current folder for issues related to the following but didn't see a good match. Pointing out my blindness is allowed if this was discussed... I have a system onto which I installed a 4.7-RC a couple of weeks ago. I then upgraded that newly installed system to

5.0-20021025-CURRENT snapshot

This will be the last post on this topic. A new 5.0-20021025-CURRENT snapshot is available via anonymous ftp at usw2.freebsd.org: /pub/FreeBSD/snapshots/i386/5.0-20021025-CURRENT New snaps will appear each day if the build completes without errors. Enjoy! John To Unsubscribe: send mail to

5.0-20021023-CURRENT available

Hi, I have have uploaded a 5.0-20021023-CURRENT snapshot to usw2.freebsd.org available via anonymous ftp: /pub/FreeBSD/snapshots/i386/5.0-20021023-CURRENT I am currently unable to boot from the kern/mfsroot floppies due to Cannot find /mfsroot. I have not had a chance to try burning

5.0-R make release panic

Hi Folks, I've been running repetitive 'make release's on a box and it died once (no serial console), and I finally got it to crash again after about 2 days. uname: (world and kernel up-to-date as of) 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 17 02:12:59 GMT 2002 df: Filesystem

Inetd configuration message logging (or lack thereof)

Hi, Comments on the following patch. The messages are invisible with a default install. This patch gets them into /var/log/messages where they can be seen. -John ps: Not in this patch, but I wonder if syslog cannot be redirected to the console when run -d. Something like: #define