Re: Problem with adding more swap !
Hi, all The documents on freebsd's website suggest that, as a system grows, it's recommended for adding more swap paritition to system. My questions are: Does it mean adding another swap to disk or to slice ? The disk structure: ad0s1 -- ad0s1a / (boot from here) -- ad0s1b swap -- ad0s1e /var -- ad0s1f /tmp -- ad0s1g /usr ad0s2 -- ad0s2e /usr1 (data) Do I need to add another swap partition as ad0s2b ? Hmmm. I am not quite sure why you would have made two separate slices on the one disk for FreeBSD instead of having another partition on slice-1, but... Anyway, what do you mean 'as a system grows'? Unless you have some very memory hungry applications or large numbers of processes that hang around but don't really need a lot of processor time, generally you figure swap size needs by memory size. You want at least more than your physical memory and 2X to 2-1/2X physical memory is the typical rule of thumb. If you already meet that, don't worry about, unless you have some other indication that you are running out of combined memory/swap (page) space. NOTE that the virtual memory system uses swap space for its paging. Typically, not much actual swapping really happens, though it can if there are a lot of processes not doing anything. You can make a file pretty much anywhere there is room and set things up to swap to it, but that should be considered only a temporary solution. The better thing is to make either a larger s1b or make an s2b partition for swap (or add a disk - ad1s1b, + whatever) as you say. In either case (enlarging s1b or making an s2b), unless you have space left in one of those slices that you did not already use up in the existing partitions, it means redoing the filesystems already on the slice. That means backing up everything on the slice, repartitioning, newfsing and restoring everything. So, given this, it would probably be a good time to rethink your whole disk layout and go from there. Maybe it would also be a good time to go to an additional or larger disk as well. jerry TIA, pjn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with adding more swap !
Hi, I've heard if there are many disks on one machine it's good (in respect of performance) for adding swap parition on multiple drive, what does this mean (if that's true) ? Well, if you can spread it across multiple controllers, it can speed things up. But, generally I think that swap is used in a serial manner, eg the first chunk gets used up before the next one is started, etc. So, that would mean that you would want to put only a little on the boot drive (you need some there for special occasions) and most of the rest on another drive and another controller if you can. Compared to the CPU, disk access is rather slow, so anything you can do to spread out the work across more than one disk tends to speed things up. But, if you are the only one using the machine and that is mostly for one activity at a time you probably won't notice any difference. jerry My box has six IDE drives two on primary, two on secondary and two connected via IDE controller. TIA, pjn --- Jerry McAllister [EMAIL PROTECTED] wrote: Hi, all The documents on freebsd's website suggest that, as a system grows, it's recommended for adding more swap paritition to system. My questions are: Does it mean adding another swap to disk or to slice ? The disk structure: ad0s1 -- ad0s1a / (boot from here) -- ad0s1b swap -- ad0s1e /var -- ad0s1f /tmp -- ad0s1g /usr ad0s2 -- ad0s2e /usr1 (data) Do I need to add another swap partition as ad0s2b ? Hmmm. I am not quite sure why you would have made two separate slices on the one disk for FreeBSD instead of having another partition on slice-1, but... Anyway, what do you mean 'as a system grows'? Unless you have some very memory hungry applications or large numbers of processes that hang around but don't really need a lot of processor time, generally you figure swap size needs by memory size. You want at least more than your physical memory and 2X to 2-1/2X physical memory is the typical rule of thumb. If you already meet that, don't worry about, unless you have some other indication that you are running out of combined memory/swap (page) space. NOTE that the virtual memory system uses swap space for its paging. Typically, not much actual swapping really happens, though it can if there are a lot of processes not doing anything. You can make a file pretty much anywhere there is room and set things up to swap to it, but that should be considered only a temporary solution. The better thing is to make either a larger s1b or make an s2b partition for swap (or add a disk - ad1s1b, + whatever) as you say. In either case (enlarging s1b or making an s2b), unless you have space left in one of those slices that you did not already use up in the existing partitions, it means redoing the filesystems already on the slice. That means backing up everything on the slice, repartitioning, newfsing and restoring everything. So, given this, it would probably be a good time to rethink your whole disk layout and go from there. Maybe it would also be a good time to go to an additional or larger disk as well. jerry TIA, pjn Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Quick upgrading question
On Mon, 13 Oct 2003 09:47:29 -0500, Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (Oct 13), [EMAIL PROTECTED] said: Hi there + happy turkey day, Thanksgiving is in November :) Not in Canada. I remember wondering years back why Western Canadians waited until late November to start the ski season, before I found out Thanksgiving comes in October north of the border. :) It should be moved a couple of weeks earlier in the States too. By the time it gets here the harvest is long gone and most of the fresh stuff is done or rotten. But, I suppose this is Off Topic for FreeBSD Questions... jerry Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with adding more swap !
Jerry McAllister [EMAIL PROTECTED] writes: Well, if you can spread it across multiple controllers, it can speed things up. Right. But, generally I think that swap is used in a serial manner, eg the first chunk gets used up before the next one is started, etc. That's wrong. See the Handbook section titled Swap Partition. http://www.freebsd.org/handbookconfigtuning-initial.html#SWAP-DESIGN So, that would mean that you would want to put only a little on the boot drive (you need some there for special occasions) and most of the rest on another drive and another controller if you can. Because FreeBSD tries to stripe the usage across all of the swap space, you're best off giving it space on all of the disks. However, if your disks are not all the same speed, you're better off sticking to the fastest ones for swap space. Hmmm. Guess I am out of date on this part. Some older systems I worked on (not necessarily FreeBSD) did not stripe swap. It's very nice that FreeBSD does. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freeBsd
can you tell me what a FreeBsd is and what i can do whit it? ral Looks like you have a lot of reading to do. Go to the FreeBSD web page and start reading. http://www.freebsd.org/ Click on the links and follow their trails for complete information. Start with the link For Newbies under Documentation, but don't stop there. In general, FreeBSD is an Operating System (OS) for computers. It is BSD because it has its roots in the _B_erkeley _S_oftware _D_istribution group at University Of California at Berkeley. It is Free because it is available to download, install, use, modify and redistribute freely merely by downloading the ISO-s from the FreeBSD site. You can also buy a CD set from a couple of companies who package the system and ports and burn them on CDs for you for a nominal cost. The rest is up to you to learn by studying and trying it out. Have fun, jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Another Newbie Question: C or C++
I need to buy a book on C or C++ to help me in FreeBSD. Which would be better to buy? This doesn't answer your C++ part of the question, but you should have the Kernighan Ritchie The C Programming Language and then get something like C A Reference Manual (Latest edition is 5th I think) by Harbison and Steele.After that you might look at C Programming FAQs by Steve Summit. I first thought a book on C would be best, because the OS is written in C. But, now I'm not sure because I read that gcc can compile C++ too (so, I'm assuming C++ must get used too). Does it even matter? Suggestions? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Info.
On Tue, 2004-01-13 at 20:13, Kevin R. Lee wrote: Sorry, one more question, what does DEC Alpha stand for? Digital Electric Corporation. (or did before Compaq bought them, before being bought themselves, by HP) Actually, I think it was Digital Equipment Corporation. DEC was a major vendor for what was then called Mini computers - refrigerator sized machines intended for use in labs and engineering workshops. Alpha was one of their brand model lines of work stations. jerry Micheas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Micheas Herman email: [EMAIL PROTECTED] Free Print Shop web: http://www.FreePrintShop.org phone: (415)648-3222fax: (415)648-4466 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Information
Hello, I was wondering what BSD stands for? Also what does AMD and Ultra SPARC stand for? Any information would be very helpful. Check out this web page: http://www.catb.org/~esr/jargon/ This set of pages seems to be either mirrored or cross referenced in a number of places. Keep at least one of the addresses ready at hand - bookmarked. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dual-booting with xp
Hello, I am trying to install FreeBSD 4.9 on a machine that already has XP installed. It has 3 SCSI drives. I would like to keep XP on the first drive, and install FreeBSD on the third drive and make it dual-boot. What's the easiest way? When I installed, I made a slice on the 3rd disk (using entire disk) and created my partitions there. I also selected the FreeBSD bootmanager, but it doesn't seem to write to the first disk, so now when I reboot, I don't get a bootmanager menu at all, but go right into XP every time. Well, that is all good, but it sounds like you didn't choose to install an MBR when you installed FreeBSD. It asks that on one of the screens along about the middle of the process. It offers three options as follows: BootMgr Install the FreeBSD Boot Manager Standard Install a standard MBR (no boot manager) None Leave the Master Boot Record untouched You need to install the FreeBSD Boot Manager (or another third party boot manager) on every disk that will have bootable slices. That includes the first disk that you are leaving MS stuff on. The reason is found in the boot process. Somewhat simplified and glossed over, it is: The BIOS runs and runs down its list of bootable devices in order of the list. Typically that is 1: Floppy Disk 2: CDrom 3: Hard disk For Hard disk, it is only smart enough to look at the first one. The BIOS hands over boot control to the first of these devices that it finds a boot record on (please pardon the grammar). If you only have one disk (the first disk) with one bootable slice (the first slice) you don't need a Master Boot Record because there is no choice needed to be made. It just uses the boot block on that first slice. But, that is not what you are trying to do. You are trying to multi-boot. So, you need the MBR. The code in the Master Boot Record on that device does a few things and then if it is set up to boot multiple slices, lets you choose which one of the slices to boot. Each of those slices needs to have a boot block on it. The boot block on the slice finishes some stuff and starts the rest of the boot process for whichever OS you have on that slice. If the Choice is to boot from a disk other than the first one, you have to select that device when the MBR offers the choices and then it jumps to the MBR on that other disk and gives you a choice of bootable slices on that drive. So, you need the MBR on each disk with bootable slices along with the OS boot block. The FreeBSD MBR will work quite fine. It is a very small one and as such doesn't allow you to customize the displays it shows up for the choices. Typically it recognizes and displays meaningful text for FreeBSD and LINUX but puts either '???' or 'DOS' for the Microsloth systems no matter what they are. But, as long as you don't care about how pretty it is it works just fun to select them. I am currently typing on a machine that is dual booted with XP and FreeBSD 4.9. The MBR offers choices of ???, DOS and FreeBSD. The ??? is a Dell diagnostic slice, the DOS is the XP and, of course, FreeBSD is FreeBSD. But, if you want, you can install one of the other third party Master Boot Records such as Grub if you like. There are a bunch of then with varying ease of use and varying size and prettiness. jerry Thanks, Duane ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Remove CRs
FreeBSD- Please help, this is really important. I was told that i could get rid of the ^m symbols at the end of the lines in my web page's html code by using sed. They said to execute sed s//^m^m index.html index.html or something like that. This got rid of everything in the file. I really need this back, so any help would be greatly appreciated. I always use tr(1) to do that, eg say your Microsloth file is myfile.txt do this: tr -d \r myfile.txt myfile Then you have a file called 'myfile' without the extra ^M-s which are Carriage Return (CR) characters identified with the \r in the command. You can also use dos2unix if you have it installed. But tr comes with FreeBSD by default. Have fun, jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find the reverse on a IP address?
Morning everyone. I'm having a major brain freeze this morning. I dont recall how to find the reverse for an IP address? I need to do some testing with a few IP addresses, to ensure they have valid reverse's set, but dont recall how to check them. If I remember, you could do it with both 'nslookup' and 'dig' correct? Sure. just nslookup xxx.xxx.xxx.xxx and if it comes back with a good/authoritive hostname it should be OK. Try man nslookup for more possibilities. jerry Anyone have a moment to help me out here? In the meantime, it's man page time... I appreciate the help. Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find the reverse on a IP address?
Sure. just nslookup xxx.xxx.xxx.xxx and if it comes back with a good/authoritive hostname it should be OK. Try man nslookup for more possibilities. Do note that nslookup is deprecated; see http://www.debianplanet.org/node.php?id=3D140 for a decent explanation why. Kind of short on information there. Maybe that is because I am not registered on that site. Anyway, is that being deprecated sort of a LINUXy thing? Does it apply to BSD, especaily FreeBSD too? jerry Kirk Strauser ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find the reverse on a IP address?
On Fri, 16 Jan 2004, Jerry McAllister wrote: Do note that nslookup is deprecated; see http://www.debianplanet.org/node.php?id=3D140 for a decent explanation why. Kind of short on information there. Maybe that is because I am not registered on that site. Anyway, is that being deprecated sort of a LINUXy thing? Does it apply to BSD, especaily FreeBSD too? Hi! deprecated means, that this program has a successor (in this case dig(1) ) and it may happen, that it disappears in a future release. So you get that warning, so that you have time to get familiar with it, that you may re-write some of your scripts still using nslookup etc. I don't mean to ask about the meaning of the word deprecated, but rather, is nslookup being deprecated a LINUXy thing, or is that going to happen in FreeBSD too? jerry HTH Olaf -- Olaf Hoyer[EMAIL PROTECTED] Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find the reverse on a IP address?
[nslookup being deprecated] On Fri, Jan 16, 2004 at 01:58:44PM -0500, Jerry McAllister wrote: I don't mean to ask about the meaning of the word deprecated, but rather, is nslookup being deprecated a LINUXy thing, or is that going to happen in FreeBSD too? No, it's neither Linux nor BSD derived. BIND is developed by the Internet Software Consortium (http://www.isc.org/products/BIND/), and they are the people responsible for that decision. Most Unix vendors ship ISC Bind code and applications standard with their OSes, plus there are quite a few shrink-wrap products based on ISC code, which explains why nslookup(1) has been such a long time a-dying. FreeBSD uses a pretty straight port of ISC BIND to provide named(8), host(1), dig(1) etc., (but AFAIK doesn't use the straight BIND resolver code in libc) -- so nslookup(1) will disappear from FreeBSD when ISC releases (and then FreeBSD imports) a BIND version without it. Same probably goes for most Linux distributions. OK. It is just that when something gets labeled deprecated often there is a note indicating that put in the man page, but I didn't see one for nslookup. jerry Cheers, Matthew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find the reverse on a IP address?
and the BIND9 documentation includes this statement: Due to its arcane user interface and frequently inconsistent behavior, we do not recommend the use of nslookup. Use dig instead. =20 These notices will no doubt appear in the base system when BIND 9 is imported. Currently FreeBSD ships with BIND 8.3.7: what the plans are for importing Bind 9 I do not know. Ah, a couple of our group has looked at Bind 9 , but so far we have not moved to it. So, guess I wouldn't see an message, even in the on the servers with 4.9 FreeBSD I just installed this week. Thanks for the further information, jerry Cheers, Matthew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Web Editing?
What do people here use to edit HTML documents? I usually use Dreamweaver, I usually use vi. But, generally, the consultants here recommend Dreamweaver. jerry but I haven't gotten the time to try to get wine working so I can run Dreamweaver on FreeBSD. TIA Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Just showing my support
Hello all, My Name Is Allen Jaworski and I am starting a small blog to show friends and family how to take better care of the computers. I have always been facinated in open source programing. I am asking permission so I can include a link in my blog to your website. Currently I am using Windows XP and Redhat Linux in my computers at home because lack of a budget. But I will soon be giving FreeBsd a try however. I don't think anyone will object to your putting a link on your site to the main FreeBSD web page. In fact, it is probably encouraged. One thing you can do to make people more happy though is when you post messages to any of the Email lists, either set your Email program to break lines at about 70 characters or manually break lines at about that width by hitting a Carriage Return (Enter) for each line. That will help those of us using text based Email readers to read you messages and will make it more likely that people will respond to them. jerry Thank you for your time, Allen Jaworski ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to mount a FreeBSD-5.1 partition from FreeBSD-4.9
On Wednesday 21 January 2004 17:26, Sergey 'DoubleF' Zaharchenko wrote: On Wed, 21 Jan 2004 15:52:25 +0100 Juan Rodriguez Hervella [EMAIL PROTECTED] probably wrote: On Wednesday 21 January 2004 14:53, Sergey 'DoubleF' Zaharchenko wrote: On Wed, 21 Jan 2004 13:26:25 +0100 Juan Rodriguez Hervella [EMAIL PROTECTED] probably wrote: Hello, please send the reply to myself cause Im not subscribe to the list I've got a FreeBSD-5.1 installation in /dev/ad0s3, but I usually run FreeBSD-4.9 from /dev/ad0s2. 5.x uses UFS2 by default. 4.x does not understand UFS2. In short, you either re-newfs the 5.x partition to be UFS1, or you are short of luck this time. I can not believe you !, I guess there is (or there will be) some work-in-progress to have UFS2 support on FreeBSD-4.X systems. If only by you:(. I'd suggest you make your 5.x partition UFS1 and be satisfied with that - that's pretty much all you can do. Or are we following Windows way of life here ? If 5.x couldn't understand 4.x, that would be a bad thing. But forcing 5.x to be absolutely compatible with 4.x is another bad thing. If you were forced to stay that compatible all the time, you wouldn't be able to do major architectural changes. If everyone thought the same way, an Athlon or a P4 would be a 80286, only MUCH faster (which it is for most olden DOS or Windows/16 programs, so your definition of `Windows way of life' is definitely contrary to mine). You don't complain 4.x can't run 5.x binaries, do you?:) But the filesystem is a different thing, imho. For example, if you use FreeBSD-4.X you can mount ext2,ntfs,msdos,cd9660,smbfs. if you use Linux, you can mount ufs. what's the reason it is not possible to make a program which understands the UFS2 filesystem under FreeBSD-4.X ? Is there any tecnical barrier ? Even if the filesystem was mounted read-only (like ntfs), that would fit me Because the development track is 5. and that is where new things are going. The 4. track gets necessary bug and security fixes, etc now, but not any major new features. The 4. track will soon be completely replaced by 5.. jerry Besides, is there any way to make my UFS2 filesystem go back to UFS1 without losing the data ? Just dump(8) it to a tape or other disk, create a new UFS2 file system where the UFS2 now lives and then restore(8) the dump. Thanks. I ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to mount a FreeBSD-5.1 partition from FreeBSD-4.9
On Wed, 21 Jan 2004, Jerry McAllister wrote: Just dump(8) it to a tape or other disk, create a new UFS2 file system where the UFS2 now lives and then restore(8) the dump. i'm sure you meant create a new UFS1 file system where the UFS2 now lives. :) Yup. My typing teacher would roll over in her grave except she is still alive (she was really young then). jerry Regards, /\_/\ All dogs go to heaven. [EMAIL PROTECTED](0 0)http://www.alphaque.com/ +==oOO--(_)--OOo==+ | for a in past present future; do| | for b in clients employers associates relatives neighbours pets; do | | echo The opinions here in no way reflect the opinions of my $a $b. | | done; done | +=+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FDisk won't detect or accept correct disk geometry from BIOS
Thanks for your thoughtful and helpful reply. I should have given more technical details. I already tried (with both 4.9 and 5.1) letting the FreeBSD install proceed with fdisk's geometry value assumptions, and what I always get is a non-bootable hard drive that gives the Missing operating system error at boot. The hard drive is IDE, not SCSI. It is a Maxtor UltraMax 40GB ATA/100 drive purchased shy of two years ago. The physical geometry reported by Maxtor in the specs for the drive is different from the geometry my BIOS reports that it has auto-detected and is using to address the drive. And both of *those* geometries are different from the one that fdisk keeps trying to assume. I've already read all the FAQs, handbooks, and support sites I could find regarding FreeBSD and disk geometry. None of them have contained any information specific to IDE drives (they all seem SCSI-centric), and none of them have clearly explained all the background context about how drive geometries work. I guess there is a physical geometry provided by the drive manufacturer, and then different geometries (all of which may be valid) your BIOS might use to address the drive depending on the mode it is using (LBA, etc). As far as I can tell, the geometry values a user is supposed to feed to fdisk are the values that the BIOS reports that it is using to address the drive, but I'm not even sure if that is correct because the documentation is so impenetrable. And of course many users are running into this issue where the drive geometries reported and used by their BIOS are simply rejected by fdisk as invalid whenever they try to enter them into fdisk, which makes no sense to me. I will definitely agree with one thing at least: I wish all this were much better documented. There are lots of pieces of documentation in various places - some up-to-date, and some obsolete and some sort of in between. It is very hard to sort out the differences. I think a lot of the problem is historical but as things have been cleaned up over the years the documentation did not keep up and not everything was overhauled along the way, just tweaked as needed. Plus, part of the problem is no-one out there who has written documentation understands the entire thing from front to back, just the parts they have worked on. I could be wrong on this, but it really looks like that. I really wish one of these geniuses would do a complete documentation of disk layout and mapping to whatever and flag bytes and boot blocks and MBRs and... This disk geometry thing is not unique to FreeBSD. The confusion exists in all OSen that make use of PCs and PC BIOSs even in MS though they try to keep that covered up. Anyway, I think you will get the missing OS message if you have not correctly installed some sort of boot block on the device. If you are single booting, you can make one big slice and then you don't need to have the MBR, just a standard boot block. If you are dual booting you have to have BOTH an MBR and then in the bootable slice, a boot block. Also, the system expects root to be in the bootable slice and to be partition 'a' in the bootable slice. (I understand you can do heroics and fudge that, but don't bother trying) The machine I am typing on right now has an IDE disk (even though most of ours have SCSI) and the Physical geometry does not match what fdisk says. It is dual booted with WinXP (actually 3-booted if you consider the vendor maintenance slice). It installs, boots and runs just fine. I don't think that the system would even be able to complete a write to the disk at slicing, partitioning and installing time if the geometry was not working out. It is just too basic to everything the install does.I think you need to look for the problem some other place, such as MBRs or partitions or something. Hopefully someone out there can offer some more useful suggestions. jerry - Original Message - From: Jerry McAllister [EMAIL PROTECTED] To: Keith Kelly [EMAIL PROTECTED] Cc: freebsd-questions [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, January 22, 2004 12:44 PM Subject: Re: FDisk won't detect or accept correct disk geometry from BIOS Please see this page: http://lantech.geekvenue.net/chucktips/jason/chuck/1044789670/index_html This is exactly the problem I am having now whenever I try to install either FreeBSD 4.9 or 5.1. Clearly, a lot of other users out there are having this problem too. FDisk absolutely refuses to accept the correct geometry values (the ones my BIOS tells me it is using to address the disk), instead insisting on using some values that are not even close to correct. Then after installation completes and I try to boot, I get a missing operating system message, which is no surprise given that the disk was addressed by the installer using
Re: FDisk won't detect or accept correct disk geometry from BIOS
Yes, I tried it both ways (installing BootMgr, and installing a standard MBR). I just thought of one more awful thing which has happened to me on a number of occasions, way embarrassingly too many times. You don't happen to have a floppy disk in the floppy drive or possibly a non-bootable CD in the CD drive do you. That is where I see that message most often. If you tried to install using the two floppies, for example and didn't pull the second one out before rebooting, it would do that. The same would be true if you put one of the other CDs in the set to load some things. I'm still guessing something to do with the MBRs and boot blocks and whatever you called the 'a' partition in the slice, etc though. jerry - Original Message - From: Chris Pressey [EMAIL PROTECTED] To: Keith Kelly [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, January 22, 2004 2:38 PM Subject: Re: FDisk won't detect or accept correct disk geometry from BIOS On Thu, 22 Jan 2004 14:24:19 -0800 Keith Kelly [EMAIL PROTECTED] wrote: Thanks for your thoughtful and helpful reply. I should have given more technical details. I already tried (with both 4.9 and 5.1) letting the FreeBSD install proceed with fdisk's geometry value assumptions, and what I always get is a non-bootable hard drive that gives the Missing operating system error at boot. Hi Keith, Just to be sure - did you elect to install BootMgr (or a regular boot record) on the drive when sysinstall asks? -Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I get into GUI?
Hi, my name is Claude, and I'm new to FreeBSD. I've installed it on a hard drive by itself, and I get it to boot. The install seemed to have completed without a glitch. My problem is that I expected the booting process to finish in the graphical user interface. Instead, it stops at a CLI prompt. Maybe I did something wrong. I tried re-configuring by booting off the CD, and I selected KDE as my user interface. But something in the configuration goes wrong, and it tells me to select a simpler interface. I've tried a couple of the others, with the same result. No, generally X is not set up to start automatically on boot. Check out startx(1) and all its related configuration files and possibilities of what it will start up. Then, after you have it set up, when you boot your machine, then log in with your working account (preferably not root) and type 'startx' and voila you have it. FreeBSD makes fewer assumptions about what you want. That means you have to do a little more to get things set up the way you want, but it also means you aren't stuck with what someone else thinks you ought to want. Most of us are really down on someone in the northwest doing our thinking and decision making for us which is _one_ of the big things that brings us to FreeBSD. jerry I did not modify anything in the kernel. Is that the problem? My computer has a Soho P4X400 Dragon Lite MB, an Intel Celeron 2.2 GHz processor, 256 MB of DDR400 memory, an Nvidia GeForce2 video card, and otherwise runs Win2000 and WinXP Pro flawlessly. I've read all sorts of help files, but am still pretty lost. Can you advise me as to how to proceed from here? Is there a forum I can post this to? Thank you very much! Claude ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to get rid of ^M character using vi
how do i get rid of this annoying character ^M using vi, in pico i used the arguments '-w' but what about in vi? Those are extra carriage return characters generally displayed as CR or ^M or \r depending on which programmers convention is being used. There are lots of ways to strip then including those using vi and sed and perl, etc. The one I use which I find easiest is to run tr(1) THis is in FreeBSD standard. You don't have to install a port just for that like you do for some of the utilities that will do it. Check out the man page. Presuming your file is myfile.crs just do: tr -d \r myfile.crs myfile.fixed and it will remove (-d) all carriage return characters (\r) and write the results to myfile.fixed. It will work for modifying other stuff across a whole file too. You just have to learn its idea of the right conventions for special characters (if it involves special characters). jerry cheers _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a few words on BIOS/FDISK geometry
Wow, Have you put this up as a FAQ somewhere? It seems like a good idea to do so. jerry I find most of the BIOS/MBR/FDISK disk geometry gospel that has recently appeared in freebsd-questions to be confusing if not actually incorrect. In the interest of world peace of mind, I feel compelled to offer my own model of reality. It really isn't that complicated. There are two common ways in which disk sector addresses are expressed. These are the LBA (Logical Block Address) number and the C/H/S (Cylinder/ Head/Sector) numbers. As pretty much everyone knows, the LBA and C/H/S values are related by an expression similar to: LBA = (C*NH + H)*NS + S where NH is the number of heads and NS is the number of sectors/track. C/H/S used to be the most common address representation but LBA has since gained popularity because it is conceptually simpler (is only one number) and because C/H/S numbers are typically limited to inconveniently small values. The physical significance of the NH and NS values has been largely eroded by the advancement of technology. We now only use these values when converting between sector address representations. The system BIOS provides a basic disk access facility sometimes called int13. There are different int13 functions for things like reading, writing and obtaining disk parameters such as geometry. The original basic int13 functions, implemented by essentially all versions of PC BIOS, expect sector addresses to be in C/H/S format. There is also a set of extended int13 functions, implemented by newer BIOS, that expect sector addresses to be in 64 bit LBA format. The disk geometry assumed by the basic int13 functions is what we mean by the term BIOS geometry. The BIOS may describe different geometries for a single disk drive in different contexts. We only care about the geometry the BIOS uses to interpret the disk addresses used with the basic int13 functions. Note that the BIOS geometry may not be related to any physical or logical geometry used by the disk itself. The common FreeBSD master bootstrap program may be installed and configured with the boot0cfg command. It uses the basic int13 functions by default but may be configured to use the extended functions (the packet option). When a FreeBSD partition is booted, the boot0 program boots the boot1 program in the second sector of the partition. The boot1 program in turn boots the boot2 program. I don't know if these programs use basic or extended int13 functions or at what point in the bootstrap sequence the bootstrap programs stop using the BIOS. The MBR (Master Bootstrap Record) partition table (aka FreeBSD slice table) which is stored in the first sector of most PC disk drives contains the starting address of each partition in both C/H/S and LBA format. There are 10 bits in the cylinder field, 8 bits in the head field, 6 bits in the sector field and 32 bits for the LBA field. By (MS?) convention cylinder and head numbers begin at 0 but the first sector number is 1. There is allegedly some important program (unknown to me) which limits the number of heads to 255. Programs that use the basic BIOS int13 functions to access partitions defined in an MBR can address at most 1024 cylinders, 255 heads and 63 sectors (somewhat less than 8 GB). (An explanation of the many disk sizes to which PC systems are sometimes limited is tempting but way beyond the scope of this posting.) The FreeBSD fdisk program needs to know the disk geometry only when filling in the C/H/S fields in the MBR partition table. If it gets the geometry wrong, bootstrap programs that use the basic int13 functions may fail. (Programs that use the extended int13 functions will not be affected!) The FreeBSD fdisk program sometimes gets the BIOS geometry wrong and we have to correct it. How can we determine the correct BIOS geometry of a disk drive in this case? BIOS configuration user interfaces can be confusing and the disk drive geometries they report may not always be those used by the basic int13 functions. The only (usually) reliable way to get a BIOS disk geometry may be to ask the BIOS via one of the int13 functions or to read it out of one of the data structures left behind by the BIOS POST (power on self test). Sometimes if we boot a FreeBSD kernel with the -v option it will tell us the BIOS geometries during the autoconfiguration monologue. I am not sure that I trust it. Sometimes software will report disk controller interface geometry instead. (Hint: if a geometry specifies more than 255 heads or 63 sectors/track, you know it is not the BIOS geometry.) I sometimes boot grub (see /usr/ports/sysutils/grub) off a floppy and ask it about a disk drive with the geometry command. As far as I know, this will reliably report the BIOS geometry. Modern BIOS geometry most frequently uses 255 heads and 63 sectors/track because that maximizes the
Re: How to build FreeBSD entirely from sources?
Hello, FreeBSD from Scratch describes a method for REbuilding a FreeBSD system entirely from sources, starting from an existing FreeBSD system. But I want to build a new FreeBSD system on a machine currently NOT running FreeBSD. How can I do this? I'm used to doing this with Gentoo Linux: With Gentoo, one extracts a stage tarball to the target partition, which contains gcc, glibc and some other binary programs, just enough to rebuild itself, using a bootstrapping script. Then one does emerge system which fetches sources for the entire base system, compiles them and installs them. After that, other applicantions can be installed with emerge packagename (comparable to Ports system). Can I install FreeBSD in a similar way? Sysinstall only installs binary packages. I am new to FreeBSD but not to building stuff from sources (I've been using Gentoo Linux for quite a while now). Yes, but you are building Gentoo from within a LINUX environment, eg you have already installed at least a basic amount of LINUX and then built stuff in that environment. FreeBSD is the same, but easier. Just download the mini-ISO and use it to do an install and include full sources. You might also want to also install X and the ports tree. Then you can cvsup if you want any updates and then modify any part of the source that you think you want, do make world and install it and. reboot. Then, if you want, modify the kernel conf file in /usr/src/sys/i386/conf/ (work with a copy and see the LINT file in that directory plus man pages for the devices for more information on kernel configuring) and loader config file, and build a new kernel and install it. Reboot again. You will have your own completely home built FreeBSD. It is all quite well documented in the handbook and discussed extensively on several web sites (try Google and you will get more than you ever wanted to know) and in several publications and books. It is different from any of the LINUXen because it is better designed, organized consistent. It is too easy (but I ain't complaining). jerry Thanks in advance, GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a few words on BIOS/FDISK geometry
Have you put this up as a FAQ somewhere? It seems like a good idea to do so. I don't have a place to put it. I would gladly offer it to anyone who does. Hmmm. I don't know how to add it to the FAQ list on the FreeBSD site. Maybe it can be submitted to the DOC project in some way. There is probably a procedure, but I don't know it. There is a doc Email list. Actually, it wouldn't hurt to add that sort of background information to the handbook, though it is probably a little deep for some people. jerry Dan Strick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to build FreeBSD entirely from sources?
On Tue, 27 Jan 2004 15:19:33 +0200 Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: On Tue, 27 Jan 2004 07:48:42 +0100 (CET) Geert Hendrickx [EMAIL PROTECTED] wrote: Hello, FreeBSD from Scratch describes a method for REbuilding a FreeBSD system entirely from sources, starting from an existing FreeBSD system. But I want to build a new FreeBSD system on a machine currently NOT running FreeBSD. How can I do this? I believe you can boot from the second (Live) CD, fdisk, label, newfs, mount partitions, extract the sources, cvsup and start building. I didn't try it, but it should work. I don't see why would you do that, but ... I mean why not install first a minimal distribution set with the sources and do the hole thing from hdd. The source is much larger than the installation of the running system. A minimal distribution is a running system. FreeBSD is organized a little differently from LINUX. CHeck it out a little bit and maybe you will see the efficiency of the way it is done. jerry -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remove boot problem
Hello, I recently installed Free BSD. I have two hard drives. I put it on the second one. I took it of the drive because of some problems. Now when I boot up a dos message comes up saying the following: F1 ??? F2 Disk 1 Boot:F1 This is your MBR talking. The last part I cant remember exactly what it says but it is something like that. I would like to know if their is something I need to delete of edit to stop this from coming up? Thank you. I don't know in MS land. In FreeBSD world check out boot0cfg(8) and related things. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Retired Linux user wants to switch
Hi, I've been using Linux for about 7 years. At the beginning the Linux community was still very small and ... All these years I've seen Linux grow. I helped people on IRC while more and more users were coming with their questions. Yesterday I decided to go back to the IRC channel, after about 4 years, to ask a question about USB (I'm not really into USB). What happened really turned me off. They called me a troll, that I should go back to Windows, I'm too dumb to use Linux and because I told them I've been on this channel even before you began using Linux they kicked me off. This is 1 of the many examples. It may sound weird, but because of what the Linux community has become I would like to try and switch some of my systems over to FreeBSD. First I have some questions about what to expect: Welcome to FreeBSD. It doesn't seem so weird. We have seen a lot of people stepping up lately. I see someone more knowledgeable than I has answered your specific questions, but on the issue of the list[s]. It is generally a friendly environment with a lot of tolerance for newbies and, like myself, thick-heads that take several times through for some things to register. You might occassionally get called a troll on a FreeBSD list, but if your question is serious and you persist without inflamitory language, people will settle down and respond with serious posts. People on these lists tend to dislike someone flaming another person more than they do posting dumb questions or being a newbie. If you really seem to be a troll, generally you won't get booted off, just ignored. Besides trolling and flaming, the worst sin on these lists seems to be jumping to post a question without doing some of your own searching first. Always check the handbook, the FAQs and Google, etc before posting - if for no other reason than it may help you better formulate your question. And, most problems and mistakes have come up before and been written about extensively somewhere. There is a huge body of material written about the system - most of it quite good, but always try for more than one opinion if you are searching the archives. People on these lists seem more interested in creating and supporting well running systems than massaging egos, unlike what you see in some places. (but I suppose having the most reliable, efficient and reasonably secure system does some good for the ego... ;-) ) jerry ... These were all question for now. I hope the story at the beginning wasn't too much and didn't violate the rules of this forum. Thank you, Mike Machuidel ;) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Acu Cobol 6.0 for Linux
[apparently the first message didn't get through; this is a repost] Your previous post got through. Probably the presumed answer is that no-one who saw it has tried this or feels competent to respond. You might some response if you could find a way to break the problem down a little more and give a little more detail. But, there probably are not many Cobol users on this list, so you need to give information that clearly establishes it as a problem with system libraries or whatever so people will feel in familiar territory. Someone might know another place (list) to ask as well. jerry Did enybody try to run AcuCobol 6.0 for Linux on FreeBSD's linulator? I tried a couple of times (with old Debian libraries and more recently Gentoo libraries) but runcbl keeps on getting a SIGSEGV right away. ccbl (the compiler) seems to work, though. Any clue? -- walter pelissero http://www.pelissero.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with mount_ntfs
When I try from to mount ntfs partition via commands: mount_ntfs /dev/ad0s1 / mnt or mount -t ntfs /dev/ad0s1 /mnt I get a messege: mount_ntfs: vfsload(ntfs): File exists What does this mean, and what i'll do next? How I can to get access to NTFS partition my hard drive? It's a while since I had to mount an ntfs, so I hope this isn't wasting your time... But are you using an incomplete description of the partition you want to mount? I'd have expected it to be more like: #mount -t ntfs /dev/ad0s1e /mnt The mount line looks perfectly correct to me. The last part of the name you are adding are slices which are what FBSD uses to divide up a partition. They are not relevant to NTFS. Just a little side terminology snit here. The 'e' refers to a _partition_ which FreeBSD uses to divide up _slices_ 's1' rather than the other way around. It is MS that calls slices partitions. FreeBSD slices basically correspond to MS primary partitions. FreeBSD partitions divide slices into the pieces on which file systems are created. Sorry for the somewhat off track comment. I haven't tried to mount NTFS slices but when I mount DOS FATs as msdos type I do not use any partition identifier (the 'e' in the above comment) because there is none. It is a FreeBSD thing and non-existant on a msdos type slice (MS primary partition, neither FAT nor NTFS). I tried a couple of different possible error scenarios -- mounting NTFS over already mounted partition and mounting the NTFS twice -- but neither generated the error the original sender is getting. Just to double-check the mount line, mine looks like /sbin/mount_ntfs /dev/ad1s1 /windows One thing I can suggest is that you run scandisk (from Windows!) over the NTFS partition, even if it us brand new. I had bizarre error from PartitionMagic on my new PC when I tried slicing off some of the NTFS partition and it turned out that there were some errors which scandisk fixed up. Final thought, it is an NTFS partition you are mounting and not a FAT16 or FAT32 one? Obvious I know, but sometimes it is the obvious! Good thought. They got us some new desk machines with XP a while back and I just assumed it had an NTFS like some previous Win2K machines, but it was actually FAT something and I almost skrewed up when I went to slice it for dual boot. So, it mounts as msdos type in FreeBSD, not ntfs type. Fortunately I woke up in the middle of running Partition Magic and noticed. So, check it out. jerry --Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: about logo
I just want to ask (i'm sorry if it's a silly question),why freebsd logo use devil character? There are several web pages that explain this quite well. Start with the FreeBSD.org page and look at its links and then do some searching - on the FreeBSD site and on Google. Try looking for Beastie. Anyway, it is a daemon and is defined as a little creature (a process in this case) that hangs around out of site and does little errands for you. Some of those errands are responding to things coming in from the net, listening to your keyboard and mouse, putting messages in log files, keeping track of the clock and running things that need to be run at special times, etc. It is a bit like Terminate-and-Stay-Resident programs (TSRs) in the Microsloth world. Why someone made a logo with a red suit and a trident fork - well some say the fork is for the system of forking processes in UNIX but I suspect it was at least in part a little impish fun. Not everything has to have a deadly dull logical reason. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: One of your employees are very rude.
I'm sorry but.. hahahahahahahahahahahaha. It's IRC. You expected something different? Love, Randi Harper [EMAIL PROTECTED] http://freebsdgirl.com On Jan 30, 2004, at 11:06 PM, lorink wrote: To whom it may concern, I just want to let the bsd team know this has been a great OS and it is meeting my needs over that of other operating systems including windows which I was a software tester of W2k back in the late 90s. While your documentation is excellent and sometimes such subjects on google searches also provide answers I recently have stumbled across a irc chanell on efnet called #freebsdhelp. Been a good chanell so far but lately there is one op nick name hideaway who has been a little on the rude side and has kicked some people or my self and not permited them to return to the chanell because of his fits. I have a log of the events that led up to my being banned from the chanell and let me know if this is a employee that represent freebsd.org I think maybe someone has mentioned, but FreeBSD.org does not have employees. Development is done and questions are answered by whoever is interested on a volunteer basis. Although it seems fairly rare to run in to a jerk on these lists, it can happen. Those would be volunteers too... As for IRC, I wouldn't know. I don't have time to waste on that. jerry Sincerly, James K ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: C/C++ Unix/Programmer/Tester
I'am interesing in becoming BSD tester or alfa tester, how I can get information about job positions in BSD development. FreeBSD is created and developed by volunteers rather than paid staff. To get a job in BSD development, you would have to get a job in a company that is using FreeBSD (or one of the other BSDs) and that, for their own reasons, chooses to have some staff working on BSD things - probably that run on top of BSD. You could also volunteer to do development, but you would not get paid for it from FreeBSD - no one does. To do this, look at the various projects and or the bug (pr) list and do a good job writing the needed code or correction and submit it. If it gets used and you do this often enough you might end up being a committer. As for testing, just download the latest CURRENT and update to the latest with cvsup and you will be running (and thus testing) the latest BSD. Check out information from the FreeBSD web page - follow the appropriate links. jerry Thanks Ricardo Balda ___ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Advertising?
I thank you for your display of considerable arrogance and unwillingness to cooperte on a socdial or business level. I didn't notice anyone displaying arrogance or unwillingness to cooperate. What I see is someone completely misunderstanding what they were doing and then trying to blame someone else for their own mistakes. Further, it is not possible for someone at FreeBSD to remove your messages from existance because no-one at FreeBSD has any determinate control over where the messages are distributed or stored or archived or made available over the net. It is not a finite thing. If you will take the time to understand what has been told to you, you will be much enlightened and maybe it will help you in avoiding mistakes in the future. Please don't continue to maintain your ignorance and use it to shift blame to others. It will just make things more difficult for yourself and compromise your own credibility. jerry - Original Message - From: Peter Risdon [EMAIL PROTECTED] To: Greg Wilson [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, February 05, 2004 8:32 PM Subject: Re: Advertising? Greg Wilson wrote: http://lists.freebsd.org/pipermail/freebsd-questions/2003-April/001602.html http://lists.freebsd.org/pipermail/freebsd-questions/2003-April/001781.html Hi I reference these two documents, where you have publish my private correspondance. This was obviously inadvertent, but as has been pointed out you mailed a mailing list, not an individual, and so your correspondence has never been private. We all read it as soon as you sent it out. The fact that this is a mailing list is made very clear on the FreeBSD website. All mails sent to this list are archived (and mirrored around the world) automatically, and this is a necessary and important part of the way these lists function. It means an archive (which is searchable) builds up as a point of reference, so people who are dealing with problems and issues can refer to it. Also, there's some chance that questions won't be asked over and over again. Again, this is made clear on the FreeBSD website. Indeed, you can search the archives right there. From time to time people do send inappropriate messages to the list. Frankly, most subscribers would prefer it if they didn't. Your mail was in this category. Inappropriate mails waste people's time. You are, in effect, asking someone to waste more time. I am writing to ask you to remove these documents which were published with out my consent. IANAL, but I'd have thought that the act of sending a mail to a public, open, archived forum constitutes consent to the contents of that mail being displayed in a public, open, archived forum. Please tell me when they are removed, The horse left the stable when you first posted the mails. I can't see that any harm has been done. But if it has, it happened when you sent the mails. Perhaps you could consider this to have been a learning experience? PWR. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [FAQ] Re: Free space wierdness
Herbert Wolverson [EMAIL PROTECTED] writes: This is good, since the correct amount of free space now shows, and the server is back to running perfectly. Can anyone shed any light as to why this discrepancy happened in the first place? I'd love to know what I can do to avoid ever having to worry about this again! The du and df commands show different amounts of disk space available. What is going on? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#DU-VS-DF How is it possible for a partition to be more than 100% full? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#DISK-MORE-THAN-FULL These two questions are discussed so frequently on this and other lists that you should be able to get numerous explanations with a small search on Google and I would be surprised if there were not a FAQ on this. So, check the web page. Basically, du and df look a slightly different things and there is a difference between how much root and regular users are allowed to write to a filesystem. jerry [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1 telnet
Darryl Hoar wrote: Greetings, I have tried to get putty configured to access my 5.1 release box using SSH. No joy, and I'm quite tired of trying. I tried to enable telnet on my 5.1 box. Uncommented inetd.conf line, and verified that the services line was in place. I tried to connect to the box with telnet and got a connection refused. Even rebooted the box with the same result. I am accessing this box on my internal network, and my firewall blocks the telnet port, so I'm not worried about outside access. So, telnet will get me by for now. Any ideas what's wrong ? Did you configure hosts.allow and such, for the ssh session. Also is you PuTTY SSH set for ssh-1 or ssh-2? jerry BTW, searched the mailing list archives on freebsd.org , but didn't find info about this. thanks, Darryl Your firewall blocks the telnet port ... Are you sure that: 1. Your firewall is not blocking the port on your LAN interface as well? 2. Your telnet/PuTTY session is attempting to connect to the correct interface? Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsd equiv of trace?
Isnt this a freebsd Mailing List? try the Solaris lists please. That doesn't make any sense. He is asking a question about BSD. He is asking for something to use on BSD that would do something similar to the trace utility he had been using on Solaris. Why would you expect a Solaris list to know more about it? jerry * Chad M Stewart ([EMAIL PROTECTED]) wrote: I think I answered my own question, ktrace and kdump Now if I can just figure out why dhcpd won't do dynamic DNS updates. :) -Chad- On Feb 9, 2004, at 12:34 AM, Chad M Stewart wrote: What is the BSD equivalent of trace on Solaris? Thanks, Chad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to safely merge two slices on harddisk?
Hi, I have a hard disk, on which I would like to merge two slices into one single slice. The disk slices are as follows: First, in the df output I see below, there is only one slice showing. That would be slice 1 of the /dev/ad1 disk eg. /dev/ad1s1. Second, it would be more useful in this case to post the output from disklabel because that would show the sector numbers of the two partitions (f and g) that you are talking about merging. Do:disklabel -r ad1s1 NOTE: df shows size estimates after all formatting and system reserves are taken out of the calculation, so it does not show the actual number of blocks that were used in creating the label for the disk. It also does not show unmounted partitions such as a possible swap partition. Here is a sample from one of my disks, (minus stock disk info stuff at the top). Note, where is says '8 partitions' it means you can defince up to 8 partitions, not that 8 partitions have been defined. Also NOTE: The size and offset values are given in 512 Byte blocks. 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 1024 819222 # (Cyl.0 - 65*) c: 355517820unused0 0 # (Cyl.0 - 2212*) f: 1048576 10485764.2BSD 1024 819222 # (Cyl. 65*- 130*) g: 6291456 20971524.2BSD 2048 1638489 # (Cyl. 130*- 522*) h: 27163174 83886084.2BSD 2048 1638489 # (Cyl. 522*- 2212*) /dev/ad1s1a98M43M47M48%/home/userB /dev/ad1s1d64G45G14G77%/home/userA /dev/ad1s1e 3.0G 2.5G 282M90%/home/userC /dev/ad1s1f 3.0G 1.0G 1.7G37%/usr/ports /dev/ad1s1g 3.0G 268M 2.5G10%/mnt /dev/ad1s1h 295M 295M -23.5M 109%/diskless_swap I want to merge /ad1s1f and /ad1s1g into one 6Gb slice. My inclination would be to make a good backup of the partitions that you want to preserve - regardless of what nice tricks you want to use and whether they should be safe. Then, when you have good backups done, the best and easiest thing to do would be to re-partition the whole /dev/ad1s1 slice and then reload from backups. But, once you have the backups, you might be able to just use disklabel to rewrite the label so the sectors in partitions f and g are combined in to a single partition f. The key thing to look for in the disklabel -r ad1s1 output is if the f: and g: partitions are truly adjacent and can be a contiguous single partition. This is probably, but it is possible that they are not. Nothing requires using partition labels in alphabetical order. So, add up the size fields of all the partitions before the ones in question. Presuming the above order and typical usage, that would be a: d:. If those sizes equal the offset of the f: partition then that part is OK. Then add in the size of the f: partition to the previous total and if that sum equals the offset value of the g: partition reported by disklabel, then you can be sure they are adjacent and contiguous. So, if you are so inclined, you can take a shot at it. But, if the size sums and offsets indicate that these two are not really adjacent, then you are stuck with complately re-labeling the ad1s1 slice. One improbable thing could come up. It is possible that there is some wasted space that was left out between the f: and g: partitions. If this is so, your size sums and offset values should tell you that. If this occurs, you can just roll that in to the combined f: and g: just by adjusting the size of the new f: partition. To try concatenating the two adjacent partitions do: disklabel -e -r ad1s1 (You could try it once first with -n (eg disklabel -e -r -n ad1s1) just to check and see what it would write) disklabel -d -r ad1s1 will put the label info in to a file of the exact format to feed back to disklabel. Then you can just edit it. When you get out of the file with a write/save it will write the label back to the disk. It will use any editor you have designated, but the default is vi. Example: You should see something like (based on wild guesses from your df above - I did not compensate for how much was taken out by newfs making superblocks, system reserves, unmounted partitions, etc, so these are not the real numbers): 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 200704 0 4.2BSD1024 819222# (Cyl.0 - 65*) c: 153896960 0 unused 0 0 # (Cyl.0 - 2212*) d: 134217728 200704 4.2BSD2048 1638489# (Cyl.0-2212*) e: 6291456134418432 4.2BSD1024 819222# (Cyl.0-2212*) f: 6291456140709888 4.2BSD1024 819222# (Cyl. 65*- 130*) g: 6291456147001344 4.2BSD1024 819222# (Cyl. 130*- 522*) h: 604160 153292800 4.2BSD1024 819222# (Cyl. 522*- 2212*) Basically
Re: I'm really upset with my new computer
I've heard that Sony and Dell don't support UNIX permissions on their proprietary hard drives. Stick with WinXP for now until a patch is committed into the source tree. That doesn't make any sense. No hard drive vendor supports UNIX permissions on their hard drives. File permissions are completely a software thing and have little to do with the hardware underneath - as long as the hardware works at all. Now, WinXP does NOT support UNIX file permissions... Ditch it and get a real OS! (I have FreeBSD installed on lots of Dell machines including the one I am currently typing on and file permissions work just fine) jerry -Craig - Original Message - From: Rob2 [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 09, 2004 12:41 PM Subject: I'm really upset with my new computer I can't even log in without permission errors, yet all the files in my home directory are rob.rob permissions. I end up at the root directory where all homeless users end up Nvidia video doesn't work. I downloaded the latest binary from Nvidia and I don't know where it went on my computer. I'm just having a bad day. BTW Win XP is working flawlessly, just to rub it in. This is Dell 8600 laptop. I just needed to rant and complain. It will get figured out in time. I remember when I bought my Sony laptop I had a whole crop of similar problems. Rob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I'm really upset with my new computer
On Mon, Feb 09, 2004 at 02:43:22PM -0500, Jerry McAllister wrote: I've heard that Sony and Dell don't support UNIX permissions on their proprietary hard drives. Stick with WinXP for now until a patch is committed into the source tree. That doesn't make any sense. No hard drive vendor supports UNIX Uh... Jerry, I think the UNIX permissions remark is a joke. I suppose. Kind of a sick troll, huh. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Choosing between sh and perl for system scripts
Now that I have a desktop workstation and network, I'm trying to learn the true admin side of BSD, such as the periodic tasks, and how to automate things. I see perl all over the system, and I know it's powerful and easy to use. What might help me decide which tool would be best for the scripts I want to write? Probably the two main things to consider are what type of processing you will be doing and how much it will be used. Perl is great for text processing - grabbing things out of text streams, mashing it around, creating easily searched and manipulated tables of that sort of stuff. It is not really so good at anything that needs a lot of floating point number crunching. Perl handles CGIs for web stuff pretty well unless you are getting thousands of hits on something. Then it can be a little slow. Or, if it involves talking to a database, maybe you would prefer PHP for that part of things. Perl is good for scripts that get used now and then. But, it is kind of big so if the script is likely to be used a lot - every second or so, then you will want to use something leaner. Probably either sh or even write it in C. Some people crab about Perl being less secure, but I think that is mostly like everything else. A poorly written script will be insecure in any language. A well written script will be more secure. Since Perl handles all your data types for you, you do not have so much of a problem of overrunning buffers, which is where most cracks develop in the UNIX world. So, in that sense, Perl can be more secure than C code. If you need something that runs in single user mode, then you will want to use sh for that. jerry NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Choosing between sh and perl for system scripts
On Tue, Feb 10, 2004 at 11:48:48AM -0500, Jerry McAllister wrote: : : : Now that I have a desktop workstation and network, I'm trying to learn the : true admin side of BSD, such as the periodic tasks, and how to automate : things. I see perl all over the system, and I know it's powerful and easy : to use. What might help me decide which tool would be best for the scripts : I want to write? : : Probably the two main things to consider are what type of processing : you will be doing and how much it will be used. : : Perl is great for text processing - grabbing things out of text : streams, mashing it around, creating easily searched and manipulated : tables of that sort of stuff. It is not really so good at anything : that needs a lot of floating point number crunching. One place I saw it used that piqued my interest was as an aid to maintaining source code. The book 'The Pragmatic Programmer' talks about perl scripts being used to mark areas that need attention, extract comments, make reports on changes, and so on. Well, since that would be a lot of mucking through text files, Perl would probably be a good choice for it. : Perl is good for scripts that get used now and then. But, it is : kind of big so if the script is likely to be used a lot - every : second or so, then you will want to use something leaner. Probably : either sh or even write it in C. For me on my home box, I will probably be using it to run backups, cvsup, build world, and so on. Hmmm. Could go either way on those. Most of our backup stuff is in either sh because it is not very complicated or C because it needs to run SUID. jerry jm -- My other computer is your Windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: checking checksums on binaries and checking for rootkits
hello, im using FBSD 4.9 ... IS there a way to check the checksum on binairies like ls , ps etc.. to check for rootkits ? On Solaris you can run md5 on a binary and compare it against a utility on SUNS website that will cehck the finger print to see whether the binary is part of a rootkit or the original binary. Does Freebsd have a tool like this ? The checksums are available for the ISOs on the FreeBSd site in the same directory as the ISOs. As for individual routines, I don't know. jerry -- Brent Bailey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to safely merge two slices on harddisk?
Malcolm Kay wrote: On Tue, 10 Feb 2004 04:19, Rob wrote: Malcolm, Thank you for your detailed answer to my question. Malcolm Kay wrote: On Mon, 9 Feb 2004 13:46, Rob wrote: Do not change the offset of 'f'. If 'g' does not physically follow 'f' on the disk then this is not going to work -- give up now!!! How can I find that out? Is it the slice order in the disk label editor from /stand/sysinstall : No! What you want is disklabel (see man page). On 5.x this seems to have been replaced by bsdlabel -- but I have no experience with 5.x. The disklabel output of the disk is: - # disklabel /dev/ad1s1c: [...zip...] 8 partitions: size offsetfstype [fsize bsize bps/cpg] c:1562963220unused0 0 # (Cyl.0 - 9728*) a: 20480004.2BSD0 0 0 # (Cyl.0 - 12*) e: 6348800 2048004.2BSD0 0 0 # (Cyl. 12*- 407*) f: 6348800 65536004.2BSD0 0 0 # (Cyl. 407*- 803*) g: 6348800 129024004.2BSD0 0 0 # (Cyl. 803*- 1198*) h: 614400 192512004.2BSD0 0 0 # (Cyl. 1198*- 1236*) b: 614400 198656004.2BSD 2048 1638491 # (Cyl. 1236*- 1274*) d:135816322 20484.2BSD0 0 0 # (Cyl. 1274*- 9728*) - I have put the partitions in a new order, such that the Cyl. counts are continuously running up. Am I right, that g physically follows f here? If so, that would mean I can merge f and g into one new partition of 6 Gb, right? Do NOT pay any attention to the supposed cylinder counts out on the right. They are only comments and probably do not even reflect actual cylinder values. Although it just happens that those cylinder comments work out to appear in order, they are very unlikely to designate actual cylinders, but rather some form of virtual cylinder count (They may coincidentally look in order but are really meaningless - ignore the funny old man pulling strings behind the curtain) The ONLY relevant ordering would be one based on the order of the partitions' offsets - which, you have listed in ascending order. As I mentioned in a long description a day or so ago, the relevant information is found in the size and offset fields. They are the ONLY thing that will tell you if the partitions are adjacent and contiguous. In this case, since partition f: begins at 6553600 and is 6348800 blocks long and partition g: starts at 12902400 which is exactly the f: partition offset and size added up, it looks like those two partitions are adjacent and contiguous. I actually wonder if the label editor of /stand/sysinstall can do what I want. Since I now know that f and g are back-to-front partitions, I could remove them and create a single new one; when I write this to disk, I can let sysinstall also create a new filesystem on the newly merged partition. I know this is potentially dangerous, but this way I have already deleted the swap partition, created a new ufs partition instead and created a file system on that; all in sysinstall. I believe it is safe, as long as I do not run 'newfs' on the existing partitions. Probably safe, but backup everything anyway. It is dangerous to bet on tinkering with rewriting the label even if the parts you want to save are kept with the same values. The label is still completely rewritten. In any case, do not use /stand/sysinstall for this. You need more direct control and should use disklabel directly. As mentioned in my previous posting use the command 'disklabel -e -r asd1s1' and then edit the tmp file it puts up and then write[save] it back. This is the most directly reliable way to do it. Since the drive is not a boot drive you don't need any other switches of flags although you may want to try it onece with the -n switch just to see what happens without actually writing anything to the real label. jerry Or am I missing something important here? The real value of backing up everything and redoing the whole disk from scratch. /jrm Thanks, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: wiping a partition
I've gotten into a wierd situation where the best course seems to be wipe a (BSD) partition - without chnaging the size or location - and then restoring from backup. Based on the Handbook (sec. 12.3.2) the correct would seem to be: make backup cd / dd if=/dev/zero of=/dev/da1 bs=1k count=1 newfs -O 2 -U /dev/da1e restore from backup Have I overlooked anything? That will wipe the whole da1 disk , not just a partition on it. I don't know what you really need, but something like cd / umount /dev/da1s1e newfs /dev/da1s1e would make the current stuff on the e partition of slice 1 on disk da1 unreadable short of using one of those heroic super recovery services. If you want the old stuff back, sandwich that with the backup and restore. jerry Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to safely merge two slices on harddisk?
Jerry McAllister wrote: In any case, do not use /stand/sysinstall for this. You need more direct control and should use disklabel directly. As mentioned in my previous posting use the command 'disklabel -e -r asd1s1' and then edit the tmp file Malcolm Kay wrote: A good chance it will work -- but pre-existing 'f' and 'g' data is lost. Thank you guys for your help. I actually did use sysinstall (sorry, Jerry) and mission is accomplished. You are lucky. sysinstall makes some assumptions in the way it calls disklabel. Your situation fit neatly within those assumptions. Yes, indeed, I lost the data is the two merged partitions 'f' and 'g', but that was no problem; I needed to keep the data in all other partitions. Sysinstall did all that for me. Well, it just let you define those other partitions in the same way they were before so effectively it left them alone. Meanwhile I learned a lot more about disklabel, thanks to your comments. Great and many thanks, Disklabel is actually quite easy to use. The man page combined with the fdisk man page can be rather confusing. The approach to writing them seem rather convoluted to me. If I felt competent enough on the subject, I would take a shot at rewriting them, but there are two many details about the extra features I do no know about. But, the main stuff is reall quite straightforward to use. jerry Rob. ___ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: networking w/ win9x
I was wondering. What is an easy, and good programe to use. To network my FreeBSD and Win98box. Depends on what you mean to network. To just hook them together you don't need anything on the FreeBSD side. If you want to be able to mount a network drive on the win box, then run Samba on the FreeBSD box and host things there. Now, if you mean you have both FreeBSd and Win98 on the same box and have it dual booted. Then, you can mount the Win disk space when FreeBSD is running by doing a mount_msdos or making the FAT slice used for win an msdos type in your /etc/fstab file. Then you can read and even write your msdos disk space while in FreeBSD. But, going the other way, you cannot access FreeBSD disk while in the MSwin side of the machine. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root access to a custom .sh defined as shell;
Am running a free server of shells in freeBSD 4.9, the amount of people solicitading new accounts has been too much that i can not handle them by me, so i wrote this .sh program to do it for me, my code its secure as much i can tell, i understand the risk involve and decide to do it anyways, soo i create a new group call 'shellauto', add new user 'newuser' promote to 'wheel', then i modify etc/shells to accept my new shell, so when some body logs to my server as 'newuser' the server run my .sh (freeshell.sh), everything works goodl but my question is ...how can i give my script root previlages ? so can addusers without me? also if there is a way to type a command directly to shell (bash) so i can define quotas of 1mb, and background procees to 3?? that way i can include those commands to my freeshell.sh ...thanks You are not supposed to be able to make a shell script have SUID root ability.So, you either need to write a wrapper in C that calls it or just rewrite the whole thing in C. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install Troubles on IBM x searie 345 and ServeRaid 6i
Hi We have here in the office two new server maschines. IBM x Server 345 with a Raid Controller: ServeRaid 6i I have download the latest FreeBSD Version 5.2.1 RC2 12.2.04 But the Kernel doen't find the Raid Controller, it's say: No driver attached When i read the doc's it must be compiled in the main kernel (IPS are the driver), from the Install CD Rom. Yes, i have try to install with the Floppy Version, too... in drivers.flp see IPS Driver... I don't have a 5.xx here to look at right now, but in 4.9, the latest I have, I don't find an IPS driver listed in lint. Do you have that right? If that driver id is correct, it must be new in 5.xx. Then you need to read up on making a custom kernel and then add the ips driver to the config file and make and install a new kernel. When you do that, work with a copy of the /usr/src/sys/i386/conf/GENERIC file rather than modifying it directly. Refer to the .../LINT file for syntax on all the drivers. You might not be able to do that starting on the raid. You may need another non-raid disk (SCSI preferably, it you have a SCSI controller) to get started. If the necessary driver is not in the 5.2 .../LINT file, then you may have to help make a driver or get someone else interested. Note, that I don't think all of the driver ids are one for one identical from Linux to FreeBSD. So, if it is ips in Redhat, it might supposed to be something else in FreeBSD. That is a little beyond my experience. By the way, where is the .ch (from your Email address) from? I have seen it several times lately. jerry Have anyone a idee how i can install Freebsd? (at the moment only RedHut 9 it's working with this server, and i want not use linux) Very thanx, Michel PS: Sorry for my english...:) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: passing disk geometry parameters to the kernel at boot time
Hi I'm having problems with FreeBSD 5.2-RELEASE getting the proper disk geometry. When I was installing I passed the correct info and installed, but once I rebooted the info is wiped off and again it has the wrong geometry what makes my system very crashy Time for you to do some searching.This has been covered in detail several times in the last 3 or 4 months. Someone write a very helpful description of disk geometry and posted it about a month ago. If you can find that, it might help you understand. But, basically, most of the time, the numbers you see are virtual and you don't want to change what the system thinks even if it isn't consistent from one utility to the next and the utilities such as fdisk make little remarks in their output. You should be going by sector _count_ from the beginning of the disk and ignoring cyl/head/sector values except in some very special situations. This is true when you slice and parititon and then especially when you boot. jerry PS: is there a way to do this in lilo or grub??? thanks in advance Jorge _ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenOffice ports build...
Hello list, How would I install/obtain a compatible binary for OpenOffice 1.1. I don't= =20 have 4+GB for a ports build of it. Either that, or how would I go about=20 merging my /usr and /home partitions so that they're one and the same (like= I=20 should have done from install). For openoffice go to http://projecs.imp.ch/openoffice/ and install it as a package. I have it running now. Note, there is an error in instructions. Instead of running 'openoffice' after the install, presuming you put the .tgz file in /usr/local and do the pkg_add on the file and it installs OK, then you need to do: /usr/local/OpenOffice.org1.1.0/program/soffice instead.^^^ see it is soffice instead of openoffice to get started. Also, it asks for a name of a directory to install in and I shortened that long part marked with ^^ above during the install and then set that /usr/local/openoffice/program in my path and it works just fine. As for combining your filesystems, it is not quite trivial though the process is fairly straightforward if they happen to be adjacent and contiguous. Last week there was a whole series of postings on that issue in the Email list. But, you would probably be better off just moving some stuff such as /usr/ports and /usr/local in to /home and making symlinks to them. Tar up /usr/ports cd /usr tar cvf /home/ports.tar ports Unroll it in /home cd /home tar xvf ports.tar mv ports usr.ports (I like to use this naming convention you can name this as you please) Make the symlink cd /usr mv ports ports.orig (little safety, don't nuke it until checking) ln -s /home/usr.ports ports Check it all out by CDing to /usr/ports and looking at stuff. It should now put you in to /home/usr.ports/ when you do cd /usr/ports Clean up cd /usr rm -r ports.orig cd /home rm ports.tar Do the same (except for names) for /usr/local and possibly /usr/share if gets large and even /usr/src if you feel the need. Some of these steps can be combined, but this strung out procedure makes me feel more secure than piping tar to tar and such. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Scripts
Hello FreeBSD people. Perhaps this is the wrong place to ask such an elemental question... I'm trying to feed a text file into a script. Script is suppose to take relevant parts and output them to a new file... Script is marked executable... less textfile | script.pl script.pl: Command not found. What gives?? Sounds like you don't have . in your path or haven't rehashed since you created the file 'script.pl'. Try doing ./script.pl textfile. If that works, then try doing a rehash. I don't know which shell you are using, but with tcsh/csh just type rehash and a CR/ENTER at a prompt. When you first start the shell, it makes a hash list of all the files in your path.That is where it searches for executables each time you type in somthing at the prompt that does not begin with either . or / Typing the rehash shell command, causes it to update its hash list. Note, just using the '' redirect command is enough to pipe the file to STDIN. You don't need any other command such as 'less'. jerry TIA Eric ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Scripts
Firstly, the abuse of 'cat' as I suggested is quite wonky, indeed. I still sometimes do it like that though, for no reason other than typing quicker than I think at times. Sounds like you don't have . in your path or haven't rehashed since you created the file 'script.pl'. I just wanted to say quickly that I'd recommend *not* ever taking '.' into your path - when someone wants you to execute something and places it into a directory where both have write rights and names it like the binary you're supposed to call, it's going to get executed first. I would agree that there are good reasons to not put '.' in your path. It was relevant to the question, but I should have added the warning about that comment.Doing ./script.pl textfile is the solution. Also didn't mention that script.pl needs to have the proper line at the start. Probably#!/usr/bin/perlor wherever the questinoer has perl installed presuming from the file name that it is a perl script. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Video card compatibility
Hello Support ! I bought FreeBSD 5.1 and Handbook for my 10 year old computer nut son for Christmas and have had problems installing the full graphical version. Good choice. Get him started right. When asked for video card on installation, I don't' know what to select. I have on-board video on the motherboard at this site. http://www.albatron.com.tw/english/it/mb/specification.asp?pro_id=35 I also have an old monitor but I don't think that's the problem. Will I need to buy a separate video card and if so would you have any suggestions? I hope someone who knows more than I about this subject also responds. But, to figure out what to put for video card and driver, etc I use three sources and I usually have to pore over all of them and combine the information. I try to get as much information from the vendor/manufacturer as possible. Usually their web pages have something useful. I dig through the dmesg output until I think I have figured out which lines refer to the video stuff. I go to the Xfree86 support web site and go through their lists. That is probably the most complete source because it is really XFree86 that is talking to your video card anyway. The Xfree86 page is: http://www.xfree86.org/support.html Then do some serious digging. jerry Thank you very much for your help!! Brad Fligor 508-627-4862 ___ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk Quota Question
I've followed the manual on FreeBsd 5.1. Recompiled the kernel with quota options. It is on the /usr file system. everything appears to be running correctly. I've made entries to fstab by the manual also. mail# cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1e /tmpufs rw 2 2 /dev/da0s1f /usrufs rw 2 2 /dev/da0s1d /varufs rw 2 2 /dev/cd0/cdrom cd9660 ro,noauto 0 0 /dev/da0s1f /usrufs rw,userquota,groupquota 1 2 But when I quota -u USERID I get mail# quota -u USERID Disk quotas for user USERID (uid 1001): none Well, what did you set quotas for [USERID] at? I don't see that in your narrative. jerry Either I'm missing something or something isn't working. Where do I look next. Sincerely, Joel Eddy Iowa Connect, Inc. http://www.iowaconnect.com Ph. 641-456-5964 Fax 641-456-5912 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: information installation freeBSD
Bonjour, je vien d'apprendre que linux à un OS 64bit -- freeBSD 64. Je n'ai jamais utilisé linux aupartavant et j'aimerai bien savoir comment pourrais je le télécharger et l'installé sur mon AMD 64. Je vous remercie d'avance. -- --- Hello, I learn that linux have a OS 64bit -- freeBSD 64. I never used linux and I will like to know how could I download it and installed on my AMD 64. Well, you are asking this on a FreeBSD mail list. FreeBSD is NOT Linux. (It is better :-) ) You can download and install FreeBSD quite easily. Start at the FreeBSD web page http://www.freebsd.org/ find and read the handbook installation instructions on that site. It explains things in detail. Basically, there are two ways. One is to download a boot/install image either for CD or floppy if you don't have CD. Use it to boot the machine and install over the net from one of the FreeBSD sites. The other way is to buy a set of installation CDs from one of several places that package a FreeBSD installation. www.freebsdmall.com is one of them, and there are others. You can create a system with both FreeBSD and Linux (and MS-Win as well) called creating a dual boot system if you want. There is information in the handbook about doing that. Also, I would guess there might be a French version of the documentation as well as download mirrors in France if that is helpful. jerry I thank you in advance. _ Spécial Saint-Valentin [1]Cliquez-ici References 1. http://g.msn.com/8HMBFRBE/2731??PS= ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New
Want to give it a try! OK. Good idea. Very experienced with all versions of windows, have been building computers for 15 years.. Sick of the windows restrictions. What am I in for?? Some learning work and then some good times with a actual working system. Have tried many versions of Linux.There are too many anymore. Where is a good place to start? What's a good read to get up 2 speed??? Start with reading pretty much everything on the FreeBSD web site. http://www.freebsd.org/ especially the handbook and FAQs. There are several good books out. I get along quite well with FreeBSD Unleashed by Michael Urban and Brian Tiemann Someone has walked off with my copy of the Complete FreeBSD which is also good.But, the FreeBSD Handbook is most authoritative and is online at the FreeBSD site and also available in print at various places. Of course, man pages are essential reading for various things. But, you knew that. jerry [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] (work) I have time to read [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] (home) I have time too play with new operating systems thanks pjr ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root is full
List, My root partition is full, but I cannot figure out how it got filled so fast the last security check claimed there to be 5% of capacity and now its at 108%. Where else can I check to see what is filling the root partition? Run du -sk * at the base of the file system (root in this case) where the problem is. Then cd in to suspicious directories - those that look excessively big and run du again Keep following bloated directories until you find your problem. I would guess you have logs (var/log) and mail (/var/mail) still in root and maybe even /tmp but who knows until you track it down a little better. You may need to either revise your disk layout or at least move some thing to a bigger partition and make symlinks. jerry Thanks in advance --will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk Quota Question
You've got /dev/da0s1f listed twice. I'm not sure what mount does in that case, but it's probably worth fixing. It probably takes the first one and ignores the second one. Sorry I missed that before. jerry On Tuesday 17 February 2004 15:10, Joel Eddy wrote: I've followed the manual on FreeBsd 5.1. Recompiled the kernel with quota options. It is on the /usr file system. everything appears to be running correctly. I've made entries to fstab by the manual also. mail# cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass# /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1e /tmpufs rw 2 2 /dev/da0s1f /usrufs rw 2 2 /dev/da0s1d /varufs rw 2 2 /dev/cd0/cdrom cd9660 ro,noauto 0 0 /dev/da0s1f /usrufs rw,userquota,groupquota 1 2 But when I quota -u USERID I get mail# quota -u USERID Disk quotas for user USERID (uid 1001): none Either I'm missing something or something isn't working. Where do I look next. Sincerely, Joel Eddy Iowa Connect, Inc. http://www.iowaconnect.com Ph. 641-456-5964 Fax 641-456-5912 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- [EMAIL PROTECTED] it was a hard sell, since he's a database person, and as far as I've seen, once those database worms eat into your brain, it's hard to ever get anything practical done again. To a database person, every nail looks like a thumb. Or something like that. - jwz ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.2 OpenOffice 1.1
[EMAIL PROTECTED] wrote: Error message trying to open soffice.cfg file??? Tom Karnes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] 3 possibilities come to mind: 1. Location. 2. Permissions. 3. Existence. Perhaps %find -name soffice.cfg -ls will get you started on the case HTH, Kevin Kinsey DaleCo, S.P. PS I don't use OO, and have no idea about the error. A quick Google search reveals that it may be a folder and need to be created Yes. I don't have the system with openoffice handy at the moment so I can't tell you the whole path, but just go to where you have OO installed .../conf I think and do: 'touch soffice.cfg' Later, if you find some things you want in it, you can add it, but for starters, empty is good enough. There is also another file like that too (eg non-existant) that needs to be created but empty is enough. I don't remember the name right now. It would help if their web page had some separate getting started documentation. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9-RELEASE + XP Pro problem
Hello All, I'm having a hell of a time getting XP Pro and 4.9 on the same drive. I've tried various ways to get them to co-exist to no avail. Here's what I'm trying to accomplish; 30 GB HD total First 24 GB = XP Last 6 GB = 4.9 Installed XP first, then 4.9, said NONE at the boot menu during install. There is your problem right there. You should have selected the full MBR. Then everything would have fallen in place with none of that other fixboot stuff at all. Just make sure your XP is fully installed first and boots OK Then install FreeBSD and select the MBR (not 'none' and not 'standard') After that, when you boot, it will come up and prompt something like: F1 = Dos F2 = FreeBSD Hit the appropriate function key and it boots. Skip pressing a key and it boots to the system it was most previously in. If you have more than just XP and FreeBSD, such as the machine I am currently typing on has a Dell Maintenance slice, then the function key selection will look a little different, but essentially the same. If your XP is using an NTFS file system the prompt might be ??? as in F1 = ??? (Dell Maintenance) F2 = ??? (XP NTFS slice) F3 = FreeBSD (Obviously, FreeBSD) That can be a little annoying, but can be lived with. If you can't live with it, once you get things all done, you can install a more elaborate boot loader that will allow you to fix up the labels, such as grub. This all works just fine if you just do the right thing and don't try to outguess it. Went to reboot and bsd had taken over either the boot sector or the mbr. Tried xp recovery console, fixmbr, fixboot, nothing worked, bsd continues to boot up by default. Yes, because you did not install the MBR at install time. So, the none effectively only knows how to boot FreeBSD. jerry What I want is to have the nt boot loader give the choice to boot into bsd by using the boot1 - bootsect.bsd method in boot.ini. What I'm I doing wrong here? Thanks, Joel ___ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: power point
hi, is there a way to convert ms powerpoint presentation into jpegs? or to view it under Freebsd? Install Openoffice. It has a presenter that can open Powerpoint files to show them or incorporate them in to presentations. You might have to tinker around to get things like you are used to, but it should work. You might prefer installing Openoffice as a precompiled package because it is very large and takes a long time and a lot of resources to build from ports. Go to: http://projects.imp.ch/openoffice/ They have a package for FreeBSD download it to /usr/local and run pkg-add on the .tgz file. Then run /usr/local/OpenOffice.org1.1.0/program/soffice Unfortunately, the instructions incorrectly says to run openoffice instead of soffice to get the setup going. Also, the install allows you to replace the installation path. I suggest you leave it as /usr/local, but change that OpenOffice.org1.1.0 part to something a little more friendly. The essential callable binaries will be put in /usr/local/bin so you will need to have that in your path and do a rehash. Also, there are two files - one is soffice.cfg and I don't remember the other at the moment (and am not near my system with openoffice) that it will complain it can't find when you try to run something. Just go to the directory they are expected to be in .../openoffice/conf I think, and do touch soffice.cfg and the same to the other one. An empty file is OK. You may add config things later if you discover the need. Also, don't wory about when it complains some Java stuff isn't present so certain features won't be available. I haven't found anything that won't work because of it. Probably something obsure or cutsie. Have fun, jerry Thank you Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9-RELEASE + XP Pro problem
On Fri, 20 Feb 2004 10:13:35 -0500 (EST), Jerry McAllister [EMAIL PROTECTED] said: Hello All, I'm having a hell of a time getting XP Pro and 4.9 on the same drive. I've tried various ways to get them to co-exist to no avail. Here's what I'm trying to accomplish; 30 GB HD total First 24 GB = XP Last 6 GB = 4.9 Installed XP first, then 4.9, said NONE at the boot menu during install. There is your problem right there. You should have selected the full MBR. Then everything would have fallen in place with none of that other fixboot stuff at all. Just make sure your XP is fully installed first and boots OK Then install FreeBSD and select the MBR (not 'none' and not 'standard') [snip] Actually, you should choose to install a standard MBR and *not* to use the FreeBSD boot loader in order to accomplish what you describe below. You are wrong here. During the install you are offered three options: BootMgr Install the FreeBSD Boot Manager Standard Install a standard MBR (no boot manager) None Leave the Master Boot Record untouched You want to choose the first one to install the FreeBSD Boot Manager The standard boot record will only boot FreeBSD and nothing else. The terminology is a little confusing here, but you want the FreeBSD boot _manager_ not just the standard boot _record_ - two different sector positions on the disk. The boot _manager_ choosed which boot _record_ to start booting with. jerry What I want is to have the nt boot loader give the choice to boot into bsd by using the boot1 - bootsect.bsd method in boot.ini. Read the following FAQ carefully. If you try it and are unsuccessful, come on back here and let us know what happened. URL: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9-RELEASE + XP Pro problem
On Fri, 20 Feb 2004 10:13:35 -0500 (EST), Jerry McAllister [EMAIL PROTECTED] said: Hello All, I'm having a hell of a time getting XP Pro and 4.9 on the same drive. I've tried various ways to get them to co-exist to no avail. Here's what I'm trying to accomplish; 30 GB HD total First 24 GB = XP Last 6 GB = 4.9 Installed XP first, then 4.9, said NONE at the boot menu during install. There is your problem right there. You should have selected the full MBR. Then everything would have fallen in place with none of that other fixboot stuff at all. Just make sure your XP is fully installed first and boots OK Then install FreeBSD and select the MBR (not 'none' and not 'standard') [snip] Actually, you should choose to install a standard MBR and *not* to use the FreeBSD boot loader in order to accomplish what you describe below. Oops, I see I have perpetuated the terminology confusion by saying the full MBR. It should be the full Boot Manager. Still, it is not the standard MBR nor the None which was the point I was trying to get at. Do we need a terminology housecleaning. It is as bad as slice and partition. jerry What I want is to have the nt boot loader give the choice to boot into bsd by using the boot1 - bootsect.bsd method in boot.ini. Read the following FAQ carefully. If you try it and are unsuccessful, come on back here and let us know what happened. URL: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9-RELEASE + XP Pro problem
I'm having a hell of a time getting XP Pro and 4.9 on the same drive. I've tried various ways to get them to co-exist to no avail. Here's what I'm trying to accomplish; 30 GB HD total First 24 GB = XP Last 6 GB = 4.9 Installed XP first, then 4.9, said NONE at the boot menu during install. Went to reboot and bsd had taken over either the boot sector or the mbr. Tried xp recovery console, fixmbr, fixboot, nothing worked, bsd continues to boot up by default. What I want is to have the nt boot loader give the choice to boot into bsd by using the boot1 - bootsect.bsd method in boot.ini. What I'm I doing wrong here? I just did a dual boot setup with XP and 5.2. I chose none intentionally, installed FreeBSD, then as I was rebooting, put in my GAG disk and installed GAG as my boot loader. It found both my FreeBSD partition and my XP partitions. I set it up, and I can safely boot into either o/s fairly easily. Gag is available on sourceforge. If you want to use Gag, that's fine. It isn't necessary if you don't mind limited labeling in the Boot Manager prompts. That works fine too. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing system user
I would not delete them. A normal user, e.g., has to be member of the group staff to su to root, etc. It is group wheel they need to be in. I suppose someone might have made staff work too, but wheel is the biggie. jerry Cheers Tom On Fri, Feb 20, 2004 at 11:51:03PM +0800, meimi wrote: I have read some document about server hardening. It suggests me removing the following users: operator, games, news, uucp and following groups: operator, staff I can guess that games is used for playing and news is used for reading news in news group. How about the other? Their descriptions in passwd are not clear. Am I safe to remove them in normal server environment (web, mail, ftp, DNS, SSH)? You can certainly remove those users and groups, but it's unlikely to gain you very much and quite likely to cause you some problems. It will certainly make it harder for you to do routine updates on your system, possibly including some security patches. So long as you don't alter the entries in the master.passwd and group files for those entities, you're pretty safe. Those IDs exist mostly to be the owners of various files: note that the shell has been set to /sbin/nologin and the password for those accounts has been locked and that they have no special privileges despite the low UID and GID numbers -- as such they are rather less dangerous than the account you use to log in via. All in all, I wouldn't bother touching those accounts. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Copy old drive to new drive - is it possible?
Hi, I have a hard drive which is on its last legs. I also have new hard drive to replace the old one. I was wondering if it is possible to simply copy everything from the old drive to the new (after formating the new drive) and have my system back up and running, or do I need to reinstall the OS and everything else? Sure - if you can put the new drive in a second slot. and if nothing dynamically changing must be preserved. Probably doing it in single is enough to handle this. FDISK and disklabel the new drive as needed with Boot Manager/MBR and boot blocks included as needed. mount the file systems on the new drive to temporary mount points use dump piped to restore to move files from old drive to the new Swap the drives so the new one is in the boot slot reboot. Read and understand the fdisk and disklabel man pages before you get started. jerry Tips, URL's or a simple 'from personal experience, best to reinstall' comments more than welcome. Thanks for your time. -Tig ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: power point
On Fri, Feb 20, 2004 at 10:38:28AM -0500, Jerry McAllister wrote: hi, is there a way to convert ms powerpoint presentation into jpegs? or to view it under Freebsd? Install Openoffice. It has a presenter that can open Powerpoint files to show them or incorporate them in to presentations. You might have to tinker around to get things like you are used to, but it should work. It takes about 8 to 12 hours to compile it. But, only a few minutes to install as a package. Again, check out: http://projects.imp.ch.openoffice/ jerry -- Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: id like to help
hi im a freebsd user and i live in istanbul and im trying to get people to use freebsd and stuff like this. i would love to help in a part of freebsd an some kind of way. is there anything i could help with? i dont mind maybe translating a few docs to turkish and stuff like that. Good idea. Chech out the FreeBSD documentation list and th doc project information on the FreeBSD. From those you can learn how to get started. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail on FreeBSD
Hi, I was wondering if there was a web based system to check mail on a freebsd system.I wanted to setup a mail system for all users on the intranet.I have successfully installed sendmail and can send and receive mail on the system.(using pine).But how do i go about setting up a system for external lan users without them telnetting into the system?.Would i need a pop3 server? Try squirrel/usr/ports/mail/squirrelmail There are others too, but squirrel works well. jerry Thanks, akshay. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fail to recognize sound device
Dear Sirs, Thank you for Giving FreeBSD for free. Basically I would like to ask you about a problem I have with the sound hardware which I wasn't able to resolve. And I also have some suggestions to make! After Installation when writing #startx, at the prompt KDE loads and I get a message than sound driver /dev/pcm couldn't be found. SuSE and Redhat both recognize my sound driver as 82801DB AC'97. Further more alot of stuff like xmms, and other applications were not installed although I checked them to be installed when I was asked. The funny thing is that those applications exist in /usr/.../ports. 1:How can I configure my sound device? Probably you still need to make a kernel config file and adddevice pcm to it and build a new kernel. Make a copy of /usr/src/sys/i386/conf/GENERIC in the same directory example NEWCONFFILE . Check in LINT in that same directory for syntax. Add the device pcm line (minus initial '#' if any Build kernel either by the old way config NEWCONFFILE cd ../../compile make depend make make install You might want to make a copy of the current kernel file before doing the make install, just in case. It lives in either /kernel or /boot/kernel depending on which version of FreeBSD you are using. Suggestions: 1: It would be really attractive if the installation of FreeBSD was as easy and comfortable(visual stuff) as SuSE's. 2: It would be nice if kdm or xdm or something was installed and needen't have to be configured after installation. For instance during the installation the user should be asked if he would like to have xdm or kdm installed ... But, probably 1/2 to 2/3 of those running FreeBSD servers don't want those things. So, ???FreeBSD is heavily used as a server OS - probably more so than as a desktop.Servers, some of which run without even a monitor hooked up, do not need nice looking desktop stuff. So, since it is is so easy to add if you want, it is better to start with just what everyone needs and then let everyone add the other stuff themselves. jerry Thanks in advance! Looking forward to your answer! Drosos. _ http://www.mailbox.gr ÁðïêôÞóôå äùñåÜí ôï ìïíáäéêü óáò e-mail. http://www.thesuperweb.gr Website ìå ÁóöáëÝò Controlpanel áðü 6 Euro êáé äþñï ôï domain óáò! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: backup
We're currently doing a back up of a FreeBSD 4.9 (2) server by plugging a USB external drive in and then doing cp /dev/ad0 /dev/da0 This takes about 30 hours, (USB 1). Is this the best way to do it, or can someone suggest a better way. We'd rather not have the server offline while we do it. I would suggest using dump (and restore if you need something recovered) if you can because cp may not preserve everything appropriately. or dump | restore if you are trying to build the file system on to the other disk. I wonder also about your choice of devices, but I don't know how you created them or mounted them. Actually, I would use their mount names rather than devices anyway. Or am I missing something here? Using dump[/restore] won't speed anything up, but it would make sure it is usable later. jerry Cheers, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: backup
You would need to use piping to restore the backup, though and that can get tricky if your new system that you need to restore the data to isn't sized the same as the old and isn't using the same version of dump. Woha, timeout. Are you saying 'dump' produces files in a format *not* guaranteed to work with 'restore' on another system if it is not running the exact same version of FreeBSD? Or having the same file system size? I had always assumed - given that it's a backup tool - that the format of the dump was portable. Generally, dump files are portable within the same OS but different versions. eg a dump in FreeBSd 3.xx can be restore in FreeBSD 4.xx, etc. But, unfortunately dump files are often not portable between OSen, especially vendor supported proprietary versions of UNIX. It is also possible that it might not be portable between OS versions, but mostly it hasn't been changing as much lately so that isn't so much a problem as it was a few years ago. dump puts a magic number in the dump file header and restore will refuse to work on files that have the wrong magic number. The magic number is only supposed to change if a new version of dump now generates a file that is incompatible with previous versions, but I don't know how precise developers have been with adhering to this imperative. Especially between vendors, they may have changed the magic number just because it is a different vendor and not because the file format is any different. But, I don't think you will find that happening within FreeBSD. The issue of not being able to restore a dump if it was piped from one system to another comes up if the two systems are different - namely different vendors. If you dump a FreeBSD file system and pipe it to a SUN OS system for writing to media, for example, then a SUN OS version of restore may well not be able to read that dump. You would need to pipe it to a restore running on a FreeBSD system. That works OK for full restores, but can be rather nasty for restoring just a few files or doing an interactive restore. But, if you pipe a dump of a FreeBSD file system to another FreeBSD system for writing. Then restore on that other FreeBSD system will almost assuredly be able to read the dump. You might want to experiment a little to be clear on procedures if you plan to do this. So, all this may sound iffy, but really, if you use dump in FreeBSD to back up a file system, (and if the media stays good, of course) you should have no problem restoring from that dump. And, really, for most cases of making a backup against disk failures (and fat finger or caffeine haze failures) that would be used to recover files on the same system, dump is generally the best choice. It maintains the information in a manner that can be restored to a full working version of the filesystem with all file information kept intact. The other methods do not guarantee that in all cases. dump's main weakness is that it works on a filesystem rather than some subset such as a few files or a specific directory tree. So, if you want to make a backup of just one or two directory trees within a filesystem, then probably tar is your best bet. Also, if you want to make something that is more guaranteed to be portable across OS boundaries, then tar is a good choice. Otherwise, use dump. jerry -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller [EMAIL PROTECTED]' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE startup slowly on initializing system service
Hi Andrew, 5.2 == The network changes might not releated to the issues w/ KDE. I would first verify that no other program is trashing your resources. I suspect whether 'vi editor' having problem because each time when I boot the PC, the screen pauses on;- What has happened in this case is that you [or someone has] have left some vi session[s] open when either a connection was ended or the system was taken down. It tries to recover those edit sessions and let the id that was editing know via an Email message where to get the information back. jerry ... Recovering vi editor sessions: another is;- Starting sshd: taking prolonged time before continue to run. What is the esay/quick way to remove 'vi' from FreeBSD. I don't need it. I use 'ee' Then check to make sure you have a newer version of KDE. Did you look at the KDE site for known bugs, maybe? KDE 3.1 is quite new and stable. I have it running on Gentoo, Debian and RH PCs respectively without problem but I will check KDE site later. What I am worrying is OpenOffice 1.1. Of the 3 OSs, Gentoo 1.4, Debian 3.0 and RH9 which I am running, OOo1.1 only works fine on Debian 3.0. OOo1.1 and RH9 are poor combination. It takes long time to start. You will find lot of complaints on its mailing list. I am looking forward to see how it will work on FreeBSD 5.2 B.R. Stephen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount questions
I need mount a fat32 partition in two diferent places. when i try to do it the second time the system says device busy.. What can i do? Why would you need to mount it in two different places (I presume you mean at the same time)? If you want to use it as a different file path string, then mount it one way and create a symlink to it with the other name. Or, if they don't need to both be mounted at the same time, you need to umount it from one mount in order to mount it the other way. It doesn't like two separate mounts of the same device at the same time. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error on create new slice
hi I having an error on create a new slice. well, I trying to install freebsd 5.1 on my primary(master) hard drive, which already contain 2 os which are Linux RH 9.0 and windows 2000 pro I try to create a new slice on the unused partion and the partion name should be ad0h or ad0 something but it turn out to be x this give me an error message of unable to find device node for dev/x from dev/ ... First, what were you running to do this - sysinstall, fdisk, ?? What steps did you take with them? Second, move up to FreeBSD 5.2 or 5.2.1 for your install. It is more bug free. Third, please take some time and read some documentation. If you are creating a slice, it would not (could not) be ad0h. It might be something like ad0s3 or maybe even ad0s4. If it was ad0 without the 's3' or 's4' then you would be attempting to wipe out the slices with Linux and W2K or probably more likely just doing something wrong. Finally, you may be having a problem with dynamic device creation. I haven't started pushing 5.xx beyond just minimal stuff yet. So, someone else will have to comment on that. jerry Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 4.9 Download Issue
Hello. Been trying to download 4.9 so I can put it on my other box but when downloading the iso (from any mirror) I get a error saying there isnt enough space to download 49ebcty7.exe to /tmp. Whats going on? I have the space. Here is the output from df -H Just what it says. The file is larger than the amound of space you have in your /tmp file system. Try CDing to someplace convenient in /usr and doing the download. That is where you have the most space. jerry df -H FilesystemSize Used Avail Capacity Mounted on /dev/ad4s1a 132M54M68M44%/ /dev/ad4s1f 264M 4.5M 239M 2%/tmp /dev/ad4s1g26G 4.4G19G19%/usr /dev/ad4s1e 264M63M 181M26%/var procfs4.1K 4.1K 0B 100%/proc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot and MBR.
I've got my primary drive divided in two partitions, one partition had WindowsXP and the other has FreeBSD 5.1-Release on it. I had WindowsXP installed and working until I put FreeBSD on the second partition and had it take control of the MBR. I know that the other partition is still bootable if I can get a pointer to it, currently the boot menu shows it as: F!: ?? F2: FreeBSD How can I get that first menu choice to look at the installation on the first partition as bootable? Making the machine a dual boot between the two system? The fact that it displays ?? is only a cosmetic problem. Have you tried selecting F1 to see if it will boot the XP slice? Mine does. Also, a side issue, in FreeBSD land, what you have is a disk with tw0 'slices' as apposed to partitions. Probably you have your FreeBSD slice divided up in to several 'partitions'. MS calls the primary divisions of a disk partitions, but in BSD UNIX land they are called slices. The second question I have, is can I put the command startx into my rc.conf file to have it boot directly into the x-server? Any help on these two would be awesome. Thanks. I have not been successfule with that sort of thing. Anyway, I don't think just putting it in rc.conf would do the trick because that just sets a bunch of variables in there. Then the stuff is actually run from rc (and some other places I think) using those variable values set in /etc/defaults/rc.conf and /etc/rc.conf.. I think you might not want your startx to fire off until after you log in anyway.That would mean putting it in .login (if you have a csh or tcsh shell) and that is what didn't work for me, though I didn't try many variations. But, someone else better weigh in on this. jerry Res Ipsa Loquitor, Mark-Nathaniel Weisman Site Master Mystic1.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: directories to exclude for backups
My Plan is to make a gzipped tarball of the entire machine, excluding directories that are not necessary. If however, there is a more sound solution then tarballing a machine for a backup, Im all ears. I know rsync is a possibility, but i'd like to have just a solid, non-active archive copy of machines. Unless you need to be portable across vendor OS I would be inclined to prefer dump to tar. jerry EXCLUDE DIRECTORIES -- /proc /dev /tmp /usr/ports/ /var/tmp/ What else would be safe to exclude? Thanks, -Ben -- This message has been scanned for viruses and dangerous content, and is believed to be clean. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UK Distributor???
Hi I am an Account Manager for Westwood Associates Ltd, an IT Reseller in the UK. One of my customers has asked for pricing on your products, but I do not know who your UK Distributor(s) is (are). Can you help? Probably a lot of people who install FreeBSD just download the free version from the net. There are mirrors in the UK. There are companies who package already burned CD sets and sell them at minimal cost often along with a printed handbook (the handbook is also available free online). The information for both paths can be found on the FreeBSD web site. Go to: http://www.freebsd.org/ and look for the appropriate links. jerry Best regards, Phil Burford Account Manager Westwood Associates Ltd Tel. 01858 545 888 Fax. 01858 545 154 Email. [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot and MBR.
Just out of curiosity what is the order in creating a dual boot system? Which operating system do you put on first? I see that having WinXP setup in partitions is not a good idea, yet I'm not aware of how to load the system in just a slice? I would appreciate any and all help in trying to get this thing online. I need my workstation back as soon as possible. Thanks. I am not sure which thing you are referring to when you use the word 'order' but... Install whatever MS-Win system you want to have first and make sure it boots OK. Then, use one or another utility to shrink the MS slice and make room for another - you can have up to 4 primary slices. FIPS works fine if the MS slice (called partition in MS land) is a FAT, but if it is NTFS you will need some more sophisticated utility like Partition Magic (which is not free - about $69 in Best Buy type stores) I have heard there is a newer free one now available that can handle NTFS and MS extended slices (partitions in MS speak) but I don't remember the name. Partition Magic will create a slice (which they call partition since they are mostly MS oriented) and mark it as a FAT32 - or something else if you tell it too. Then install FreeBSD. Presuming you use the CD sysinstall method, when you get to the partitioning stage it shows you the primary slices on the disk and what they currently have in them. Put the cursor on the new FAT slice that was created when you resized stuff with PM or FIPS and 'D' delete it. Then hit 'C' create and it will make that a FreeBSD slice. Then hit 'S' make it bootable (which, non-intuitively will put an 'A' in the Flags column to indicate it should be bootable. I have also, sometimes, moved the cursor up and marked the slice with the MS system in it as bootable (hit 'S' on it) but sometimes not bothered and it hasn't seemed to make a difference as long as the MS system booted OK before I got started. As soon as you get this done and hit 'Q' to save and go on, you will be presented with a screen that has three choices. BootMgrInstall the FreeBSD Boot Manager Standard Install a standard MBR (no boot manager) None Leave the Master Boot Record Untouched On this screen you want to choose the first one: BootMgr Then use the tab to make sure OK is selected and go on to the next stuff. After this you will be put in to a screen to divide up the FreeBSD slice in to partitions. Do this as needed for your installation From here on out you are past the boot stuff. You will choose what you want installed - if you have room, just grab it all, and where you want to install from - FTP or CD, etc Finish up the install and network configuration. When you boot, you will be presented with a menu something like: F1 DOS F2 FreeBSD or maybe F1 ?? F2 FreeBSD or I have on one machine F1 ?? F2 DOS F3 FreeBSD because it is a Dell machine and has a bootable Dell Slice with their maintenance stuff on it. You get a menu listing for every slice that is marked bootable regardless of what it is. It labels all MS FAT slices as 'DOS' regardless of which MS system is on it.. You get the ?? if the Boot Manager finds it bootable, but doesn't know sort of system it is - such as for NTFS. It doesn't have to know what kind of system it is to boot it so the ?? doesn't matter. It is just a cosmetic annoyance. IF it is too much for your stomach to take, then you can get a fancier Boot Manager such as GAG or GRUB and install it and you can configure those with whatever labels you want to use. Those can be installed later after the system is fully installed and you have some time to play. The basic FreeBSD boot manager is small to fit in the official one sector space that is available. The fancier boot managers generally use some additional space that, by convention is never otherwise used, but is not officially available for it. I kind of with they (whoever does this sort of official definition) would just officially redefine the standard so the whole unused cylinder was official boot mangler space. jerry Res Ipsa Loquitor, Mark-Nathaniel Weisman Site Master Mystic1.net -Original Message- From: Mark Weisman Sent: Thursday, February 26, 2004 4:59 PM To: Jerry McAllister Cc: [EMAIL PROTECTED] Subject: RE: Boot and MBR. You are right, I have them setup originally under WinXP as partitions, then added FreeBSD to the second partition where it calls it a slice. Divided up the slice into the required folders. I have tested, and it is not cosmetic, in that when I select that menu item, the computer goes to the next row and stays indefinitely. I can put WinXP back on the computer if I have to, however, wouldn't that put the WinXP MBR on the box? I've gone in under fdisk and set the slice bootable, however nothing. I'm not sure how to install it now to just that slice. Any help would be greatly appreciated. Res Ipsa Loquitor
Re: Boot and MBR. Thank YOU!
Sorry for being such a pest, my boss kept asking why my computer wasn't working, and I'm not ready to ready for him to know I've got BSD loaded. I was in panic mode because I couldn't get my Windows XP screens and applications to come up. I deeply apologize, I was finally able to read all of your message Jerry and it worked they way you said it would. All is well, I'm on my way to prove that I can get twice the stuff I need through the open source community than we can buy through Microsoft. Thanks for all the posts and help. You guys rock! Glad it is working. You can experiment later with prettier Boot Manglers, etc, but up and actually running always seems to me to be the first step. jerry Res Ipsa Loquitor, Mark-Nathaniel Weisman Site Master Mystic1.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: slice X?
I have installed FreeBSD before, but it has been a while since I've messed around with it. I am attempting to install on my secondary desktop machine which also runs Linux. ad0s1-ad0s3 are linux partitions as well as ad0s4 which is an extended partition (containing more linux partitions). When I try to create a new slice, it gives it the name 'X' which causes a problem when I try to create new partitions on that slice: Unable to create partitons on device: /dev/X I didn't see anything about this in the FAQ. Anyone have any ideas? Only 4 _primary slices_ are allowed on any disk. From your narrative above, it sounds like you already have that many used up on the disk - eg ad0s1, ad0s2, ad0s3, ad0s4. If so, the system will not allow you to create any more - an ad0s5 or beyond. Since FreeBSD must be installed in a primary slice, you will have to do something about your current disk use. You will need to add a new disk or reorganize the existing disk to consolidate its use so you can free up one slice designation. Do you really need that many separate slices dedicated to Linux? Do you have 4 different versions of Linux running on the machine? I am not a Linux user, but if you have only one version of Linux running (or 2 or 3) can't it just use one slice which is subdivided to make separate file systems - essentially the way it is done in FreeBSD?If so, then you would need only one primary slice per version of Linux and one for FreeBSD. If you really need all those primary slices for Linux, then you will need another disk in order to add FreeBSD. I haven't tried to create more than 4 primary slices on a disk so I don't know what the error messages look like. If it makes things look like it created a slice called 'x', then it is kind of poor about how it reports things. It will not have created a usable slice no matter what it appears to call things. It most properly should tell you the operation failed or is not possible. So, of course, if it didn't really create the slice, it will not be able to create partitions withing that slice. Note in this, the difference between a primary slice and a partition which subdivides a slice. Your narrative appears to use the terms consistent with the FreeBSD standard, so I am assuming you know this, but this issue seems to result in many misunderstandings. The MS world calls a partition and, unfortunately so does a few FreeBSD utillities that fail to follow the FreeBSD standard. All of which can add to the confusion. jerry Thanks, Aaron ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: run perl scrip with post form from apache
Thanks for you pointers, they helped me to move further on into different problem. I added the addhandler statement and ExecCGI There are no Limit/Limit at all The httpd-error.log has these messages now (2)No such file or directory: exec of /usr/local/www/data/sim.pl failed [client ] Premature end of script headers: /usr/local/www/data/sim.pl I haven't followed the whole thread, just seen this piece. But, whenever I have seen that error message (and it has been many times) I discovered that the blank line ending the header in the page I am trying to write back out is missing. It has to have a completely empty line - not even any white space characters on it. Sometimes it got that way because some part of my cgi code failed and sometimes it was because I just forgot to include the double newline (\n\n) in my print statement. I won't guarantee that is it, but is something to check. jerry The sim.pl file is in that directory and it was given to me as am working script. Any idea what is wrong now ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Open Office start up problem
Hi, This is probably a simple problem, but can someone please tell me what's happening here? $ ./soffice .: Can't open /usr/home/eamon/OpenOffice.org1.1.0/program/freebsd-local.sh: No such file or directory $ I got that too and noticed that, sure enough, there was no such file as freebsd-local.sh in that directory. So, I CD-d there and did a 'touch freebsd-local.sh' and it all seems happy now. Maybe I missed a step that should have put it there, and I have been negligent in pursuing OpenOffice docs, but it's working so... There was one more file that it wanted and an empty file seemed to make it happy, but I can't remember the name right now. After doing a touch on both of them, things came up and ran fine as far as I can tell. I am not a very demanding user of those kind of office packages so I may be eliminating some niceties by cheating like this that I just haven't notices. There is probably something in the docs about those files, so, if all else fails read the instructions... jerry Thanks, Eamon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSd on PowerEdge 2300?
I wanna know if it's possible to install FreeBSD 4.9 on DELL PowerEdge 2300? My install failed when the install CD search for Hard Drive, can I have help please? Sure. We have a several of 2300-s running FreeBSD and most have been upgraded to 4.9 (or reinstalled as 4.9).They have also run 3.2, 4.3 and 5.1. I presume the HD is SCSI. Is it possible that it is not seated completely back in to the slot?Is the disk in slot 0? (Actually, I think it will work in the wrong slot if there are no other disks before it, but...) The only time I have ever had trouble on a 2300 is when a disk was not seated well and locked in to the slot. You didn't post much information about what you saw, so it is hard to guess. Maybe it would help to copy any messages that appear on the screen as it attempts to boot that might relate to the SCSI controller or the HD. jerry Thanks. My email : [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Md5sum
Hi all folks, Where can I find this small program 'md5sum'. I could not find it on CD1 which is the only CD in my possession. Is that different from plain ole md5(1) ?? That comes included in the base install. It is what is used to generate the checksums in the file that goes along with the FreeBSD ISOs. jerry # locate md5sum /usr/X11R6/bin/gst-md5sum /usr/X11R6/man/man1/gst-md5sum.1.gz /usr/local/share/python2.3/Tools/scripts/md5sum.py Is it gst-md5sum similar to md5sum. From 'man gst-md5sum' it seems a program to generate sum but how to checksum. Kindly advise. TIA B.R. Stephen Liu ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to remove a non-empty directory
Hi all folks, Kindly advise where can I find the small program 'midnight commander' for FreeBSD. OR what command line shall be applied on FBSD to remove a non-empty directory together with its content I have never tried anything called midnight commander, but you might check in the ports collection. If you installed the skeleton like you should have, go to /usr/ports and start looking around. As for removing a non-empty directory: rm -r dirname I normally cd to the dir's parent (just above it) and do a couple of checks of where I am and what I am rm-ing before actually doing it, because once you hit enter it is gone. If you happen to have any files in that directory tree with flags set, especially schg, then it will not remove those, but will all the others. Then you would have to go in and run chflags noschg on those files and then go back out and run the rm -r again. It will ask you if it is OK to remove those files and act like it did, but it won't.kernel is one of those files that normally have schg set on it. see man chflags jerry TIA B.R. satimis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LINT file?
fbsd_user wrote: And you think that, that's ok? Somebody messed up big time removing all the LINT comments. That's totally unacceptable. Aren't you going to submit an problem report about that. That's just so stupid it could not have been done with official approval. There could never be any reason to justify doing that. If defeats the whole purpose of having the LINT kernel max option statement file. You have to point out these blunder by submitting an problem report. Get on the stick and do your volunteer part in keeping Freebsd what we all expect it to be. FBSD_USER, #1.) FreeBSD is a VOLUNTEER project #2.) Who made you in charge or deciding what's acceptable and not ! #3.) If you REALLY think it's unacceptable, why not submitt what comments you think should be in there. And if you are unable to understand the programming at all, then may I suggest that you SHUT THE FUCK UP!! Oh now that's a really helpful response. Anyway, my 4.9 LINT has comments. I certainly hope to see them when I get to 5.xxx. Without the comments LINT is essentially useless. Just long lists of cryptic character strings are not very helpful, even if there is a man page on every one. jerry / Flame mode off ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tar command and OpenOffice 1.1 question
Hash: SHA1 Try `man tar', then reply if you still have questions. Quintin Stephen Liu wrote: | Hi all folks, | | I have following packages download from OpenOffice site to a folder in 'user' | directory; | | /home/user/download/ | en-ooodict-GB-1.2.tgz | openoffice-1.1.0_1.tbz | | 1) Can I use following command to extract OOo1.1 tarball to a designated | directory; | | # cd /home/user/download/ | # tar jxvf openoffice-1.1.0_1.tbz -C /usr/share | | 2) Is tar command and its tags on FBSD same as Linux | | 3) Is /usr/ an ideal diretory for OOo1.1 to be extracted to | | 4) Can I use following command to extract the dictionary tarball | | # cd /home/user/download/ | # tar zxvf en-ooodict-GB-1.2.tgz -C /usr/share/OpenOffice.org1.1.0/ I am presuming you have downloaded the appropriate binary install from Openoffice. Put the file in /usr/local Do not unroll the file with tar and run psk-add on itpkg-add openoffice-1.1.0_1.tbz During the process it will ask where you want to install it and you can choose something a little shorter than .../openoffice-1.1.0_1 if you want, but since you will have all the utilities in your path and so won't have to use that long name all the time, it doesn't really matter. Best to leave the base path as /usr/local though. Wherever you have put /usr/local and symlinked it if you have, is OK. jerry | | Remark: 'OpenOffice.org1.1.0' is a new folder generated during extracting OOo | 1.1 tarball. | | Kindly advise. TIA | | B.R. | Stephen Liu | | ___ | [EMAIL PROTECTED] mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-questions | To unsubscribe, send any mail to [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFARDM+kt6kXuDr+LcRAuozAJ9snLzPNqMci6nb/Pwvl3aT9fpJNgCg0O7j BMSW88mGaz8zHklPq5KhNnE= =PvbJ -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tar command and OpenOffice 1.1 question
On Tuesday 02 March 2004 13:01, ÀîÓî wrote: Hi Stephen Liu, The simple way is to use PORT to install OpenOffice. For most things the simplest way if to install from ports, because most things are relatively small and the build easy and the author makes a version for whatever system the author uses (not necessarily FreeBSD) so the port maintainer creates a build that will do it for FreeBSD and you have to use that build process. But in the case of openoffice, the simplest way is to download the binary package from http://projects.imp.ch/openoffice, plunk it in to an appropriate directory (/usr/local) and run pkg-add on it. This is because the build for openoffice is so large (4 GB) and long (many hours) and the openoffice people kindly build FreeBSD versions for you all ready to plug in and use in just a few minutes. The only caveats are that one of the isntructions are wrong. You have to start up the setup by running .../base_path/soffice instead of .../base_path/openofficeand there are a couple of config/script files missing that you probably are expected to eventually fill with local config and startup settings, but which can just be empty until you get clear about what you want to configure.One of those is .../openofficexxx/program/freebsd-local.sh but I don't remember the other at the moment. It will complain and refuse to start and name the missing file. You can just go to the directory and do a 'touch(1)' on those files to create empty ones and it will then start up fine. jerry Hi, Tks for your advice. I am aware of make install 'packagename'' on /usr/ports/. Because I am running FreeBSD 5.2 on a slow PC I tried avoiding installing OOo from source code. It will take lengthy time to go through compile, make, make install, etc. I have experience on Gentoo running installation from source code. On a slow PC it would be much earier to install OOo1.1 from its tarball. For the small program 'midnight commander', it took 30 minutes to complete being an example This is my 1st time installing/running UNIX. I don't have much confidence on myself even though this is not my first time installing OOo from tarball nor my first time using tar command. I have no idea whether there are diference opertaing them between UNIX and Linux. Therefore I start to post. Anyway thanks again for your advice. B.R. Stephen Hi all folks, I have following packages download from OpenOffice site to a folder in 'user' directory; /home/user/download/ en-ooodict-GB-1.2.tgz openoffice-1.1.0_1.tbz 1) Can I use following command to extract OOo1.1 tarball to a designated directory; # cd /home/user/download/ # tar jxvf openoffice-1.1.0_1.tbz -C /usr/share 2) Is tar command and its tags on FBSD same as Linux Yes, they are the same. 3) Is /usr/ an ideal diretory for OOo1.1 to be extracted to It depends on your partition. 4) Can I use following command to extract the dictionary tarball # cd /home/user/download/ # tar zxvf en-ooodict-GB-1.2.tgz -C /usr/share/OpenOffice.org1.1.0/ Remark: 'OpenOffice.org1.1.0' is a new folder generated during extracting OOo 1.1 tarball. you must mannually create the directory. Kindly advise. TIA B.R. Stephen Liu ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] = = = = = = = = = = = = = = = = = = = = Ö Àñ£¡ ÀîÓî Yu Li Library, Chinese Academy of Sciences 33 Beisihuan Xilu, Beijing 100080 Tel: +86-010-82626611-6619 010-82629002 Fax: 010-82626611-6619 E-mail: [EMAIL PROTECTED] ÀîÓî [EMAIL PROTECTED] 2004-03-02 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tar command and OpenOffice 1.1 question
Hi Jerry,
Tks for your advice.
- snip -
I am presuming you have downloaded the appropriate binary install
from Openoffice.
Put the file in /usr/local
Do not unroll the file with tar
and run psk-add on itpkg-add openoffice-1.1.0_1.tbz
During the process it will ask where you want to install it and you
can choose something a little shorter than .../openoffice-1.1.0_1
if you want, but since you will have all the utilities in your path
and so won't have to use that long name all the time, it doesn't
really matter. Best to leave the base path as /usr/local though.
Wherever you have put /usr/local and symlinked it if you have, is OK.
Yes I have 2 tarballs downloaded to
/home/user/Download/OpenOffice-1.1/
en-ooodict-GB-1.2.tgz
openoffice-1.1.0_1.tbz
OK. I think the .tbz one is for 5.xx FreeBSD. For 4.9 there is
an OpenOffice.tgz. I didn't do the dictionary one so don't
know much about that one.
Whether your suggested to run
# cd /home/user/Download/OpenOffice-1.1/
# pkg-add openoffice-1.1.0_1.tbz
(or pkg_add ???)
Give the path to '/usr/local/'. Will it create the directory
'openoffice-1.1.0_1' under 'usr/local', i.e.
/usr/local/openoffice-1.1.0_1
Suggest:
cd /home/user/Download
cp openoffice-1.1.0_1 /usr/local/.
cd /usr/local
pkg_add openoffice-1.1.0_1.tbz
replace instances of {BASE} with /usr/local if needed
/usr/local/OpenOffice-1.1.0_1/program/soffice to set up
later runs of soffice will start openoffice running.
(presuming you are running 5.xxx) suggest moving the openofficexxx.tbz
to /usr/local/ and running pkg-add on it.
The pkg-add command would be as above: pkg-add openoffice-1.1.0_1.tbz
It will create the openoffice-1.1.0_1 directory. It does it in the
directory you are in when you run pkg_add, I think. Since I followed
the recommendation and put it in /usr/local and CD-ed there and ran it,
I don't know just how it will do it if run from somewhere else. But,
however, that is where you want it to end up. I also shortened the
install dir name to .../openoffice1 when it asked but that shouldn't
make any difference.
Also, by the way, you want to put the path to .../openoffice/program
in your regular path statement in .login or wherever works best for
you and your chosen shell.
and then to run 'setup' from there afterwards.
How about the dictionary 'en-ooodict-GB-1.2.tgz'
I didn't use that so I don't know.The install would
be the same. Put it in /usr/local/ and run pkg-add on it.
Beyond that I don't know.Alternately it might go in the
.../OpenOffice1.1.0_1/ directory and then run pkg_add.
jerry
B.R.
Stephen
| Remark: 'OpenOffice.org1.1.0' is a new folder generated during
extracting OOo
| 1.1 tarball.
|
| Kindly advise. TIA
|
| B.R.
| Stephen Liu
|
| ___
| [EMAIL PROTECTED] mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-questions
| To unsubscribe, send any mail to
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFARDM+kt6kXuDr+LcRAuozAJ9snLzPNqMci6nb/Pwvl3aT9fpJNgCg0O7j
BMSW88mGaz8zHklPq5KhNnE=
=PvbJ
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LINT file?
Anyway, my 4.9 LINT has comments. I certainly hope to see them when I get to 5.xxx. You will see them, as Kris noted already, in NOTES. If you want to see them in LINT, do something like $ cd /usr/src/sys cat conf/NOTES i386/conf/NOTES i386/conf/LINT :) ... I feel like that this separation of a file needed for developers (LINT) and file readable by others (NOTES) nevertheless has some sense. For example, one doesn't have to make sure that NOTES is in any way compilable, it's `lines that can be cut/pasted into kernel' config file. That way, one may be able to enumerate more options, even they are mutually exclsive. That's just one reason that came to my mind. The reason for splitting notes into conf/NOTES and arch/conf/NOTES seems more obvious: common devices go into the former, specific - into the latter. Well if they are all there and well kept up, it could be OK. I hope near the top of the LINT file there will be a comment referring us to that NOTES file then. It will be helpful to keep down the high blood preassure of those of us in a panic. jerry HTH. -- DoubleF Jesus Saves, Moses Invests, But only Buddha pays Dividends. --Signature=_Tue__2_Mar_2004_18_58_01_+0300_DnChs3If.e7IrC0r Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFARK8dwo7hT/9lVdwRAiRrAJwLQbjc4M3CYynFLcjrpjDJKayJxwCfSC5c pKXb1XITI9bQs+cg/Psk5R4= =YaPD -END PGP SIGNATURE- --Signature=_Tue__2_Mar_2004_18_58_01_+0300_DnChs3If.e7IrC0r-- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I test for NO tcp flags being set, in ipfilter?
See subject. :) A note: That is impolite and unhelpful. You should put your information including the auestion in the body of the message. Without that, the question does not show up in the edit file for a response unless the person responding qoes way out of their way to grab it. Since you are asking volunteers for free help, I would think you woul d want to make it as easy for them as possible for them to respond. Geez, now I have forgotten what the question was. Oh well. jerry -ste ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: production box: 4.9, 5.1, 5.2+ ???
I hesitate to ask this because it sounds stupid. I went down to the tech book store and bought freeBSD on CD's. it happened to be 5.1. I, a neophyte, assumed it was kosher. I bought it and installed it on 2 machines and pretty much ok so far. Now I've been reading about the STABLE and CURRENT branches and cvsup and all other kinds of keeping up. Unfortunately, by the time a book with CD gets published and all the way through the distribution chain to a bookstore, the next version is likely to be nearly out or already out. The CD is good for getting started learning about FreeBSD, but is probably old enough that you wouldn't want to use that version for a production server. So, you can install it and use cvsup to upgrade everything to the latest - probably a good learning exercise anyway. Or, you can play around with it enough to become familiar and then download the latest mini-ISO and start over from scratch - also a good learning exercise. What I want is production boxs with of course bug fix and security upgrades, but not needing always the latest app releases. If you are running production servers, the general word is that you might still want to stick with 4.xx and 4.9 is the latest release of the 4.xx branch. The 5.xx branch was begun to allow work on some significant and non-compatible changes to the system. (not everything is non-compatible, but some things are) Major development work is being done on the 5.xx branch, but the 4.xx branch continues to be upgraded, mostly now with bug and security fixes, but occasionaly with improved features. This will continue until the 5.xx branch is deemed solid and bullet proof as far as they can tell and that the new features are complete and everything works together. Then regular development on the 4.x branch will be discontinued. _Only_ security fixes and _major_ bug fixes will be applied to the 4.xx branch. Development of features, bug fixes and security fixes will then continue on the 5.xx branch, but not major non-compatible feature changes. It will be considered stable and a new branch - 6.xx will sprout which is just the latest (at that time) 5.xx reopened for major changes and renamed a 6.xx branch. After that time there will (may) be feature additions to 5.xx, as now with 4.xx, but those are expected to not introduce non-compatible changes. Of course, bug fixes and security fixes will continue to be applied as they will to all branches that are still being supported. The 4.xx branch would be supported for a while in that manner, along with 5.xx. In a year or two, 4.xx would no longer be supported and no longer get any fixes although you might be able to still apply some fixes with a little tinkering. There are some comments on possible 5.xx flaws in the EMail lists. Search the archives. The FreeBSD web site Release notes etc have notes on what new features are available in 5.xx. The long and short of it is that which one you install right at this moment should be either 4.9 or 5.2.1 (whether you get there from scratch or cvsupping) and the choice depends on 1: is your production environment critical such that an unexpected flaw in the new 5.xx branch would severly hurt you. 2: Do you really need some feature in 5.2 that is unavailable in 4.xx. If it is yes to 1 and no to 2, then install 4.9. If it is no to 1 and no to 2, then it is a coin flip. Maybe 5.2.1 just to get in to the future or 4.9 for ease in installation and configuration. If it is no to 1 and yes to 2, then install 5.2.1 jerry I've tried to grok the release engineering and all but I don't get it. I'm going to put freeBSD on 2 other machines as well, but don't know whether to install 4.9, use my 5.1 CD's (and then presumably have to go to 5.2 + ??? to keep up?), 5.2 or what. Not to mention the 2 already installed. I want to keep all 4 machines pretty much in synch. thanks for any clarification i can get on: 1. which is best production version 2. what is best essential upkeep mechanism (not so much for apps but for bug fixes in OS and security fixes/patches on essential stuff like OpenSsh) thanks much... lee ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: production box: 4.9, 5.1, 5.2+ ???
thanks Jerry for this detailed reply. i really appreciate it. from what you have said i think 4.9 might be indicated. but i have one more question. device drivers. i have kind of bleeding edge sound and ethernet cards. in fact i've already had to put in an older NIC to get 5.1 to work as-is. i haven't tackled the on-motherboard sound card problem yet. but i know freeBSD drivers are kind of behind (compared to windoz) so would it be harder to get a bleeding driver for 4.9 than 5.2.1? Well, actually, FreeBSD is mostly up-to-date on drivers. But, there are some that are available only in 5.xx. That is one of those things that would be a feature only in 5.xx - my number 2 question in my discussion. There are supported hardware lists on the FreeBSD web site. If you look at the main home page http://www.freebsd.org/ you will see over on the right two releases listed. Under each there is a link for Hardware Notes. Check those. When it comes to video cards and mouse, you need to check the XFree86 web site for those compatibilities. That is: http://www.xfree86.org/ jerry tks. lee Jerry McAllister wrote: I hesitate to ask this because it sounds stupid. I went down to the tech book store and bought freeBSD on CD's. it happened to be 5.1. I, a neophyte, assumed it was kosher. I bought it and installed it on 2 machines and pretty much ok so far. Now I've been reading about the STABLE and CURRENT branches and cvsup and all other kinds of keeping up. Unfortunately, by the time a book with CD gets published and all the way through the distribution chain to a bookstore, the next version is likely to be nearly out or already out. The CD is good for getting started learning about FreeBSD, but is probably old enough that you wouldn't want to use that version for a production server. So, you can install it and use cvsup to upgrade everything to the latest - probably a good learning exercise anyway. Or, you can play around with it enough to become familiar and then download the latest mini-ISO and start over from scratch - also a good learning exercise. What I want is production boxs with of course bug fix and security upgrades, but not needing always the latest app releases. If you are running production servers, the general word is that you might still want to stick with 4.xx and 4.9 is the latest release of the 4.xx branch. The 5.xx branch was begun to allow work on some significant and non-compatible changes to the system. (not everything is non-compatible, but some things are) Major development work is being done on the 5.xx branch, but the 4.xx branch continues to be upgraded, mostly now with bug and security fixes, but occasionaly with improved features. This will continue until the 5.xx branch is deemed solid and bullet proof as far as they can tell and that the new features are complete and everything works together. Then regular development on the 4.x branch will be discontinued. _Only_ security fixes and _major_ bug fixes will be applied to the 4.xx branch. Development of features, bug fixes and security fixes will then continue on the 5.xx branch, but not major non-compatible feature changes. It will be considered stable and a new branch - 6.xx will sprout which is just the latest (at that time) 5.xx reopened for major changes and renamed a 6.xx branch. After that time there will (may) be feature additions to 5.xx, as now with 4.xx, but those are expected to not introduce non-compatible changes. Of course, bug fixes and security fixes will continue to be applied as they will to all branches that are still being supported. The 4.xx branch would be supported for a while in that manner, along with 5.xx. In a year or two, 4.xx would no longer be supported and no longer get any fixes although you might be able to still apply some fixes with a little tinkering. There are some comments on possible 5.xx flaws in the EMail lists. Search the archives. The FreeBSD web site Release notes etc have notes on what new features are available in 5.xx. The long and short of it is that which one you install right at this moment should be either 4.9 or 5.2.1 (whether you get there from scratch or cvsupping) and the choice depends on 1: is your production environment critical such that an unexpected flaw in the new 5.xx branch would severly hurt you. 2: Do you really need some feature in 5.2 that is unavailable in 4.xx. If it is yes to 1 and no to 2, then install 4.9. If it is no to 1 and no to 2, then it is a coin flip. Maybe 5.2.1 just to get in to the future or 4.9 for ease in installation and configuration. If it is no to 1 and yes to 2, then install 5.2.1 jerry I've tried to grok the release engineering and all but I don't get it. I'm going to put freeBSD on 2 other machines as well, but don't know whether
Re: Tar command and OpenOffice 1.1 question
Hi Jerry,
Tks for your 2 emails and detail advice.
- snip -
/home/user/Download/OpenOffice-1.1/
en-ooodict-GB-1.2.tgz
openoffice-1.1.0_1.tbz
- snip -
Suggest:
cd /home/user/Download
cp openoffice-1.1.0_1.tbz /usr/local/.
cd /usr/local
pkg_add openoffice-1.1.0_1.tbz
replace instances of {BASE} with /usr/local if needed
/usr/local/OpenOffice-1.1.0_1/program/soffice to set up
Proceeded as follows;
# cp /home/user/Download/openoffice-1.1.0_1 /usr/local/
# cd /usr/local/
# pkg_add openoffice-1.1.0_1.tbz
pkg_add: could not find package glib-1.2.10_10 !
pkg_add: could not find package gtk-1.2.10_10 !
pkg_add: could not find package ORBit-0.5.17 !
I don't know. I was installing on FreeBSD 4.9 and using
the openoffice-1.1.0_1.tgz file.
You are apparently installing on FreeBSD 5.xx, so if you can find
it in ports, ??? I haven't tried it there.We have some 5.x
machines running here, but I am not using them, nor have we put
openoffice on them.
Anyway, if you have it running happily now, enjoy it. The rest is silence.
jerry
# cd /usr/ports/
# make search key=glib-1.2.10_10 | grep glib-1.2.10_10
# make search key=gtk-1.2.10_10 | grep gtk-1.2.10_10
# make search key=ORBit-0.5.17 | grep ORBit-0.5.17
Could not find them.
Finally I untar 'openoffice-1.1.0_1.tbz' and then ran './setup'
Now OpenOffice-1.1 is running on FBSD
But I am still interested to learn the FBSD way of installing OpenOffice-1.1.
Where can I find those dependencies?
TIA
B.R.
Stephen
later runs of soffice will start openoffice running.
(presuming you are running 5.xxx) suggest moving the openofficexxx.tbz
to /usr/local/ and running pkg-add on it.
The pkg-add command would be as above: pkg-add openoffice-1.1.0_1.tbz
It will create the openoffice-1.1.0_1 directory. It does it in the
directory you are in when you run pkg_add, I think. Since I followed
the recommendation and put it in /usr/local and CD-ed there and ran it,
I don't know just how it will do it if run from somewhere else. But,
however, that is where you want it to end up. I also shortened the
install dir name to .../openoffice1 when it asked but that shouldn't
make any difference.
Also, by the way, you want to put the path to .../openoffice/program
in your regular path statement in .login or wherever works best for
you and your chosen shell.
and then to run 'setup' from there afterwards.
How about the dictionary 'en-ooodict-GB-1.2.tgz'
I didn't use that so I don't know.The install would
be the same. Put it in /usr/local/ and run pkg-add on it.
Beyond that I don't know.Alternately it might go in the
.../OpenOffice1.1.0_1/ directory and then run pkg_add.
jerry
B.R.
Stephen
| Remark: 'OpenOffice.org1.1.0' is a new folder generated during
extracting OOo
| 1.1 tarball.
|
| Kindly advise. TIA
|
| B.R.
| Stephen Liu
|
| ___
| [EMAIL PROTECTED] mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-questions
| To unsubscribe, send any mail to
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFARDM+kt6kXuDr+LcRAuozAJ9snLzPNqMci6nb/Pwvl3aT9fpJNgCg0O7j
BMSW88mGaz8zHklPq5KhNnE=
=PvbJ
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /root file system full
Good Morning, I have recently installed FreeBSD 4.9 and have thoroughly enjoyed my first foray into the BSD world. Indeed my first foray into any non-windows OS. So far I have encountered quite a few problems but have always managed to find an answer in the handbook or by searching through the extensive resources available on the net. Great documentaion! This is the first time I have needed to ask a question. Good. My / filesystem is full. 109%. I want to know what is on the / filesystem, what I can get rid of, how to get rid of it and how to make sure that it doesn't happen again. First, use the program to check usage of a disk. Since it is / that is overfull, log in or su to root cd / du -sk * Then find out which directory trees or files are using up all the space. CD in to those directories and do the same thing until you find some things that seem unexpectedly large or unnecessary. Then you can delete unneeded things. In spite of a pretty good system, upgrades and installs can use up space and leave extra stuff lying around. Some of them clean up after themselves well and some don't do so well. As for the amount of space you need in a / filesystem, I think that the 128 MB is unrealistic. If you have just a base system and stay right on top of it all the time, you can get by with that amount. With disks being so much larget nowdays, I let myself have more, maybe double or so. But, on the machine I am on at the moment, although I have a bigger root, only 43 MB of it is used. The next thing is to figure out your whole disk partitioning scheme. Generally I make sure that /var and /usr either are separate file systems or at least that the parts of them such as /var/spool and /var/log and /usr/ports and /usr/src and /usr/local are all moved to some big space and symlinked. Without knowing more about what you have where, it isn't possible to say anything more specific. jerry Any thoughts? For background information: The / filesystem is the suggested default of 128mb. The handbook says that root is generally about 40mb of data and that 100mb should be enough to allow for future expansion needs, so 128mb should be adequate. During installation I installed everything, sources, ports, documentation, etc. I have CVSuped source to RELENG_4_9. I have CVSuped ports. I have recompiled the kernel 3 or 4 times. I have redirected the /tmp directory to /usr/tmp (these locations are from memory but you get the idea) I got a bit carried away installing ports during installation (a kid in a candy store?) and currently have about 206 installed. I have been updating ports recently using portupgrade with the recursive switches -rR. At the time the first filesystem full error message was seen I was portupgrading arts -Rr which was upgrading a lot of other ports as well. That process stopped with an error message stating that a conflict between xfmail and qt existed and that qt could not be upgraded untill xfmail was deinstalled so there may be a lot of working data still on the system. Would that be on root? Thanks for your help, Ron Joordens Melbourne, Australia ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual-boot FreeBSD 4.x/5.x
Is it possible to dual boot FreeBSD 4.9 and 5.2.1 on one system, each using a different / partition, but sharing the same /usr partition for example? I'd really like to try out some of the features of 5.x, but be able to easily go back to 4.9 if I find it too unstable. I don't think you could really share a /usr partition between the two systems. There are too many differences. Anyway, you could not install binaries for one and expect them to run in the other. jerry --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C =20 --A6N2fC+uXW/VQSAv Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFASGAu+vN6RuSjKAwRAnFPAJsFN+NEhYvV3AjC4t7zFkohUQ058wCfXZv4 QZOAD3SHkCKHf3LRgzz/JyA= =SDSf -END PGP SIGNATURE- --A6N2fC+uXW/VQSAv-- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
