Re: Qwest DLS MSN Premium Linksys Router FreeBSD.. Oh my
Kris Anderson [EMAIL PROTECTED] writes: I'm getting off cable (Comcast and 6 megabits) and Good move. Their fine print - Don't forget the finer print. Invisible print might be a better term; good luck even finding it before committing yourself. More below. home phone pac kage ($24.99 otherwise), free Check out which phone pac that is. I doubt very much if regular phone service is considered to be a home phone pac; I mangaged to find (after considerable searching) their page for ordering non-pac phone service to get a 12.50 basic service (before more than that in various fees and taxes, one which seems to be part of _their_ taxes -- grrr). restrictions may apply. MSN ISP requires agreement to MSN Acceptable Use Policy. Yeah, after considerable searching I found a MSN Subscription Agreement link at http://support.msn.com/ which took me to a member sign-in form. Do you really want to do business with a company that does business like that? So am I right in still thinking that with MSN as the ISP my setup it isn't going to be FreeBSD friendly and that my spiffy little Comcast setup isn't going to work with MSN as the ISP? I can't help you; and I wouldn't help MSN if I could. I know I first bought a (used) modem that was guaranteed to work with Qwest and a non-MSFT ISP, but I later learned that it would only work with Qwest+MSN and had to pay a restocking fee to get most of my money back. Grrr. I found what seems (in about 5 mo) to be a good ISP at opusnet.com . Relatively good contract terms and in actual practice, so far. And about as cheap as they come. Note that _almost_ all ISPs have indemnity clauses whereby you agree to pay their legal and other costs if some third party makes claims against the ISP which involve you in any way, whether or not you've done anything wrong in most such clauses. Another facter is how far away the courthouse and your lawyer would be. Last time I looked, Quest had no indemnity clause for their pure DSL service, but they had one in their ISP contract and, of course, MSN does too. I say of course, but I should note that MSN.net is one of increasingly-few web sites that has no indemnity clause in the site-use contract. Even such open source sites as Slashdot have them these days. I assume the risk of using such sites in read-only mode, but seldom, if ever, post anything to them. BTW, my insurance guy knows of no personal insurance against such indemnity risks. I bought a DSL modem at Fry's for about 10 $ more than Qwest's, mostly because Qwest has given me many reasons to dislike and distrust them and partly because my modem has a 2-yr guarantee. It is a Zoom ADSL X5 and seems to work fine and was easy to configure once I got past some problem that I had with Mozilla not accessing the modem's configuration web forms correctly. (I've already forgotten the cause.) Beware that the Zoom modem package says in big print that it comes with DSL filters and in fine print it says how many it comes with, which I didn't notice was _zero_. Grrr.) With the Zoom modem, at least, you may configure it to run DHCP and give the modem a fixed (eg, 10.something) IP address or run DHCP on whatever you connect to the modem. The Zoom X5 is also a 4-port router, but this one was not wireless like the Qwest modem. Finally, beware that a few weeks ago DSL providers like Qwest got permission (from the US gov) to refuse to do business (after 2005, IIRC) with good ISPs like opusnet.com, so don't be suprised if your choice in 2006 is between Qwest+MSN and Comcast+Comcast. Grr. -- Grry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What are the likely causes of reboots?
Paul Schmehl [EMAIL PROTECTED] writes: What are the possible causes of spontaneous reboots? And what artifacts would be left behind that might indicate the I had an old EISA 486 do that several times a week when the external RAM cache went flakey. I don't recall the error logs, except a vague recollection that they gave no clue. The only way I determined the cause was because I could (and did) turn off that cache in the BIOS setup. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How can I programatically eject a live cd?
/usr/ports/sysutils/eject/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hidden spot on hard drives?
Norberto Meijome [EMAIL PROTECTED] writes: Where does HPA(Host protected Area) sit in all this? is this the 'boot sector' trick? I don't know. I just heard that some computer makers are somehow reserving as much as half the HDD for a full copy of the OS to recover from when the normal one trips over itself. I'm guessing that this has more to do with MSFT licensing terms than with saving a buck from not including a CDROM. I wonder if there's some low-level way to tell a modern disk drive where you want sector 0 to start. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: passwd file corrupted
Efren Bravo [EMAIL PROTECTED] writes: #vipw root returns- usage: vipw [-d directory] See that usage msg? Compare it with your commands. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stored hard drive failure?
If you're really serious (to borrow a phrase), you'll do backup to several different media and maybe different formats. With RAID or backup to an always-powered second HDD, you can loose all of your disks if the case power supply or MB fails in certain ways. (I know someone who lost a disk when the MB failed.) Or if someone steals your computer or in a fire. With removable HDD, you risk physical damage either from lack of use or shock. FYI, I kept a 45 GB IBM and a 80 GB Seagate drive in a outside storage shed which got hot, cold, and damp for 10 months and they work fine. I guess I've been lucky because I've had only one failure from about 15 lightly-used disks and have occasionally reused 5- to 10-year-old disks for short durations after years on the shelf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hidden spot on hard drives?
Jonathon McKitrick [EMAIL PROTECTED] writes: 1. Any idea where this info could be stored? The obvious place is the end of the first track between the boot sector(s) and the first partition. But that's probably too easy and well-known. As others have noted, Unix (eg, dd) has easy access to all of the standard sectors of the HDD. But I think I recall reading about some software that does some kind of special accesses of the disk drive, say to write to sector # and then tell the disk to mark that sector bad and use one of the spare sectors in it's place. Something tricky like that that OS code doesn't know how do without a custom driver that understands very low-level HDD control. Of course, if their software can undo it, anyone's could, but not if you don't know how, or maybe they've managed to pick the sectors cryptographically or something, making the job really tough. I've also heard of copy protection moving heads half a cylinder and storing data between normal tracks, but that was probably on floppies; HDD tracks probably almost overlap as it is. 2. Any way the same thing could be done under FreeBSD? Of course, but here's no code to do it now, AFAIK. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: music on FreeBSD
Danny Pansters [EMAIL PROTECTED] writes: CCL is fine for contributed docs and artwork. Everyone seems to do it. There's no license issue. At least one CCL allows no derivation under any terms, which would at least raise an issue, I'd hope. I'm not aware of any CCLs in FreeBSD other than the two GNU licenses (but I haven't looked for others). I'm not sure who he should ask if they want that; releng@ ? From http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/pref-license.html The FreeBSD project discourages completely new licenses and variations on the standard licenses. New licenses require the approval of [EMAIL PROTECTED] to reside in the main repository. The more different licenses that are used in the tree, the more problems that this causes to those wishing to utilize this code, typically from unintended consequences from a poorly worded license. I doubt if no-commercial-use licenses would be approved for use in the base OS, because of the previously-mentioned sale of CDROMs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: Re: music on FreeBSD
I've had a few more thoughts on the matter. If core wants the music and the only question is licensing, maybe core and you could agree on a custom license which allows anyone to copy it unmodified (which must include being copied as a single file from any web site) or including it unmodified in a compilation or other derivative work (eg, FreeBSD), but not if that work consists predominately of music. It would be easier if you could just allow all uses in unmodified form (I think there's such a CCL), and better if you could allow generic translations of digital format. OTOH, I'm guessing core could find someone to donate some music under a BSD-type license, without a lot of effort. Or get some non-proprietary music off an out-of-copyright record or movie which is probably on the web somewhere already. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What do scary messages from dump mean?
On FreeBSD 5.4-R, I did a backup using 4 dump/restores and each dump (-0L) gave two scary-looking lines like those that stick out here: ... DUMP: estimated 71239 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] warning: ./.snap: File exists expected next file 4037, got 180 DUMP: DUMP: 72413 tape blocks DUMP: finished in 10 seconds, throughput 7241 KBytes/sec ... 1) Why should dump warn about ./.snap when the manpage implies that not having one is a problem that it explains how to fix? 2) What's the expected line trying to tell me? I can guess that file 4037 means inode 4037, but I don't know what I'm supposed to do with this information. One could worry that the dump was bad. Should it be telling me things like that? What could the manpage say to explain such a message? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld
Radek Válko [EMAIL PROTECTED] writes: I'm little bit new in FreeBSD and I would like to know more about buildworld process. I really tryed to find this information but I wasn't successful. My question is what everything is exactly build during this process. The entire base OS, excepting the kernel and kernel modules. For examle if I have minimal installation of FREEBSD 5.2.1 and I will synchronize my source tree to 5-stable and then do make buildworld what happend? Same answer. AFAIK, the best doc of this is the top of /usr/src/Makefile. Is the new system again only minimal or full installation? I suppose that you're using the language of the installer and I'm sorry to say I'm unsure what that means, unless it's referring to installing more or fewer packages (or ports), and make buildworld has nothing to do with those. But you CAN build and install more or less than the base OS, by using a custom /etc/make.conf, for instance, using NO_SENDMAIL; see /usr/share/examples/etc/make.conf and make.conf(5) manpage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Periodic Weekly Report
Giorgos Keramidas [EMAIL PROTECTED] writes: # flame:/usr/src$ find . -type f | egrep -e '\.(man|[0-9]+)$' | xargs grep '\.Ft[[:space:]]*$' A Bourne script which egreps installed manual directories: find $(manpath|sed s/:/\ /g) | xargs grep -EZH $@ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Good Operating systems book?
Jorge Mario G. Mazo [EMAIL PROTECTED] writes: I would like to hear what books are good for newbies like me! Some good reading to get exposed to some history and culture as well as some high-level discussion of programming is The Art of UNIX Programming by Eric S. Raymond 2004 Addison Wesley ISBN 0-13-142901-9; ESR tends to be a Linux guy but you wouldn't know it from this book. He includes a fair number of small-paragraph quotes from some UNIX pioneers. There's more whys in the book than hows. And cheap by today's standards at 40 USD. 525p. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot solution
K Wieland [EMAIL PROTECTED] writes:
If anyone could add to this I would be interested.
I suppose that you say
Even if you choose not to alter the MBR.
because of the last install menu item below
{ { BootMgr, Install the FreeBSD Boot Manager,
{ Standard, Install a standard MBR (no boot manager),
{ None, Leave the Master Boot Record untouched,
(from src/release/sysinstall/menus.c)
That last one is clearly misleading, even if it is in the context of
picking a boot manager, because later fdisk operations are certainly
able to change the MBR's primary partition table, including the
active bits that gave you trouble.
I'll try to get the menu items changed to something like:
{ { BootMgr, Install the FreeBSD interactive boot manager,
{ Standard, Install the FreeBSD non-interactive boot manager,
{ None, Don't Install any boot manager,
If you'd like, you could file a formal PR about this (and CC me,
please) and maybe someone will beat me to it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Problem
Glenn Dawson [EMAIL PROTECTED] writes: boot0cfg -B -s 5 ad0 boot0cfg -B -s 2 ad2 I don't remember who asked what before, but you should also try: boot0cfg -B -s 5 -o packet ad0 boot0cfg -B -s 2 -o packet ad2 fdisk /dev/ad0 fdisk /dev/ad2 bsdlabel /dev/ad0 I wouldn't bother if you don't have BSD on that disk. bsdlabel /dev/ad2 and bsdlabel /dev/ad2s1 bsdlabel /dev/ad2s2 bsdlabel /dev/ad2s3 bsdlabel /dev/ad2s4 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what was it ?
Yuri van Overmeeren [EMAIL PROTECTED] writes: Depends on the filesystem you use, FAT16 has a 2GB limit, FAT32 (in theory) supports very large partitions but I think you could get in trouble at 127GB or 137GB with MS-Dos. Newer MS-Dos (or other doses) support FAT32. Old is relative, huh? I recall the big hurdle for a long time was the BIOS INT 13 limits of 1024/16/63 C/H/S ~= 504 MB. The minicomputer at work a few years before that had 14 (?) disk packs of several platters each which held either 5 or 10 MB. Then there was my first CP/M PC with 48 or 64k RAM and 50k floppies. And embedded systems that fit in 2k RAM. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Problem
John Do [EMAIL PROTECTED] writes: fdisk, etc, looked good. boot0cfg -v /dev/ad0 # flag | start chs | type| end chs | offset | size 1 0x80 0: 1:10x07 1023 254:63 63 40001787 OK. boot0cfg -v /dev/ad2 # flag | start chs | type| end chs | offset | size 1 0x00 0: 1:10x07 1023 254:63 63 133114527 2 0x00 986: 2:10x05 903 15:63 133114590 10239138 3 0x001024 254:630x83 1023 254:63 143364060 48195 The type on line 2 should be 0xa5, not 0x05, but I suspect a typo. I don't know if one of the flag's needs to be 0x80, or not. Both of my disks have one marked 0x80. It's probably OK, and just means you don't have a default slice, eg, set with -s 2 in boot0cfg. I don't remember who asked what before, but you should also try: boot0cfg -B -s 5 -o packet ad0 boot0cfg -B -s 2 -o packet ad2 You didn't say if you tried those, but it doesn't seem to be the problem (yet). You would need -o packet on ad2 and LBA BIOS mode, I think since your FreeBSD slice goes past 1024 cyls. But that 133114590 number looks right, and I see no other problem. So it looks like the the MBR code just doesn't see the second disk. Probably because the BIOS doesn't play well with the MBR code, and I can't think why. It should even have to get the geometry right since it only has to grab the first sector of the disk. And you know other software can see the disk. At this point I'd give up on boot0 and try to find a Grub (or GAG?) floppy to boot from. It should let you boot both systems. Or try a boot manager from the MSFT world. Sorry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install GRUB for FreeBSD
John Do [EMAIL PROTECTED] writes: Linux GRUB is simple and intuitive to use and BSD loader has me lost after weeks :( I know both enough to say that BSD's is way more intuitive and much simpler to configure and install. I even installed GRUB into MBR and the BSD bootloader won't go away! :( I've made mine go away several times. Note that you shouldn't need to get rid of the MBR on the second disk, with Grub on the first. I don't know if Grub can be made to boot the second disk's MBR, or not. Probably. Someone please tell me what the best way to install grub is I guess you need it in the MBR but where will the menu.lst be stored? It starts out on a floppy file system. Then you either just boot off the floppy, or you install it to the hard disk MBR, other first-track sectors, and maybe your OS's root FS. I don't recall if you need a menu.lst or not. That is, I don't know if Grub can be installed only to the first track, or needs the menu.lst in an FS; it seems like a bad requirement, if so. You might search the Internet for a pre-build Grub floppy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install GRUB for FreeBSD
Micah [EMAIL PROTECTED] writes: In order for grub to work as a menu, it requires a stage 2 loader that resides somewhere on your hardrive outside of the MBR. It's my understanding that grub was too big to fit just in the MBR and that necessitated this arrangement. If you don't mind manually typing in Yeah, but I definitely remember that Grub installs stuff on other sectors of the first track, probably staring with the second sector. So it should be able to store the menu stuff there too, but I don't know if it actual can (I also had it using the menu file in /boot/boot/grub, I think it was for some odd reason). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel and c partition
Valerio daelli [EMAIL PROTECTED] writes: Is it preferable to use another partition? At least because /boot.config only works on a, it has been recommened that a be used, and maybe because almost every one uses it, I've never learned what bad things happen if you don't use a. You're unlikely to ever use /boot.config, BTW. 5.4 didn't install one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Environment setting for make
Joel Hatton [EMAIL PROTECTED] writes: # E.g. use `env MAKEOBJDIRPREFIX=/somewhere/obj make' However, and at this risk of exposing my inexperience and just plain old sounding foolish, how does this method of setting MAKEOBJDIRPREFIX differ from: setenv MAKEOBJDIRPREFIX /somewhere/obj It's effect is only seen by make, instead of all subsequent commands. It also works in a Bourne shell where the Bourne equivalent of the second method is: MAKEOBJDIRPREFIXj=/somewhere/obj make Also, in the example above, is the backquote '`' intended, or is that for compatibility for something like tex? It's a (misguided, IMO) attempt at having left and right quotes. In some fonts, it's almost invisible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Environment setting for make
Joel Hatton [EMAIL PROTECTED] writes: I'm a little confused about the Bourne shell, however. Do you mean that (1) 'MAKEOBJDIRPREFIX=/somewhere/obj make' is equivalent to (2) 'setenv MAKEOBJDIRPREFIX /somewhere/obj' or (3) 'env MAKEOBJDIRPREFIX=/somewhere/obj make'? Can (1) be substituted for (3)? Yes, (1) == (3), except (3) works in any shell. From my trials, (1) and (2) aren't similar as MAKEOBJDIRPREFIX remains unset in the shell after make exits for (1). In csh (2) has the same effect as the Bourne 'export MAKEOBJDIRPREFIX=/somewhere/obj' Correct. And same as 'MAKEOBJDIRPREFIX=/somewhere/obj; export MAKEOBJDIRPREFIX' ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installation woes
Rogelio Rodríguez [EMAIL PROTECTED] writes: I have Phoenix Award BIOS v6.00PG (as it seems to identify itself) and a Seagate Barracuda 7200.7 Plus (ST3120026A) and they don't seem to like each other. When partitioning, it's suggested that the harddrive geometry seems unlikely though the install seems to go off without a problem--tried changing the geometry to what the BIOS believes the geometry to be that doesn't work. Anywho, it can boot off of the harddrive but can't mount root. At the mountroot prompt, '?' tells me that acd0 is the only drive. So there's no hard drive after all. The motherboard is an ABIT KV8 Pro... Any ideas? It would help to provide more details, like which version you were installing and more about the error symptoms. I'm not sure even what the mountroot prompt is. Do you get the beastie ASCII art? Are you getting a lot of boot messages before it prompts you? Did any say anything about ad0 or such? It seems odd that it would boot the kernel with /boot/loader, but not find a filesystem to mount, because that filesystem is the one it should find. You didn't by any chance mount /boot on a separate filesystem than /, did you, like in Linux? You can't easily do that with FreeBSD. I will say that in the last several years, my big disks have always been 255/63 heads/sectors in the BIOS, but FreeBSD 5.4 complains and uses 16/63 and everything works fine. (I seem to remember it using 255/63 in 4.X, but maybe my memory's failed me on that.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can I do this?
Bob Hall [EMAIL PROTECTED] writes: Make the changes in rc.conf so that the box will be configured correctly then next time it is rebooted. To change the address without rebooting, you'll have to use ifconfig. Do For some of the variables in rc.conf, you can reactivate changes using scripts in /etc/rc.d, but I'm sorry to say I don't know if this is the case here. Maybe: /etc/rc.d/netif ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing a MBR (and more) that ??? trashed
Gayn Winters [EMAIL PROTECTED] writes: 1. What did/do I need to do to completely fix the Master Boot Record? (Short of reinstalling FreeBSD!) I like what the other guy said about -o packet. 2. Was the disk label on the FreeBSD slice ad1s2 really corrupted? If Unlikely, at least until you ran sysinstall. I've never figured out how it handles existing disklabels. Badly, in my limited experience. Use bsdlabel from a rescue CD and see what you have there. If you're concered about the mount points, mount the / device and look in /etc/fstab. 3. I couldn't get sysinstall to fix this mess - even though I thought it was fixing the FreeBSD partition mount points and applying a new BSD Boot Manager. I couldn't get these fixes to commit. Can sysinstall fix this mess without reinstalling? I'd use a rescue system -- either CD or another hard disk. 4. How do I avoid this situation when I add another disk? (Other than trash the w2k partition.) I don't know about dual-booting MSFT, but you could dd the first tracks of the HDD and it's primary partitions to files on a formatted floppy or two for safe-keeping, before doing anything that could mess up the boot records. You might want to save the first track of your FreeBSD primary partition too. You can then put them (or selected sectors) back with dd from most unixy rescue OSes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: one answer
legalois [EMAIL PROTECTED] writes: But that does not explain when, how or why? It was earlier than 20'jun'93, the oldest master.passwd in CVS which says that it was imported from 386BSD 0.1. It's easier to guess an explanation for this orignal entry: daemon:*:1:31::0:0:The devil himself:/root: That lasted only 8 months in FreeBSD, and the exorcism was not mentioned in the CVS commit message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4.11 minimal install man pages
David Christensen [EMAIL PROTECTED] writes: Any suggestions? See what manpath command gives you. If bad, read it's manpage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i386/amd64 co-exist
Sean [EMAIL PROTECTED] writes: I would like to be able to setup a system so that on power up I can choose weather to boot into either i386 or amd64. Is this possible or would I some how have to install the two releases on their own? I'm fairly sure it could be done, but you'd have to have pairs of most system and program directories and do a bunch of unusual (AKA untested) configurations and have some custom boot scripts and it would likely be more trouble than it's worth. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Will USB serial ever be fixed?
Paul Marciano [EMAIL PROTECTED] writes: So without wanting to offend (whilst secretly being pretty frustrated with the corner I find myself in) I would like to know, hopefully from someone responsible for the subsystem, if ucom/ftdi is likely to be fixed in the next six months. You can probably learn something about who, if anyone, is responsible by poking around http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't execute a script
bob self [EMAIL PROTECTED] writes: xxd scripttest: 000: 2321 2f62 696e 2f73 680d 0a65 6368 6f20 #!/bin/sh..echo ^^-- BAD NEWS It doesn't work on 5.4, either, or probably any Unixy OS. BTW, the base OS comes with hd for a similar display. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't execute a script
N.J. Thomas [EMAIL PROTECTED] writes: Normally, that doesn't matter because most Unix utilities are multi-eol-format aware, but you can't have it in the shebang line because the OS interprets the extra carriage as part of the command, so it is looking for /bin/sh^M, which doesn't exist. Know any reason that shouldn't be fixed? POSIX requirement maybe? What software reads the whole shebang line? (The sh shell apparently reads at least part of it, but I suppose some library functions do too.) Should I write a PR on it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tarring a dump. Problems with a pipe
Robin Smith [EMAIL PROTECTED] writes: dump -0 -f - /dev/yourfilesystem |bzip2 -c dump.bz I compressed a filesystem dump (on Athlon 64/3200+, i386 OS) and bzip2 compressed to 50% of 2 GB in 1118 sec gzip compressed to 52% of 2 GB in 306 sec But bzip2 can compress much better than that on some stuff. If your goal is a small backup, bzip compresses better. If your goal is a quick backup to disk, gzip is faster. If your goal is a quick backup to tape, bzip is faster because tape is so slow, unless your CPU can't keep up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tarring a dump. Problems with a pipe
Parv [EMAIL PROTECTED] writes: In this context, by bzip did you actually meant bzip2? (There is a archivers/bzip port.) No, I presented bzip2-labeled test results and then made statements about archivers/bzip. But I suppose they're true about bzip2 too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configuring xterm
Rem Roberti [EMAIL PROTECTED] writes: 2) The font size in the xterm window is quite small. How do I change the font size? A quick but temporary way not yet mentioned is to press ctrl and then drag pointer-button-1 to select a new size. Try the other two buttons too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What is 6.0-BETA4?
That is, what event created it and, if it is a changing thing, what event will cause it to stop changing? I'm guessing from the announcement which says that one can get it from from the RELENG_6 CVS branch, that it is a generic name for any OS made from RELENG_6 between its announcement and the later announcement of a so-called 6.0 release candidate. Correct? Or are there some kind of markers in the CVS? Or...? And do release candidates have their own actual CVS branches and tags? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How should I partition 2 80 gig drives?
bob self [EMAIL PROTECTED] writes: I want to set up FreeBSD 5.4 Release to fully use 2 80 gig hard drives. I'm not sure how I should set these up in disklabel editor. I just want to use this as a general purpose machine. I've been happy giving my two 80 GB disks 4 equal-sized primary partitions so it's easy to back one up, esp. before doing an upgrade, etc. Or use one or more for extra storage, etc. Maximizes flexibility and I seldom fill one anyway. I only regret that I let the first pri.part. be oddly sized because it can't have the first track. I told myself I'd use those for Linux or data. I've always tried to partition on cylinder boundaries, but the partitioner didn't obey for the first pri.part. I plan to try partitioning my next disk on track boundaries, with all four the same size. As for FreeBSD divisions, I have something like: subpart CylsApprox MBUse a16 125 / b70 549 swap e70 549 /var f11388926 /usr g11388926 /home /: I'm using 71 MB on / with by far the biggest user being three versions of /boot/kernel/, so 125 seems about right. swap: Swap should be big enough to hold all the programs you plan to run at the same time, minus your RAM size. Except, if you plan to make OS crash dumps, swap should be at least as big as your RAM and another MB might be safer. 500 MB - RAM seems a good minimum these days, except the installer probably requires 0. (I seldom use any swap with 512 MB RAM, but xosview can show a broken program filling it up, so it's good to have more than the minimum.) /usr, /home: Use your own judgement on the size ratio. I'm using 3 GB in /usr and I've got a lot of stuff not needed for ports and system re-building. /tmp: Maybe have the following in /etc/fstab so /tmp files are kept in RAM. (Use /var/tmp for files you don't want to go away when OS halts.) md /tmpmfs rw,-s128m 0 0 With a similar setup, I've tried mounting / read-only and observed no problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD vs. window managers
Louis LeBlanc [EMAIL PROTECTED] writes: So, two things that are important: ease of configuration and flexibility. You want those small tweaks to be painless, but you also want the WM to be able to do what you want it to. So far, I've not found anything I wanted that FVWM2 couldn't do. Documentation (man pages) are well written enough that tweaks are pretty easy to manage now too. Amen. Want to do something? Read man fvwm, edit .fvwm2. Done. I gave KDE a couple of good tries and while it's nice to have on the Gnoppix Live CDROM, for example, I don't want to climb it's learning curve to configure it to my own preferences in daily use. I keep the right 1.5 of my 4-page screen normally devoted to a column of gizmos that do everything I need to do. You can easily write gizmos (eg, Tk/Python) and hook them it into fvwm's button/display system, though fvwm has all the built-in gizmos I've needed except my online/offline button/indicator/GMT-display. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/profile and PATH
Miguel Cárdenas [EMAIL PROTECTED] writes: I tried to setup PATH in ~/.profile and now is updated but how can I setup this variable system wide? specifically want to add the Qt and MySQL binary directories to the PATH... Yeah, man login.conf, but it's heavy reading which I suspect many people avoid by over-riding whatever it sets in the startup scripts of the shells they use. So man sh, man csh, etc. You're probably looking for /etc/profile, at least. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting a RHLinux 7.1 partition
Isaac Grover [EMAIL PROTECTED] writes: Once I had FreeBSD 5.4 set up, I put the RHLinux drive in the FreeBSD machine as primary slave. Manually mounting the drive didn't seem to work since I could find which /dev/ entry the RHLinux drive ended up on, and of course fdisk wouldn't help for the same reason. So I pulled the RHLinux drive from the FreeBSD machine, set it up as primary master on another machine, and was going to do the necessary file copies over the network. However, now it boots up with the FreeBSD menu, giving me one option (F1) to boot FreeBSD, and pressing F1 yields a beep from the PC speaker, and no boot. Sorry, but FreeBSD doesn't just install MBRs willy-nilly. After you put the Linux drive in the FreeBSD box you must have manually run some program that installed a new MBR on the Linux drive, and there's only a few likely possibilites (which you should remember using): sysinstall (the OS installer/upgrader), fdisk, boot0cfg, bsdlabel/disklabel. What happened to my RHLinux MBR and how can I either: 1) restore the MBR or 2) retrieve my data? I'm suspecting it's all still on the Linux disk in your FreeBSD box and you moved the wrong disk, which won't boot in its new box. If you need to replace the Linux disk's MBR, a Linux rescue floppy or CDROM which can run LILO or GRUB should handle it. Or you could make a Grub floppy on another system and booting from that, use it's command line to poke around and learn where the Linux stuff is located so you'll know what to tell the boot loader (MBR, lilo, Grub, etc) to boot to. If you can't get the booting fixed, put the disk in a Linux system and try mounting its partitions there and run LILO or GRUB after reading how to configure them. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mouse wheel problem
Efren Bravo [EMAIL PROTECTED] writes: Have I a bad configuration? You might need these in your /etc/rc.conf (and a re-boot): moused_enable=YES moused_flags=-z 4 5 ##moused_flags=-m 1=3 -m 3=1 -z 4 5 ## I'll try un-swapped buttons for a while. moused_port=/dev/psm0 moused_type=auto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: changing keyboard behaviour
manish jain [EMAIL PROTECTED] writes: i want my console's delete key to work as forward delete and not as backspace. can anyone help me out with this small problem ? Copy one of /usr/share/syscons/keymaps/* to /etc/keymaps, edit it, and put this in /etc/rc.conf: keymap=/etc/keymap Unless you used console generically. further, when i press the arrow keys in an xterm, it echoes wierd characters to the xterm. how can i set this right ? Here's some junk from my .Xresources file (see X manpage) that might answer your next question too. XTerm*background: grey80 XTerm*foreground: black XTerm*font: 10x20 !! Next resource is ignored if put on VT100 widget only. !! But even when set to xterm, it seems to ignore the xterm entry (with li=65) of /etc/termcap and use 24-lines. !! Before adding this 11'jul'01, TERM=xterm (don't know how it got set) I found this one in /etc/termcap. !!XTerm.termName: xterm-xf86-v32 This started causing problems. XTerm.termName: xterm !! For wheel-mouse: ! !# Scrolling on wheel mouse: half a page normally, line per line with shift XTerm.vt100.translations: #override\n\ ShiftBtn4Down,Btn4Up:scroll-back(1,line)\n\ ShiftBtn5Down,Btn5Up:scroll-forw(1,line)\n\ CtrlBtn4Down,Btn4Up:scroll-back(1,page)\n\ CtrlBtn5Down,Btn5Up:scroll-forw(1,page)\n\ Btn4Down,Btn4Up:scroll-back(1,halfpage)\n\ Btn5Down,Btn5Up:scroll-forw(1,halfpage)\n !# In the scrollbar we map buttons 5 4 to 1 and 2 otherwise, core dump !# This will move proportionnaly to cursor position but we dont know how to !# program the same exact behavior as in the text widget. XTerm.vt100.Scrollbar.translations: #override\n\ Btn5Down: StartScroll(Forward)\n\ Btn4Down: StartScroll(Backward)\n !! VT100: !! 89x36 for 1024; XTerm*VT100.geometry: 120x54+1+1 XTerm*VT100.cursorColor: Orchid XTerm*VT100.fullCursor: true XTerm*VT100.saveLines: 5000 XTerm*VT100.cutNewline: false XTerm*VT100.jumpScroll: on XTerm*VT100.scrollBar: on XTerm*VT100.scrollTtyOutput: off XTerm*VT100.scrollKey: on XTerm*VT100.titleBar: false XTerm*VT100.trimSelection: on XTerm*VT100.highlightSelection: true XTerm*VT100.trimSelectiontrimSelection: true !! reverseWrap is not an issue when using a fancy command line editing shell, but is good with sh. XTerm*VT100.reverseWrap: on !! Character (word) class (I think I like the defaults just fine.) !XTerm*VT100.charClass: [low-]high:value !! All non-white, printing chars (same as shorter 33-126:48): !XTerm*charClass: 33-47:48,58-64:48,91-96:48,123-126:48 !! Alternate screen support on XTerm*VT100.titeInhibit: true XTerm*VT100*loginShell : true XTerm*VT100.Translations: #override \n\ Ctrl KeyPressUp: scroll-back(1,line) \n\ Ctrl KeyPressDown: scroll-forw(1,line) \n\ Ctrl KeyPressLeft: scroll-back(1,halfpage) \n\ Ctrl KeyPressRight: scroll-forw(1,halfpage) \n\ Ctrl KeyPressPage_Up: scroll-back(1,page) \n\ Ctrl KeyPressPage_Down: scroll-forw(1,page) \n\ Shift Btn1Down: select-start() \n\ Shift Btn1Motion: select-extend() \n\ Shift Btn1Up: select-end(SECONDARY,CLIPBOARD) \n\ Shift Btn2Up: insert-selection(SECONDARY,CLIPBOARD) \n\ Shift Btn3Down: start-extend() \n\ Shift Btn3Motion: select-extend() \n\ Shift Btn3Up: select-end(SECONDARY,CLIPBOARD) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dualboot with FBSD boot manager
Erik Norgaard [EMAIL PROTECTED] writes: Thanks, I tried to look at the options in the BIOS. I can enable or disable the SATA disks. Look where you can tell it to boot off a CDROM and ensure that it can't also be configured to boot off second hard disk. So, it appears that I have to install the FreeBSD bootmanager (or some other multiboot boot manager) on the XP disk? On the boot disk, at least. And depending on which BM you use, maybe also on the other disk. (Unless you want to have your BM on a floppy or CDROM. It's been more than 5 years since I had a multiboot, so I'd like to know how I can do this and still get back to the original settings. How can I backup the existing MBR? From a rescue floppy or some Unixy OS, use something like this: dd if=/dev/ad0 of=ad0.mbr count=1 Know that fancy BMs (not FreeBSD's; I don't know about XP's) partially reside in other places than the MBR. IIRC, Grub uses a few sectors between the MBR and the first primary partition, plus some files in a regular filesystem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Users unable to select their own window manager in X.
Roland Smith [EMAIL PROTECTED] writes: ModulePath /usr/X11R6/libexec/fvwm/2.4.19/ If you're just using the default (which that looks like), just comment it out; I've never had one in my config file and never had an upgrade problem. Or use the + feature described in the ModulePath description to add dirs to the default. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I change which server to download ports from?
Robert G. [EMAIL PROTECTED] writes: I'm not talking about SUPFILE= in /etc/make.conf to change which CVS server I download all the ports, I'm talking about when I download/install individual ports it seems to pick a random server. Sometimes the server is one in another country, and I download a 30MB file at 5KB/sec which takes some time (I have 6.5Mbps). Is there an option to change this to a server of my choice? MASTER_SITE_OVERRIDE in /usr/ports/Mk/bsd.ports.mk sounds like what you want (to use in your make). There's also a RANDOMIZE_MASTER_SITES, but I don't see it defined anywhere, so I suspect your servers were not as random as it seemed. Maybe look at /usr/ports/Mk/bsd.sites.mk too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot problem (stage 2 boot?)
Sean [EMAIL PROTECTED] writes: Just installed on a new system and I am unable to boot. You might get better help if you include details like what you installed. Currently when that system boots it comes up with what looks like the following example from the handbook FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: Of course, standard 5.x kernel is in /boot/kernel/kernel booting from cd and going into Fixit it fdisk shows partition 1, 2, and 3 unused, and Freebsd is on partition 4. I thought it should be on partition 1? I suppose you've tried 0:ad(3,a)/kernel but maybe not: 0:ad(3,a)/boot/loader but I doubt if either will work because it's supposed to be done automatically. But if you got to the boot: prompt, you shouldn't need to worry about the boot manager (i.e., the MBR). It looks like the system is reading the boot records at the start of some FreeBSD primary partition (presumably, the 4th) and it should then try to run /boot/loader. Some disk geometry problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot problem (stage 2 boot?)
Glenn Dawson [EMAIL PROTECTED] writes: I doubt there's nothing wrong with the MBR per se, but if it's looking in the wrong place for the third stage loader you'll see exactly the problem you have. Where it's probably refers to boot code, not to the MBR, which doesn't look for anything except the confusingly-named first-stage boot loader (same as /boot/boot1) in the first sector of your 4th primary partition. Then that loads the second-stage boot loader (same as /boot/boot2) which gives the boot: prompt after failing to run /boot/loader and failing to run a kernel. It seems that finding boot1 and boot2 is possible with bad geometry, but finding /boot/loader or the kernel is not. ??? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to write to disk during installation
Mattia Popolla [EMAIL PROTECTED] writes: and sorry for my bad english! I noticed nothing unusual about it, for e-mail. I'm trying to install FreeBSD/i386 5.3-RELEASE FROM A DOS PARTITION. Fine English, but I don't understand. I'm sorry if there is some standard install method like this I'm unaware of. I have two HD units, with no partitions: Primary master - C: - ad0 (the primary partition) Secondary master - D: - ad2 I copied the distribution in C:/FREEBSD. Yeah, but you copied to it where? How did you copy it? What commands to computer? Booting FreeBSD from floppies I get some error messages, like these: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error4: aborted LBA 1 ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error4: aborted LBA 1 ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error4: aborted LBA 2 ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error4: aborted LBA 1 ... Does Booting FreeBSD mean booting FreeBSD kern.flp floppy, or what? When do you get those messages? You usually should also report messages seen just before and just after your problem messages. Unit ad2 is an old 1624 MB Western Digital HD (model WDC AC31600H, PIO MODE 4, no ULTRA DMA) but IT IS NOT FAILING, all the clusters are OK, and it works perfectly with MS DOS/Windows. I've also freshly formatted it using the MS-DOS FORMAT command. The latter was a waste of time, except maybe as a kind of test. The results of the format was just some change of data on the disk partition, which the FreeBSD install doesn't care about. Can this be a driver problem? The other HD (unit ad0) seems to work, but I can't make partitions in it! What can I do? Please help me!!! It does look like a driver problem, to this amateur -- no driver expert. It seems to have detected a PIO device as a DMA device. I'd check my BIOS setup to see if I can force PIO instead of DMA. I'd try removing the slave device, if any. If desparate, try swaping primary-secondary. At last resort, maybe a BIOS update. That's all I can think of, other than the standard support advice of trying to install a more recent (or even older) OS version. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: creating filesystem images
David Kelly [EMAIL PROTECTED] writes: The advantage of dump/restore is that only the necessary data is written. With dd all the unused blocks on the media are also written, including the filesystem, which will probably work on the larger card. If you don't mind educating me further for no particular need... I've long known about the UNIX concept of everything being a string of bytes, but came to the conclusion early in my Linux days that disks couldn't be used as a filesystem after a dd unless their cylinders were the same size (or maybe it was just tracks). Has this all gone away with FreeBSD's removal of block devices and/or with LBA disks? Can I get always (excepting un-related problems) get usable filesystems after dd if=/dev/ad1 of=/dev/ad1 bs=almost anythingb? As a separate issue, some boot stuff can get messed up, right? Or do partition tables use LBA now too? Seems like they'd have to, but I don't remember reading about it anywhere. Tar or pax are not bad choices in addition to dump/restore. bsdtar yes, but pax and gtar (tar in 4.x?) don't handle file flags, if OP needs those. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6 upgrade from RELENG_5
Joel Hatton [EMAIL PROTECTED] writes: Hi, Before I go crazy and change my RELENG_5 to 6 and resync my sources, can someone point me at a README/UPDATING for upgraders? I'm sure I'll find one _after_ I cvsup, but I'd like to read it first. Do locate UPDATING if you don't know where it's kept (src) and so then look at http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING and click on the left-most link and then the upper-left-most link. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: reorganizing partitions
Robin Smith [EMAIL PROTECTED] writes: I intend to do this by the appropriate ugly mess of cp -pRP commands I can't comment on vinum issues, but cp -pR (-P is default) doesn't handle stuff like file attributes, AFAIK. Check, but I think 4.11 has the new FreeBSD tar (not gtar) which is the think to use if you can't use dump/restore. Read your manual, but it's something like: tar cf - --one-file-system -C $SRCDIR . | tar xkpPf - -C $DSTDIR (I esp. wonder about kpP.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disk management
Dick Hoogendijk [EMAIL PROTECTED] writes: So let me ask you: If I delete the XP partition (i.e. with the fbsd fdisk progam) and write the partition table back to disk, will this ruin my third fbsd part? If you want to be real careful, save off a copy of the MBR (to floppy?) with something like: dd if=/dev/ad0 of=MBR count=1 or slight less safely using boot0cfg -f MBR (incomplete cmd). You can even use dd...|hd or the fdisk of a Linux Live CD to examine the partition table, so you're sure where your current FreeBSD partition is located. As for your question, one can only say it shouldn't. I doubt if it changes the partition table at all, but I don't know for sure. It certainly doesn't touch the partition itself. I can't help with MSFT stuff, thru lack of experience. The scary part is that there seems to be a misunderstanding of my disk by Microsoft programs (using a LBA disk setting) and my FreeBSD (using CHS settings). I can only put ONE option on in the bios though ;-) Since it was an option, my BIOSes have always been set to LBA, and FreeBSD (and Linux) seem to use both LBA and CHS in different places, keeping me confused, but I've never needed to use non-LBA. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Few simple questions..
Eric Murphy [EMAIL PROTECTED] writes: Im useing the emu10k1 driver and have sound comming out of all my speakers (includeing the sub) is there a way to adjust each channel? Maybe some sort of advanced mixer?? Try: sh -c 'less $(ls -d /usr/ports/audio/*mix*/pkg-descr)' (See next file with :n) I recently installed something called feedparaser its a news feed parser that works with some desklets. I installed it by issueing this command: python setup.py install... How can I remove these packages? Ive checked all over online and in the --help theres a bunch of install commands but no deinstall commands? If feedparaser docs don't say how, look at setup.py code; it's likely to be fairly easy to find where it handles that install argument and you might find a corresponding thing to uninstall or at least see what files it installed. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where to FreeBSD Boot Manager?
Garrett Cooper [EMAIL PROTECTED] writes: Soo-Hyun Choi wrote: Which drive should I install the FreeBSD Boot Manager? Thank you. Your primary 1st channel IDE drive-the one you have devoted for Windows use-unless you plan on using a bootdisk to startup FreeBSD :). If you have or can install a fancy boot manager (i.e., not FreeBSD's), starting in the MBR of the first disk, then you can sometimes do without a BM on the second disk, but if you're going to use a normal FreeBSD disk layout and you don't have a fancy BM, then you'll normally want a FreeBSD Boot Manager in the MBR of both disks. The first one lets you boot from the partitions on the first disk or start the second disk's MBR from which you can boot FreeBSD. Except I don't know about dual booting with MSFT OSes. I've read it's possible with the FreeBSD BM. The list archives have info on that. Garrett: I got my BSEE from your school before it became the MSFT Academy. :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and projects for kids
Gayn Winters [EMAIL PROTECTED] writes: Anyone tried PicoBSD as an example of a small OS? PicoBSD is almost certainly not what you're looking for. All of the useful PicoBSD documentation is pretty-much in the manpage and in a few files under /usr/src/release/picobsd/; it's just a way of building a FreeBSD OS that is stripped way down. Can anyone advise me as to how much of FreeBSD I need to load before there are interesting games for 10 year olds in the games ports? With X and the lang/python port, the games/pysol port has a many dozens of solitare card games that I would have liked at 10, but it might not do much for today's kids. And games/scrabble is about the only other one I've tried except xboing which would be fun but no longer works for me. games/xbill could be considered educational, I suppose. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: searching ports doesn work
Marcel Lautenbach [EMAIL PROTECTED] writes: /usr/ports and did make search lsof Current handbook says make search name=lsof or make search name=lsof. I get a notcie that says something of generating INDEX, please wait. Looks like it just did make which is make index. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW to boot off the 5.4-Release CD with a different kernel that supports more hardware
Ricky [EMAIL PROTECTED] writes: Thanks in advance for any help regarding this. This isn't the short-cut you were probably hoping for, but this should explain how to make a CD like the Project did: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html There's also a release(7) manpage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding Disk Drive
And http://www.freebsd.org/doc/en_US.ISO8859-1/articles/formatting-media/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cache-only named won't resolve localhost
Alex Zbyslaw [EMAIL PROTECTED] writes: Gary W. Swearingen wrote: Mozilla apparently doesn't even use my local DNS as it still hangs. (I must admit that I've never checked my caching DNS's cache.) Mozilla will use resolve.conf, if it is there. It will also cache answers for a long time and requires restarting if you, say, add a host to /etc/hosts. I missed the beginiing of the thread, but why would you want to run without /etc/resolv.conf? That was just a side-issue I threw in after I read a comment about using resolv.conf's domain and/or search. Its manpage says: On a normally configured system this file should not be necessary. so I just tried doing without it; host, dig, and nslookup don't need it (even when not told which DNS server to use), but my mail hung up, so either Gnus or, more likely, sendmail needs resolv.conf. The orignial and still-remaining problem was that Mozilla hangs when given localhost/index.html or localhost.localhost/index.html. Then I noticed host didn't work and that bothered me. But I got that fixed and I don't much care about the original Mozilla problem. It appears the Mozilla doesn't use my resolver library, /etc/hosts, or my localhost cache-only DNS server. I did try restarting Mozilla after reading your comment. Don't worry about it. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I need one command
Carstea Catalin [EMAIL PROTECTED] writes:
I run squid on my freebsd box and i need to know the free memory.
In redhat exist a nice command #free to show the free memory. In
$ top | grep Mem:
Mem: 91M Active, 271M Inact, 91M Wired, 232K Cache, 60M Buf, 45M Free
$ top | awk '/Mem:/ { print $12 }'
45M
$ vmstat
procs memory pagedisks faults cpu
r b w avmfre flt re pi po fr sr ad0 ad2 in sy cs us sy id
2 2 0 207316 46040 47 0 0 0 37 0 0 0 341 485 363 0 0 99
$ vmstat | tail -1 | awk '{ print $5 }'
46040
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with xorg.conf
[EMAIL PROTECTED] writes: However none of them have an effect! Please help! Adding to what others have said.. You can learn a lot by looking at (something like): /var/log/Xorg.0.log If your monitor and controller are fairly new, you should find info about their possible (and actual) settings. And read xvidtune manpage if you haven't already. And there's a good SEE ALSO list in the Xorg manpage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cache-only named won't resolve localhost
Chuck Swiger [EMAIL PROTECTED] writes: Note that the resolver will treat lookups of localhost. and localhost differently if you have a domain or search directive specified in /etc/resolv.conf. You could and perhaps should ensure that the one ending in a period exists in a zone file on the nameserver, and maps via an A record to 127.0.0.1: Apparently so. I've sorta followed your suggestions and used the following rather verbose master/localhost with good results (except Mozilla). You needn't read further; I've just added some observations. $TTL 604800 localhost. IN SOA localhost. root.localhost. ( 20050816 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Minimum ;Name Server: localhost.INNSlocalhost. ;Host Address: localhost.INA 127.0.0.1 ;Host Alias: localhost.localhost.INCNAMElocalhost. ; The End. Now host, dig, and nslookup work OK, even without an /etc/resolv.conf file. But sendmail seems to need the later. (It just has nameserver 127.0.0.1.) I tried to make localhost.localhost the canonical domain and localhost. the alias (so it would better correspond to the reverse mapping which has 127.0.0.1 localhost.localhost.), but it then wouldn't resolve localhost OR localhost.localhost. My DNS book implies taht any domain name can be assigned to a host, as it can with the CNAME above, but it seems that important software either insists that a host has a two-part domain name or chokes on a FQDN like localhost., which ends with a dot. So be it. Mozilla apparently doesn't even use my local DNS as it still hangs. (I must admit that I've never checked my caching DNS's cache.) I know little about proxies, but I tried configuring Mozilla to use a localhost proxyand it then resolved localhost OK, but my funky python-only web server couldn't find the index.html it found with 127.0.0.1. Oh well, I don't much care about Mozilla problems as long as I can work around it, which I can. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stable server
Carstea Catalin [EMAIL PROTECTED] writes: what version of freebsd do u recomand for a stable server? The Handbook recommends against using a stable branch (RELENG_5 or RELENG_4, which might not even compile) without first thoroughly testing the code in your development environment. But if one is going to thoroughly test the code, one might as will use HEAD, except that it is likely to fail and be a waste of time (or your testing is not thorough enough). So it seems to me that one's choice is between thorough testing of RELENG_5 or less thorough testing of RELENG_5_4 or RELENG_4_11. I'll leave it to those with more experience for choosing between the last two, but it sounds like it's a toss-up, with some recommendations being influenced by conservatism or a desire for more 5 testers. :) Another factor (besides testing effort) in the choice between RELENG_5 and RELENG_5_4 is the number of fixes as measured by the time since RELENG_5_4_0_RELEASE. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MS 9129 wont boot 5.4CD but will 4.11
Chris Ryan [EMAIL PROTECTED] writes: starts all normally until the boot from CD:. I would first boot another unixy OS off HDD or Live CD and compute the md5 checksum of the CD (maybe using dd bs=2k ... once to size the CD and once to exclude that last two blocks) and compare with the checksum listed at www.freebsd.org. Or make another CD or CD image and compare md5sums or just diff the two CDs or CD image. If OK, and I was pretty convinced that there was a bug of some kind, I'd try asking on the 5.4 mailing list, freebsd-stable, and/or file a formal problem report, or since such problems are tough to debug, especially by those without the hardware in question, I might just boot off a floppy (images are on the CD) or install from an older OS version until I could upgrade from the new CD using sysinstall after booting the older OS from the HDD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failed installation of FreeBSD 5.4
Milscvaer [EMAIL PROTECTED] writes: that. There must be something wrong with the boot records that fdisk is not correcting. I know friends who have had unuseable boot records as well and have to boot from floppies, Its not really a big inconvenience. Spend some time with the boot, boot0cfg, fdisk, bsdlabel, manpages and the handbook. Note that fdisk can install either a DOS-type MBR (and set active part) or a FreeBSD-type MBR (use F1...). Also note that fdisk does not install the boot records that are probably not working for you: the ones at the start of your primary partition. These are installed by bsdlabel with -B option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitor Tuning
Greg 'groggy' Lehey [EMAIL PROTECTED] writes: Others have said this already, but to clarify: adjusting the monitor parameters may enable you to get higher resolution or less flicker, but they're unlikely to make it sharper unless they were previously out of the operating range. Nowadays that's seldom, since monitors will just refuse to operate out of spec. Yeah, and lower resolutions and more flicker (lower refresh rates) usually give sharper images. I once got rid of a lot of fuzziness by wrapping the video cable with aluminum foil; which was feasible because it was only a few inches between the MB and a backpanel connector. But you might consider your longer video cable routing to keep it as far as possible from RF noise. I've also seen a montitor get fuzzy when setting too close to a noisy computer or another monitor. Another thing that sometimes helps and sometimes hurts is to give your monitor a good slap. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installer can't find hdd
Efren Bravo [EMAIL PROTECTED] writes: I think that the problems is in fBSD that it doesn't able to communicate with IDE banks, it raise the errors: ... if the motherboard's controller isn't supported by fBSD, what could I do, should I send to garbage the motherboard? If you're convinced it's a FreeBSD problem and you'd like to do future FreeBSD users a favor, then write up a formal problem report (find link on home page) and also post your 5.4-R problem on [EMAIL PROTECTED] If you're keen on trying to get the problem fixed, try 6.x on it and if it does the same thing, report the problem on [EMAIL PROTECTED] If you are really ready to trash the MB, and it's reasonably new, some developer _might_ want it to debug the problem down on. Maybe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cache-only named won't resolve localhost
Lowell Gilbert [EMAIL PROTECTED] writes: Of course it won't work for nslookup(1); it's not supposed to. nslookup is specifically intended for querying a name server. The documentation for host(1) isn't as clear on the subject, but my reading of it seems to indicate the same thing. Well that sure explains something. But I was also looking at the bind docs thinking it should be able to read /etc/hosts or call the name server host's resolver (gethostbyname, etc.), but didn't find anything, I suppose because someone thinks it is a bad idea since the resolver library is supposed to look at both databases. I'm still wondering if I should be declaring a forward zone for localhost or localhost.localhost; it seems kinda strange that the script would set up a reverse for it, but say nothing about the forward. I'm also wondering now what host-type command just queries the resolver. But I guess ping works well enough. So why it isn't working for mozilla is the only anomaly you are seeing. What is the syntax you are using for pointing mozilla at your localhost, and what are the precise results? I've tried: localhost/index.html localhost.localhost/index.html (getting desparate:) localhost:80/index.html http://localhost/index.html This worked immediately: 127.0.0.1/index.html The bad Mozilla results are a status line saying Connecting to something... and, IIRC, I saw a twirly thing until it times out after several minutes, with no error message. I didn't see anything related to DNS in preferences. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failed installation of FreeBSD 5.4
Milscvaer [EMAIL PROTECTED] writes: I would like to try to boot the system on the hard driv e from a floppy. Maybe there is something wrong with the boot record on the HD. Does anyone know if this is possible and how I can do that? Sure, but you've left us in the dark as to what you have to work with there. Do you have FreeBSD or some unixy OS on another system or on a live CD? Or just a floppy fixit? Or what? Do you have enough hard disk space to leave your /usr/home out of the picture until you get FreeBSD going on another part of the disk? (Maybe after deleting unneeded parts of /usr/home's filesystem.) Anyway, if you can run a FreeBSD off a fixit or live CD somehow, you can bsdlabel to put /boot/boot = boot+boot2 on a floppy so you should be able to get a boot2 prompt (the one before the loader prompt) and try to boot your 5.4 from there. Or you could try using fdisk and boot0cfg and bsdlabel to put new boot records (MBR, boot1, and boot2) on a floppy or on your hard disk, too. If you can DL and burn a CD, get yourself a live CD or CD-based fixit, else try to find room on your HD for a fresh minimal FreeBSD install, else get an old HD and install fresh to that. Another thing you could try is getting a Grub floppy off the Internet and try booting from the Grub command line. I suppose that your problem is related to the fact that your upgrade is reusing your old partition(s) and maybe old boot records. BTW, if you can keep your /usr/home out of the picture and then copy it to your new system, you can end up with nice new UFS2 filesystems. BTW, if that's your only copy of /usr/home, you probably shouldn't be trying to install a new OS on the disk anyway. You should be able to find another HD for a small FreeBSD (or a copy of /usr/home) for VERY little money these days. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cache-only named won't resolve localhost
I think I followed the bind manual and poked around /var/named and it has been working OK for a few weeks until I pointed my browser to localhost and then I tried host localhost. It can resolve 127.0.0.1 back to localhost.localhost. fine, but if I try my name localhost or localhost.localhost, I get this: ;; connection timed out; no servers could be reached (at least until I tried it just now while on-line, when it works OK, resolving my modem/router's localhost, I suppose). /etc/hosts: ::1 localhost.localhost localhost 127.0.0.1 localhost.localhost localhost 10.0.0.4localhost.localhost localhost /etc/hosts.conf: # Auto-generated from nsswitch.conf, do not edit hosts bind /etc/resolv.conf (same with this file missing): nameserver 127.0.0.1 I can ping localhost OK. I thought that host should use the same stub resolver as ping before trying bind. Can I not use /etc/hosts with a cache-only named? Must I have an authoritive zone for localhost? Or what? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Browser ?
Nikolas Britton [EMAIL PROTECTED] writes: Like what? Like the indemnification clause in http://mail.google.com/mail/help/terms_of_use.html One can limit their exposure to such risks by accessing such services as read-only services, except for their normal SMTP services which, AFAIK, are covered only by implied licenses with no indemnification. I hope. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: differences in supported filesystems between FreeBSD versions
Dmitry Mityugov [EMAIL PROTECTED] writes: I am not sure how safe it is. Is it safe to use a HDD partitioned and formatted by one version of FreeBSD with a newer version? I know there I recently ran into the problem of not being able to access 5.x file systems and 5.x backups from a 4.x system. (5.2+ and 4.7 4.8, IIRC.) (I got a new amd64 computer that wouldn't boot 5.x from the old hard drives because I no longer had a GENERIC or other compatible kernel and I had no Internet access or 5.x CDROM. I could run 4.x, but it couldn't mount 5.x partitions or even restore 5.x dump backups. Had to go back to an old 4.x backup until I got back on the Internet and got 5.x going.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 install problem. Newbee needs help.
William Manley [EMAIL PROTECTED] writes: I am a new FreeBSD user and I have an installation that has gone bad. My problems started when I enabled XDM for a graphical logon into Gnome. When I logged in as root the system just looped back to the logon screen. I then assumed I had configured my .xinitrc file wrong so I booted the install cdrom into Fixit mode and tried to mount the root filesystem on the hardisk which the operating system would not let me do. The following are the commands I typed with the output. I don't use gnome or kde, but I'd think you'd want to use gdm for a gnome desktop or kdm for a kde desktop and if you want to use xdm, be prepared to do some reading and configuration to make it give you a Manley desktop. BTW, one usually tries to run as little software as possible as root mostly to limit damage caused by buggy (or I suppose infected) software or operator error. After you get your desktop running as a non-root user, some graphical programs will do needed things as root and/or you'll start up a terminal emulator like xterm with the shell run by root. KDE, at least, offers a root terminal, but you can switch from normal to root with the su command. mount /dev/ad0s1a /mnt operation not permitted Not sure, but I wonder if /mnt is already in use. Try mkdir /ad0s1a; mount /dev/ad0s1a /ad0s1a disklabel -r ad0 no valid label found That -r is obsolete, but someone else explained the real problem. Does the warning tell me that my bios is not set up properly for FreeBSD to work with the hardisk setup. The handbook says to set up your bios to select hardisk's naturally. Before starting the install I looked at the bios and was not sure what to configure. Should I go to the basic page and set the hardisk as uninstalled? Any help in getting back into my system will be appreciated. If I have to reinstall I'll do it. If your install seemed to go OK and you've got a graphical login screen, you're probably in fair shape. You might want to try the install again and not use xdm. Or: You might need to tell us more about what you see at login. Try logging in as a normal user. Probably won't work any better. If the screen offers some other stuff, like a safe mode or single user mode, try that. Or try to interrupt the boot before you get to the graphical screen by tapping the space bar as soon as you see major changes in the kind of boot messages (eg, from BIOS to FreeBSD). If you can get the thing to give you a prompt, try help or ? and check that out and then try boot -s to get into single-user mode as root. If you manage to do that, or get things mounted from the CD or floppy fixit mode, you want to disable XDM, but I'm sorry I forget how that's done. Look it up on the net or ask. I think your goal is to get a normal non-graphical login prompt; log in as root and then read manual pages (or use web from another OS) until you figure out how to configure your Gnome setup using gdm. BTW, I know many insist on having a graphical login, but some of us have been using graphical desktops for 10 years and more and still log into a normal text terminal first and start the graphics with a command, maybe because we don't log in often and when we're logging in a lot it's usually because we're having problems and we don't want X then anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to recover data? - Formatted, Fdisk'd, and disklabeled ad1, now ad0 with FreeBSD is messed up
Mark Kane [EMAIL PROTECTED] writes: Mounting /dev/ad0s1a showed what was my root partition before. I tried mounting ad0s1b, and it gave Incorrect Super Block. I went on to guess ad0s1f, mounted it, and it was /usr. Appears like /usr/home/myuser/ exists and my files are there. b is almost always a swap sub-partition which will have more-or-less random data on it and so can be expected to give Incorrect Super Block. But it was smart to try them all. Glad to hear you found your files. I'm not sure given the info that I have what the proper way to get FreeBSD back up and running again, and to make sure ad1 is ready is. Again, if possible (and it sounds like it is now), try not to write to ad0 until you get a copy of your data on another medium. Use the Fixit CD or buy a 1 GB disk if you have to, and install FreeBSD on that and then use it to get the 60GB disk in shape and your data back on it. THEN try to fix ad0. You might also consider consolodating your most important data so you can back it up on CDs or DVDs. I bought a used tape drive for 10$ and now keep important stuff on several CDs different brands and types of CD and 4mm and 8mm tapes. I replied to a reply on the list a few minutes ago saying that if I mount /dev/ad1s1d, it shows the full 55G size and 51G avail that is supposed to be the ad1 60GB drive. I'm not sure why that's d though. It sounded like he decyphered it from your previous msg. Your idea of trying to mount them all sounds better. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: install from CD-R fails
[EMAIL PROTECTED] writes: and then press CR it just repeats the dialog, and refuses to find the installation images on the very same CD that it just booted from in the first place?! And, there is The method of accessing the CD's boot code is very different than the method of accessing the CD's normal filesystem so yours is (or at least used to be) a common problem (I saw often with old Linux). This system has all SCSI peripherals: the controller is a Tekram PCI board model DC-390F with Symbios 53C875 chip, 3 HDDs and the Plextor CD-R. I'd be very suprised if that 53C875 chip is NOT supported by the 5.3's CD's kernel with either the ncr or sym driver. So I have no easy (or other) solution to your problem. Like someone else said, you can access the boot log in another virtual terminal (try each Alt-F#, where # is 1 to 12) and see if it detects your CD drive. You're probably aware that if you're Internet connected, you could have sysinstall install using FTP instead of from the CD. I would probably be pessimistic and guess that I wasn't going to be able to install from that CD or drive and look for some other method, like a 5.4 version, or a temporary ATAPI CDROM or FTP from another system which can mount the CD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
Mark Kane [EMAIL PROTECTED] writes: This is a brand new motherboard. Giga-Byte GA-K8NS Pro. FreeBSD 5.4-RELEASE (amd64). I was also doing some searching around and found a list post about FreeBSD 5 and DMA write problems: I've got a GA-K8NSC-939 running 5.4-R (i386) with two 80GB using UDMA100 that I've run pretty hard occasionally with dump/restore, diff -r kind of operations, with no problems. I ran 5.4-R (amd64) lightly for a few days without noticing disk problems. You said one of your disks was a slave. I've read rumors that that's a bad thing if its master is a CDROM, but I'd think it should just run slower than it's capable of. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I use ccache and ports?
Björn König [EMAIL PROTECTED] writes: Robert S wrote: A freebsd n00b question. How do I set ports up to use ccache [...] Presumably I put something into /etc/make.conf. Yes, add the following lines to /etc/make.conf CC=/usr/local/libexec/ccache/cc CXX=/usr/local/libexec/ccache/c++ /usr/ports/devel/ccache/pkg-descr makes that sound like A Good Thing. Any ideas why it's not built into cc/c++, or FreeBSD scripts? Should we all be using it? Reasons not to? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I use ccache and ports?
Björn König [EMAIL PROTECTED] writes: Because these are compilers, not compiler caches. I suppose it's not the task of a compiler to speed up the build process, but rather producing good binaries from source code. I think of the Unix dogma one task, one tool. GCC violates that one almost as much as Emacs. :) GNU is Not Unix, it seems. And I'm guessing that compilers use lots of caches; GCC just hasn't (yet) bought into optionally maintaining some caches between invocations to keep things simple, so the manpage is only 2600 lines. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD handbook, 16.3.2.2
Nikolas Britton [EMAIL PROTECTED] writes: # disklabel -Brw da1 auto what did the -r option do, why is it used in this example when bsdlabel doesn't support it. It enabled the labeling of an unlabeled disk. It's used because the handbook is still in transition from the old disklabel. My copy has a note there saying to omit the -r on =5.1. # disklabel -e da1 # create the `e' partition Why do I have to make the 'e' partition, explain why 'e' is used and why can't use other ones like a, c, or d? An explanation of what to do when your editing the partition table would also be nice. Yup, but if you're just complaining -- please don't, and if you're trying to get it changed, please learn the proper channels. Problem reports are recommended or at least sending your complaint to the doc@ mailing list, though neither of those methods is very likely to get things changed much faster than it would anyway, unless you can provide some alternative text -- preferably as a diff -u of the SGML source files, but OK as plain text. # newfs -d0 /dev/da1e This command doesn't even work! and what about -O2 and -U options? if it did work I would have made a UFS1 partition with no soft-updates. On 5.x? I think the default is UFS2 and you could turn on the soft updates at a later time. But I get your point. # mkdir -p /1 -p? what do I need that for? Looks useless to me too. Maybe somebody never uses mkdir without it. Some good reading: http://www.freebsd.org/docproj/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot manager behavior questions
Michael Dexter [EMAIL PROTECTED] writes: 1. Is there any equivalent to nextboot(8) for the boot manager such that a boot selection can be made prior to the boot sequence so that the choice can be made remotely instead of only at the console? Read about boot0cfg's -s. And please shorten your lines. 2. Can anyone confirm that the Default behavior is simply F1 (first slice) the first time it is invoked and then any other choices become the next default? The FreeBSD BMs don't behave that way. /boot/mbr just boots the active partition and doesn't change it. The other is described in the boot0cfg manpage. In theory, this should work and be the equivalent of choosing F4, right?: boot: 0:ad(0,4,a)/kernel BIOS drive 0, ata drive 0, slice 4, partition a, 5.x default boot of /kernel Alas, it only bells at me and gives me the same suggested syntax. Wrong; it's not the equivalent. Hitting F4 causes the bootstrap on s4 to run. This normally starts /boot/loader but in some cases produces your boot: prompt. The handbook shows it in a boot2 Screenshot. I'm unsure why you can't get the boot: prompter to transfer you to another slice. Maybe it requires that you pass the kernel some options. You might have better luck asking it to start /boot/loader which provides more gizmos for changing defaults, etc. Does anyone know the syntax to perform the boot-to-cd from the boot manager feat? Not I. And you're likely to confuse people if you use boot manager like that. FreeBSD docs call it the stage-two bootstrap or something similar (even though it is seldom the second stage of the bootstrap process). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x separate /boot slice?
Michael Dexter [EMAIL PROTECTED] writes: I would like to try a separate /boot slice as permitted by FreeBSD 5.x... I forget where you got that from. Anyway, the boot(8) manpage makes it pretty clear that your /boot must be on the a of whatever s you're booting, but I'm not as sure as others that you can't get the loader to then boot up a kernel from that /boot but using some other / on another s, probably on its a. I'd be investigating /boot/defaults/loader.conf and its #currdev=disk1s1a # Set the current device #root_disk_unit=0 # Force the root disk unit number #rootdev=disk1s1a # Set the root filesystem and/or how to execute the built-in loader(8) commands, like unload, set currdev, etc. It sounds like that's possible (something about execing in scripts), but you might have to learn a bit of Forth. Try booting to the loader command line, and try to get it to use a kernel+modules from one s and a / from another. loader(8)'s boot_askname sounds encouraging. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl options loader.conf or sysctl.conf
dick hoogendijk [EMAIL PROTECTED] writes: I'm a bit confused about whcih options needs to be set where. You're not alone. I know i.e. that hw.ata.atapi_dma=1 needs to be set in /boot/loader.conf while others are set in /etc/sysctl.conf. I need to know where I can find info on the rules about this. Now I'm dependant on what I happen to read somewhere. Well, sysctl(8) refers to loader.conf(5), sysctl.conf(5), loader(8), which refer to /boot/defaults/loader.conf /etc/sysctl.conf and don't forget the handboot and FAQ. I read something about vfs.read_max=16 - where do I set this I wonder? Since sysctl.conf is read in only when going multi-user and that sounds like something you'd want always, I'd put it in loader.conf. Is there info about this somewhere? Google? If you think it's needed, please write a PR (probably on /boot/default/loader.conf). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about gcc
Kun Niu [EMAIL PROTECTED] writes: It seems that I should install the as program. Can someone tell me where I can download the tbz ball? An inet search for as? :) Or as.tgz or as.tbz. The devel/bin86 port has a as86 program that _might_ be the same thing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Migrate primary disk (duplicate)
[EMAIL PROTECTED] writes: I tried every combination: fdisk -I ad3 fdisk -B -b /boot/mbr ad3 fdisk -I ad3 fdisk -B -b /boot/boot0 ad3 fdisk -B -b /boot/mbr -I ad3 Assuming that you've got the rest of the file systems configured and populated properly, as I think you said, and you really only need to get the MBR right... I'd try using boot0cfg, which has always worked for me. BTW, you don't need -b /boot/mbr because that's the default. Just based on my manpage reading: It sounds like -I and -B do quite different things and using them together is problematical. With -I, it sets up the partition table to support only ad3s1. With -B, it probably doesn't touch the partition table, and only changes the boot code in the first 446 bytes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Migrate primary disk (duplicate)
[EMAIL PROTECTED] writes: I tried every combination: fdisk -I ad3 fdisk -B -b /boot/mbr ad3 fdisk -I ad3 fdisk -B -b /boot/boot0 ad3 fdisk -B -b /boot/mbr -I ad3 ... the disk doesn't boot. So fdisk -B ad3 shouldn't work if you don't have a valid partition table which also has the correct fdisk partition marked active (or bootable, which I'm fairly sure is the same thing, despite what the fdisk manual implies). But is seem that fdisk -I ad3 should work if you have a s1 correctly configured and populated. But after using it, I'd run fdisk ad3 and verify that your s1 is marked (active). It sound like /boot/mbr behaves like an IBM/MSFT MBR, while /boot/boot0 is the standard FreeBSD MBR configured by boot0cfg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with booting MBR
[EMAIL PROTECTED] writes: From dmesg: ad0: 9541MB WDC WD100BA/16.13M16 [19386/16/63] at ata0-master UDMA33 I think you just said that vicbsd root# fdisk /dev/ad0 vicbsd root# bsdlabel /dev/ad0s1 work OK, but that your problem (from a prior msg) is: # fdisk -B -b /boot/boot0 ad0 fdisk: cannot open disk /dev/ad0: No such file or directory That makes no sense. If I understood this right, there's something very wrong and you ought to be filing a PR about it and/or reporting the problem on the mailing list for 5.4 development, freebsd-stable. Also: You might rather use boot0cfg instead of fdisk as the former allows you to configure stuff that the later doesn't. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bind CTRL-ALT+DEL action
Lowell Gilbert [EMAIL PROTECTED] writes: Aymeric MUNTZ [EMAIL PROTECTED] writes: Is it possible to bind any action to combinated keys such as CTRL+ALT+DEL? Yes. In X, it's kind of tricky to apply modifiers to a particular combination, so I'm not sure how to do that particular one, The problem with X is that there are so many ways and places to do it and higher-level programs can hide the lower-level settings. X has a xkb system (see xkbcomp manpage and elsewhere) that lets you mess with low level stuff, which can be handy to enable special buttons on fancy keyboards. Many X programs (eg, Xemacs) can be configured with custom keys and key combinations. The window manager fvwm2 seems fairly easy. This allows ctrl-alt-delete to do something (defined in the config file) Key Delete A CM something ^ ^^- Alt | +-- Ctrl + Any context ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Migrate primary disk (duplicate)
Alexandre D. [EMAIL PROTECTED] writes:
Here is the complete process I follow:
sysctl kern.geom.debugflags=16
dd if=/dev/zero of=/dev/${disk} bs=1k count=1
Shouldn't be needed, but if you're concerned, write enough sectors
to zero the start of {disk} and the start of {disk}s1 -- something
like 63+16; bs=100k maybe.
fdisk -BI ${disk}
Again, -B and -I don't sound like a good combo.
disklabel -B -w -r ${disk}s1 auto
You said you were running 5.4. AFAIK, there's no -w, -r, and no
auto. Other than that it looks fine. :) (But knowing the way some
developers think, they might have been removed from the manpage only.
G.)
disklabel -R ${disk}s1 generique.disklabel
newfs /dev/${disk}s1a
newfs /dev/${disk}s1d
mount /dev/${disk}s1a ./mnt
cd ./mnt
dump 0uafL - / | restore xf -
Looks like you're dumping to a file named ./mnt/L. Does ./mnt
really have anything else in it after that restore?
-generique.disklabel file---
a: 4194304004.2BSD
b: 2097152 * swap
d: * *4.2BSD
Could be. Have it print out the resulting disklabel and see if looks
OK.
If I do the same with /stand/sysinstall in stead of
dd if=/dev/zero of=/dev/${disk} bs=1k count=1
fdisk -BI ${disk}
disklabel -B -w -r ${disk}s1 auto
It works well.
Could it be because it uses boot0cfg and you use fdisk?
(You haven't said whether you're telling sysinstall to install a
standard MBR or a FreeBSD MBR or none.)
If you're curious, you can dump the two main boot sectors
a readable file and compare the sysinstall version with the
fdisk version and /boot/mbr and /boot/boot0.
dd if=/dev/ad0 count=1 | hd /tmp/ad0
dd if=/dev/ad0s1 count=1 | hd /tmp/ad0s1
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Migrate primary disk (duplicate)
Alexandre D. [EMAIL PROTECTED] writes: I made several tests. the exact problem is to install the freebsd boot manager. But your fdisk -B -b /boot/boot0 should have done that. I'm not sure if it has defaults that would work for you though. boot0cfg tells you what defaults it will use and lets you change them. If I use any command line utility to restore the boot manager, it doesnt work. Does any include boot0cfg? If I use /stand/sysinstall, choose fdisk and Install the FreeBSD boot Manager, it works What is the exact command line for this? Depends upon what you want. Read boot0cfg manpage; it's short. I used this once: boot0cfg -Bv -o packet,noupdate -s 3 -t ad0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remove all of KDE
Dick Hoogendijk [EMAIL PROTECTED] writes: On 01 Aug jdyke wrote: If i `pkg_delete kdebase` will it delete all sub packages. or do those have to go one at a time? pkg_delete kde\* removes most if not all of kde* stuff. Using -r should also get rid of packages that depend on the kde stuff. You might ought to use -rn first, and study output. BTW, it seems that pkg_deinstall is meant to be used instead of pkg_delete (outside old scripts, anyway). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
Glenn Dawson [EMAIL PROTECTED] writes: The only danger in not having the slice table is that if you use non BSD tools, such as the ones that come with windows, they will potentially write over things that that you don't want them to. The FreeBSD FAQ mentions more serious dangers. Also, without the slice table on your boot disk, the BIOS wont know what to do since it looks for the active slice and attempts to boot it. A i386-standard PC BIOS shouldn't, by itself, try to boot anything except the boot code in the MBR. That code can then use the BIOS just for reading more boot code from the disk, without any partition table considerations. That's why most PCs can boot a DD FreeBSD sys. (As soon as enough code is read in, the BIOS can be dispensed with entirely and the 1024'th cyl exceeded even with non-LBA BIOSes. I'm not sure which booters, if any, do this, but probably Lilo Grub, which both use a partition table.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 5.4 -R install error
A R [EMAIL PROTECTED] writes: On install i get this error : Unable to find device node for /dev/ad0s1b in /dev! The creation of filesystems will be aborted It looks like it was trying to do something (swapon?) with the swap device, but the devfs system never created a /dev/ad0s1b for it because (I'm guessing) you never asked for one during the disk labeling part of the install. Except that I'd be suprised if it would let you out of the disk labeler without insisting upon a swap device. (Not that one SHOULD be required.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I´ve some problems with the diskettes
(Badly formatted message omitted) I suspect that you didn't follow the README's instructions and instead tried to put the 2880k boot.flp on a 1440k floppy. You only need the other two images if you have a 1440k drive. IIRC, the big one is for a few special drives and for use on El Torito bootable CDROMs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Deleted /var/db directory
zlatozar [EMAIL PROTECTED] writes: Is there a way to recover my db of all installed ports? How I can reinstall all my ports? Will reinstall helps? I think your ports (eg, /usr/ports/*/*) are still installed and most of your package files (eg, /usr/local/bin/portinstall) are too, but your package db is gone and that is only going to be fixed by re-installing packages again from ports or packages. I'd probably just pretend nothing happened and do portinstall as needed occasionally, otherwise I'd use my /usr/ports/distfiles/ to help me guess what I had previously installed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what to do? amd64 - i386
dick hoogendijk [EMAIL PROTECTED] writes:
cd /usr/ports/www/opera; make -V ONLY_FOR_ARCH
Just tried this, but got no response. Maybe it works now.
#!/bin/ksh -o posix
find /usr/ports -name Makefile | while () ; do
read DIR
cd ${DIR%Makefile}
BBB=$(make -V BROKEN 2/dev/null)
OOO=$(make -V ONLY_FOR_ARCHS 2/dev/null)
if [ -n $BBB -o -n $OOO ]; then
echo $PWD
if [ -n $BBB ]; then
echo BROKEN$BBB
fi
if [ -n $OOO ]; then
echo ONLY_FOR $OOO
fi
fi
done
## The End.
There are a few things that will not work at all on amd64 right now,
however: OpenOffice.org, proprietary media codecs, hardware OpenGL
acceleration...
Any ideas about _WHAT_ does not work? Do you have examples?
If I can't live without them, then.. ;-))
I forget, but too many for me. Found somebody with Google that got
several broken things running, but he didn't say how.
I had a few problems with base-system stuff but probably could have
lived with that. (Eg, I had to use older ncr instead of sym.) The
problems are with the ports, so waiting for 6.x won't help.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem with burncd, hardware or not ?
[EMAIL PROTECTED] writes: only wrote -1 of 32768 bytes: Input/output error burncd: ioctl(CDRIOCFLUSH): Input/output error I got something like that on 5.4 (i386 or amd64, I forget) and cured it by using cdrecord from cdrtools port after rebuilding kernel to support it. That might tell you whether it's hardware or software. Some would say you should use send-pr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
Nikolas Britton [EMAIL PROTECTED] writes: Drive: Dangerously dedicated /dev/da0s1 newfs -O2 -U I think you're using dangerously dedicated wrongly. A DD disk is one which has no standard partition table in the MBR; the disklabel sectors (16) start at sector 0 (or with your no-secondary-partitions- either method, your filesystem would start there (newfs /dev/da0)). You've got a standard partition table with the s1 entry in use, which is not dangerous. The FAQ has an entry on DD disks. I can't say much about your main question; I've never heard of doing it. It sounds less dangerous than putting a FS in a file, like we do with ISO filesystems all the time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using a hard drive without partitions
Nikolas Britton [EMAIL PROTECTED] writes: But in FreeBSD your disk needs a slice otherwise it's not compatable with fdisk / bsdlabel / growfs... I think. One of the main reasons for using a DD disk is so you don't have to mess with those things; they are of no use on a DD disk (assuming that you cover the whole disk with the file system). You haven't said how you plan to use this disk. If you're going to use it for raw data, you don't need disk labels or file systems or anything, you just write (eg, ) and read (eg, ) from it, or tell your custom driver about it. Do you want to mount it for files? You've got a standard partition table with the s1 entry in use, which is not dangerous. The FAQ has an entry on DD disks. But it is dangerous because it starts at sector 0. I've read that FAQ as well as greg's book, Lucas's book, unix power tools, the man pages, handbook, etc. I will reread them again. WHAT is dangerous? Yes, a DD disk is (more) dangerous, but you don't have a DD disk. Your s1 doesn't start at sector 0 and so it isn't considered dangerous. Your s1 probably starts at the 64th sector. And I'll take a guess that your newfs /dev/ad0s1 (if it works at all) is starting the new filesystem at least 16 sectors further on, after the disk label area (which it probably assumes is there). The newfs manpage says that the disk must first be labeled. I'm going to be working on this server today and I'll post some of the details of fdisk, bsdlabel, etc. to see if I can help clarify things. Yeah, I'd like to see your bsdlabel ad0s1; I'm wondering if you have a disk label with c when you think you have no disk label. Can you mount /dev/ad0s1c? Can you mount dev/ad0s1? Seems to me you'd either want to be safe and use ad0s1a or live dangerously and use ad0a or even ad0 if it seems to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
Glenn Dawson [EMAIL PROTECTED] writes: pp-p_fstype = FS_BSDFFS; pp-p_fsize = sblock.fs_fsize; pp-p_frag = sblock.fs_frag; pp-p_cpg = sblock.fs_fpg; } The last line is the one that inserts that number. sblock.fs_fpg is the number of frags per cylinder grounp. Glenn, can you tell me which of those numbers, if any, can be changed after a newfs has been done and the file system well occupied with data? (The lousy sysinstall disk labeler wiped out several of my disk labels and I restored them with zeroes in those fields of the disk label. It worked OK, but I'm guessing it only worked because the bsdlabel defaults were the same as they were when I first did bsdlabel...; newfs If defaults had changed or I used non-default values the first time, I'd have been SOL, right? Or do those values just serve as optimization/tuning values for the kernel?) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can someone clarify ipfw's in/out/recv/xmit/via concepts?
Dave McCammon [EMAIL PROTECTED] writes: Here is a link to a thread that help me to understand the in/out/recv/xmit stuff. Thanks guys. I think I've got most of it now. Incoming packets are those entering the OS kernel implementing the ipfw firewall, but not necessarily those entering the ipfw firewall each time the kernel uses it. Outgoing packets are those leaving. Depending upon firewall config, the firewall can test packets one or two times as they enter the kernel, considering them as incoming, and one or two times as they exit the kernel, considering them as outgoing. (See ipfw diagram.) An exception is that when bridging, it tests packets only once, considering them as incoming only. (The latter based on my tests.) When it tests an incoming packet it doesn't try to predict which interface it will be transmitted on (not sure why, if NAT isn't on), so in rules don't match against an xmit interface. When it tests an outgoing packet, it knows which interface it was received on and which interface it will be transmitted on so out rules may match against both recv and xmit interfaces. Using via if0 is like using three rules: in recv if0, out xmit if0, and out recv if0. Using out via if0 is like using two rules: out xmit if0 and out recv if0. Using in via if0 is like using in recv if0. I'm not claiming that the above is any better than the manpage; I'm just trying to quickly hang some simple facts out there to be shot down if untrue. (Maybe someday I'll set up a routing firewall to test more of them than I have yet.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with booting MBR
[EMAIL PROTECTED] writes: # DeviceMountpoint FStype Options DumpPass# /dev/ad1s2b noneswapsw 0 0 /dev/ad1s2a / ufs rw 1 1 /dev/ad0s1a /usr/local ufs rw 0 0 /dev/ad0s1d /varufs rw 0 0 /dev/ad0s1e /tmpufs rw 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Now, even though I read the booting procedure in the handbook and somewhere else in the internet, issuing the various fdisk -b B, disklabel -b .., boot0cfg .., I was completely unable to modify the MBR and make this FreeBSD only computer boot directly into this OS. If you're sticking to FreeBSD's boot0 MBR, you'll have to put one on each disk. I don't know if boot0 can remember F5 as the default choice for auto-booting or not. But one way or another the first disk's boot0 needs to use F5 to start the second disk's MBR/boot0 which needs to use F2 by hand or from boot0cfg config. You could also use grub or lilo to do it too, but it's harder to set up. P.S. Is it possible that some problems can arise by the fact that I used an a slice (ad0s1a)for mounting /usr/local and freebsd starts from ad1s1a? Only the easy-to-fix problems that you're having. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
