5.x to 6.x source update, bootblocks?
Hi all, Here's a quicky... I've been running around upgrading some boxes to 6.2 from 4.11 using the directions in UPDATING. I noticed that in the 4.x to 5.x step it's basically mandatory to install the new bootloader: cd /sys/boot make STRIP= install I see no such notes in the 5.x to 6.x guide. Should I repeat this process? I figure having the latest bootloader should not cause problems, correct? Thanks, Charles ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mfs and buildworlds on the SunFire x4600
Oliver Fromme wrote: [...] I don't think it makes much sense to benchmark mfs. It is a known fact that a real tmpfs (like Solaris and Linux have) would be better. I think it's even listed on the FreeBSD ideas web page, but nobody is actively working on it, AFAIK. On the other hand, I'm not 100% convinced that it would be worth the effort either. I think Howard Su is working on tmpfs (see freebsd-arch@ 2007-04-22 with subject move audit/priviliage check into VFS or freebsd-fs@ 2007-04-17 with subject handle special file type in tmpfs) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: top shows 'swapped'
Ken Chen wrote: When I use 'top' command to check my system, some processes are shown like 'php'. The manual told these processes are swapped out. But my problem is .. I don't have swapping device (swapoff -a). Where are they swapped to ? last pid: 29144; load averages: 0.69, 0.67, 0.82 up 19+11:25:27 21:05:03 89 processes: 1 running, 88 sleeping CPU states: 1.2% user, 0.0% nice, 0.9% system, 0.0% interrupt, 97.8%idle Mem: 309M Active, 27M Inact, 127M Wired, 19M Cache, 60M Buf, 4136K Free Swap: PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 29141 nobody 1 40 37164K 15932K select 0 0:00 4.55% php 28856 nobody 1 4 -15 36936K 7612K sbwait 0 0:44 1.66% php . . . 29116 nobody 1 4 -15 33732K 13140K accept 0 0:00 0.00% php 24937 nobody 1 8 -15 31740K 0K wait 1 0:00 0.00% php 24948 nobody 1 8 -15 31740K 0K wait 0 0:00 0.00% php 24931 nobody 1 8 -15 31740K 0K wait 0 0:00 0.00% php 24950 nobody 1 8 -15 31740K 0K wait 1 0:00 0.00% php 24932 nobody 1 8 -15 31740K 220K wait 1 0:00 0.00% php The are only used when the process flag PS_INMEM is clear, which is supposed to indicate that the process is or is not in memory. This flag is only ever cleared in swapout, called from swapout_procs. My bet is that the processes are being marked for swap but the dirty pages never actually go anywhere since you don't have a backing store. Maybe someone more familiar with the inner workings of the VM system can fill us in on what happens on a system with no swap. Bill LeFebvre ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: top shows 'swapped'
Ken Chen [EMAIL PROTECTED] wrote: When I use 'top' command to check my system, some processes are shown like 'php'. The manual told these processes are swapped out. Actually it means that they're not mapped into RAM, but in practice that should be the same. Just out of cusiosity I grepped the kernel sources for the PS_INMEM flag and found just two places where it could possibly be cleared for a process: during creation of a child process within the fork() system call, and when a process is being swapped out. But my problem is .. I don't have swapping device (swapoff -a). Where are they swapped to ? If you don't plan to configure any swap at all, I recommend you build a kernel with options NO_SWAPPING. It removes the code for swapping processes from the kernel. (By the way, I recommend you always configure some swap, even if you don't intend to use it under normal circumstances, except maybe on diskless machines.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one? -- Tom Cargil, C++ Journal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock problem
Jeffrey Goldberg wrote: Oliver Fromme wrote: Martin Dieringer wrote: Oliver Fromme wrote: Are you sure that your /etc/ntp.conf ist correct? # cat /etc/ntp.conf server time.fu-berlin.de iburst maxpoll 9 driftfile /var/db/ntp.drift logfile /var/log/ntpd You must add restrict lines for every server and for localhost, like these: restrict time.fu-berlin.de nomodify restrict 127.0.0.1 Sorry, I forgot one line: restrict default ignore Why? The default line is for security reasons, so nobody else can modify your ntpd. The nomodify line enables time synchronization with the server, but prevents it from being able to modify your ntpd settings. Finally, the line for localhost enables you to use tools like ntpdc and ntpq locally. It's all explained in the ntp.conf(5) manual page. Other than that, the config looks good. There's no need to add further time servers. The time adjustment algorithms of NTP make use of multiple time sources. NTP works best with having at least three reachable servers. Of course ntp is designed to keep good time even when you are disconnected from the net, but it builds up its data from multiple sources and using triangulation to correct for errors. NTP works perfectly well with a single source. Having multiple sources is not necessary on an end client (but it doesn't hurt either, of course). Of course, on a server that provides NTP service itself to a subnet or similar, having multiple upstream servers is desirable. In fact, ntpd refuses to synchronize against a server that does not have at least two upstream servers (non- stratum-16) itself. Martin's Problem with ntpd is not a precision problem. His problem is that his ntpd does not synchronize at all. Adding more servers certainly won't solve that problem. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd In My Egoistical Opinion, most people's C programs should be indented six feet downward and covered with dirt. -- Blair P. Houghton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: top shows 'swapped'
* Bill LeFebvre ([EMAIL PROTECTED]) wrote: The are only used when the process flag PS_INMEM is clear, which is supposed to indicate that the process is or is not in memory. This flag is only ever cleared in swapout, called from swapout_procs. My bet is that the processes are being marked for swap but the dirty pages never actually go anywhere since you don't have a backing store. Maybe someone more familiar with the inner workings of the VM system can fill us in on what happens on a system with no swap. I'm seeing this sort of thing too -- I do have swap, but it's not being used by these processes (swapoff -a didn't do anything to them): Mem: 1672M Active, 5337M Inact, 279M Wired, 400M Cache, 215M Buf, 74M Free Swap: 10G Total, 12K Used, 10G Free 1251 www 1 40 87884K 0K accept 2 0:00 0.00% httpd 1106 root 1 200 12756K 0K pause 1 0:00 0.00% smbd 950 root 1 1150 8536K 0K select 3 0:00 0.00% pure-ftpd 1143 mysql 1 80 5220K 0K wait 3 0:00 0.00% sh 1288 root 1 50 3644K 0K ttyin 2 0:00 0.00% getty The bulk of the data is probably swapped to the on-disk binaries, but this would imply there isn't a single page unique to each process. Quite why it's bothering in the first place with 5GB Inact I'm not sure -- is it unmapping idle processes to conserve VM objects? I also find it interesting that I only noticed this behavior a few days ago and suddenly someone else mentions it too :) -- Thomas 'Freaky' Hurst http://hur.st/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock problem
Martin Dieringer wrote: # ntpq -p remote refid st t when poll reach delay offset jitter == *time192.53.103.108 2 u 19 64 77 91.454 301.926 860.104 and the clock is only 3 seconds late now... The delay, offset and jitter values are in milliseconds, so your current offset is about 0.3 ms. When you keep ntpd running, the offset should be reduced slowly. ntpd calculates the drift of the local clock. During times when it cannot reach the server, it corrects the local clock using the recorded drift. ok this sounds beautiful, but what if the drift is irregular? Normal quartz-controlled hardware clocks don't have an irregular drift. PC clocks aren't well-known for their precision, but the drift should be fairly constant. If your drift is noticeably irregular, then there is some- thing very wrong with your machine. I'm afraid that ntpd won't work very well under such circumstances. In that case you'll have to find out the cause of the problem and fix it, or help a FreeBSD to fix it (by providing the necessary pieces of information). But 2 minutes is also too much ntpd should be able to handle that without problems. yes maybe, sometimes... Well, I agree that 2 minutes per day is much. Normally the maximum drift that can be corrected by slewing the clock is about 45 seconds per day (500 ppm). However, if the offset is larger than a certain limit, ntpd will step the clock anyway, so even a drift of 2 minutes should be correctable. (I think the limit is 128 ms, and the step will occur if the limit is exceeded for at least 15 minutes. But I'd have to look at the source code to be sure; the manual pages are sometimes not up- to-date with regard to such details.) I have to redialup every 24h which normally works fine. How are you redialling? If you get a new dynamic IP address, it might be necessary to restart ntpd. MYADDR: !bg /etc/rc.d/ntpd restart great! 8-( as restart does not work because the pid seems to be wrong and usually there are 5 or so ntpd's running... ? Hu? There should be exactly one ntpd process running. You should clean up (kill all of them, remove any bogus PID file if there's one left, then restart ntpd). btw, this is on the other machine which is now 2 minutes off again, maybe 1 hour after correct setting: # ntpq -p remote refid st t when poll reach delay offset jitter == chronos.zedat.f .PPS.1 u 457 512 377 366.965 37369.6 8640.85 log: 8 May 16:11:08 ntpd[57617]: synchronized to 130.133.1.10, stratum=1 8 May 16:11:08 ntpd[57617]: time reset +0.651381 s 8 May 16:11:08 ntpd[57617]: kernel time sync disabled 2041 8 May 16:12:22 ntpd[57617]: synchronized to 130.133.1.10, stratum=1 8 May 16:13:30 ntpd[57617]: no servers reachable now: 16:57 A jitter of 8 seconds is really a lot. Is your uplink that bad? Of course, that adds to the problem that you already have because of (supposedly) irregular drift. If you have multiple machines behind the same uplink, it might be a good idea to configure one of them as an NTP server (preferably the one which has the smallest drift), and let all your other machines use that machine as the NTP time source. So at least all your own machines are synchronized with each other, and you separate the problem of the drift from the problem of a bad uplink. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: top shows 'swapped'
Thomas Hurst wrote: I'm seeing this sort of thing too -- I do have swap, but it's not being used by these processes (swapoff -a didn't do anything to them): Mem: 1672M Active, 5337M Inact, 279M Wired, 400M Cache, 215M Buf, 74M Free Swap: 10G Total, 12K Used, 10G Free 1251 www 1 40 87884K 0K accept 2 0:00 0.00% httpd 1106 root 1 200 12756K 0K pause 1 0:00 0.00% smbd 950 root 1 1150 8536K 0K select 3 0:00 0.00% pure-ftpd 1143 mysql 1 80 5220K 0K wait 3 0:00 0.00% sh 1288 root 1 50 3644K 0K ttyin 2 0:00 0.00% getty The bulk of the data is probably swapped to the on-disk binaries, You probably mean that the text pages of the binary have not been paged into memory (that's different from swapping). That's unlikely. but this would imply there isn't a single page unique to each process. I don't think that could happen. As soon as you link with libc (which sh, httpd and others certaily do), you get a bunch of global variables and other things that are not shared across processes. Quite why it's bothering in the first place with 5GB Inact I'm not sure -- is it unmapping idle processes to conserve VM objects? That doesn't happen. FreeBSD has a feature to proactively swap processes that have been idle for a certain time, but it's disabled by default, see: sysctl vm.swap_idle_enabled I also find it interesting that I only noticed this behavior a few days ago and suddenly someone else mentions it too :) I don't see it on any of my FreeBSD 6-stable machines, but they run RELENG_6 of about 2 months ago. Maybe a subtle bug has been introduced recently. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd A language that doesn't have everything is actually easier to program in than some that do. -- Dennis M. Ritchie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x to 6.x source update, bootblocks?
Date: Wed, 9 May 2007 01:54:15 -0400 (EDT) From: Charles Sprickman [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi all, Here's a quicky... I've been running around upgrading some boxes to 6.2 from 4.11 using the directions in UPDATING. I noticed that in the 4.x to 5.x step it's basically mandatory to install the new bootloader: cd /sys/boot make STRIP= install I see no such notes in the 5.x to 6.x guide. Should I repeat this process? I figure having the latest bootloader should not cause problems, correct? V5 is when UFS2 was introduced as well as moving the kernel and modules locations. That is why the need to re-build boot. This has not happened since V5, so there is no need to manually re-build the boot again. It gets re-built in any case. The procedure in the 4 to 5 upgrade was to allow the boot of the newly built kernel. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpm6CxzCjxhp.pgp Description: PGP signature
Re: Creating one's own installer/mfsroot
Daniel O'Connor wrote: On Wednesday 09 May 2007 03:40, Matthew X. Economou wrote: Could anyone recommend a good guide for developing one's own mfsroot images suitable for recovery or scripted installation (not using sysinstall)? It appears that one could develop a simplified network-based installation process based around fdisk, disklabel, newfs, mount_ufs, fetch, and pax, perhaps tied together with the usual scripting tools (maybe miniperl or sh/sed/awk). You could see how make release FreeSBiE do it. You could also look at the INSTALL guides for (early versions of?) Dragonfly, it taught me how to install a BSD system from scratch, using only what's in base of liveCD :) (I consider it a bad sign that I've actually needed that knowledge once to set up a production machine - I thought we're not in the stone age anymore :( ) signature.asc Description: OpenPGP digital signature
Re: [kde-freebsd] problem hal - k3b ?
On Mon, Apr 30, 2007 at 07:50:45PM +0200, Thomas Quinot wrote: * Oliver Peter, 2007-04-26 : My problem is the same as Beni's. Splash screen appears and hangs. I have to press power button to turn off and on my laptop. Didn't try ctrl+alt+del though. I have the same problem with my 7.0-CURRENT (yesterday). If I can assist you testing or debugging drivers please drop me an e-mail. FreeBSD 7.0-CURRENT i386 with k3b-1.0_1 / hal-0.5.8.20070403_1 Thank you for your message, Thomas. This looks similar to kern/112119, which is fixed by rev. 1.52 of sys/dev/ata/atapi-cam.c, committed today on HEAD. Sorry for my late reply. Of course this works great for me, too. -- Oliver PETER, email: [EMAIL PROTECTED], ICQ# 113969174 Worker bees can leave. Even drones can fly away. The Queen is their slave. pgp7Pk5DgV9pa.pgp Description: PGP signature
Re: 5.x to 6.x source update, bootblocks?
On Wed, May 09, 2007 at 01:54:15AM -0400 I heard the voice of Charles Sprickman, and lo! it spake thus: I've been running around upgrading some boxes to 6.2 from 4.11 using the directions in UPDATING. I noticed that in the 4.x to 5.x step it's basically mandatory to install the new bootloader: FWIW, I moved some (the last, I think; yay!) 4.x boxes up to 6.x last weekend. I did NOT install a new bootloader before booting the 5.x kernel, but I DID have a serial console available to manually point it at the new location for that boot (the installworld after that put the new loader in place so I didn't have to do it manually after that). That was enough. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Creating one's own installer/mfsroot
Ivan Voras wrote: Daniel O'Connor wrote: On Wednesday 09 May 2007 03:40, Matthew X. Economou wrote: Could anyone recommend a good guide for developing one's own mfsroot images suitable for recovery or scripted installation (not using sysinstall)? It appears that one could develop a simplified network-based installation process based around fdisk, disklabel, newfs, mount_ufs, fetch, and pax, perhaps tied together with the usual scripting tools (maybe miniperl or sh/sed/awk). You could see how make release FreeSBiE do it. You could also look at the INSTALL guides for (early versions of?) Dragonfly, it taught me how to install a BSD system from scratch, using only what's in base of liveCD :) (I consider it a bad sign that I've actually needed that knowledge once to set up a production machine - I thought we're not in the stone age anymore :( ) Well, that kind of knowledge is also what lets us leave (say) the bronze age. We have set up a boot CD (or pxeboot/nfs environment) where we can run a Ruby script that will take directives from a configuration file, configure the disks, slices and partitions, align the partitions to start on a block boundary appropriate for the underlying RAID system, to end on a cylinder boundary, populate filesystems as required, etc. Also useful for using an existing system to set up CF cards for Soekris systems with the correct geometry, etc. Building the system images and installation time filesystems is done from a build system that builds everything in chroot environments, with as little dependency on the host system as possible. It manages make buildworld/installworld/kernel, ports, non-ports installations (ie: user generated scripts), dependencies, parallel builds, making jails, etc. From this we have a system where system installations are reproducible and recoverable. Upgrading uses the same output from the build process using a nanobsd-like second slice allowing inplace upgrades with little downtime and recovery to the previous version. But the most important thing is that the upgrade image was created using the same process as the installation image, so we can always get to the same image after a full system rebuild. If anyone is interested, let me know and I'll see what I have to do to release it. Regards, Jan Mikkelsen [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
cu: Got hangup signal on sio0 probe
Hi there, Please Cc: me when replying. % obiwan:root# cat /boot.config % -D % obiwan:root# grep ttyd0 /etc/ttys % ttyd0 /usr/libexec/getty std.9600 dialup on secure This works correctly but on startup, when the kernel probes sio0, I get Got hangup signal. Is it expected? I think I can understand this, but is there any way to workaround this? Thank you. -- Jeremie Le Hen jeremie at le-hen dot org ttz at chchile dot org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cu: Got hangup signal on sio0 probe
On Thu, May 10, 2007 at 12:19:27AM +0200, Jeremie Le Hen wrote: % obiwan:root# cat /boot.config % -D % obiwan:root# grep ttyd0 /etc/ttys % ttyd0 /usr/libexec/getty std.9600 dialup on secure This works correctly but on startup, when the kernel probes sio0, I get Got hangup signal. Is it expected? I wonder if that's some sort of reference to carrier detect being wired wrong on whatever device or adapter you have connected to your serial port. However, I can't find this string referenced anywhere in the kernel source code for RELENG_6. An (admittedly bad) egrep shows: $ egrep -r Got .+ signal /usr/src /usr/src/contrib/amd/amd/nfs_start.c:/* Got a signal */ /usr/src/usr.bin/make/job.c: * Got a signal. Set global variables and hope that someone will /usr/src/usr.sbin/bluetooth/bthidd/bthidd.c:syslog(LOG_NOTICE, Got signal %d, total number of signals %d, /usr/src/usr.sbin/bluetooth/hcsecd/hcsecd.c:syslog(LOG_DEBUG, Got signal %d, total number of signals %d, /usr/src/usr.sbin/bluetooth/sdpd/main.c:log_notice(Got signal %d. Total number of signals received %d, What version of FreeBSD are you referring to? I think I can understand this, but is there any way to workaround this? Consider using uart(4) as a possible alternative, but depending upon the answer to the above question, this might not be applicable. I wrote some directions on how to get uart(4) to work, and one caveat I found when attempting to use it. Those docs are here: http://jdc.parodius.com/freebsd_uart.txt -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Creating one's own installer/mfsroot
: You could also look at the INSTALL guides for (early versions of?) : Dragonfly, it taught me how to install a BSD system from : scratch, using : only what's in base of liveCD :) :... : :We have set up a boot CD (or pxeboot/nfs environment) where we can run a :Ruby script that will take directives from a configuration file, configure :the disks, slices and partitions, align the partitions to start on a block :... I came up with a neat little script-driven remote configurator called rconfig (/usr/src/sbin/rconfig in the DragonFly codebase) as an alternative to the standard features in our installer. I recommend checking it out. http://www.dragonflybsd.org/cvsweb/src/sbin/rconfig/ rconfig is really easy to use. Basically its just a client/server pair with socket broadcast capabilities. All it does is negotiate a shell script download from the server to the client (server on the same subnet), then runs the script on the client. That's it. I wanted to be able to boot a CD, login as root, dhclient the network up, and then just go 'rconfig -a' and have my script do the rest. It takes a bit of time to write the shell script to do a full install from fdisk to completion, but if you have a fully working CD based environment (all the binaries in /, /usr, a writable /tmp, /etc, and so forth)... then shell scripts are just as easy to write as they are on fully installed machines. I use rconfig to do fresh installs of my test boxes from CD, with all the customization, my ssh keys, fstab entries, NFS mounts, etc that I need to be able to ssh into the box and start using it immediately. NFS booting is 'ok', but requires a lot of infrastructure and gets out of date easily. Often you also have to mess with the BIOS settings, which is very annoying because you have to change them back after you finish the install. I used NFS booting for a while, but just couldn't depend on it always being operational. With rconfig I just leave the rconfig server running on one of my boxes and the worst I have to do is tweak my script a bit. And adding smarts to the script is easy whereas you just can't add much smarts to a NFS boot without a lot of messing around with the RC sequence. In anycase, check it out. My assumption is that rconfig would compile nearly without modification on a FreeBSD box. -Matt Matthew Dillon [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on sparc64/sparc64
TB --- 2007-05-10 03:04:37 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-05-10 03:04:37 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2007-05-10 03:04:37 - cleaning the object tree TB --- 2007-05-10 03:05:10 - checking out the source tree TB --- 2007-05-10 03:05:10 - cd /tinderbox/RELENG_6/sparc64/sparc64 TB --- 2007-05-10 03:05:10 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-05-10 03:19:08 - building world (CFLAGS=-O2 -pipe) TB --- 2007-05-10 03:19:08 - cd /src TB --- 2007-05-10 03:19:08 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2007-05-10 04:25:18 - generating LINT kernel config TB --- 2007-05-10 04:25:18 - cd /src/sys/sparc64/conf TB --- 2007-05-10 04:25:18 - /usr/bin/make -B LINT TB --- 2007-05-10 04:25:18 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-05-10 04:25:18 - cd /src TB --- 2007-05-10 04:25:18 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Thu May 10 04:25:18 UTC 2007 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/iir/iir_pci.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/isp/isp.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/isp/isp_freebsd.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/isp/isp_library.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/isp/isp_pci.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm
