Re: make world fails in usr.sbin/config?
On Tue, May 25, 2010 at 1:05 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/05/2010 11:40:23, Stefan Bethke wrote: For the record: I'm now running -stable as of last night, compiled without issue on ZFS filesystems throughout. No idea what caused the issue in the first place, and what made it disappear though, but updating to the correctly built -stable made the build on ZFS work again. (It also involved an accidential upgrade and downgrade via -current, since I checked out the wrong tag with csup. Yikes.) I've a new machine that's been running 8-STABLE on ZFS for about a week now. Had no problems installing and then upgrading to recent 8-STABLE although I did start with installing an 8-STABLE snapshot rather than 8.0-RELEASE. (See: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror) Verb. Sap. If you're booting from ZFS, beware of updating the zpool version without due care and attention. 8.0-RELEASE was on version 13, 8-STABLE is now on version 14. (Use 'zpool update' to see what the status is on your machine -- this just gives you a report, and doesn't update anything.) Updating the zpool version is pretty smooth and simple, but *remember to immediately rebuild and reinstall gptzfsboot or zfsboot bootcode on your drives*. If you don't do that, your system won't be able to find the pool with the root filesystem and so won't be able to reboot. Old thread, I know. But I encountered this error today and my solution was that /tmp was tmpfs and it was full. Cleaning that up fixed the error. -- chs, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
root mount error
Hello I've got trouble with FreeBSD 8 Stable First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to yesterday revision I don't remember exact number, but I've have this problem aobut week or two so it's not so important, also as it doesn't work on i386 too. After installing new kernel I've just build - indeed it always was GENERIC for both arch's on clean system - I've got an a kernel painc caused by disability to mount root partition because kernel couldn't see the drive. By pressing '?' I've sen only acd0 that represents CD-ROM. In debug messages I haven't found anything about ad0 - than hdd was identified before new kernel was installed. I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is working with diabled SATA native mode. I've not found any info 'bout this error in recent 8.Stable so I don't know how to handle this one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !!
On Sun, Dec 26, 2010 at 4:43 PM, Jean-Yves Avenard jyaven...@gmail.com wrote: On 27 December 2010 09:55, Jean-Yves Avenard jyaven...@gmail.com wrote: Hi there. I used stable-8-zfsv28-20101223-nopython.patch.xz from http://people.freebsd.org/~mm/patches/zfs/v28/ I did the following: # zpool status pool: pool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 cache label/zcache ONLINE 0 0 0 errors: No known data errors so far so good [r...@server4 /pool/home/jeanyves_avenard]# zpool add pool log /dev/label/zil [r...@server4 /pool/home/jeanyves_avenard]# zpool status pool: pool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 logs label/zil ONLINE 0 0 0 cache label/zcache ONLINE 0 0 0 errors: No known data errors so far so good: # zpool remove pool logs label/zil cannot remove logs: no such device in pool Is that a typo, or the actual command you used? You have an extra s in there. Should be log and not logs. However, I don't think that command is correct either. I believe you want to use the detach command, not remove. # zpool detach pool label/zil -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Accidentally aborted upgrade via freebsd-update - how to recover?
OK, so I'm a late adopter - up til now I've always upgraded FreeBSD machines from source or picking the update from a CD, but I decided to try freebsd-update to finally get my home machine from 6.4 to 7.1 (and thence hopefully to 8.1). Everything went well up through the merge steps, until I noticed a merge I had forgotten to resolve in /etc/hosts.allow, so at the Does this look reasonable (y/n)? prompt I answered 'n', thinking that would put me back into the editor. Instead it dumped me to the command line and aborted the update completely. How can I continue from here without downloading and applying 29000+ patches all over again, not to mention having to manually resolve the updated $FreeBSD lines in a ton of config files? (Or worse, having it try to apply patches which have already been applied?) I just tried typing sudo freebsd-update install and sudo freebsd-update install -r 7.1-RELEASE but that gives me: No updates are available to install. Is there some way to resume where I left off? -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: OK, so I'm a late adopter - up til now I've always upgraded FreeBSD machines from source or picking the update from a CD, but I decided to try freebsd-update to finally get my home machine from 6.4 to 7.1 (and thence hopefully to 8.1). Everything went well up through the merge steps, until I noticed a merge I had forgotten to resolve in /etc/hosts.allow, so at the Does this look reasonable (y/n)? prompt I answered 'n', thinking that would put me back into the editor. Instead it dumped me to the command line and aborted the update completely. How can I continue from here without downloading and applying 29000+ patches all over again, not to mention having to manually resolve the updated $FreeBSD lines in a ton of config files? (Or worse, having it try to apply patches which have already been applied?) I just tried typing sudo freebsd-update install and sudo freebsd-update install -r 7.1-RELEASE but that gives me: I've never run this command for a specific release. No updates are available to install. What happens if you run freebsd-update install ? If you haven't installed anything, there is nothing to rollback. A feature that is part of freebsd-update. Is there some way to resume where I left off? I'm not aware of any method to do this, other than to remove everything under /var/db/freebsd-update and start from the beginning. -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On Mon, Dec 27, 2010 at 02:47:53PM -0800, Jason Helfman wrote: Thanks for the prompt response! On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: ... How can I continue from here without downloading and applying 29000+ patches all over again, not to mention having to manually resolve the updated $FreeBSD lines in a ton of config files? (Or worse, having it try to apply patches which have already been applied?) I just tried typing sudo freebsd-update install and sudo freebsd-update install -r 7.1-RELEASE but that gives me: I've never run this command for a specific release. No updates are available to install. What happens if you run freebsd-update install ? Same message. If you haven't installed anything, there is nothing to rollback. A feature that is part of freebsd-update. I guess I should have realized that, at least. Is there some way to resume where I left off? I'm not aware of any method to do this, other than to remove everything under /var/db/freebsd-update and start from the beginning. OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Kernel/World Upgrade causes Hang
I recently rebuilt the world and kernel and everything built just fine and when I went to boot into the new kernel, it hangs. I had to revert back to my previous kernel. Currently I'm running: FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 20:44:06 CST 2010 r...@server.domain.net:/usr/obj/usr/src/sys/server amd64 When it hangs upon boot-up it simply stops here. I don't know how I can figure out what is causing the root of the hang. I'd really like to get this machine upgraded. Ppc0 cannot reserve I/O port range PowerNow0 Cool ‘N’ Quiet K8 on cpu0 Device_attach: PowerNow0 attach return 6 PowerNow0 Cool ‘N’ Quiet K8 on cpu1 Device_attach: PowerNow0 attach return 6 PowerNow1 Cool ‘N’ Quiet K8 on cpu0 Device_attach: PowerNow0 attach return 6 PowerNow1 Cool ‘N’ Quiet K8 on cpu1 Device_attach: PowerNow0 attach return 6 Time Counters Tick every 1.000 msec hang Any help is greatly appreciated. -Troy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On Mon, Dec 27, 2010 at 12:58:28PM -1000, Clifton Royston thus spake: On Mon, Dec 27, 2010 at 02:47:53PM -0800, Jason Helfman wrote: Thanks for the prompt response! Your welcome :) On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: ... How can I continue from here without downloading and applying 29000+ patches all over again, not to mention having to manually resolve the updated $FreeBSD lines in a ton of config files? (Or worse, having it try to apply patches which have already been applied?) I just tried typing sudo freebsd-update install and sudo freebsd-update install -r 7.1-RELEASE but that gives me: I've never run this command for a specific release. No updates are available to install. What happens if you run freebsd-update install ? Same message. You may want to just try and run the 'fetch' again. freebsd-update -r 7.1-RELEASE fetch If you haven't installed anything, there is nothing to rollback. A feature that is part of freebsd-update. I guess I should have realized that, at least. Is there some way to resume where I left off? I'm not aware of any method to do this, other than to remove everything under /var/db/freebsd-update and start from the beginning. OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. I believe there is with a handcrafted mergemaster.rc file. I was told by Colin that this 'bug' was introduced at some point with freebsd-update, as branches at one point weren't tagged. When they started to get tagged, freebsd-update started to compare. -jgh -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: New ZFSv28 patchset for 8-STABLE: ARRRGG HELP !!
Hi On Tuesday, 28 December 2010, Freddie Cash fjwc...@gmail.com wrote: On Sun, Dec 26, 2010 at 4:43 PM, Jean-Yves Avenard jyaven...@gmail.com wrote: On 27 December 2010 09:55, Jean-Yves Avenard jyaven...@gmail.com wrote: Hi there. I used stable-8-zfsv28-20101223-nopython.patch.xz from http://people.freebsd.org/~mm/patches/zfs/v28/ I did the following: # zpool status pool: pool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 cache label/zcache ONLINE 0 0 0 errors: No known data errors so far so good [r...@server4 /pool/home/jeanyves_avenard]# zpool add pool log /dev/label/zil [r...@server4 /pool/home/jeanyves_avenard]# zpool status pool: pool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 logs label/zil ONLINE 0 0 0 cache label/zcache ONLINE 0 0 0 errors: No known data errors so far so good: # zpool remove pool logs label/zil cannot remove logs: no such device in pool Is that a typo, or the actual command you used? You have an extra s in there. Should be log and not logs. However, I don't think that command is correct either. I believe you want to use the detach command, not remove. # zpool detach pool label/zil -- Freddie Cash fjwc...@gmail.com It was a typo, it should have been log (according to sun's doc). As it was showing logs in the status I typed this. According to sun, it zpool remove pool cache/log A typo should have never resulted in what happened, showing an error for sure; but zpool hanging and kernel panic? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On Mon, Dec 27, 2010 at 03:02:56PM -0800, Jason Helfman wrote: On Mon, Dec 27, 2010 at 12:58:28PM -1000, Clifton Royston thus spake: On Mon, Dec 27, 2010 at 02:47:53PM -0800, Jason Helfman wrote: On Mon, Dec 27, 2010 at 12:44:26PM -1000, Clifton Royston thus spake: ... How can I continue from here without downloading and applying 29000+ patches all over again, not to mention having to manually resolve the updated $FreeBSD lines in a ton of config files? (Or worse, having it try to apply patches which have already been applied?) ... If you haven't installed anything, there is nothing to rollback. A feature that is part of freebsd-update. I guess I should have realized that, at least. Is there some way to resume where I left off? I'm not aware of any method to do this, other than to remove everything under /var/db/freebsd-update and start from the beginning. I started over but without removing the directory, and found that after redownloading all the metadata, it DTRT: nothing more got downloaded, and it apparently identified all the automatic merges as already patched. It seems to be starting over at the beginning of the ones to manually patch up. OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. I believe there is with a handcrafted mergemaster.rc file. I was told by Colin that this 'bug' was introduced at some point with freebsd-update, as branches at one point weren't tagged. When they started to get tagged, freebsd-update started to compare. Ah, I saw that discussion a while back on one of the lists for mergemaster, but I didn't realize it applied to freebsd-update as well. Next time around, I'll revisit the email thread and figure out which options I want to pull in to skip those lines. -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel/World Upgrade causes Hang
Hey Troy, I can't speak for the rest of the list but I think we're missing a bit of information here. What are you trying to build and boot, 8.1, 8.2pre ? Are you building a GENERIC kernel ? I notice you're currently using a custom one. If you're not, I would suggest trying GENERIC first. You might want to post your whole boot message if it can be recovered. Also and in case you don't know, you may quickly test your kernel like so: nextboot -k yourkernelhere Next reboot, the host will try yourkernelhere, and on the reboot after that, revert to your regular kernel. Other than that, quick things to check: 1/ built world before kernel 2/ built kernel SINGLE THREADED (no -j X to speed it up, which you can do for the world) 3/ tracked the *correct* version in the cvsup file (I've had this case where I was running fbsd8 zfs boot, and was building a 7.x kernel by mistake cause I was tracking releng7 -.- ) 4/ retrieved and managed to boot a stock GENERIC kernel from 8.1 or 8.2, whichever you're tracking On 12/27/10 11:42 PM, Troy wrote: I recently rebuilt the world and kernel and everything built just fine and when I went to boot into the new kernel, it hangs. I had to revert back to my previous kernel. Currently I'm running: FreeBSD server.domain.net 8.0-STABLE FreeBSD 8.0-STABLE #1: Sat Jan 23 20:44:06 CST 2010 r...@server.domain.net:/usr/obj/usr/src/sys/server amd64 When it hangs upon boot-up it simply stops here. I don't know how I can figure out what is causing the root of the hang. I'd really like to get this machine upgraded. Ppc0 cannot reserve I/O port range PowerNow0 Cool ‘N’ Quiet K8 on cpu0 Device_attach: PowerNow0 attach return 6 PowerNow0 Cool ‘N’ Quiet K8 on cpu1 Device_attach: PowerNow0 attach return 6 PowerNow1 Cool ‘N’ Quiet K8 on cpu0 Device_attach: PowerNow0 attach return 6 PowerNow1 Cool ‘N’ Quiet K8 on cpu1 Device_attach: PowerNow0 attach return 6 Time Counters Tick every 1.000 msec hang Any help is greatly appreciated. -Troy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: root mount error
Hey michael, First, I'd advise making use of FreeBSD's nextboot utility to test new kernels: http://fuse4bsd.creo.hu/localcgi/man-cgi.cgi?nextboot+8 Second, I would suggest reading the handbook's excellent section on upgrading your machine or rebuilding the kernel: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html Now, a likely cause of your problem is the installation of a custom kernel with removed support for whatever your hard disk drive or raid controller is recognized as. Did you reinstall your old, working kernel, or are you actually asking for help doing just that ? On 12/27/10 9:18 PM, Michael BlackHeart wrote: Hello I've got trouble with FreeBSD 8 Stable First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to yesterday revision I don't remember exact number, but I've have this problem aobut week or two so it's not so important, also as it doesn't work on i386 too. After installing new kernel I've just build - indeed it always was GENERIC for both arch's on clean system - I've got an a kernel painc caused by disability to mount root partition because kernel couldn't see the drive. By pressing '?' I've sen only acd0 that represents CD-ROM. In debug messages I haven't found anything about ad0 - than hdd was identified before new kernel was installed. I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is working with diabled SATA native mode. I've not found any info 'bout this error in recent 8.Stable so I don't know how to handle this one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On 12/27/10 11:58 PM, Clifton Royston wrote: OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. -- Clifton Wait, do you mean like, mergemaster -F ? Excerpt from the manual: -F If the files differ only by VCS Id ($FreeBSD) install the new file. I've discovered this rather recently, it's a *lifesaver* This comes from fbsd7's version though, I can not say for the one you're still running on fbsd6 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On 12/27/2010 16:40, Damien Fleuriot wrote: On 12/27/10 11:58 PM, Clifton Royston wrote: OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. -- Clifton Wait, do you mean like, mergemaster -F ? Excerpt from the manual: -F If the files differ only by VCS Id ($FreeBSD) install the new file. I've discovered this rather recently, it's a *lifesaver* This comes from fbsd7's version though, I can not say for the one you're still running on fbsd6 You always want to run mergemaster from the version you are upgrading _to_. It doesn't happen often (by design) but occasionally mergemaster has to grow special knowledge of specific files/directories/etc. in a new FreeBSD version. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel/World Upgrade causes Hang
Sorry. I am on the RELENG_8 tree and I believe it was building 8.2pre. I did the build about 4 days ago. I am building a custom kernel. Yes I definitely built the world before the kernel and it worked. I did not use -J anything. There is no boot message, it just hangs with what I wrote below. Below is the kernel config I'm using. machine amd64 cpu HAMMER ident servername-removed # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD# Network Lock Manager options NFS_ROOT# NFS usable as /, requires NFSCLIENT options NTFS# NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat (sgtty) options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_43 # Needed by COMPAT_LINUX32 options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options COMPAT_LINUX32 # Compatible with i386 linux binaries options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. options KBD_INSTALL_CDEV# install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache options INCLUDE_CONFIG_FILE # Include this file in kernel options IPSTEALTH options INVARIANTS options INVARIANT_SUPPORT # Make an SMP-capable kernel by default optionsSMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # For SMBFS - mount_smbfs to work by users options SMBFS # SMB/CIFS filesystem options NETSMB # SMB/CIFS requester options LIBMCHAIN # MBUF management library options LIBICONV# Kernel side iconv library # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) device atpic # 8259A compatability # Linux 32-bit ABI support options LINPROCFS # Cannot be a module yet. # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On Tue, Dec 28, 2010 at 01:40:26AM +0100, Damien Fleuriot wrote: On 12/27/10 11:58 PM, Clifton Royston wrote: OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. -- Clifton Wait, do you mean like, mergemaster -F ? Excerpt from the manual: -F If the files differ only by VCS Id ($FreeBSD) install the new file. So *is* freebsd-update invoking mergemaster? There wasn't anything in its man page indicating that, or indicating how to pass flags to it if it is. My assumption was that it wasn't, because it doesn't show the usual mergemaster 4 options with each file (new, delete new, merge old/new, or defer to later.) -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Accidentally aborted upgrade via freebsd-update - how to recover?
On Mon, Dec 27, 2010 at 04:52:03PM -0800, Doug Barton thus spake: On 12/27/2010 16:40, Damien Fleuriot wrote: On 12/27/10 11:58 PM, Clifton Royston wrote: OK, and oh well... I wish there were some way to automate the diffing out of the $FreeBSD lines. I suppose those might be the artifact of some previous upgrade, so that the file version present is not the one expected for FreeBSD 6.1. -- Clifton Wait, do you mean like, mergemaster -F ? Excerpt from the manual: -F If the files differ only by VCS Id ($FreeBSD) install the new file. I've discovered this rather recently, it's a *lifesaver* This comes from fbsd7's version though, I can not say for the one you're still running on fbsd6 You always want to run mergemaster from the version you are upgrading _to_. It doesn't happen often (by design) but occasionally mergemaster has to grow special knowledge of specific files/directories/etc. in a new FreeBSD version. As far as I can tell, freebsd-update doesn't use mergemaster. /usr/src/usr.sbin/freebsd-update/freebsd-update.sh Source installation does, however I don't believe a binary upgrade does. -jgh ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
