OT: thank you to all developers!
Last night I finally got around to building up my first "real" 4.0-RELEASE machine (kind "late" since 4.1 is creeping up on us I know ... but ). I installed 4.0 "fresh" from the CDs, copied my previous machine's /etc files over from a CD backup (with minor edits of course :), cvsup'ed 4-STABLE, rebuilt and installed world and a new kernel, and replaced my 3-STABLE firewall/gateway machine in a matter of hours. All went totally without a hitch in the world and absolutely screams with speed! A huge, giant, chocolate-covered thanks to all developers -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
chapter about using the fixit floppy?
[ cc'ing to -hackers because some content may be relavent outside -doc ] Hello all, Is there a chapter of the Handbook that details how to use the "fixit" floppy? I moved a disk from controller to controller yesterday and in doing so rendered my system unbootable (ad4 went to ad0, fstab is hosed, ooops) because I forgot to change /etc/fstab before shutting down. Rather than just temporarily putting the controller back, rebooting, changing /etc/fstab then moving it again I decided to get some worth out of those CDs I bought (grin :), get my hands dirty, and use the "fixit" option. IMO, it seems like the "fixit" shell one is given via this option (and I suppose by using the "fixit.flp" image) is more difficult to "use" than it should be. I don't profess to be the expert-of-all-gods in FreeBSD but I've sysadmin'ed SunOS boxes and been dorking with FreeBSD since 2.0.5, so I wouldn't consider myself a "newbie" to Unix. Still, it took me a while before I was able to mount my root partition so I could edit the lousy etc/fstab file. I knew the partition I wanted was ad0s1a but there was no device file for this partition in /dev or /dist/dev (aka /mnt2/dev I believe). So, I copied over MAKEDEV from /dist/dev and after seeing reference to using the $MAKEDEVPATH variable I was able to get MAKEDEV to work with a single edit--mknod is hard coded in there as /sbin/mknod but inside the "fixit" shell, mknod is reached through /mnt2/sbin/mknod (there were other trivialities like symlinking /dist/etc/group to /etc/group so mknod wouldn't complain about the group 'operator' not existing, etc.). So, my questions are two-fold: 1) Can we/shouldn't we populate the CD's /dev with every entry that could be created with MAKEDEV (including all the partitions that can be within slices of a disk)? If that were the case, then all I would have had to do was "mount -t ufs /mnt2/dev/ad0s1a /whatever" and went about my business editing. 2) If this is NOT a good thing to do, can we/should we make MAKEDEV not point to /sbin/mknod but rather to something in the path? At that point it should be trivial to write a section of the handbook detailing that all somebody needs to do to make devices is: cd /dev MAKEDEVPATH=$PATH; export MAKEDEVPATH sh /mnt2/dev/MAKEDEV whatever0 and they could then begin the business of fixing what needed fixing. If populating the CD's (and/or fixit floppy's) /dev with all known devices isn't the correct thing to do, I can provide patches to MAKEDEV if that's the correct route as well as a section for the handbook (at least in ASCII--I'll need help sgml'ing it). I'm looking for input from people. Perhaps it was just too late last night and I'm being dense (i.e. is the "fixit" procedure really this 'difficult' to use). Comments? Thanks, -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation [EMAIL PROTECTED] My opinions are mine, not Intel's. Running [EMAIL PROTECTED] FreeBSD 3.5-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
unable to use disklabel -B from fixit floppy?
Hello all ... hope this is the right group for this Last night I had to re-install win98 on my IDE drive (dual-boot) and it happily clobbered my mbr. No problem. I've had this happen before. I booted up 4.0 from my CDs and chose the "Fixit" option from the CD-ROM. I tried: disklabel -B ad0 and I got this back: disklabel: bad bpack magic number (label is damaged, or pack is unlabeled) huh? So, then I just fell back to method #2 which I've done before in going into the partition editor within sysinstall, editing NOTHING but hitting 'w' to write the current information along with the boot sector. This happily worked. But, why did I get the wierd error above? Previously I had compiled and installed a new 4.1-STABLE world. Is the disklabel command from 4.0 somehow incompatible with device entries or something else in 4.1-STABLE? I also tried downloading the fixit.flp image from 4.1-RC, making that, and using that as the floppy from within sysinstall. Still no dice in using disklabel. Is this error message familiar to anybody? -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation [EMAIL PROTECTED] My opinions are mine, not Intel's. Running [EMAIL PROTECTED] FreeBSD 4.0-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: unable to use disklabel -B from fixit floppy?
[ copying -doc because I've got a doc patch for the FAQ ... perhaps :) ] [ On Thursday, July 27, John Baldwin wrote: ] > > Umm, well. First off, disklabel -B doesn't fix your MBR. fdisk does that, > or boot0cfg if you are using boot0 to dual-boot. However, can you type Hmmm. Must have just been bit-rot in my brain from WAY back. Maybe it was the 3.x to 4.x transition where I remember seeing ``do disklabel -B'' ... can't remember. OK, now I know boot0cfg so I'll remember that. Thanks very much! > disklabel ad0 now and get useful information? Or disklabel ad0sX (where X > is the slice number for your FreeBSD slice)? oh yes, no problems. > Yes, this touches the MBR. The disklabel command serves the same purpose as > the label editor in sysinstall. IOW, you use disklabel to lay out partitions > (a-h) within a FreeBSD slice. > > See if disklabel ad0 works now. Absolutely. Since this is a way to recover the MBR in addition to what was already in the FAQ, I hacked up some changes to that FAQ entry. Attached is a diff--be gentle, this is my very first time attempting to hack SGML :) ... (I will go ahead and just send-pr this as well ) --- book.sgml.orig Thu Jul 27 11:08:53 2000 +++ book.sgml Thu Jul 27 11:38:03 2000 @@ -1306,22 +1306,22 @@ -Can Windows 95 co-exist with FreeBSD? +Can Windows 95/98 co-exist with FreeBSD? -Install Windows 95 first, after that FreeBSD. FreeBSD's boot -manager will then manage to boot Win95 and FreeBSD. If you -install Windows 95 second, it will boorishly overwrite your +Install Windows 95/98 first, after that FreeBSD. FreeBSD's boot +manager will then manage to boot Win95/98 and FreeBSD. If you +install Windows 95/98 second, it will boorishly overwrite your boot manager without even asking. If that happens, see the next section. -Windows 95 killed my boot manager! How do I get it back? +Windows 95/98 killed my boot manager! How do I get it back? You can reinstall the boot manager FreeBSD comes with in one of -two ways: +three ways: @@ -1351,6 +1351,24 @@ prompt, be sure to select "Boot Manager." This will re-write the boot manager to disk. Now quit out of the installation menu and reboot off the hard disk as normal. + + + +Boot the FreeBSD boot floppy (or CD-ROM) and choose the +Fixit menu item. Select either the Fixit floppy or +CD-ROM #2 (the live file system option) as appropriate +and enter the fixit shell. Then execute the following command: + + +Fixit# boot0cfg -B bootdevice + + + +substituting bootdevice for your real boot device such +as ad0 (first IDE disk), ad4 (first IDE disk on auxiliary controller), da0 +(first SCSI disk), etc. + + + -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation [EMAIL PROTECTED] My opinions are mine, not Intel's. Running [EMAIL PROTECTED] FreeBSD 4.0-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
does this affect FreeBSD too?
Just saw this on slashdot http://www.guninski.com/openbsdrace.html looking over the Open/NetBSD patches, does this apply to us as well? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation [EMAIL PROTECTED] My opinions are mine, not Intel's. Running [EMAIL PROTECTED]FreeBSD 4.3-STABLE. FreeBSD: The Power to Serve. http://www.reynoldsnet.org/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
mgetty+AutoPPP pointers?
Hello all, I want to configure a server machine I have at home to answer a phone line via internal modem and setup a PPP connection to the "outside world" (the machine is connected via broadband) for a Win98 machine being the remote caller. I've read up a little on mgetty and its use of AutoPPP to fire off pppd via various google searches. Many of the links I've brought up are reasonably decent explanations, but based around Linux setups. Does anybody have any bookmarked pointers to setting up mgetty+AutoPPP under FreeBSD -STABLE? I've dug through a few bits and I know our in-tree compilation of pppd is compiled with -DCHAPMS (which the Linux-related pointers said to make sure you used when compiling pppd) and our port of mgetty+sendfax does define -DAUTO_PPP during compilation (which was another "must"). Is there anything else that is needed to enable the code to DTRT? If anybody has done this sort of thing and wishes to share config files, or "gotchas" I would much appreciate it! Please 'cc:' me. After grepping the archives, it looks like this topic has come up a lot with varied answers but no real "pointers." If somebody has pointers or sample config files, I would be happy to try and mark them up and submit them to the -doc project! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, (space for rent, cheap!) | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
boot0 screen output with dual-boot of FreeBSD / WinXP
Hello all, a quick question about boot0. I recently put together a new machine and had always planned to dual-boot FreeBSD -current and WinXP on it. At first I used FreeBSD to partition the 120Gb drive into roughly "half". I installed FreeBSD on the second slice and just last night installed XP onto the first "partition" (windows term). Of course XP clobbered the boot manager, but having rescued it before from win98 I booted from the CD and chose the 'W' option within the partition stage to get my boot mgr back. After rebooting from there I see: F1 ?? F2 FreeBSD at the prompt once the machine boots. My fuzzy memory seems to recall from years back that seeing ??'s was "bad" as it meant the boot mgr couldn't find out something it wanted. I chose both F1 and F2 in multiple boots and each OS boots fine and acts normal. I dug into the boot0 code a little bit trying to see why ?? was printed and not something else. First off I used /stand/sysinstall again to see what the partition type was. This is what it showed me: Disk name: ad2FDISK Partition Editor DISK Geometry: 14593 cyls/255 heads/63 sectors = 234436545 sectors (114470MB) Offset Size(ST)End Name PType Desc SubtypeFlags 0 63 62- 12 unused0 63 104856192 104856254ad2s1 4 NTFS/HPFS/QNX7 104856255 129580290 234436544ad2s2 8freebsd 165 234436545 5103 234441647- 12 unused0 Then I dug into the code a bit and saw this: # These values indicate bootable types we know the names of # .byte 0x1, 0x4, 0x6, 0xb, 0xc, 0xe, 0x83 .byte 0x9f, 0xa5, 0xa6, 0xa9 # These are offsets that match the known names above and point to the strings # that will be printed. # .byte os_misc-. # Unknown .byte os_dos-. # DOS .byte os_dos-. # DOS .byte os_dos-. # DOS .byte os_dos-. # Windows .byte os_dos-. # Windows .byte os_dos-. # Windows .byte os_linux-.# Linux .byte os_bsd-. # BSD/OS .byte os_freebsd-. # FreeBSD .byte os_bsd-. # OpenBSD .byte os_bsd-. # NetBSD # # And here are the strings themselves. 0x80 or'd into a byte indicates # the end of the string. (not so great for Russians but...) # os_misc: .ascii "?";.byte '?'|0x80 os_dos: .ascii "DO"; .byte 'S'|0x80 os_linux: .ascii "Linu"; .byte 'x'|0x80 os_freebsd: .ascii "Free" os_bsd: .ascii "BS"; .byte 'D'|0x80 So, it appears that partition type "7" just isn't a "known" type. Other partition types seem to just "map" to print "DOS" (or whatever else). I couldn't see where the "os_misc" string would be printed in the case of an error of any sort, so can I assume that all is well with this partition and dual boot combo and just ignore the '??'? Is it possible to add in another table entry for type 0x7? Is it advisable? Thanks, -Jr -- John & Jennifer Reynolds johnjen at reynoldsnet.orgwww.reynoldsnet.org Structural / Physical Design - ICG/PNG SCD jreynold at sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. FreeBSD: The Power to Serve! "Unix is user friendly, it's just particular about the friends it chooses." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SURVEY: Sound cards that work under FreeBSD
Hello all, I'm working with Nik Clayton to update FAQ 3.15 to give a more comprehensive list of sound cards known to work with FreeBSD. That's why I'm sending out this template to this list. Please take the time to fill it out with information regarding your sound card so that we can compile a better list for posterity. I will do my best to keep the list current as FreeBSD evolves (please send to me or cc: me along with the list--it'll be easier to filter responses than grabbing them out of -hackers-digest :). Please be as specific about makes, models, chipsets, etc. as you can. The author of the first mail received regarding a specific sound card will be listed as the contributor of that information (unless he/she does not want his/her e-mail address listed :). Please note also that I would like information about sound cards that do NOT work (as of yet) under FreeBSD if anyone has experience with them. Hopefully, this will go well and we will be able to branch out into other pieces of supported/non-supported hardware in the future. Thank you. Survey: --- 1) The sound card make and model/chipset. Please be as specific as you can with board rev numbers if possible. Please include wether the card is ISA or PCI. 2) FreeBSD version(s) it was tested with. List *all* versions of FreeBSD for which you can verify that the sound card does/doesn't work (don't include -BETA or -SNAP releases but dates on -STABLE and -CURRENT branches are welcome). 3) Appropriate lines from your kernel config file / PNP setup. i.e. what did you have to do to get this card working? Did you need patches not committed to a particular branch (if so URLs would be welcome)? Do you use OSS drivers instead? 4) Sample dmesg output for properly configured device. Show the world what boot messages relate to the device after properly configured. 5) Miscellaneous notes. State anything "not obvious" to the casual FreeBSD user. Good examples might be, "volume is 0 by default, use mixer(1) to adjust at boot time," or "sh MAKEDEV snd1 for the 1st device, not snd0." 6) Is it OK to publish your e-mail address / name as the contributor of this information? You may type in an anti-spam version of your e-mail address below if you would like that option instead. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | jreyn...@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
SURVEY: Sound cards that work under FreeBSD
Hello all, I'm working with Nik Clayton to update FAQ 3.15 to give a more comprehensive list of sound cards known to work with FreeBSD. That's why I'm sending out this template to this list. Please take the time to fill it out with information regarding your sound card so that we can compile a better list for posterity. I will do my best to keep the list current as FreeBSD evolves (please send to me or cc: me along with the list--it'll be easier to filter responses than grabbing them out of -hackers-digest :). Please be as specific about makes, models, chipsets, etc. as you can. The author of the first mail received regarding a specific sound card will be listed as the contributor of that information (unless he/she does not want his/her e-mail address listed :). Please note also that I would like information about sound cards that do NOT work (as of yet) under FreeBSD if anyone has experience with them. Hopefully, this will go well and we will be able to branch out into other pieces of supported/non-supported hardware in the future. Thank you. Survey: --- 1) The sound card make and model/chipset. Please be as specific as you can with board rev numbers if possible. Please include wether the card is ISA or PCI. 2) FreeBSD version(s) it was tested with. List *all* versions of FreeBSD for which you can verify that the sound card does/doesn't work (don't include -BETA or -SNAP releases but dates on -STABLE and -CURRENT branches are welcome). 3) Appropriate lines from your kernel config file / PNP setup. i.e. what did you have to do to get this card working? Did you need patches not committed to a particular branch (if so URLs would be welcome)? Do you use OSS drivers instead? 4) Sample dmesg output for properly configured device. Show the world what boot messages relate to the device after properly configured. 5) Miscellaneous notes. State anything "not obvious" to the casual FreeBSD user. Good examples might be, "volume is 0 by default, use mixer(1) to adjust at boot time," or "sh MAKEDEV snd1 for the 1st device, not snd0." 6) Is it OK to publish your e-mail address / name as the contributor of this information? You may type in an anti-spam version of your e-mail address below if you would like that option instead. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
