Re: startx and xinit under FreeBSD8
On Fri, Dec 11, 2009 at 04:57:06PM -0500, Steven Friedrich wrote: I installed FreeBSD to another partition, so I could check it out. I selected All sources and binaries and KDE4. When I tried startx, it complained that it didn't exist. It's just a script, so I copied it over from my 7.2p5 partition. Now it complains that xinit doesn't exist. Why didn't these two get laid-down by the install?? Well, you now need to either select X during install or install it from ports after the installation. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: HP USB 2.0 Tape Drive
On Wed, Dec 09, 2009 at 03:50:04PM -0800, Doug Sampson wrote: Hi, I'm looking to buy a tape drive and am currently looking at USB 2.0 DAT tape drives from HP. I searched the hardware compatibility list and cannot locate any information tape drives except the disclaimer that SCSI tape drives do work on SCSI controller cards that are recognized by the FreeBSD OS. The only thing I can find is that apparently the ehci driver must be used if USB 2.0 interface is to be used with a tape drive. Does anyone have had positive or negative experience using these USB-based DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) StorageWorks Q1581SB DAT 160 Tape Drive. If there are other branded USB 2.0-based tape drives (i.e. Quantum) that you've used with little or no problems, I would be interested in knowing about these. I don't think you will have a problem using a USB2 interface. But, I really cannot recommend DAT. That type of system seems to have been pushed beyond its ability.The tapes fail frequently.The only thing nice about DAT is its rapid search ability. But, if you can't read what you thought you wrote, it doesn't matter how fast you can search for it. jerry ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dangerously Dedicated
On Thu, Dec 10, 2009 at 03:08:16AM +0100, Polytropon wrote: On Thu, 10 Dec 2009 02:33:17 +0100, Rolf Nielsen listrea...@lazlarlyricon.com wrote: As far as I understand it, it's called Dangerously Dedicated because it may cause other systems not to recognise the disk. Primarily, it's called dedicated (only) because it describes a setting where a whole hard disk is dedicated to the FreeBSD operating system. The addition dangerously seems to describe the danger that other operating systems cannot handle such a disk layout, or may cause problems to them - but I don't know this for sure because I'm not a multi-booter. :-) It is dangerous because other systems cannot talk to it. It is dedicated because only FreeBSD can talk to it. It is a somewhat redundant term but it sounds good and important. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dangerously Dedicated
On Thu, Dec 10, 2009 at 10:43:37AM -0500, Robert Huff wrote:
Jerry McAllister writes:
It is dedicated because only FreeBSD can talk to it.
Is this correct? What about {Net, Open, DregonFly}BSD, or
Linux?
Not Linux without some programming, but maybe some of the other BSDs.
jerry
Robert Huff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Root exploit for FreeBSD
On Thu, 10 Dec 2009 20:21:26 +0100 Julian H. Stacey j...@berklix.com replied: Fortuantely, I had no problem setting up a black FreeBSD box to preserve my sanity. A tip for those threatened with no BSD box at work: FreeBSD runs fine _inside_ a box that looks like a multi sheet scanner. OK, slow, but invisible to managers who require MS only. These scanners often lie abandoned in company junk rooms ( cheap on web), as people know they used to need MS's abandoned NT (= Not There) operating system. Well they do ... until one installs BSD. Credit to David M. who did the FreeBSD work. Pictures of hardware to look for in junk rooms: http://www.berklix.com/scanjet/ Cheers, Julian Out of pure morbid curiosity, would you please answer this question for me. You work for a corporation that specifically requires the use of a specific OS, the OS itself is not material to this question. It also forbids the use of any unauthorized OS or equipment on the companies network. You decide to ignore their directives and eventually: 1) Get caught 2) Cause a problem with the company's network, etc. Now, when you get fired and possible charged with a crime, do you: 1) Cry and bitch that they are being unfair? 2) Accept the fact that you deserved to be dismissed? Where I use to work, two or three employees were fired each year because they thought they knew more than everyone else. They failed to realize that they were being compensated to do what they were told and not what they thought they should be doing. The bottom line is if they are not smart enough to follow company directives, they are certainly not capable of instigating their own protocol. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Grandpa Charnock's Law: You never really learn to swear until you learn to drive. [I thought it was when your kids learned to drive. Ed.] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dd (to erase disk) from emergency holographic shell
On Sun, Dec 06, 2009 at 05:34:31PM +, Anton Shterenlikht wrote: I need to erase all of my fbsd disk. I booted the installation cd, launched Emergency Holographic Shell, but cannot find any command, except rm and pwd. The holograqphic shell is not the one you want. You want the Fixit. jerry I'd like to erase my disk with dd if=/dev/null of=/dev/ad0 Please advise many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount dump0 as ISO9660 filesystem?
On Fri, Dec 04, 2009 at 04:50:43PM -0800, Nerius Landys wrote: Your dump is just a regular file sitting on a hard drive with a file system that's already mounted. If you created an on-disk ISO image of that file, you'd have to mount the file system of that ISO image to read the file. If you burned the ISO image to a CD, you'd mount the CD's file system to read it. Either way, the file remains just a file, and is read using restore(8). I'll offer a guess that you're confusing things with tar(1) (which is often used for backups) and the recent changes. From the manpage: This implementation can extract from tar, pax, cpio, zip, jar, ar, and ISO 9660 cdrom images and can create tar, pax, cpio, ar, and shar archives. The above means you can now do nifty things like 'tar xvf mybackup.iso', and if you've configured a pre-processor for less(1), even niftier things like: less backup.tar.gz less backup.zip less backup.iso It's also possible you might be thinking of file system snapshots (which can be mounted). Check the Handbook for details. All I really want to do is take my dump file and see the files inside it, and do things with those files such as copy or md5sum (not edit). And I don't even know which tool do use to accomplish that. For example, if I took a dump 0 of /usr (which I did), I would like to see the file /usr/home/nlandys/.zshrc inside the dump, and then actually see (read) this file and/or copy it over scp or to another filesystem. Well, restore(8) is the utility intended for looking at and extracting files from dump files. I don't know if you can do all those things directly from a dump file using restore. You may have to restore a file to disk first and then act on that file for some of them. But some might work. I usually make a directory I call 'unroll' somewhere with lots of extra space, put stuff there and work on things from there and clean up afterwards. But, you are welcome to experiment. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount dump0 as ISO9660 filesystem?
On Thu, Dec 03, 2009 at 03:27:48PM -0800, Nerius Landys wrote: I heard somewhere that you can mount a dump as an ISO9660 filesystem, but I cannot find any Google answers on this subject. I have never heard of this. You can put a dump in an ISO, but I don't think a dump is directly mountable. I think you have to create the ISO with the normal makeiso. Then, it might be mountable. But, I could be wrong. jerry I took my dump in the following fashion: dump -0Lan -C 16 -f - /usr | gzip -2 | ssh-to-some-remote-location So, I have a file named dump0-var.gz. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: authdaemond issues / breakage after upgrade to 8.0
On Wed, 02 Dec 2009 00:38:23 -0800 Corey Chandler li...@sequestered.net replied: I recently upgraded from FreeBSD 7.2 to 8.0. This resulted in a strange error with authdaemond (part of the Courier imap package, used to authenticate users) when used in conjunction with postfix; I've rebuilt all of the packages, but the config they're using has worked since the 6.0 days. I attempt to send a message using SASL and get the following in my logs (passwords and hashes have been consistently redacted; nothing else has been altered): I believe I saw some chatter regarding SASL and FreeBSD-8.0 a while ago on the SASL forum. I know that there is a problem that Wietse Venema (Postfix) has with 8.0 and created a hack to correct. I don't believe it has anything to do with SASL though. You might want to try the cyrus-sasl2 list: http://asg.web.cmu.edu/sasl/ or the Postfix forum. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | It destroys one's nerves to be amiable every day to the same human being. Benjamin Disraeli ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE and dangerously dedicated disks
On Tue, Dec 01, 2009 at 08:34:05PM -0800, Randi Harper wrote: I'm going to just reply to all of these at once. On Tue, Dec 1, 2009 at 1:03 PM, Jerry McAllister jerr...@msu.edu wrote: On Tue, Dec 01, 2009 at 07:59:42AM -0500, Maxim Khitrov wrote: On Sat, Nov 28, 2009 at 12:28 PM, Peggy Wilkins enli...@gmail.com wrote: Due to history I won't go into, all my production (currently 7.2-RELEASE) systems are installed onto dangerously dedicated disks. What exactly do I need to do to upgrade them to 8.0? (I'm not asking for an upgrade procedure, I'm familiar with that, but rather, how this change impacts the upgrade.) I think that the suggestion that the disks need to be reformatted is extreme and I hope something less extreme will suffice. Just to point out the obvious, you shouldn't use dangerous and production in the same sentence. :) It may be a less than optimal idea, but many disks used in production have been implemented using the dangerously dedicated method. Also, just to be clear, does this statement refer to boot disks, data disks, or both? It doesn't make sense to me that dangerously dedicated could have an impact on UFS filesystems specifically. A partition table is just a partition table, regardless of what filesystems might be written on disks, yes? Am I misunderstanding something here? I don't know why it would have an affect, but they say it does. Did you see all the mailing list chatter about new installations failing due to sysinstall not being able to newfs device names that didn't exist? This is related. Also, a partition table isn't just a partition table. It's a little more complex than that. It has *nothing* to do with the filesystems inside. It has everything to do with the way that FreeBSD looks at the drive to figure out what's on it. See man pages for geom/gpart. There are others that have given a better explanation than I can provide (marcus, juli). Search the archives. Trust me, I didn't remove DD support from sysinstall just to make life more complicated for everyone. I did this because as it stands right now, it doesn't work. I take this to mean that any disk that is created without slice and partition within slice needs to be redone. Probably it can all be done in sysinstall, but you can do it with fdisk/bsdlabel/newfs. Or sade, although sade hasn't yet been updated to reflect the lack of DD support. Just don't use that option. Yah, there are other disk building utilities. It does not matter if it is a boot disk or just a data disk. It is whether or not it has a (one or more, up to 4) slice defined and within the slice[s] partitions defined which are turned in to filesystems. You can tell by the dev names in /etc/fstab. If they have the full device name /dev/da0s1a, ... da0s1h, they are NOT dangerously dedicated and you should not have to worry. If the machine is dual booted with some MS thing as the other OS, then it is very unlikely that they are dangerously dedicated. But, if they are like /dev/da0 or /dev/da0s1 (but with no 'a, b..h') then they are dangerously dedicated and you need to convert them. What? No. 's1' refers to slice 1 (or partition 1, as you're referring to it). bsdlabel is used inside this slice to create a partition for each mount point (a,b,c, etc). See http://www.freebsd.org/doc/en/articles/formatting-media/x76.html. This documentation needs to be updated, but at least it'll give you a good explanation of how it used to work. With DD mode, you're creating a label against the drive itself, not a slice within. Yes, I am probably conflating a couple of similar things. But, I have seen 'dangerously dedicated' used to describe both situations and so included both here. First you would have to back up the contents of the disk, partition by partition (mountable filesystem by mountable filesystem) however you have it. Since it is 'dangerously dedicated' it is likely you have a single filesystem per disk that needs backing up. Check out that backup to make sure it is readable. There is no going back. The backup can be done to tape or USB external disk or network or any other media that will not be affected, has room and can be written and read from the FreeBSD system. I think you're confusing running newfs against an unlabeled slice with DD mode. See above. DD mode means no slices, just a label for partitions. Not 'a single filesystem'. See above.I have seen it used both ways. I know the difference, but choose to include both possibilities. Snipping how-to on setting up a drive as it's unnecessary. She asked for a less extreme measure. The poster clearly has some idea as to what is going on and probably doesn't need her hand held in setting up a new drive. Well, in the past it has usually meant making a second response with all those details anyway, so I just
Re: 8.0-RELEASE and dangerously dedicated disks
On Wed, Dec 02, 2009 at 09:48:05AM -0800, Randi Harper wrote: On Wed, Dec 2, 2009 at 7:23 AM, Jerry McAllister jerr...@msu.edu wrote: Some of the responses have said that UFS handling of 'Dangerously dedicated' has not gone away, just sysinstall handling of it. That may be true and if that is true, then you can probably still access dangerously dedicated drives. But, I would think it is a good opportunity to convert them while the uncertainty reigns. Once again, it has nothing at all to do with UFS. Clearly you didn't search the mailing list archives like I said you should. I removed the support from sysinstall because it was *broken* due to changes with geom. It is not a sysinstall thing, it's a oh look, sysinstall lets you do something that doesn't work anymore thing. You'd think if the person that made these changes to sysinstall was commenting on the issue, that should clear up any uncertainty. But you can go ahead believing whatever makes you happy. OK. If it is a geom thing, then its a geom thing. The statement that it might be a good time to convert dangerously dedicated disks to sliced and partitioned drives is still the point of the piece you quoted and still is valid. ALthough I have made a few DD disks in the past, I do not run with them and so don't really care other than someone was asking about it. Since I do not use DD disks, I am assuming this doesn't affect me. For someone else, the best thing to do is back up their stuff, rebuild the disk with the appropriate utilities (fdisk/bsdlabel/newfs or whatever works for you) and restore their stuff. jerry -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE and dangerously dedicated disks
On Wed, Dec 02, 2009 at 10:30:10AM -0500, Bob Johnson wrote: On 11/28/09, Peggy Wilkins enli...@gmail.com wrote: Can someone elaborate on what exactly this statement in the 8.0 detailed release notes means? http://www.freebsd.org/releases/8.0R/relnotes-detailed.html#FS 2.2.5 File Systems ?dangerously dedicated? mode for the UFS file system is no longer supported. Important: Such disks will need to be reformatted to work with this release. [...snip...] It doesn't make sense to me that dangerously dedicated could have an impact on UFS filesystems specifically. A partition table is just a partition table, regardless of what filesystems might be written on disks, yes? Am I misunderstanding something here? Unless someone has changed the meaning of the term in the last few years, a dangerously dedicated disk is one that has the FreeBSD file system on it with no partition table. It is basically an artifact of the pre-Microsoft origin of BSD (there were reasons it stayed around, but they ought to be ancient history by now). Since UFS is the standard FreeBSD filesystem, DD disks contain UFS filesystems almost by definition. So, to get to the main point of your confusion (and unless I am the one that is very confused), dangerously dedicated disks do not have partition tables. That's what makes them dangerous. It confuses things that expect to find a partition table. If your partition name has an s (slice number) in it (e.g. ad2s1a) it is not dangerously dedicated. A DD disk partition would have a name like ad2a with no slice number. At least, that's the way it used to be. I quit using DD disks years ago when it became clear to me that the unintended side effects aren't worth the few bytes you save. Every once in a while a BIOS, or a utility, or something else pops up that expects to find a partition table and gets confused without it. It appears that it has happened again. Thanks for helping to clear up my confusion... I hope I helped. Good. Except that in FreeBSD land you are talking about a slice table. To carry things forward consistently, the partition table is within a slice and describes FreeBSD partitions a..h (and more now I guess). Only in MS or Lunix land should primary divisions be called partitions and then they are _primary_ partitions. But, even some of the fdisk and other documentation still mucks this up and occasionally refers to slices as partitions. Maybe we can come up with some new terminology like 'blobs' and 'dollops' to get away from the problem. jerry -- -- Bob Johnson fbsdli...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE and dangerously dedicated disks
On Tue, Dec 01, 2009 at 07:59:42AM -0500, Maxim Khitrov wrote: On Sat, Nov 28, 2009 at 12:28 PM, Peggy Wilkins enli...@gmail.com wrote: Can someone elaborate on what exactly this statement in the 8.0 detailed release notes means? http://www.freebsd.org/releases/8.0R/relnotes-detailed.html#FS 2.2.5 File Systems ???dangerously dedicated??? mode for the UFS file system is no longer supported. Important: Such disks will need to be reformatted to work with this release. Due to history I won't go into, all my production (currently 7.2-RELEASE) systems are installed onto dangerously dedicated disks. What exactly do I need to do to upgrade them to 8.0? (I'm not asking for an upgrade procedure, I'm familiar with that, but rather, how this change impacts the upgrade.) I think that the suggestion that the disks need to be reformatted is extreme and I hope something less extreme will suffice. Also, just to be clear, does this statement refer to boot disks, data disks, or both? It doesn't make sense to me that dangerously dedicated could have an impact on UFS filesystems specifically. A partition table is just a partition table, regardless of what filesystems might be written on disks, yes? Am I misunderstanding something here? I don't know why it would have an affect, but they say it does. I take this to mean that any disk that is created without slice and partition within slice needs to be redone.Probably it can all be done in sysinstall, but you can do it with fdisk/bsdlabel/newfs. It does not matter if it is a boot disk or just a data disk. It is whether or not it has a (one or more, up to 4) slice defined and within the slice[s] partitions defined which are turned in to filesystems. You can tell by the dev names in /etc/fstab. If they have the full device name /dev/da0s1a, ... da0s1h, they are NOT dangerously dedicated and you should not have to worry. If the machine is dual booted with some MS thing as the other OS, then it is very unlikely that they are dangerously dedicated. But, if they are like /dev/da0 or /dev/da0s1 (but with no 'a, b..h') then they are dangerously dedicated and you need to convert them. First you would have to back up the contents of the disk, partition by partition (mountable filesystem by mountable filesystem) however you have it. Since it is 'dangerously dedicated' it is likely you have a single filesystem per disk that needs backing up. Check out that backup to make sure it is readable. There is no going back. The backup can be done to tape or USB external disk or network or any other media that will not be affected, has room and can be written and read from the FreeBSD system. Then, boot a FreeBSD system that does not have the disk in question mounted. Probably you will need to use a 'fixit' image from the install CDs. Just for example, lets say, once your are booted, the disk to be converted shows up as /dev/ad1 and that it was all in one file system and that you want it to continue to be all in one file system. Do the following: (This makes a bootable drive and bootable partition with the standard FreeBSD MBR) (The dd-s just make sure old stuff is cleared) dd if=/dev/zero of=/dev/ad1 bs=512 count=1025 fdisk -BI ad1 dd if=/dev/zero of=/dev/ad1s1 bs=512 count=1025 bsdlabel -w -B ad1s1 bsdlabel -e ad1s1 The last bsdlabel command will bring up an edit screen. I suggest that you make at least some swap on this disk. So, you will want partition 'b' for swap and partition 'a' for everything else. Edit the partition label so it looks like: # /dev/ad0s3: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 8729532204.2BSD2048 16384 49160 b:** swap c: 898676100unused 0 0 # raw part, don't edit Those sizes are just an example. Use sizes that fit your disk. Using a * as the last size means it will use all remaining disk and the * in offset means it will calculate it properly. Of course, don't do anything to the 'c' line. Once that is done, newfs the partition to make a filesystem. newfs /dev/ad1s1a Note that fdisk and bsdlabel do not need the full path. They figure it out. But, the last I knew, newfs still does.Probably the defaults on newfs will work just fine. If you have huge numbers of tiny files you might want to adjust '-i' bytes per inode to increase number of inodes. You might also want to turn on softupdates with '-U'. jerry Thanks for helping to clear up my confusion... plw Peggy, Were you able to find an answer for this? I also have a number of servers and firewalls that use dangerously dedicated disks (boot and data). I don't see why UFS would care if it's mounted from ad1a vs. ad1s1a. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo
Re: mysql60-server??
On Wed, 25 Nov 2009 14:59:39 -0800 Gary Kline kl...@thought.org replied: I took a class in the Ingres db suite from one of the guys who wrote it. Think that Postgress is a follow-on. It strikes me as almost a *certainty* that any commerical project could be done better by the open-source community. ---If it's got your *NAME* on it, you're going to be certain it's superior, whereas if you're coding just for a paycheck, sure, you'll do a good job. But not as outstanding as an open-source suite. The determining factor is suitability to task. Once that is determined, then cost to implement comes into play. BTW, I totally disagree with your statement regarding commercial product' vs open source and quality. If that were really true then Open Office would be equal to or superior to MS Office. In actuality, it is at best equal to Office 97, and that is even stretching the point. Commercial software is written with the end-user in mind. Commercial software that does not sell will not be around very long. On the other hand, open-source software tends to be written with the developer as the focal point with the hope that others will share their point of view. Neither philosophy is inherently superior. In the final determination the end user has to determine which meets their suitability to task requirements; whether that be cost, suitability or both. BTW, I am running mysql-server-6.0.11 on one of my PCs. It handles tables for my mail system and several other sundries. It is only under a light load; however, I have never had a single problem with it. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Luke, I'm yer father, eh. Come over to the dark side, you hoser. Dave Thomas, Strange Brew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ifconfig - GUI interface available?
On Thu, 26 Nov 2009 17:11:38 +0100 Andreas Rudisch cyb.@gmx.net replied: On Thu, 26 Nov 2009 16:35:55 +0100 herbert langhans herbert.raim...@gmx.net wrote: Its merely a matter of comfort. Like on OSX or the infamous MS-thing, there is a simple window. It shows all the ssid, you click on one (maybe the password is already assigned) and you get the certain wifi net. I use the laptop in different networks, often its auto selecting the wrong one. It would be great to point and click and get the connection.. Hence the link and the keyword wpa_supplicant. Any way, here is another link: http://www.freebsd.org/cgi/man.cgi?query=wpa_supplicant.confsektion=5 Take a look at the example section. You can define multiple networks. I think it is pretty obvious that the OP is searching for a GUI to facilitate configuration of his device. I had actually thought about attempting to write one. At some future date, assuming I have the time and can assimilate all the info I need, I might attempt to do so. rant Personally, I have always felt that one of the major stumbling blocks to getting users to switch to a non-Windows based system is the degree of difficulty in configuring devices. The majority of users do not have the time or inclination to read through how-to documentation, assuming it even exists, gather scads of information, and then attempt, usually unsuccessful on the first attempt, to get a simple wireless device working when they can accomplish the same feat with little or no user intervention on a Windows machine. Even OSX greatly simplifies the installation process. Virtually every device that cannot be configured and activated by Windows comes with its own installation program. I really believe that it is fundamentally possible to accomplish the same feat in a non-Windows environment. Just my own 2¢. \rant -- Jerry ges...@yahoo.com |=== |=== |=== |=== | There are no emotional victims, only volunteers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: php4-gd
On Sat, 21 Nov 2009 13:23:39 +0100 Ruben de Groot mai...@bzerk.org replied: Like COBOL and FORTRAN are dead? Maybe not DEAD, but definitely comatose. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | A friend of mine won't get a divorce, because he hates lawyers more than he hates his wife. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2, usb mouse, uhub0: device problem (IOERROR),
On Fri, 20 Nov 2009 11:38:22 -0800 Chuck Swiger cswi...@mac.com replied: It's quite possibly to your credit that you've actually checked whether a USB mouse has been tested as compliant, but when I do a search for Mice/trackballs/pointers, I get 68 results, including a dozen or so from both Logitech and Microsoft. I also got 68 matches; however, under 'wireless' I found '0'. Either I am searching incorrectly, or nobody has a 100% compliant wireless mouse. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | So little time, so little to do. Oscar Levant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2, usb mouse, uhub0: device problem (IOERROR),
On Fri, 20 Nov 2009 12:28:39 -0800 Chuck Swiger cswi...@mac.com replied: I also got 68 matches; however, under 'wireless' I found '0'. Either I am searching incorrectly, or nobody has a 100% compliant wireless mouse. These 68 results include stuff like: http://www.usb.org/kcompliance/view/view_item?item_key=d7fe8fb052dda415dd3944736104ea858189d7e1 http://www.usb.org/kcompliance/view/view_item?item_key=1ca3f8c653307ce26ff101a9af50beb1921cbe28 ...which is a Microsoft Wireless Laser Mouse 5000 Microsoft Wireless Mouse Receiver v1.0. There seem to be wireless Logitech products there as well, like: http://www.usb.org/kcompliance/view/view_item?item_key=04bb314c07a5f1822148869b329d73a40fe82eae ...aka Cordless Desktop Receiver / C-BU44. Thanks! I guess the 'wireless' menu item is either not working, or I am using it incorrectly on that site. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Thou hast seen nothing yet. Miguel de Cervantes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dump
On Thu, Nov 19, 2009 at 04:22:12PM +0100, Bernt Hansson wrote: Hello list. I've been testing backups with dump, works well BUT -L does not work. For example dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d gives an error: no such file or directory. The .snap directory exists Is it possible that '/mnt' does not exist? jerry How does one set the nodump flag on a filesystem/directory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd partitions on a dos/fat slice?
On Sun, Nov 08, 2009 at 02:52:57AM -0700, Peter wrote:
iH,
Pulled an old disk lying around...
and started mounting partitions in it.
The weird thing is that the first slice [~15GB] is said to be fat, but I
do have freebsd partitions on it:
denver:#mount|grep ad10
/dev/ad10s1a on /maxtor500GB (ufs, NFS exported, local, soft-updates)
/dev/ad10s1d on /maxtor500GB/var (ufs, local, soft-updates)
/dev/ad10s1f on /maxtor500GB/usr (ufs, local, soft-updates)
/dev/ad10s1e on /maxtor500GB/tmp (ufs, local, soft-updates)
/dev/ad10s3d on /maxtor500GB/data (ufs, NFS exported, local, soft-updates)
/dev/ad10s2d on /maxtor500GB/data2 (ufs, local, soft-updates)
denver:#fdisk /dev/ad10
*** Working on device /dev/ad10 ***
parameters extracted from in-core disklabel are:
cylinders=969021 heads=16 sectors/track=63 (1008 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=969021 heads=16 sectors/track=63 (1008 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 6 (0x06),(Primary DOS, 16 bit FAT (= 32MB))
start 63, size 31455207 (15358 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 31455270, size 31455270 (15359 Meg), flag 80 (active)
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 62910540, size 913857525 (446219 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
UNUSED
denver:#
There are what appears to be a freebsd base install from Jul 19/20th 2007
on /dev/ad10s1{a,d,e,f}
denver:#ls -l /maxtor500GB/tmp/
total 2
drwxrwxr-x 2 root operator 512 Jul 20 2007 .snap
denver:#ls -l /maxtor500GB/
total 38
drwxrwxr-x 2 root operator 512 Jul 20 2007 .snap
drwxr-xr-x 2 root wheel 1024 Jul 19 2007 bin
drwxr-xr-x 7 root wheel 512 Jul 19 2007 boot
..
denver:#df -hl|grep ad10
/dev/ad10s1a 496M 11M445M 2%/maxtor500GB
/dev/ad10s1d 989M106K910M 0%/maxtor500GB/var
/dev/ad10s1f 16G 97M 15G 1%/maxtor500GB/usr
/dev/ad10s1e 727M580K668M 0%/maxtor500GB/tmp
/dev/ad10s3d 422G384G4.0G99%/maxtor500GB/data
/dev/ad10s2d 15G 11G2.5G81%/maxtor500GB/data2
running sysinstall also show s1 as 'fat'
I've been writing/reading a lot of data from it just fine - Curios why s1
is being detect as a 'fat' partition and not a fbsd slice.
Have not tried to put this disk into a windows/another box...
I don't know why other than it has apparently been marked
with an fstype (sysid) of 6 at some time. Maybe something
started and went long enough to muck with the slice table but
then did nothing else.
Anyway, if you can mount, read and write it OK, I would not
worry too much. If you plan to wipe and it for a new install
it should not be a problem.
jerry
]Peter[
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Sun, 15 Nov 2009 21:18:36 -0700 (MST) Warren Block wbl...@wonkity.com replied: On Mon, 16 Nov 2009, Polytropon wrote: On Mon, 16 Nov 2009 02:21:28 +0200, Manolis Kiagias son...@otenet.gr wrote: Just the fact that I now have to edit an xml file to simply add a Greek keyboard layout is annoying enough. The fact that annoys me is that configuration seems to have disassembled into several parts that are not located in a central file (such as xorg.conf has been); I have no problem with editing text files if I need to, but now it's getting somewhat complicated - I'm not confortable with the fact that FreeBSD is (getting) complicated, I always loved it because everything is so simple. But xorg is not FreeBSD, so this is an unreasonable statement. FreeBSD is simple. X has never been particularly simple, and the fact that complexity grows over time is nothing new, either. But I am not complaining! :-) I've been told that those changes are absolutely needed to design the creation of new software more efficiently and cheaper; this is often confused with bloat, but it's not, it's evolution! And there's no way around. Of course there is: if you're happy with the state of your software, stop there! Don't upgrade. Don't replace what's working with something newer. That option is usually more difficult than it initially seems. The rest of the world tends to keep on evolving. I would be more happy if things would really get better, or even not worse, but sadly, they seem to. Software gets slower as well as less accessible - Gtk 2, used by many programs, is a good (bad) example. Am I supposed to buy new computer to replace perfectly running systems just to keep the overall usage speed of everything at the same level? As above, you don't *have* to upgrade. Keep the old software, and the old hardware will run it. Like everybody, I grumble about changes that don't seem to improve things at the user level. But I try to remember that without change, nothing can improve. It's also worth remembering that open source projects like xorg give the users the rare privilege of being able to make a difference. Test code, provide hardware, document bugs or fixes, do or fund development. If that were true, it might be worth noting. Unfortunately, it rarely works like that. I recently started using a Logitech wireless mouse/keyboard. Of course the mouse did not work in X, although it performed fine outside of X. After investing valuable time in Googling for a solution, I ended up editing files for HAL and adding Section ServerFlags Option AllowEmptyInput OFF EndSection to the 'xorg.conf' file. rant Honestly, that is not acceptable. On every Windows and MAC system I tested, the combo works without this garbage. It just works. No drivers to install, unless I want the extended capabilities of the keyboard/mouse. Why does it have to be so freak-in difficult here. How the hell are we suppose to entice potential users to non Window's platforms when a simple thing like adding a keyboard or mouse to a system becomes a challenge. /rant -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Do unto others before they undo you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Partition naming, fstab, and geli
On Sun, Nov 15, 2009 at 07:23:15PM -0700, David Allen wrote: Say I have performed a standard installation of FreeBSD onto a single IDE drive with the following entries in /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d /var ufs rw 2 2 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 Then I added more drives. 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? It really doesn't matter. Just don't use 'c' and I usually skip using 'b' and even often use it for a little additional swap. But, just pick a habit that works for you and stick with it. /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Leave the fstype alone. Use the noauto option. Probably set dump and pass to 0 also. So, for example, if you do not want it to try and mount /dev/ad3f at boot time, the line would look like: /dev/ad3f /bar3 ufs rw,noauto 0 0 Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Partition naming, fstab, and geli
On Tue, Nov 17, 2009 at 03:04:27AM +1100, Ian Smith wrote: In freebsd-questions Digest, Vol 285, Issue 2, Message 2 On Sun, 15 Nov 2009 19:23:15 -0700 David Allen wrote: Say I have performed a standard installation of FreeBSD onto a single IDE drive with the following entries in /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d /var ufs rw 2 2 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 Then I added more drives. 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 If you added these with sysinstall (or sade) it will tend to choose 'd' for the first partition on other than the / partition (which is named 'a' on install). Or at least, it's always started with 'd' for me :) Generally, using 'a' for root is needed if the slice is a device and root (/) will be there. But, probably because of that, the tradition of reserving 'a' is strong enough that many people and some utilities just do it that way unless specifically directed otherwise. But, if it is a second (third, fourth, etc) slice/drive that will not have a root partition, it doesn't actually matter. I tend to use 'a' if the drive will be entirely one slice and one partition used for some special work or scratch space, but stick with 'd..h' if there will be more than one partition and just leave 'a' alone - for no other reason than habit. As for 'd' vs 'e', sometime a long time and many generations ago there was a convention of reserving 'd' for something. I don't remember what it was. It was pre FreeBSD 3 and pre 1997 and maybe even pre any FreeBSD and applied in some earlier Unix-en before the court cases, but not after. That old convention accounts for documentation starting with using 'e' for extra partitions and skipping 'd'. But, whatever that old convention was, it has not been used for so long that it is meaningless nowdays and 'd' can be used for whatever extra partition you want. jerry But if you're doing it manually starting with 'e' is fine. I suspect the handbook section you quoted to Polytropon later is more an example than definitive. You can happily mount an 'a' partition from another drive that was once a system disk; it's more of a convention really. 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 Yes. Here I must differ with Polytropon, though your format for the options isn't perhaps quite right. From an old fstab here: # DeviceMountpoint FStype Options DumpPass# /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdosfs ro,noauto 0 0 /dev/ad0s2b noneswapsw 0 0 /dev/ad0s2a / ufs rw 1 1 /dev/ad0s2d /varufs rw,noatime 2 2 /dev/ad0s2e /usrufs rw,noatime 2 2 /dev/ad0s4d /paqi4.5ufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 3 /dev/ad0s4e /paqi4.5/varufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 /dev/ad0s4f /paqi4.5/usrufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 # 25Apr06 ext 20Gb USB disk. DON'T autoadd these, deadly if da0 absent! # .. xx fsopts, everything incl fsck must ignore .. /dev/da0s3d /usbdsk ufs xx,noauto,nosymfollow 3 3 /dev/da0s3e /usbdsk/var ufs xx,noauto,nosymfollow 4 4 /dev/da0s3f /usbdsk/usr ufs xx,noauto,nosymfollow 4 4 # 26May06 shintaro 1G flashdrive .. just doc, can't mount using these .. /dev/da0s1
Re: how to do a custom install?
On Sun, Nov 15, 2009 at 08:59:32PM +1100, David Rawling wrote: -Original Message- From: Gary Kline Sent: Sun 15/11/2009 8:03 PM due to strange disk problems i was down for around 30 hours. i am currently wiping dos/win off in favor of 7.2-R and i have a question about doing a custom install that would let me slice the drive into more that four pieces. You probably only need one slice (which MS calls a primary partition) but, you probably want to subdivide the slice in to FreeBSD partitions. i am building, by default, /, /var SWAP, and /usr it has been years since my custom install where [[*some*]] technique let me slice something like, say, Again, note the difference between slice and partition in FreeBSD. Slices are identified by numbers 1..4 and are the primary division. Partitions are subdivisions of a slice and are identified by letters a..h with 'c' reserved for the system to use. Then, you create mount points which are really directories with names such as / and /var and /usr and mount those drive-slice-partitions to the mount points. Swap is a special type that does not get mounted. jerry /, /var, /tmp, /usr/local/ SWAP, and /usr anybody remember what keys to hit in the installation procedure? tia, gary I can't say that I remember the keystrokes, but you can have multiple disk slices (aka Windows/DOS partitions) and within each slice, multiple BSD partitions (IIRC up to 8). I have mine partitioned into (generally) / - 1GB swap - 2x - 4x RAM /tmp - 4GB /var - 20GB /usr - 40% /backup - remainder I use the whole disk for BSD (single slice) and create the partitions as whatever size suits. Dave. -- David Rawling PD Consulting And Security Email: d...@pdconsec.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ATI Eyefinity support in FreeBSD
On Fri, 13 Nov 2009 19:06:10 -0500 PJ PJ af.gour...@videotron.ca replied: [snip] Hey, this is indeed very interesting. But did you read the fine print at the bottom of the page? Linux support scheduled to be enabled via a future ATI Catalyst™ driver release. Nobody cares about us FreeBSD fraks... :'( Yes, I did see the reference. I don't blame ATI though. After all, they have to first appease their largest user base. Unfortunately, that means that Linux users are put on hold for an indefinite period of time. Once that project is consummated, the development or porting of drivers to other platforms commences. It would be nice if some patronage were shown to FreeBSD earlier in the cycle though. I cannot help but wonder if this will turn into a nVidia-64 debacle; i.e., waiting years for a serviceable solution. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | That money talks, I'll not deny, I heard it once, It said Good-bye. Richard Armour ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ATI Eyefinity support in FreeBSD
I recently came across this web page regarding ATI: http://www.amd.com/us/products/technologies/eyefinity/Pages/eyefinity.aspx Is this supported under FreeBSD also? -- Jerry ges...@yahoo.com |=== |=== |=== |=== | No one gets sick on Wednesdays. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remote re-installation of current FreeBSD system.
to select that boot. It used to be on CD-1, but you may need to check that in case they moved it. Just put in the CD and boot and see what you get. Select the option and if it gives you a prompt, then you are running from it. It won't hurt your disk at that stage. If you really just have a single slice and no partitions, then your mounts in fstab would be just: /dev/ad0s1 / If you do not have a partition, but are running directly from a slice, eg have an unlabeled slice, then do the following. dd if=/dev/zero of=/dev/da0s1 bs=512 count=1024 bsdlabel -w -B ad0s1 bsdlabel -e ad0s1 That will clean up a little, start an initial label on the slice and then put you in to an edit screen. It will look something like: # /dev/ad0s3: 8 partitions: # size offsetfstype [fsize bsize bps/cpg] c: 89867610 0unused 00 # raw part, don't edit Edit that file so you have partitions you want Do NOT modify the c: line then write and exit. In vi, that would, of course, be ESC:wq that will write the label to the slice on the disk. If you already have partitions - eg there was an ad0s1a mounted to / Then skip the dd and the first bsdlabel and just do: bsdlabel -e ad0s1 You will get the partition edit screen about the same as before but it will have the current partitions in it, something like: # /dev/ad0s3: 8 partitions: # size offsetfstype [fsize bsize bps/cpg] a: 78643204.2BSD 2048 16384 49160 b: 2572288 786432 swap c: 898676100unused0 0 # raw part, don't edit d: 1048576 33587204.2BSD 2048 16384 8 e: 6291456 44072964.2BSD 2048 16384 28552 f: 6291456 106987524.2BSD 2048 16384 28552 g: 72877402 169902084.2BSD 2048 16384 28552 NOTE: All these sizes and offsets are given in blocks of 512 bytes. You will need to modify these to make room for your /usr/local Do NOT modify the c: line One advantage of the new bsdlabel is that it will calculate offsets and the final partition for you - just put a '*' in the field. Note: On the disk above these partitions are currently mounted as: a: / b: swap d: /tmp e: /usr f: /var g: /home So, to squeeze in a partition for /usr/local you might do this: I will make it 2 GB in partition g: and that makes /home go to h: # /dev/ad0s3: 8 partitions: # size offsetfstype [fsize bsize bps/cpg] a: 78643204.2BSD 2048 16384 49160 b: 2572288* swap c: 898676100unused0 0 # raw part, don't edit d: 1048576*4.2BSD 2048 16384 8 e: 6291456*4.2BSD 2048 16384 28552 f: 6291456*4.2BSD 2048 16384 28552 g: 4194304*4.2BSD 2048 16384 28552 h:**4.2BSD 2048 16384 28552 This way, bsdlabel will calculate the offsets correctly and put all available remaining space in the last (h:) partition. Now my mounts (in fstab) would need to be: a: / b: swap d: /tmp e: /usr f: /var g: /usr/local h: /home You can divide this up however you want. You could put just the swap (you really should have a good amount of swap) and your /usr/local separately and all the rest in partition a: if you want. Then you would only have partitions a:, b: and d: To mount as: a: / b: swap d: /usr/local eg, following rebuilding the partitions, including creating the new /usr/local partition and restoring the backups, do the following. cd /usr mv local oldlocal mkdir local mount /dev/ad0s1g /usr/local (I just pulled a partition 'g' out of the air. Use what you actually make it) cd /usr/oldlocal tar cvpf /usr/local/loc.tar cd /usr/local tar xvpf loc.tar Now, check it out and make sure files in the new /usr/local are good cd /usr rm -rf oldlocal cd /usr/local rm loc.tar Then you should be good to go. Any input, advice, tips etc would be very welcomed. (trying to be prepared before attempting anything) The main thing is to do backups that are stored on media off the unit you are modifying.Use dump(8) and restore(8). jerry Thank you, -r ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remote re-installation of current FreeBSD system.
On Fri, Nov 13, 2009 at 05:12:06PM -0500, Jerry McAllister wrote: On Fri, Nov 13, 2009 at 03:28:04PM -0500, Roger wrote: Hello all, I'm in control of a dedicated server and I would like to re-install FreeBSD. I found the following guide: http://www.freebsd.org/doc/en/articles/remote-install/ which seems to cover pretty much all should need but it assumes that I have some other OS (linux) installed, since I have FreeBSD 7.2-p4 I wonder if maybe there is an easier way. Well, you say a dedicated server, but you do not say it is remote. The article is for a remote install - that is, one where you cannot put your hands on the actual machine. I just noticed your subject line. You should really put all relevant information in the body of your post and not depend on the subject line doing any more than filtering. Anyway, if it is really remote, then take that article seriously but for only one disk, forget the gmirror raid stuff. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 06:57:02PM -0600, Jesús Abidan wrote: i did it like you say, but something is happening with my installation, it boots always the first OS, i don't have any ideas for having a dual system... argh!! Perchance, is your other system MS-Vista? As I mentioned in a previous response, I have heard of people having problems with dual booting with Vista and having to follow some other procedure for that. But, I haven't used Vista (and do not intend to) so you will have to do some archive searching to find those pieces of information. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 02:12:22PM -0600, Jesús Abidan wrote: so, then i need to create 2 slices with gparted, install windows on the first one, and install freebsd on the second one and label this partition automatically by the installer (ad0s1, ad0s2, etc) and install the bootmgr? Yes, essentially except for those partition names. Create the two slices/primary partitions. Install the MS-Win in the first one. I think then MS will call it 'c:' Anyway, FreeBSD will think it is ad0s1. Then install FreeBSD in the second slice/primary partition. MS will not even know it is there. FreeBSD will call it ad0s2. During the install, that ad0s2 slice will be subdivided according to how you tell it into FreeBSD partitions with names like ad0s2a (for root) and ad0s2b (for swap), ad0s2d for whatever - maybe /tmp, ad0s2e for something else, such as /usr, etc. For my general purpose machines I usually subdivide in to the following partitions: amounts as / eg: mount /dev/ad0s2a / b swap cdescribes the slice and is not a real partition dmounts as /tmp eg: mount /dev/ad0s2d /tmp emounts as /usr etc fmounts as /var gmounts as /home or something similar For my systems that are single purpose central servers I tend to do this: amounts as / everything but swap and afscache goes in root. b swap cslice description d/afscache If I have a second drive for scratch or work space I tend to do: amounts as /work and uses up all the space except extra swap bused for additional swap cdescribes the slice The sizes of the various partition-subdivisions depends on the size of the disk and the use being made of the machine and what I want to install on it and how I want to handle backups. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 01:22:58PM -0600, Jesús Abidan wrote: ok. the slices in freebsd are little tricky, i will check my installation and send some feedback later. ?? FreeBSD slices are pretty straight forward. They are just the name of the 4 primary divisions of a disk - limited to 4 by BIOS. MS just calls them primary partitions instead of slices. The major difference is how they might be subdivided. MS does what it calls logical partitions. FreeBSD subdivisions are just called partitions. The fdisk(8) utility creates slices (or primary partitions in MS, though the FreeBSD fdisk is not very conversant with some of the new MS types so you may be better off using something else to create primary partitions/slices if other OSen are being accomodated). Slices (or primary partitions) are identified by numbers 1..4. The bsdlabel(8) utility in FreeBSD is what subdivides a slice in to partitions. It used to be that it was limited to 7 real partitions identified with letters a..h with the letter 'c' reserved to describe the whole slice and not usable as a real partition. Partition 'a' is normally root mounted as '/' and partition 'b' is used as swap. These two (a b) are conventions and not enforced, except that some software may make these assumptions.My understanding is that the newest versions of FreeBSD (8.0) modify or remove the limit and you can have letters above 'h' and thus more subdivisions in a slice, but I haven't tried that yet. In FreeBSD, to create a filesystem from a partition, you run newfs(8) on it. jerry Thanks a lot. 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 12:27:13PM -0600, Jesús Abidan wrote: i pressed f2 for freebsd and nothing happens... i pressed f1 for windows. I install freebsd on the first partition and now it occurs the viceversa, i cannot boot windows, does it have to be something with the order of the partitions? i mean primary, logical o something like this? MS-Win should optimally be installed on the first primary partition. This is called 'slice 1' by FreeBSD. Then FreeBSD should
Re: cannot boot freebsd
On Thu, Nov 12, 2009 at 10:04:29AM -0600, Jesús Abidan wrote: i think i have the problem... i have two hard disks, IDE and SATA, i saw in my MS XP, my root label is F: instead of C: maybe it is something related to jumpers or something like that? That is a little surprise to me, but I am not up on the ins and outs of IDE/SATA labeling.Most of my machines - all of the servers - have SCSI or SAS disk which does it differently (and more easily). My only SATA machines have only a single disk. One thing to ask is: what does it have as c:, d: and e: ?? Maybe something is plugged in the wrong - or inconvenient - order on the controller. Or, I suppose there might be a jumper issue. jerry 2009/11/12 Jesús Abidan jabi...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cannot boot freebsd
On Thu, Nov 12, 2009 at 09:38:27AM -0600, Jesús Abidan wrote: First, please send all messages to the freebsd-questions list and not just to me. That is proper list etiquette, plus you will be able to get responses from more than just me. Others may know more. In other words, always do a 'reply all' on list email. read this: First, be aware that all the information necessary to boot FreeBSD must be located within the first 1,024 cylinders of the hard disk. This is necessary for the FreeBSD boot manager to work; it means that when you partition the disk for FreeBSD using FIPS, either the root partition must be completely located within the first 1,024 cylinders or you can use a separate boot partition that is completely located in the first 1,024 cylinders. Use the Start and End cylinder readouts in FIPS to determine where your partitions start and end. If you choose the latter option, the root partition does not have to be completely located in the first 1,024 cylinders. Note that completely located means that the partition has to both start and end below the 1,024th cylinder. Simply starting below the 1,024th cylinder is not good enough. This is obsolete information for most computers with BIOS and disks created later than about 1998. That really means all computers functioning today. It is also obsolete for FreeBSD systems which do not use BIOS to talk to the disk. There are numerous web sites that explain this including some documentation on the FreeBSD web site:http://www.freebsd.org/ jerry http://www.informit.com/articles/article.aspx?p=32084seqNum=4; as i see, do i need to create a partition(located in the first 1024cylinders) to BOOT from? (sorry) 2009/11/12 Jesús Abidan jabi...@gmail.com no, it's not vista, is XP 2009/11/12 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 06:57:02PM -0600, Jesús Abidan wrote: i did it like you say, but something is happening with my installation, it boots always the first OS, i don't have any ideas for having a dual system... argh!! Perchance, is your other system MS-Vista? As I mentioned in a previous response, I have heard of people having problems with dual booting with Vista and having to follow some other procedure for that. But, I haven't used Vista (and do not intend to) so you will have to do some archive searching to find those pieces of information. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 02:12:22PM -0600, Jesús Abidan wrote: so, then i need to create 2 slices with gparted, install windows on the first one, and install freebsd on the second one and label this partition automatically by the installer (ad0s1, ad0s2, etc) and install the bootmgr? Yes, essentially except for those partition names. Create the two slices/primary partitions. Install the MS-Win in the first one. I think then MS will call it 'c:' Anyway, FreeBSD will think it is ad0s1. Then install FreeBSD in the second slice/primary partition. MS will not even know it is there. FreeBSD will call it ad0s2. During the install, that ad0s2 slice will be subdivided according to how you tell it into FreeBSD partitions with names like ad0s2a (for root) and ad0s2b (for swap), ad0s2d for whatever - maybe /tmp, ad0s2e for something else, such as /usr, etc. For my general purpose machines I usually subdivide in to the following partitions: amounts as / eg: mount /dev/ad0s2a / b swap cdescribes the slice and is not a real partition dmounts as /tmp eg: mount /dev/ad0s2d /tmp emounts as /usr etc fmounts as /var gmounts as /home or something similar For my systems that are single purpose central servers I tend to do this: amounts as / everything but swap and afscache goes in root. b swap cslice description d/afscache If I have a second drive for scratch or work space I tend to do: amounts as /work and uses up all the space except extra swap bused for additional swap cdescribes the slice The sizes of the various partition-subdivisions depends on the size of the disk and the use being made of the machine and what I want to install on it and how I want to handle backups. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 01:22:58PM -0600, Jesús Abidan wrote: ok. the slices in freebsd are little tricky, i will check my installation and send some feedback later. ?? FreeBSD slices are pretty straight forward. They are just the name of the 4 primary divisions of a disk - limited to 4 by BIOS
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 11:02:35AM -0600, Jesús Abidan wrote: Hi there, i have a problem here, i installed windows in mi box and i left a partition for freebsd, i finished install of freebsd and installed the boot mgr of freebsd but when i reboot only windows boots with f1 pressed? how can I make the system boots both? Not sure all of what you see, but if you literally mean that when you press F1 it always boots MS-Win, that is probably correct. You will have to press F2 or maybe F3 (depending in which slice you installed FreeBSD) to boot FreeBSD. I suspect you mean something a little different, but if so, please elaborate. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 12:27:13PM -0600, Jesús Abidan wrote: i pressed f2 for freebsd and nothing happens... i pressed f1 for windows. I install freebsd on the first partition and now it occurs the viceversa, i cannot boot windows, does it have to be something with the order of the partitions? i mean primary, logical o something like this? MS-Win should optimally be installed on the first primary partition. This is called 'slice 1' by FreeBSD. Then FreeBSD should be installed on slice 2. If the slices are not to your liking, then you may need to use some utility such as Parition Magic 7 (I had trouble with PM-8) or gparted to define the primary partitions/slices before you do any of the installs. But, still, MS-Win should be installed first and go in the first slice and FreeBSD later in another slice. That is because MS-Win doesn't play very well if installed later and/or in a different slice. When you install FreeBSD (after the MS-Win install) select installing the FreeBSD MBR (not none or default minimum).It should be smart enough to find both. I have heard some complaints about MS-Vista and having to do some other monkeying around to get an MBR to handle it correctly, but I don't know details and I do not (lucky me) have any Vista machines to joust with. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 11:02:35AM -0600, Jesús Abidan wrote: Hi there, i have a problem here, i installed windows in mi box and i left a partition for freebsd, i finished install of freebsd and installed the boot mgr of freebsd but when i reboot only windows boots with f1 pressed? how can I make the system boots both? Not sure all of what you see, but if you literally mean that when you press F1 it always boots MS-Win, that is probably correct. You will have to press F2 or maybe F3 (depending in which slice you installed FreeBSD) to boot FreeBSD. I suspect you mean something a little different, but if so, please elaborate. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 01:22:58PM -0600, Jesús Abidan wrote: ok. the slices in freebsd are little tricky, i will check my installation and send some feedback later. ?? FreeBSD slices are pretty straight forward. They are just the name of the 4 primary divisions of a disk - limited to 4 by BIOS. MS just calls them primary partitions instead of slices. The major difference is how they might be subdivided. MS does what it calls logical partitions. FreeBSD subdivisions are just called partitions. The fdisk(8) utility creates slices (or primary partitions in MS, though the FreeBSD fdisk is not very conversant with some of the new MS types so you may be better off using something else to create primary partitions/slices if other OSen are being accomodated). Slices (or primary partitions) are identified by numbers 1..4. The bsdlabel(8) utility in FreeBSD is what subdivides a slice in to partitions. It used to be that it was limited to 7 real partitions identified with letters a..h with the letter 'c' reserved to describe the whole slice and not usable as a real partition. Partition 'a' is normally root mounted as '/' and partition 'b' is used as swap. These two (a b) are conventions and not enforced, except that some software may make these assumptions.My understanding is that the newest versions of FreeBSD (8.0) modify or remove the limit and you can have letters above 'h' and thus more subdivisions in a slice, but I haven't tried that yet. In FreeBSD, to create a filesystem from a partition, you run newfs(8) on it. jerry Thanks a lot. 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 12:27:13PM -0600, Jesús Abidan wrote: i pressed f2 for freebsd and nothing happens... i pressed f1 for windows. I install freebsd on the first partition and now it occurs the viceversa, i cannot boot windows, does it have to be something with the order of the partitions? i mean primary, logical o something like this? MS-Win should optimally be installed on the first primary partition. This is called 'slice 1' by FreeBSD. Then FreeBSD should be installed on slice 2. If the slices are not to your liking, then you may need to use some utility such as Parition Magic 7 (I had trouble with PM-8) or gparted to define the primary partitions/slices before you do any of the installs. But, still, MS-Win should be installed first and go in the first slice and FreeBSD later in another slice. That is because MS-Win doesn't play very well if installed later and/or in a different slice. When you install FreeBSD (after the MS-Win install) select installing the FreeBSD MBR (not none or default minimum).It should be smart enough to find both. I have heard some complaints about MS-Vista and having to do some other monkeying around to get an MBR to handle it correctly, but I don't know details and I do not (lucky me) have any Vista machines to joust with. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 11:02:35AM -0600, Jesús Abidan wrote: Hi there, i have a problem here, i installed windows in mi box and i left a partition for freebsd, i finished install of freebsd and installed the boot mgr of freebsd but when i reboot only windows boots with f1 pressed? how can I make the system boots both? Not sure all of what you see, but if you literally mean that when you press F1 it always boots MS-Win, that is probably correct. You will have to press F2 or maybe F3 (depending in which slice you installed FreeBSD) to boot FreeBSD. I suspect you mean something a little different, but if so, please elaborate. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RC3?
On Wed, Nov 11, 2009 at 09:00:04AM +1100, Alex R wrote: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.0/ shows that there is an RC3 ISO image available for download? How many RC's until the final release? Depends on what they find is needed to get the RELEASE ready to go. Check the following: The Release Engineering page. http://www.freebsd.org/releng/index.html And the wiki entry referenced in the Release Engineering page. http://wiki.freebsd.org/8.0TODO Looks like 8.0 is expected very soon. But, it will come when ready not on an MS fantasy schedule. It is all on the FreeBSD web side.http://www.freebsd.org/ jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Migrating from Linux (keeping partitions at install time)
On Sat, Nov 07, 2009 at 09:34:48PM +, David Chanters wrote: Hi all, I am considering switching from Debian Linux to FreeBSD. I am wondering if at install time, sysinstall is able to allow me to keep /home from my Debian installation. /home on Debian is currently a separate partition in its own right, mounted as RXT3. I only have the one hard disk in my machine. So, questions: 1. Can the installer be told to not touch /home at install time (I appreciate I would have to ensure I mapped the current /dev/hda2 terminology to slices in BSD parlance) If you have enough other room to install FreeBSD on the disk and that /dev/hda2 partition is not right in the middle of space you need for installing FreeBSD. eg, as long as it is in some ignorable place/space on the disk. 2. Does the fact that this is an EXT3 partition matter? (I have read FreeBSD supports ext2, and ext3 is just ext2 with a journal, so it can be mounted as ext2 if needed). I don't know if ext2 vs ext3 matters. It might. I would be inclined to want to make a backup of everthing on that partition and keep it somewhere you can get back to after FreeBSD is installed. Either tar or rsync it all to somewhere. Dump(8) is sensitive to OS, so it is one circumstance in which I do not recommend dump/restore for this type of backup. Now, providing that ext3 thing is not a problem, you can probably leave that filesystem/partition there if you have plenty of other space to install FreeBSD and set things up. Then you would probably want to copy everything from that old /home to a new one in FreeBSD space. You would just mount the old one as something like /oldhome and copy the stuff from it to whereever you have space in FreeBSD - maybe a new /home filesystem. Not so sure I did anything for your most important question - if ext2 s ext3 is a problem, but I hope the rest is helpful. 3. Is it possible/beneficial to convert this to UFS once FreeBSD is installed? Yes, absolutely - mount it and copy it to a FreeBSD filesystem if you plan to use it any amount. Good luck, jerry Thanks in advance for any help. David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/fstab + embedded spaces
On Tue, 03 Nov 2009 12:13:24 -0500 Michael Powell nightre...@hotmail.com replied: carmel_ny wrote: I was attempting to create this entry in the /etc/fstab file. It is to a WinXP machine. //u...@bios/My Documents /laptop smbfs rw,noauto 0 0 It fails because 'fstab' does not allow embedded spaces in device names, not does it allow enclosing the name in quotes. I did some Googling and discovered that I am not the only one annoyed by this behavior. I discovered this patch that had been submitted awhile ago. http://lists.freebsd.org/pipermail/freebsd-bugs/2007-October/026469.html Changing the share name is not really an option. Is there some way of making this work in 'fstab'? I can use the name including spaces in 'mount_smbfs' so that is how I am currently mounting the share. It just seems strange that 'fstab' by not accepting the use of quoting is not in step with how FreeBSD usually operates. Don't know if this works for fstab, but the normal way to escape spaces is with a \, like this: //u...@bios/My\ Documents /laptop smbfs rw,noauto 0 0 May not work in fstab but you can try it and see. Thanks for the suggestion. Unfortunately, it doesn't work either. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | The most winning woman I ever knew was hanged for poisoning three little children for their insurance money. Sherlock Holmes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Effing HAL
On Fri, 30 Oct 2009 11:04:18 -0500 Adam Vande More amvandem...@gmail.com replied: On Fri, Oct 30, 2009 at 10:58 AM, Freminlins freminl...@gmail.com wrote: I've read the responses and comments here, so don't think I'm ignoring anyone because I haven't responded directly. I rebuilt xorg-server without HAL. I killed hal stone dead and started up the new (i.e. old-skool) xorg. It all works fine. My mouse and keyboard work as specified in the xorg.conf file, rather than in the new-fangled xml way of doing things or adding setxkbmap to my xinitrc file. I am also 18MB of RAM better off. Specifically for Adam, who asks a rhetorical question about HAL, memory usage and top. The answer for me is 18MB too much. No my point was top is not accurate measure of HAL's memory usage. HAL has shared library's just like many other applications. My advice to anyone who has problems with X and HAL - rebuild xorg-server without HAL (it doesn't take long), then start from that base. I have to say this HAL way of doing things is using a sledgehammer to crack a nut. Sure X can be a bit horrible to configure, but HAL itself is ugly, resource hungry and doesn't work 100%. It seems to be an example of supposedly making things easier, except when it doesn't work. This is only because of your misinterpretation of data and failure to RTFM. Once you have to start reading a manual to create a configuration to get basic keyboard to work, things are getting seriously out of hand. A common user should not be required to have a working knowledge of XHTML and obscure directives in order to get a piece of equipment working. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | If you cannot in the long run tell everyone what you have been doing, your doing was worthless. Edwin Schrodinger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: win 7 dual boot
On Tue, Oct 27, 2009 at 10:16:27PM -0400, Aryeh M. Friedman wrote:
Jack L. wrote:
I was able to dual boot win7 and freebsd 8 without any problem, just
installed windows first and installed freebsd with the freebsd boot
manager and it said F1 windows and the rest are FreeBSD
I am attempting to avoid having to reinstall the fb side of things ;-)
Sure. Then, probably doing as you said - install the Win7 and let it
do its thing and then reinstall the FreeBSD MBR. You should probably
be able to use the Fixit CD boot for that. I don't know EasyBCD,
but if it worked before, it will probably work with this too.
I don't think anything much has changed in that area.
jerry
On Tue, Oct 27, 2009 at 7:11 PM, Aryeh M. Friedman
aryeh.fried...@gmail.com wrote:
I am about to go out and buy windows 7 to replace my vista partition...
when
I installed vista I had to do some boot manager tricks (both before and
after install)... namely I had to allow windows to nuke my mbr then use
EasyBCD to remake it in such a way that vista would still find it's
magic
bytes in the mbr... does anyone know if win 7 has any similar issues
and/or
any other weirdness in reguards to dual booting?
Completely side question I use sysutils/fusefs-ntfs to mount my vista
partition do I need to change anything in my /etc/rc.d/* hierachy and/or
/etc/fstab after installing win 7 (I use a direct call to ntfs-3g instead
of via the mount patch [which doesn't work on 8.0-XXX it seems {I am on
RC2
right now}]?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How do I replace the built-in OpenSSL with a source tarball ?
On Wed, 28 Oct 2009 08:57:52 -0700 (PDT) George Sanders gosand1...@yahoo.com replied: I would like to: - upgrade the built-in OpenSSL that comes with FreeBSD (in my case, 6.4-RELEASE) - replace it with OpenSSL that I build myself from the source tarball If I do this with a plain old: ./config ; make ; make install OpenSSL does indeed build and install, but it installs in an alternate location and does not overwrite the FreeBSD built-in. Ok, should be easy to fix - I will simply use an: --prefix config directive and point it to /usr: --prefix=/usr However, that does not work - running: /usr/local/ssl/bin/openssl version shows me that this binary has not changed. Ok, no problem, I will simply use: --prefix=/usr/local instead ... but that also does not work. No matter what I do, I cannot get the OpenSSL source tarball to overwrite my built-in OpenSSL in FreeBSD - I always end up having two binaries in two different locations. Can someone tell me how to just cleanly replace the built-in OpenSSL with the source tarball ? I use this in my /etc/make.conf file: WITH_OPENSSL_PORT=yes -- Jerry ges...@yahoo.com |=== |=== |=== |=== | (null cookie; hope that's ok) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: flashplugin
On Wed, 28 Oct 2009 22:25:53 +0100 Polytropon Polytropon free...@edvax.de replied: [snip] That's not FreeBSD's fault. If professional web designers need to optimize their content in order to prevent you from properly accessing it, it's their fault. I would complain to them, or just ignore them. Content that its creator doesn't want me to see is not worth seeing. You don't really believe that do you. Web creators attempt to make their sites accessible to the largest possible audience. It is probably cost prohibited, if even reasonably possible to make a site 100% viewable in every browsers (don't forget lynxs) available. Any intelligent business plan would dictate that they therefore concentrate on the largest possible audience. This problem, like the nVidea 64 bit drivers, rests with FreeBSD. You simply cannot expect any software developer to develop and maintain a product for what is in reality a niche OS. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | I am more bored than you could ever possibly be. Go back to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: flashplugin
On Mon, 26 Oct 2009 20:06:30 -0400 PJ PJ af.gour...@videotron.ca replied: Thank you very much Herbert, I appreciate your input. As I wrote in my original query, I had auccessfully installed the lilnux-flashplugin9 on FreeBSD 7.2 both on a 64 bit portable _ Acer Travelmate 4400 - and on a couple of disks on the same machine (i386). I followed the instructions from http://crnl.org/blog/2008/11/01/flash-9-for-freebsd-71#comment-form upgrade FreeBSD. Once that's done the rest is straight forward. Step 1: Enable Linux compatibility and linprocfs Add linux_enable=YES to /etc/rc.conf. Add compat.linux.osrelease=2.6.16 to /etc/sysctl.conf. Add OVERRIDE_LINUX_BASE_PORT=f8 to /etc/make.conf. Add this line to /etc/fstab: linproc /usr/compat/linux/proc linprocfs rw 0 0 Then run these commands: mkdir -p /usr/compat/linux/proc mount /usr/compat/linux/proc /etc/rc.d/abi start /etc/rc.d/sysctl start Step 2: Update ports and install all the needed software You will now need to install the following ports and their dependencies: cd /usr/ports/emulators/linux_base-f8 make install clean cd /usr/ports/www/linux-flashplugin9 make install clean cd /usr/ports/www/nspluginwrapper make install clean Follow the nspluginwrapper instructions to enable all available plugins: # nspluginwrapper -v -a -i Auto-install plugins from /usr/X11R6/lib/browser_plugins Looking for plugins in /usr/X11R6/lib/browser_plugins Auto-install plugins from /usr/local/lib/npapi/linux-flashplugin Looking for plugins in /usr/local/lib/npapi/linux-flashplugin Install plugin /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so into /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so Auto-install plugins from /root/.mozilla/plugins Looking for plugins in /root/.mozilla/plugins Restart or open Firefox 3 and enter about:plugins into your address bar. You should see something like the following: And that's it! Open your favourite Flash site and all should work. If your browser doesn't register the Shockwave Flash plugin as pictured above, you might need to do a bit of extra work as I had to do on one of my machines: cd /usr/local/lib/firefox3/plugins ln -s /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so npwrapper.libflashplayer.so I'm not sure why one of my machines needed this, but it might happen to you so this is just a heads up. Update: I have learned that the change with the plugin directory is due to a change in FreeBSD's Firefox 3 port. If you're running port version 3.0.1_1 or later you will need to use the new plugin directory as shown above. CVS change history can be seen here. Enjoy! That is precisely why I keep an XP box nearby. There is no way in hell that I would want to personally, or expect a colleague for that matter, to waste valuable time getting a simple plug-in to work; especially since I can do it in a matter of seconds on a Microsoft product. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Nuclear war would really set back cable. Ted Turner ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bad sectors: how bad can it be
On Tue, 27 Oct 2009 08:16:07 +
Matthew Seaman m.sea...@infracaninophile.co.uk replied:
Gr_newald Micha_l wrote:
Dear list,
after an incorrect power-off of my FreeBSD system, it does not boot
any more, BTX stops even before showing the cute beastie menu.
Starting the machine by other means, I found that the hard-drive is
installed on has bad sectors. I am looking for advices on how to
recover from this, if possible.
Basically the question is: shall I discard my hard-drive with
bad-sectors, or can I continue using it?
The Linux system I use to diagnose this says:
hdb: media error (bad sector): status=0x51 { DriveReady
SeekComplete Error }
hdb: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
...
Buffer I/O error on device hdb, logical block 1663200
etc.
Since I use computers (1992) these are my first bad sectors :) (on
hard drives, taking floppies into account is no fun!). I hence have
several questions:
-- is it possible to let these sectors?
-- to which extents a hard-drive with bad sectors is usable?
-- while the apparition of these bad sectors coincide with an
incorrect power-off, are the two events related? The machine
suffered plenty improper power-offs (or many), in the last years and
did not react so badly!
Yes. Back up your data and replace that disk ASAP. It's toast.
All disks come with a built-in set of spare sectors, which the firmware
will automatically substitute for any sectors that go bad. If you get
to the state where the OS is seeing bad blocks, it means the disk has
run out of spare sectors. It's worn out.
A friend of mine had a lap-top that exhibited similar behavior. After
trying the usual methods, he used SpinRite
http://www.grc.com/intro.htm at its highest level on the disk. It
ran for 97 hours; however, when completed, the disk worked like new.
While replacing the drive is certainly a good idea, if you need
information on it that you cannot otherwise extract, you might want to
try another method.
--
Jerry
ges...@yahoo.com
|===
|===
|===
|===
|
Never pay a compliment as if expecting a receipt.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: WD External Disc Drive
On Tue, Oct 27, 2009 at 12:55:51AM -0700, per...@pluto.rain.com wrote: ... If you are refering to a kind of hard disk, use disk with k. Think like diskette. If you are refering to optical media, use disc with c. Think like CD = compact disc. An arbitrary convention adopted by you and a few other people does not invalidate the dictionary spellings and usage. Am I the only one who is finding the longevity of this bikeshed a bit disk-gusting? Ah, in the throes of a bad economy, so we can't afford an over-priced movie or exhorbitant concert tickets, we need some sort of entertainment. Bikesheds are cheap. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bad sectors: how bad can it be
On Tue, Oct 27, 2009 at 08:31:18AM +0100, Grünewald Michaël wrote:
Dear list,
after an incorrect power-off of my FreeBSD system, it does not boot
any more, BTX stops even before showing the cute beastie menu.
Starting the machine by other means, I found that the hard-drive is
installed on has bad sectors. I am looking for advices on how to
recover from this, if possible.
Basically the question is: shall I discard my hard-drive with bad-
sectors, or can I continue using it?
The Linux system I use to diagnose this says:
hdb: media error (bad sector): status=0x51 { DriveReady
SeekComplete Error }
hdb: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
...
Buffer I/O error on device hdb, logical block 1663200
etc.
Since I use computers (1992) these are my first bad sectors :) (on
hard drives, taking floppies into account is no fun!). I hence have
several questions:
-- is it possible to let these sectors?
-- to which extents a hard-drive with bad sectors is usable?
-- while the apparition of these bad sectors coincide with an
incorrect power-off, are the two events related? The machine suffered
plenty improper power-offs (or many), in the last years and did not
react so badly!
If a disk begins to have actual bad sectors - ones that cannot be
written and/or read then it is likely that the problem will progress
and soon the disk will be unusable. All modern disk drives have built
in remapping of bad sectors and you will normally not see any error
messages until so many sectors go bad that it runs out of spare ones.
So, it should replaced.
But your situation makes it just a little more difficult to make this
broad generalization. In this case, it might just be that the power
outage came at a bad time and in a bad place so it caused a couple of
essential sectors to be incorrectly written. If it was in an inode or
a superblock it could make it unusuable, but possible to recover, at
least everything but the bad ones. You can use an alternate superblock.
This incorrect writing due to a power loss is actually not very likely,
but could happen. Anyway, in that case, if you could get what you need
off the disk, you could then just reformat/renewfs it, load stuff back
up and go back to using it.
So, study up on recovering data by using an alternate superblock
and see what you can find out. If you rebuild it and it continues
to put out bad sector messages, then discard it.
Since disk is relatively cheap nowdays, it might be more worth your
time to just get another one and start over anyway. Probably able
to get a much larger capacity disk that way too.
Good luck and have fun,
jerry
--
Thank you in advance for your advices,
Michaël___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why is sendmail is part of the system and not a package?
On Tue, Oct 27, 2009 at 05:03:12PM -0200, Gonzalo Nemmi wrote: On Tuesday 27 October 2009 4:32:45 pm Erik Norgaard wrote: Jonathan McKeown wrote: Just as a matter of interest, if you want to rip sendmail out of the base system, which MTA would you like to replace it with? Or are you suggesting the system ship with no way to handle mail? This thread moving of topic from OP, but it is always fair to debate what should be considered a base system. Is an MTA a requirement or a remnant from history? Dear Erik: Contrary to your belief the thread isn't moving of topic from OP, it's just taking the same default route it has been taking for ages: 1) telling the OP the OS needs an MTA 2) telling the OP he can replace the default MTA 3) telling the OP he can remove given MTA from base 4) telling the OP about historical reason 5) Not telling the OP why has FreeBSD has left so many historical reason behind to persuit new goals but retained Sendmail as the default MTA for historical reasons. Sorry .. but that's the way it goes every time someone asks the same question. I will add one more that covers it best. Sendmail works just fine and there is no ACTUAL CURRENT reason to get rid of it.Years ago it had some weaknesses which have been fixed. So, that leaves personal preference as the only real reason for wanting to replace it. In that case, if your personal preference is to replace it, go ahead. There are several candidates and an earlier post described well how to do it. As for putting it in ports and taking it out of base, well, some message system is often needed before ports are installed. Sendmail fills the bill.Some other could also, but since Sendmail works just fine and is already there, then it is. jerry And if an MTA is a requirement then asking which one is the best choice is also a fair question. An equally fair answer could be whichever change requires the least work. Indeed No different than asking, why is NIS still in the base? Why no ldap? why BIND, but no http? Why NFS? etc... Let me save you the trouble; the answer to mot of that questions will be: historical reasons and that other solutions can can only dream of enjoying a fraction of the respect that BIND and Sendmail command in the industry Believe it or not ... I think the only void answer is because of tradition, that just seems to show that noone really remembers why some choice was made. BR, Erik Best Regards Gonzalo Nemmi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why is sendmail is part of the system and not a package?
On Tue, Oct 27, 2009 at 08:45:59PM -0200, Gonzalo Nemmi wrote: On Tuesday 27 October 2009 7:31:34 pm Jerry McAllister wrote: On Tue, Oct 27, 2009 at 05:03:12PM -0200, Gonzalo Nemmi wrote: On Tuesday 27 October 2009 4:32:45 pm Erik Norgaard wrote: Jonathan McKeown wrote: Just as a matter of interest, if you want to rip sendmail out of the base system, which MTA would you like to replace it with? Or are you suggesting the system ship with no way to handle mail? This thread moving of topic from OP, but it is always fair to debate what should be considered a base system. Is an MTA a requirement or a remnant from history? Dear Erik: Contrary to your belief the thread isn't moving of topic from OP, it's just taking the same default route it has been taking for ages: 1) telling the OP the OS needs an MTA 2) telling the OP he can replace the default MTA 3) telling the OP he can remove given MTA from base 4) telling the OP about historical reason 5) Not telling the OP why has FreeBSD has left so many historical reason behind to persuit new goals but retained Sendmail as the default MTA for historical reasons. Sorry .. but that's the way it goes every time someone asks the same question. I will add one more that covers it best. Sendmail works just fine and there is no ACTUAL CURRENT reason to get rid of it.Years ago it had some weaknesses which have been fixed. I wonder what would have happened if Sir Isaac Newton followed the same line of though ... Or maybe there was an ACTUAL CURRENT reason to develop infinitesimal calculus ... which .. of course, by that time, nobody knew it even existed. Or maybe there was an ACTUAL CURRENT reason to discover the law of universal gravitation ... Weird.Try cutting down on caffeine. Or maybe .. not ... So, that leaves personal preference as the only real reason for wanting to replace it. Let me get this straight .. that means that every Linux distro, NetBSD, OpenBSD and DragonFlyBSD are all doing it just out of personal preference? Yup. In that case, if your personal preference is to replace it, go ahead. There are several candidates and an earlier post described well how to do it. Yes, that has already been pointed out quite a few times. As for putting it in ports and taking it out of base, well, some message system is often needed before ports are installed. Sendmail fills the bill.Some other could also, but since Sendmail works just fine and is already there, then it is. Fit the bill ... well.. so did the Geocentric model .. and it actually did work just as fine .. and even better yet since it also mantained the status quo ! ... but then Galileo came and you know the rest of the story ... Actually it didn't. It didn't describe observable conditions and events. jerry jerry Best Regards Gonzalo Nemmi And if an MTA is a requirement then asking which one is the best choice is also a fair question. An equally fair answer could be whichever change requires the least work. Indeed No different than asking, why is NIS still in the base? Why no ldap? why BIND, but no http? Why NFS? etc... Let me save you the trouble; the answer to mot of that questions will be: historical reasons and that other solutions can can only dream of enjoying a fraction of the respect that BIND and Sendmail command in the industry Believe it or not ... I think the only void answer is because of tradition, that just seems to show that noone really remembers why some choice was made. BR, Erik alo Nemmi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: incorrect info in mysql docs
On Sun, 25 Oct 2009 18:21:11 + Chris Whitehouse cwhi...@onetel.com replied: I just noticed this at http://dev.mysql.com/doc/refman/5.1/en/automatic-start.html On FreeBSD, startup scripts generally should go in /usr/local/etc/rc.d/. The rc(8) manual page states that scripts in this directory are executed only if their basename matches the *.sh shell file name pattern. Any other files or directories present within the directory are silently ignored. In other words, on FreeBSD, you should install the mysql.server script as /usr/local/etc/rc.d/mysql.server.sh to enable automatic startup. That's not actually right is it? My mysql is started by /usr/local/etc/rc.d/mysql-server. rc(8) says *.sh is for older style startup scripts or for scripts that are to be read into the current shell. A start-up script is install automatically when using the ports system. You do need to activate it via /etc/rc.conf however. Perhaps MySQL could be prodded to post a reference to this on their website. It might help to avoid confusion. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Death is Nature's way of recycling human beings. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Force installation of dependencies
On Wed, 21 Oct 2009 13:53:05 +1000 Warren Liddell (shin...@maydias.com) replied: is there a command that when comnpiling a certain pkg will tell it to forcefully re-do every single dependcy for that particular pkg ? portmanager: to add/update/repair a single port with logging and forcing all of it's dependencies to be rebuilt portmanager x11/gnome2 -l -f -- Jerry |=== ges...@yahoo.com|=== |=== |=== | From 0 to what seems to be the problem officer in 8.3 seconds. Ad for the new VW Corrado ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: (no subject)
On Wed, 21 Oct 2009 02:26:45 -0700 (PDT) nicholas addei (uncleka...@yahoo.co.uk) replied: please am not able to install gnome on freebsd 7.2,after loging in as root would appreciate your help. :49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i Maybe next time you could include a SUBJECT: with your post. Anyway, your post is useless. Exactly what is your problem? Might I suggest that you use script or whatever else you prefer to create a complete log of your failed installation attempt and then either paste it here if it isn't too large, or place a link to it here. You might also consider cleaning out the /usr/ports/distfiles' directory and then running: portsclean -C -L -PP if you have it installed before attempting a new build. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | An idea is not responsible for the people who believe in it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: (no subject)
On Wed, Oct 21, 2009 at 02:26:45AM -0700, nicholas addei wrote: please am not able to install gnome on freebsd 7.2,after loging in as root would appreciate your help. You will get more help if you first, use a meaningful subject line on your post and then if you put some useful information in the post - such as just what you tried and what happened along with what messages that were displayed. jerry :49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i 86 Send instant messages to your online friends http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: (no subject) Gnome
On Wed, 21 Oct 2009 19:36:27 +0200 Lokadamus Lokadamus lokada...@gmx.de replied: nicholas addei schrieb: please am not able to install gnome on freebsd 7.2,after loging in as root would appreciate your help. :49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i 86 Normaly you do pkg_add -r gnome But know i get an error back. pkg_add -nr gnome Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Latest/gnome.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Latest/gnome.tbz' by URL With cd /usr/ports/x11/gnome2 make install will it work, but some hours/ days need to install. An old 1GHz System need 3 days for KDE 3 ;). http://www.freebsd.org/doc/en/books/handbook/packages-using.html http://www.freebsd.org/doc/en/books/handbook/ports-using.html Running as root: pkg_add -nr gnome2 It works here. Is your ports tree up-to-date? -- Jerry ges...@yahoo.com |=== |=== |=== |=== | The sudden sight of me causes panic in the streets. They have yet to learn - only the savage fears what he does not understand. The Silver Surfer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: small question about tape-based dumps
On Sat, Oct 17, 2009 at 06:49:02PM -0600, Tim Judd wrote: On 10/17/09, Jerry McAllister jerr...@msu.edu wrote: snip You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry snip If dump is the tool for tapes, and tar is named after tape archives... Do both of these utilities write the *proper* EOF to whatever medium it's writing to? I bring this up, because dump can also write to a file on a formatted FS. Does the file end with this same EOF? What does tar do? EOF means something completely different on a file system than it does on a tape. So, yes, the system knows where the file ends on both, but it is done differently. jerry Why have a mt weof function if it's useless? I'm loosing the logic in this one, trying to make sure things work as they should. I admit tapes on bsd are so foreign to me, I might as well be speaking $another-language. It is not useless. It just isn't necessary in that situation. Remember, mt(1) is used on more than just dumps. jerry Please help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: small question about tape-based dumps
On Sat, Oct 17, 2009 at 08:09:22PM -0600, Tim Judd wrote: On 10/17/09, Stevan Tiefert stevan-tief...@kabelmail.de wrote: Am Samstag, den 17.10.2009, 18:49 -0600 schrieb Tim Judd: On 10/17/09, Jerry McAllister jerr...@msu.edu wrote: snip You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry snip If dump is the tool for tapes, and tar is named after tape archives... Please, no flamewar!!! Wasn't planning on starting one. Sorry if it came across that way. Do both of these utilities write the *proper* EOF to whatever medium it's writing to? They both write EOF. I bring this up, because dump can also write to a file on a formatted FS. Does the file end with this same EOF? What does tar do? There is only one EOF: The EOF. Why have a mt weof function if it's useless? I'm loosing the logic in this one, trying to make sure things work as they should. I admit tapes on bsd are so foreign to me, I might as well be speaking $another-language. weof is not useless. There are some file operations without writing an EOF, like streams or something like that, but tar and dump are writing with an EOF at the end of files :-) So it's a item for good measure rather than an item as necessity in creating backups. Not a good measure. It would do something different from what you expect. You might get 2 EOF-s in a row and the system think you have two files - one with stuff and one empty one. jerry Thanks for all the info. I'm happy knowing more. --Tim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I hate to bitch but bitch I must
On Fri, Oct 16, 2009 at 05:54:23PM -0400, PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? No, it clearly says tunefs CANNOT be run on an active filesystem. Then it says, in order to change an active file system you have to first make it a NOT active filesystem - eg make it read-only or just unmount it. but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? That means it is a BUG that it won't work on an active files system - eg that someone should fix this defficiency and make it so it will work on an active filesystem. The man writer thinks it 'should' be able to work that way. jerry To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: small question about tape-based dumps
On Fri, Oct 16, 2009 at 08:43:26PM -0600, Tim Judd wrote: Replies inline On 10/16/09, Jerry McAllister jerr...@msu.edu wrote: On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? You can easily put more than one dump on a tape if there is room enough for them. Check out the mt(1) command. Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. If you need to restore, it is just the same. The first dump is the first file. The second dump is reached by skipping 1 file with the mt command, etc. I actually rewind and skip between each dump of multiples made to the same tape. I also use the no-rewind device for the tape. So first dump is:dump 0af /dev/nsa0 / I understand that this creates a dumpfile on nsa0, and as I understand tapes (which may be wrong, which I ask for clarification here).. To mark a end-of-file to be able to fast-forward/rewind, why can't you use: mt -f /dev/nsa0 weof It's description in mt(1) says it writes the end-of-file mark at current position You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry For second dump: mt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 1 dump 0af /dev/nsa0 /usr So if we use weof, would the 2nd dump then be: dump 0af /dev/nsa0 /usr mt -f /dev/nsa0 weof thirdmt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 2 dump 0af /dev/nsa0 /var And 3rd: dump 0af /dev/nsa0 /var mt -f /dev/nsa0 weof etc. when all donemt -f /dev/nsa0 rewind mt -f /dev/nsa0 offline And I've never used offline, guess I'll start now. I have this all in a script that also writes an index file as the first file on the tape. Of course if you are doing a change dump the dump command is going to look more like: dump 1af /dev/nsa0 etc. jerry With regards Stevan Tiefert Thanks for any input! --TJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best procedure for full backup of live system
On Fri, Oct 16, 2009 at 12:12:56AM -0700, Nerius Landys wrote: You can do all this though it might be more than needed. Only the level 0 dumps are needed. Thanks again guys. My final series of steps to take full backups: bsdlabel ad4s1| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/bsdlabel_ad4s1 dmesg -a | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dmesg dd if=/dev/ad4 bs=512 count=1 | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/MBR cat /etc/fstab| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/fstab dump -0Lan -f - / | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-root.gz dump -0Lan -f - /tmp | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-tmp.gz dump -0Lan -f - /var | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-var.gz dump -0Lan -f - /usr | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-usr.gz ... where port 2 on localhost is a pipe to my remote desktop with the 500 GB harddrive. If I missed anything important please let me know. Are you clear about what you have to run on the other machine to receive the data and put it where you want? jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: small question about tape-based dumps
On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? You can easily put more than one dump on a tape if there is room enough for them. Check out the mt(1) command. Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. If you need to restore, it is just the same. The first dump is the first file. The second dump is reached by skipping 1 file with the mt command, etc. I actually rewind and skip between each dump of multiples made to the same tape. I also use the no-rewind device for the tape. So first dump is:dump 0af /dev/nsa0 / For second dump: mt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 1 dump 0af /dev/nsa0 /usr thirdmt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 2 dump 0af /dev/nsa0 /var etc. when all donemt -f /dev/nsa0 rewind mt -f /dev/nsa0 offline I have this all in a script that also writes an index file as the first file on the tape. Of course if you are doing a change dump the dump command is going to look more like: dump 1af /dev/nsa0 etc. jerry With regards Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: clone-dump-restore
On Wed, Oct 14, 2009 at 09:29:42PM -0400, PJ wrote: I believe that my problems arise out of subliminal refuse syndrome: the brain refuses to comprehend dump and restore TOs and FROMs. In other words, I'm beginning to see that dump -0af TO ( - or device/file) FROM (device or directory/file) and restore -rf (TO curr.dir FROM device or file) or dump -0af - (FROM device or file) | restore -rf - (TO device or directory) or do I still not have it right? It's the stdout and stdin that makes me stumble. Do I really need to mount the partitions or can I just dump and restore from device to device directly? The manual says I should be able to dump restore across the lan too... Basically. on dump, the filesystem to be dumped comes last on the command line. The place to write the dump is that which is named right after the -f If there is no -f then it defaults to a tape device. If a '-' follows the -f, then it writes to standard out. The name must be the first thing after the -f or it will get confused. On restore, there is no filesystem name to come last. You have to be cd-ed to where you want it written. So, the only thing to consider is its -f. For restore, that tells from where to read. If it is a device or file name, it reads from that. If it is '-' it reads from standard in. If there is no -f it defaults to the tape device. Again, the name must be the first thing after the -f if there is a -f. The pipe '|' tells the system to take the standard out from the first process and feed it to the standard in of the second. That passing is not a function of dump/restore, but of the system. The pipe just passes data. It doesn't force the utilities (dump or restore) to do anything about it. But, putting the '-' on dump and restore tells them to pay attention to standard out/in. You can cause dump to send standard out over the net and restore to read standard in from the net.I used to do that, but it has been a long time and I don't have time at the moment to go and check the details to make sure I tell it correctly. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best procedure for full backup of live system
On Wed, Oct 14, 2009 at 08:42:47PM -0700, Nerius Landys wrote: My server is increasingly having important work stored on it, and I need to start taking backups of a lot of directories, especially /home, /opt, /etc, /usr/local/etc, and maybe others. The ideal backup (and what I've done in the past) is to take a full low-level dd image of the disk while the system is down (this is easy to do in a situation where you have dual boot). Or, since the output of dd would take up tons of space and would only be usable on an identical hard drive, use dump to take the backup while the machine is turned off (again easy to do on a dual boot). But now, I cannot bring down the machine. My plan is to do a tar gzip of / on the fly, and pipe that to ssh (remote machine). However, the system is live, and files will be in the progress of changing. My question is, what is the recommended procedure of taking a full backup on a live system? Ideally, if my hard drive were to crash, I would like to have such a backup so as to make it possible to copy over the entire backup to a new identical harddrive without doing any reinstall or configuration. Should I use tar/gzip? dump? What exact command should I use? I guess I'll back up all of / including system files, because there is not too much data. I will be piping the output to ssh. Use dump(8) to back up each filesystem that is important and that cannot be easily recreated (such as by reinstalling). Don't bother with any of that tar and dd stuff as long as the dump will be read on a similar system (FreeBSD). Use the -L switch for making a dump on a live filesystem. It forces a snapshot so files are not in transition while the backup is done - or rather, makes it so the backup is of an intact image. Your big issue then is where to write the dump, how often to do it and how many copies you want to keep of it. You can do full dumps and dumps of just what has changed since the last time a file was dumped. I call those full dumps and change dumps. The documentation referrs to them as level 0 for full dump and level 1-9 as the change dumps. The man pages give a complicated scheme for managing full and change dumps. Probably most people really need only a level 0 and a level 1, maybe a level 2. Basically the point of the change dumps is to make smaller backup images which takes less time and less media. You only make the full dump (level 0) once every week or every month - whatever your needs are. Then, in between you only dump the files that have changed since the last full dump. If that change dump file gets too big as well, then you jump to the next level on change dump. So, you do a level 0, then, the next day a level 1. If it is small (meaning only a relatively few files have changed) then the third day you still make a level 1. If the level 1 dump is now real big (meaning a lot of files changed) then on day 4 you go to a level 2 dump, etc. It is probably a good idea to regularize the process of choosing levels. That is why the man page has such a complicated scheme that covers all conditions. But, as I indicated, most people with a personal or office/department level server often need only a need the regular full (level 0) dump, plus a daily level 1 dump in between the full dumps.In fact, I have some servers that are small enough that I just make level 0 dumps each time. Now, if you have a big system with lots of new files and changed files all the time, then you will have to organize your dumps in a more sophisticated manner. Generally, level 0 dumps take whatever amount of media they need to contain the whole filesystem. Then, for the change dumps (level 1..9) you hope to keep then to only one unit of media. If a change dump goes over one unit of media, then you move up a level the next time. The same goes for if the change dump starts to take a lot of extra time. As for media, it can be to an external disk, a tape or over the net to some big storage space. Try to spread it out so that each set of dumps is not on the same physical media as other ones - eg rotate your media. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FWD: is this Intel CPU ok for 7.2 AMD64?
On Thu, Oct 15, 2009 at 03:13:49PM +0200, Len Conrad wrote: -- Original Message -- From: Len Conrad lcon...@go2france.com Reply-To: lcon...@go2france.com Date: Wed, 14 Oct 2009 22:48:26 +0200 the FreeBSD 6.2 i386 dmesg.boot shows: CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,RSVD2,MON,DS_CPL,EST,TM2,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM Logical CPUs per core: 2 real memory = 3220963328 (3071 MB) avail memory = 3150913536 (3004 MB) ACPI APIC Table: DELL PE BKC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 32-55 on motherboard ioapic2 Version 2.0 irqs 64-87 on motherboard thanks, Len == So, is there a definite, unique answer? Yes. Does it matter whether I run IA64 or AMD64 in the above Dell 1850? Yes. Run AMD64. It is not an Itanium which is the IA64. It is a I686 which is the long standing ...86 family which, in 64 bit is supported on FreeBSD by AMD64. jerry Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphics card recommendation
On Wed, 14 Oct 2009 08:31:00 -0700 free...@t41t.com free...@t41t.com (free...@t41t.com) replied: I'm in need of a new graphics card for a new computer, that I hope will run FreeBSD (with a strong preference for AMD64) and compiz-fusion on a dual-monitor, which I believe means the 3D acceleration has to be in good working order. I don't really care whether the graphics driver is binary, or freely-licensed. Has anyone bought a recent graphics card that they know to be working in x64 with 3D acceleration? I've heard Nvidea support is probably better than ATI. Some of the GPU choices I see are like GeForce 9400/9500/9600 GT, GSO, and/or GTX+ series or the GTS/GTX 2** series. Are some of those better-supported than others? I didn't see anything recent on this list or the website, and there wasn't much response on IRC. Recommendations would be appreciated. Thanks! nVidia (AMD64) is not supported in 7.x versions of FreeBSD as far as I know. There was some talk of it being supported in 8.x, but I have not heard from anyone actually doing so. All my machines use nvidea cards, and the lack of support for it in FBSD, even after an extended period of time, is a real PIA. -- Jerry ges...@yahoo.com The bold youth of today is very lonely. Poul Henningsen [1894-1967] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTP Client synchronization with a Windows 2003/2008
On Tue, 13 Oct 2009 17:13:16 +0200 Jacques Henry (caramba...@googlemail.com) replied: Hello, I am using a System based on FreeBSD 6.3. On this System an automatically generated ntpd.conf file is generated in order to synchronize the System clock with a NTP Server. I want to use a Windows 2003 or 2008 Server to act as the NTP Server. On the Windows System the NTP Server (Windows Time Service) is *correctly* running. The thing is that even if there are NTP traffic between the client and the Server (NTP Client and Server IP packet), My FreeBSD is not synchronizing at all: freebsd-clientntpq -p 127.0.0.1 remote refid st t when poll reach delay offset jitter === NTP_server 192.168.10.6 2 u 103 102411.037 -587367 0.002 As you can see the offset is huge and never decreases as in a normal way... My ntpd.conf file looks like: --- # File is automatically generated # Do not edit tinker panic 1 tinker step 1 # ntp servers list server 172.30.1.5 # files informations driftfile /etc/ntp.drift # restriction informations restrict default ignore # do not allow request by default restrict 127.0.0.1 # allow localhost for debugging restrict 172.30.1.5 nomodify my ntp.drift file -101.101 I know that maybe the Microsoft NTP/SNTP implementation is not RFC-compliant, but is there a way to configure my NTP client in a more compatible (less strict) way to adjust its time with a Windows Server? You might want to check out these two URL's for starters: http://lists.ntp.isc.org/pipermail/questions/2007-January/012469.html http://msdn.microsoft.com/en-us/library/ms884917.aspx -- Jerry ges...@yahoo.com My folks didn't come over on the Mayflower, but they were there to meet the boat. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: server specification.
On Tue, 13 Oct 2009 12:45:02 -0600 Tim Judd (taj...@gmail.com) replied: Certain OEMs (ahem, Dell) I don't pick due to it's known legacy support or Technical Support unsupporting an OS that they don't get paid for. Even if it's a hardware problem, they ask try to duplicate the problem in windows, then we'll be able to support you. I turn Dell down, when I deal with my customers. I have had excellent results with both Dell and HP. In the case of Dell, twice they have shipped over night parts I required that were under warranty at no cost to myself. I think it is a little naive to feel that a company is suppose to support any product that they are not actively associated with. There cheaper models do use quite a bit of legacy products; however, the intermediate and top end machines are far better. They also offer the customer far more ways to customize the product. -- Jerry ges...@yahoo.com The bugs you have to avoid are the ones that give the user not only the inclination to get on a plane, but also the time. Kay Bostic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: best FBSD version for commercial use.
On Sat, 10 Oct 2009 06:06:39 -0400 jhell jh...@dataix.net wrote: [snip] I will agree with that. And raise that its not a good idea to be part of the early adopter club for commercial use. Somebody has got to go first. As so aptly stated by Robert Crandell, chairman of American Airlines in the late 1990's, If you're not the lead dog, the view never changes. -- Jerry ges...@yahoo.com Let others praise ancient times; I am glad I was born in these. Ovid (43 B.C. - A.D. 18) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: binutils
On Sat, 10 Oct 2009 15:45:39 +0200 (CEST)
Alexander Best (alexbes...@math.uni-muenster.de) replied:
there's a project called binutils in p4 but i don't know anything
about it (version, status, etc.). the problem with binutils from the
portsdir is that even when it's installed gcc still uses the the
base-binaries because gcc is statically linked. so in order to use the
binutils from the ports dir you also have to install a gcc port (which
gets linkey dynamically).
a very dirty workaround is to install binutils from the ports, rename
the base binary you don't want to use anymore and instead create a
link to /usr/local/bin/*.
here's an example. this way i could build mplayer with sse3 support.
although the base gcc (4.2.1 in my case running 9-current) supports
sse3, the base GNU assembler version (2.15) doesn't.
what i did was to install the binutils port,
`mv /usr/bin/as /usr/bin/as_old` and `ln
-s /usr/local/bin/as /usr/bin/as`.
now the base gcc picks up the new GNU assembler binary.
cheers.
alex
oh...and i agree: binutils should be updated. actually a lot of base
code needs to be updated. some of it hasn't been touched for over a
decade. ;)
Is FreeBSD-8.0 also going to continue to use the older version {GNU
assembler 2.15 [FreeBSD] 2004-05-23} or are they updating to the latest
version. If the obsolete version is all ready causing compiler
problems, it would seem like the logical thing to do.
--
Jerry
ges...@yahoo.com
There is brutality and there is honesty.
There is no such thing as brutal honesty.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: binutils
On Sat, 10 Oct 2009 10:53:35 -0400 Lowell Gilbert (freebsd-questions-lo...@be-well.ilk.org) replied: Unfortunately, it's under an unacceptable license. I was not aware of that. What is the problem? Perhaps, if it is not all ready available, the FreeBSD developers can devise some directive to place in the '/etc/make.conf' file that would force the use of the 'port' version instead if it was available in a fashion similar to what is done with OpenSSL; i.e. WITH_OPENSSL_PORT=yes. Perhaps, WITH_BINUTILS_PORT=yes. -- Jerry ges...@yahoo.com Men never do evil so completely and cheerfully as when they do it from religious conviction. Blaise Pascal, Pens_es, 1670 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: binutils
On Sat, 10 Oct 2009 10:35:01 -0700 Chuck Swiger (cswi...@mac.com) replied: On Oct 10, 2009, at 9:34 AM, Jerry wrote: On Sat, 10 Oct 2009 10:53:35 -0400 Lowell Gilbert (freebsd-questions-lo...@be-well.ilk.org) replied: Unfortunately, it's under an unacceptable license. I was not aware of that. What is the problem? Somewhere around binutils-2.17, it switched to using GPLv3. Perhaps, if it is not all ready available, the FreeBSD developers can devise some directive to place in the '/etc/make.conf' file that would force the use of the 'port' version instead if it was available in a fashion similar to what is done with OpenSSL; i.e. WITH_OPENSSL_PORT=yes. Perhaps, WITH_BINUTILS_PORT=yes. That's not a bad idea, although you can likely export PREFIX=/usr and install the binutils port, and get the desired result. The only problem with that is that it would get over written when updating 'world'. I am not sure if a user could exclude binutils from being installed when building world. Nor, am I certain that it would not cause a problem somewhere down the line. I don't like messing with system files. In any case, the FreeBSD developers are going to eventually develop a working relationship with software written using the GPLv3 license. -- Jerry ges...@yahoo.com A widow is more sought after than an old maid of the same age. Addison ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: best FBSD version for commercial use.
On Fri, Oct 09, 2009 at 07:44:04PM -0700, Nerius Landys wrote: My 2 cents, as far as I know 7.1 will be maintained longer than 7.2 according to the freebsd.org website. That is, security fixes will be rolled out for 7.1 a while after 7.2 reaches End Of Life. That made me decide to go with 7.1 when I had to make the switch from 7.0 a few months ago. 8.0 was not out at that time. I don't think that is correct. There must be something unclear there. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: windoz, how do i install it last
On Tue, Oct 06, 2009 at 01:28:31PM +0200, Bertram Scharpf wrote: Hi, Am Dienstag, 06. Okt 2009, 07:05:23 -0400 schrieb Henry Olyer: So I have a FreeBSD system. Is their a way to install windoz? Say, XP-pro? Or whatever... Replace or dual boot? The standard FreeBSD boot manager offers a choice which of the slices 1-4 you want to boot from. Just install #...@% into the first slice and FreeBSD into the second. You weren't listening. The OP said FreeBSD is already in the first slice and wants to know if MS-Win can be installed in a later slice - most presumably so it will not be necessary to reinstall the FreeBSD. jerry Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Getting lphoto to run
FreeBSD-7.2 running Xfce 4 Desktop Environment version 4.6.1 (Xfce 4.6) I am unable to get 'lphoto' to run. This is the output when it initially is started: QSettings::sync: filename is null/empty kbuildsycoca running... QSettings::sync: filename is null/empty Reading Library failed open Creating Default Empty Library QObject::connect: No such signal QDateTimeEdit::lostFocus() QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'unnamed') Traceback (most recent call last): File /usr/local//lib/python2.6/site-packages/Lphoto/lphoto.py, line 720, in module mw = LMainPhoto(app) File /usr/local//lib/python2.6/site-packages/Lphoto/lphoto.py, line 49, in __init__ self.initModePanel(self.mainView) File /usr/local//lib/python2.6/site-packages/Lphoto/lphoto.py, line 344, in initModePanel self.newAlbumButton = self.createToolBarButton(None, buttonadd.png, hb, add a new album) File /usr/local//lib/python2.6/site-packages/Lphoto/lphoto.py, line 303, in createToolBarButton b = QPushButton(label, vb) TypeError: argument 2 of qt.QPushButton() has an invalid type DCOP aborting call from 'anonymous-56132' to 'lphoto' lphoto: ERROR: Communication problem with lphoto, it probably crashed. -- Jerry ges...@yahoo.com In the beginning was the word. But by the time the second word was added to it, There was trouble. For with it came syntax ... John Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Swap and memory optimization
On Thu, Oct 01, 2009 at 09:58:36AM +0200, bsd wrote: Hello, I have a FBSD 6.4p7 box that I use as a mail server - 1Go RAM - RAID1 Works quite well. As I plan to put 100 more mail accounts soon on the server I was wondering if the memory swap was ok on the server considering these figures: last pid: 18956; load averages: 0.04, 0.11, 0.05 up 19+08:36:23 09:53:38 125 processes: 1 running, 124 sleeping CPU: 0.0% user, 0.0% nice, 1.5% system, 0.4% interrupt, 98.1% idle Mem: 499M Active, 70M Inact, 362M Wired, 41M Cache, 111M Buf, 20M Free Swap: 2000M Total, 160M Used, 1840M Free, 8% Inuse Though It looks good to me - the server swaps a bit (between 8 to 14%) and there is not much memory left. Let me know what you think about these figures. Unless something else is going on or you are running some commercial server that gets huge amounts of traffic, you should have no capacity problem with this setup. You might want to upgrade to a more recent FreeBSD. jerry Thanks. Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz P Please consider your environmental responsibility before printing this e-mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: backups cloning
potentially really trash things. So, if you want to build a disk with dump-restores you want it to be on another disk. If you want, you could dump a filesystem and write the dump to a file on any filesystem that has room for it. After all, it is just a file. Or you could create a new directory where there is lots of room and do the dump piped to restore in to that new directory. But, there is not much reason to do that unless you are just practicing with dump and restore. Doing that you haven't really created anything except a copy of stuff in a place where it would also be lost if the disk failed. So, it only makes sense to write a dump to some media other than where you are reading it from - another disk, tape, wherever. I am beginning to think that you have to have a system running and dumpt to another disk on that system and then remove that disk and install in another box and boot from that? Am I getting close? I know it's a lot to ask, but then, I know you guys are capable... :-) You are making it much more complicated than necessary. It is true that the most complete and pristine set of dumps can only be made from a system that is down in single user mode or even more so, from a separate boot from a fixit CD or other boot device. But in reality, that is rarely done. Systems cannot be taken down and left down for great lengths of time like that. So, dumps are normally made on and from running systems. Where you write the dump to and in what form is determined by what use you want to make of the dump as I mentioned above. Really, just pick your media. The dump system still assumes it is tape so if you don't use any -f then it will try to write to a tape drive. But, -f somefile or -f somedevice is now the norm. ( a pipe '|' is common if it goes directly to a restore or goes over the net to another host) Then write the dump to it and you have a backup. I do not know why your root dump is not working. You said there are errors, but I am not used to using my telepathic powers so I am having trouble seeing what those errors are. It might clear up a little if you reported them in your post, though I can't be sure of that. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: backups cloning
On Tue, Sep 29, 2009 at 10:48:30PM -0400, PJ wrote: Polytropon wrote: On Tue, 29 Sep 2009 21:26:19 -0400, PJ af.gour...@videotron.ca wrote: But what does that mean? But ad2s1a has just been newfs'd - so how can it be dumped if its been formatted? When you're working on this low level, triple-check all your commands. Failure to do so can cause data loss. In the example you presented, ad1 was the source disk, ad2 the target disk. You DON'T want to newfs your source disk. And what exactly does stdout mean? This refers to the standard output. In most cases, this is the terminal, the screen, such as # cat /etc/fstab will write the /etc/fstab to stdout. If you redirect it, for example by using or |, you can make stdout a file, or the input - stdin - for another program. This is how the dump | restore process works: It leaves out the use the tape or use the file, but instead directs the output of dump - the dump itself - to the restore program as input to be restored. What is dump doing? outputting what to where exactly? The dump program is outputting a dump of the specified partition to the standard output, which in this case is directly trans- mitted to the restore program, which picks it up and processes it = restores it. I don't see it or should I say, understand this at all. Have a look at the command line again, simplified: # dump -0 -f - /dev/ad0s1a | restore -r -f - Run the dump program, do a full backup of the 1st partition of the 1st slice of the 1st disk, write this dump to the standard output, pipe this output to the restore program, do a full restore, read the dump to be restored from standard input. and then the restore is from what to where? The restore program gets the dump to be restored from the standard input - remember, that's the output of the dump program - and writes it to the current working directory. That's the reason why you should always check with # pwd in which directory you're currently located, because that will be the place where the restored data will appear. write error 10 blocks into volume 1 do you want to restart: Could you present the command you're actually using, especially with where you issued it from? Duh I think I see where this is leading... I'm pretty sure it was issued from / which makes it redundant, right? I should have issued it from somewhere else, like from home, usr or whatever but not from / as that is what I was trying to dump :-[ No, that is not a problem. You can be in any directory and do the dump command, except if you want that restore to work you have to be in the receiving filesystem/directory. I just noticed that I missed that you were newfs-ing the wrong partition. That was the one you wanted to read from and your newfs would wipe out everything on it.If you do the newfs - a good idea - it has to be on the new filesystem you will be writing to. jerry The first time I tried with -L the error was 20 blocks... Both the slices for dump from and to are same size (2gb) and certainly not full by a long shot ( if I reccall correctly, only about 14% is used) I'm not sure where you put the dump file. Write error seems to indicate one of the following problems: a) The snapshot cannot be created. b) The dump file cannot be created. And what's this about a snapshot? AFAIK, I'm not making a snapshot; anyway, there is no long pause except for the dumb look on my face upon seeing these messages. Check man dump and search for the -L option. The dump program, in order to obtain a dump from a file system that's currently in use, will need to make a snapshot because it cannot handle data that is changing. So it will dump the data with the state of the snapshot, allowing the file system to be altered afterwards. As it is, I am currently erasing the brand new 500gb disk on which I want to restore. Excellent. Things started out really bad... don't u;nderstand what is going on. Polite question: Have you read the manpages and the section in the Handbook? Yes... but my brain can't handle it all so quickly... and being as impatient as I am, I tend to miss things on the run... it usually comes to me sooner or later... unfortunately, it's more often later than sooner... I've been reading the stuff in the man pages, and getting more confused by googling... Actually, I've been trying to get things straightened ot for at least 3 days already. I installed a minimal 7.2, booted up and turned to another computer to do some serious work. About 2 hours and 49 minutes later I notice messages on the 7.2 about a page fault or something like that and then the system reboots. This often indicates a hardware problem
Re: backups cloning
On Wed, Sep 30, 2009 at 05:08:05AM +0200, Polytropon wrote: Forgot to mention this: On Tue, 29 Sep 2009 22:23:00 -0400, PJ af.gour...@videotron.ca wrote: 1. will the s1a slice dump the entire system, that is, the a, d, e, f and g slices or is it partitions? The ad0s1 slice (containing the a, d, e, f and g partitions) can be copied 1:1 with dd. By using dump + restore, the partitions need to be copied after another. In each case, the entire system will be copied. For this purpose, even the long lasting # dd if=/dev/ad0 of=/dev/da0 bs=1m # dd if=/dev/ad0 of=/dev/da0 bs=512 count=1 method can be used. It can be used, but it is not a good way to do it. That is because it copies sector by sector and the new disk/filesystem may not match the old exactly. Besides when it is newly written on a file by file basis, it can be more efficiently laid out and accomodate any changes in size and sector addressing. dd cannot do that. jerry -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Swaping Fs (from ntfs to ufs), or ntfs3g?
On Tue, Sep 29, 2009 at 09:14:38AM +0100, Jeronimo Calvo wrote: great I will do a massive Cp as both fs are mounted under BSD, (ntfs just with read access)... should you suggest guy to do a normal #cp /media/DATAWIN /media/UFShd as there is no any soft and hard links on this partition... will be fine? Are their subdirectories that need copying too. If so, use the -R flag. You might want to do cp /media/DATAWIN/* /media/UFShd/. jerry Thanks! 2009/9/28 Jerry McAllister jerr...@msu.edu: On Mon, Sep 28, 2009 at 05:06:34PM +0100, Jeronimo Calvo wrote: Hi folks, Scenario: 3 hds, 1 of them with a NTFS partition and loads of media on it, I was thinking to activate ntfs3g under Freebsd 7.2 STABLE, but since Im having this partition since a while... and i will no need to have it on this FS, what you recommed for moving this partition into ufs format... to make it 100% reliable? what steps will you do? I would suggest you create the UFS filesystem, then tar up the files in the NTFS partition that you want to move and then untar that on the FreeBSD UFS (or UFS2) filesystem. You might have to install a tar utility on the MS system. You can also just mount the NTFS file system on FreeBSD and then do a massive copy of the files you want in to the UFS[2] filesystem. In both the case of doing a tar or a mass copy (cp) wildcards are good. Hopefully you have the files on the NTFS organized reasonably in directories. If you don't and they are interspersed with lots of files you do not want to copy, then it can get tedious but you can still do it. It will just need much more manual attention. jerry BR! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Whic mail server?
On Sun, Sep 27, 2009 at 06:01:22AM -0700, Aflatoon Aflatooni wrote: Hi, I am running a server that is acting as the mail server for only internal users (about 50 users). Currently we are running Sendmail, but reading on other discussions I noticed that qmail and other programs are suggested. I am wondering if qmail is thought to be better than sendmail. Is there a matrix of features and functionalities that would compare the different mail servers? No, sendmail is as good or better, especially in a situation such as you describe.Some people believe that sendmail can be hard to configure, and it is a little arcane to do it directly in the sendmail.cf file. But there are things that help nowdays. Anyway, if you already have it configured and working your are past that already. Most of the things these others complain about being to complicated are more exotic and special-cased stuff. Then they become religious zealots about their favorites. Any suggestions on spam filters like spam-assassin? Learn to use procmail. jerry Thank you ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Whic mail server?
On Mon, Sep 28, 2009 at 09:49:37AM -0400, Jerry McAllister wrote: On Sun, Sep 27, 2009 at 06:01:22AM -0700, Aflatoon Aflatooni wrote: Hi, I am running a server that is acting as the mail server for only internal users (about 50 users). Currently we are running Sendmail, but reading on other discussions I noticed that qmail and other programs are suggested. I am wondering if qmail is thought to be better than sendmail. Is there a matrix of features and functionalities that would compare the different mail servers? No, sendmail is as good or better, especially in a situation such as you describe.Some people believe that sendmail can be hard to configure, and it is a little arcane to do it directly in the sendmail.cf file. But there are things that help nowdays. Anyway, if you already have it configured and working your are past that already. Most of the things these others complain about being to complicated are more exotic and special-cased stuff. Then they become religious zealots about their favorites. Any suggestions on spam filters like spam-assassin? Learn to use procmail. Sorry, I meant to say spamassasin + procmail jerry jerry Thank you ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Question about FreeBSD installation procedure
to send PM-8 back for a refund. A free utility that works quite well, though with less pretty graphics is 'gparted'. Download it and make a boot disk from it. Boot it up. Ignore warnings of not being able to book if the boot sector is beyond a certain number. That is archaic. Follow the instructions. A couple of extra things to know. Most of the free utilities are a bit old and do not handle MS NTFS file systems properly. gparted seems to be OK. That is one thing Partition Magic 7 does well. The other is that I have heard that MS Vista totally screws things up. It seems to cause problems with MBRs, but I don't know just what they are. I haven't had to mess with Vista yet and am not wishing to ever see it on any of my machines.I have not heard about Win-7 yet and if it presents any particular problems. I have attached a copy of the screenshot showing the partition table; I wanted to install FreeBSD into sda8. Attachments are not allowed in the list so it was stripped. Can this be done. Well, hopefully you mean 20GB and 2 GB instead of 20 MB and 2 MB. If you have a free 20 GB primary-partition, sure it can be done. It is a little small for todays standards, but FreeBSD will install and run from that much. Just plop the FreeBSD install CD in the drive and boot it up. You might have to tinker with the BIOS if the CD is not in the BIOS boot list. jerry Thank you in anticipation. -- Bret Busby Armadale West Australia .. So once you do know what the question actually is, you'll know what the answer means. - Deep Thought, Chapter 28 of Book 1 of The Hitchhiker's Guide to the Galaxy: A Trilogy In Four Parts, written by Douglas Adams, published by Pan Books, 1992 -- Forwarded message -- Date: Sat, 26 Sep 2009 21:28:37 +0800 From: Bret Busby b...@busby.net To: b...@mailserver Subject: screenshot of partition table of laptop -- -- Bret Busby Armadale West Australia .. So once you do know what the question actually is, you'll know what the answer means. - Deep Thought, Chapter 28 of Book 1 of The Hitchhiker's Guide to the Galaxy: A Trilogy In Four Parts, written by Douglas Adams, published by Pan Books, 1992 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Swaping Fs (from ntfs to ufs), or ntfs3g?
On Mon, Sep 28, 2009 at 05:06:34PM +0100, Jeronimo Calvo wrote: Hi folks, Scenario: 3 hds, 1 of them with a NTFS partition and loads of media on it, I was thinking to activate ntfs3g under Freebsd 7.2 STABLE, but since Im having this partition since a while... and i will no need to have it on this FS, what you recommed for moving this partition into ufs format... to make it 100% reliable? what steps will you do? I would suggest you create the UFS filesystem, then tar up the files in the NTFS partition that you want to move and then untar that on the FreeBSD UFS (or UFS2) filesystem.You might have to install a tar utility on the MS system. You can also just mount the NTFS file system on FreeBSD and then do a massive copy of the files you want in to the UFS[2] filesystem. In both the case of doing a tar or a mass copy (cp) wildcards are good. Hopefully you have the files on the NTFS organized reasonably in directories.If you don't and they are interspersed with lots of files you do not want to copy, then it can get tedious but you can still do it. It will just need much more manual attention. jerry BR! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Requesting Service
On Mon, Sep 28, 2009 at 04:32:52PM -0400, don carlos wrote: Hello and Good day, We are looking for a company that provides on-site services on installing FreeBSD mailserver. We currently have a FreeBSD based mailserver running and we need to upgrade it. We need all emails and addressbooks to be transferred into the new server. We will provide the hardware. Can you please advise if you do such services or if you could refer us. In what part of the world would this be? jerry Many Thanks, Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Whic mail server?
On Sun, 27 Sep 2009 06:01:22 -0700 (PDT) Aflatoon Aflatooni aaflato...@yahoo.com wrote: Hi, I am running a server that is acting as the mail server for only internal users (about 50 users). Currently we are running Sendmail, but reading on other discussions I noticed that qmail and other programs are suggested. I am wondering if qmail is thought to be better than sendmail. Is there a matrix of features and functionalities that would compare the different mail servers? Any suggestions on spam filters like spam-assassin? Qmail is not, nor has it been, actively supported for years. Personally, I use Postfix. Is is far easier IMHO to configure that Sendmail and it is actively supported. The developer regularly answers questions on the Postfix forum. Amavisd-new http://www.ijs.si/software/amavisd/ works fine with Postfix. You might want to stay away from MailScanner http://www.mailscanner.info/ though. The Postfix author discourages its use and Postfix does not support it. -- Jerry ges...@yahoo.com Every cloud has a silver lining; you should have sold it, and bought titanium. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Warning: PHP Update from 5.2.10 to 5.2.11 and FastCGI
On Sun, 27 Sep 2009 10:03:37 -0400 Michael Powell nightre...@hotmail.com wrote: Found the problem. The mailheader patch for 5.2.10 clashes with the Suhosin patch for 5.2.11. I rebuilt PHP with Suhosin and without mailheader patch and now it's all happy again. Now my php -v reads like Jerry's. Did you file a PR for this? -- Jerry ges...@yahoo.com Remembering is for those who have forgotten. Chinese proverb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Warning: PHP Update from 5.2.10 to 5.2.11 and FastCGI
On Sat, 26 Sep 2009 13:34:25 -0400 Michael Powell nightre...@hotmail.com wrote: Today I did a portupgrade of PHP from 5.2.10 to 5.2.11. This broke both lighttpd and Apache web servers, on which I run PHP as FastCGI. I do not know if this affects those who use mod_php as I do not use it. I use mod_fcgid instead. Execute php -v at a prompt and it will spew the following and segfault. testbed suhosin[48982]: ALERT - canary mismatch on efree() - heap overflow detected (attacker 'REMOTE_ADDR not set', file 'unknown') If you are using FastCGI the workaround is to do make config in lang/php5 and deselect the Suhosin option. There is something very broken in the Suhosin patch as far as CLI and FastCGI is concerned. -Mike No problems on my machines. PHP 5.2.11 with Suhosin-Patch 0.9.7 (cli) (built: Sep 24 2009 19:08:59) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies Did you rebuild all of the ports that depend on PHP? I used portmanager with the '-p' option to update all dependencies. portmanager -u -l -y -p That should get everything working.Update you ports system first however. -- Jerry ges...@yahoo.com A life spent in search of the perfect hash brownie is a life well spent. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 02:48:58PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 12:25:38 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: [snip] It's still a little unclear. If you want the FreeBSD systems to participate in the Windows networking, look at mount_smbfs and Samba. I want to be able to access a FreeBSD box from another FreeBSD box. I rarely access a Windows machine from FreeBSD as it is just easier to do it the other way around. Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? jerry Anyway, I have been given a few ideas to follow upon. Thanks! -- Carmel car...@hotmail.com SAFETY I can live without Someone I love But not without Someone I need. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 03:40:41PM -0500, David Kelly wrote: On Tue, Sep 22, 2009 at 03:29:43PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 14:08:21 -0500 David Kelly dke...@hiwaay.net wrote: [snip] It would, but he's approaching the problem with Windows-colored glasses. I am not sure what that is even suppose to mean, so I'll just ignore it. It means you are trying to make Unix conform to your Windows habits. For security, simplicity, and security (yes, security twice) we are not in the habit of wantonly sharing our file systems. Historically remote login has been difficult on Windows systems while file(system) sharing has been relatively easy so Windows Administrators learned how to manage systems by pushing files around on shared file systems. I'm saying it sounds an awful lot like that is what you are trying to do. If so then you will quickly find Unix doesn't like to let root (Administrator) easily cross system boundaries. Really, it sounds like this guy is a candidate for AFS. Actually probably serious over-kill for his situation, but it does wonders.I think there is now (again) an OpenAFS for FreeBSD. AFS plus X-windows would more than do it. jerry Meanwhile others have listed a multitude of utilities for shooting files across multiple machines, including simple terminal login and more advanced GUI X11 login. None of which use shared file systems as their core connection method. Expanding on what I said earlier, if joe is userid 1001, do not reuse 1001 on any other machine unless joe has an account there too. Unix file ownership is by userid and groupid *numbers*. The number doesn't have to be defined in the password or group databases to be used. Most file sync and archivers only use the numbers. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 03:27:35PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 14:53:17 -0400 Jerry McAllister jerr...@msu.edu wrote: [snip] Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? It will put a key there for every place you go to with ssh. The only annoyance is when you upgrade a machine, or otherwise cause the key for a machine to change, you may have to go in to that file and manually delete the old key before it will store another one for the same address. That is easy, but I always forget to do it until the key is refused, and of course, I am in a hurry. jerry -- Carmel car...@hotmail.com Lady Luck brings added income today. Lady friend takes it away tonight. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 04:22:54PM -0500, David Kelly wrote: On Tue, Sep 22, 2009 at 04:46:49PM -0400, Jerry McAllister wrote: On Tue, Sep 22, 2009 at 03:27:35PM -0400, Carmel NY wrote: I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? It will put a key there for every place you go to with ssh. I think this is the place one puts the public key of accounts (not the host) from which one is *coming* from that one wishes to accept login without further challenge. ~/.ssh/known_hosts automatically (prompted first time) records the host public key of places you have been so as to warn you that the connection is not to a previously known machine. You are right. I didn't look at the file name closely. You can still have more than one. jerry -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: postfix + cyrus sasl: no go
On Sat, 19 Sep 2009 06:33:00 -0700 (PDT) Colin Brace c...@lim.nl wrote: Hi all, I have compiled postfix with the SASL2 option. After creating the saslpass file, I added the appropriate lines to main.cf: smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/usr/local/etc/postfix/saslpass smtp_sasl_security_options = and restarted postfix. However, when I try to send an email, I see these lines in maillog: Sep 19 15:07:19 venus postfix/smtp[75188]: warning: unsupported SASL client implementation: cyrus Sep 19 15:07:19 venus postfix/smtp[75188]: fatal: SASL library initialization Also, postconf -A doesn't return anything. FWIW, postconf -a returns dovecot. Any ideas what is going wrong here? versions: postfix-2.6.5,1 cyrus-sasl-2.1.23 FreeBSD 7.0 This question really belongs on the Postfix forum. In any case: 1) Post the complete output of postconf -n 2) Post the contents of: /usr/local/lib/sasl2/smtpd.conf 3) Please check: http://www.postfix.org/SASL_README.html 4) Post the output of a telnet session to your mail server In the mail/postfix directory, do a make rmconfig then redo the config; i.e., make config. Be sure to enable SASL2. You also will probably need to enable a database format; i.e.,berkley, MySql or whatever you intend to use. If you ever intend to use TLS/SSL, now would be the time to enable it. Then do: make clean make deinstall make reinstall make distclean Check again with a telnet session and post the output if it still does not work. -- Jerry ges...@yahoo.com I was in Vegas last week. I was at the roulette table, having a lengthy argument about what I considered an Odd number. Steven Wright ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: postfix + cyrus sasl: no go
On Sat, 19 Sep 2009 10:12:40 -0700 (PDT) Colin Brace c...@lim.nl wrote: Jerry-107 wrote: 2) Post the contents of: /usr/local/lib/sasl2/smtpd.conf Jerry, this file doesn't exist on my system. Please, check the URL I sent previously. You have SASL2 configured incorrectly. It needs the smtpd.conf file to work correctly. There is an abundance of documentation of the Postfix site describing how to configure the file. Start with the URL I sent you. You really should post on the Postfix forum for best results also. -- Jerry ges...@yahoo.com Why you say you no bunny rabbit when you have little powder-puff tail? The Tasmanian Devil ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Killfiles (was Re: reporter on deadline seeks comment about reported security...)
On Thu, 17 Sep 2009 09:04:58 +0200 Jonathan McKeown j.mcke...@ru.ac.za wrote: On Wednesday 16 September 2009 16:59:27 Paul Schmehl wrote: --On Wednesday, September 16, 2009 06:08:50 -0500 Jerry ges...@yahoo.com The backscatter is useful in a way, in that it confirms that my original reasons for applying an ignore filter on Jerry's email address still apply, but I wish a few more people would just ignore him as well. If he's not trolling for angry responses, I find it hard to see what he's doing here at all, given how little good he has to say about FreeBSD or the people involved with it. Ah,boo-hoo. Since I am a believer in free speech and vehemently anti censorship you find my beliefs at odds with your totalitarian socialistic/fascist concepts. Nothing proved the failure of Communism like the building of the Berlin wall. Your use of kill filters, and continued advocacy of censorship and withholding of vital news confirms your political alliance. By the way, I love the way you just 'trolled' into, hijacked the thread and modified the 'subject'. Real class act on your part. -- Jerry ges...@yahoo.com Serfs up! Spartacus ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CD doesn't eject from the drive.
On Wed, Sep 16, 2009 at 09:22:10PM -0700, Yuri wrote: I have PIONEER Model DVD-RW DVR-112D. I started the command cdda2wav -v255 -D5,0,0 -B -Owav to grab audio but stopped it with Ctrl-C. Now disk doesn't eject. Both eject command and cdcontrol -f /dev/acd0 eject commands hang, and system log gets messages, see below. It seems like a bug in atapi driver, since it didn't clear the state of cdrom hardware after controlling app died. Anybody knows how to eject the disk now without rebooting? Do you have some process active in the CD image - such as is some process or shell (X-window or whatever) CD-ed to somewhere in the mount point of the DVD.eg, say you mounted the DVD at /cdrom and then did a cd /cdrom/song or whatever or some process you were using such as the 'cdda2wav' utility CD-ed to it and was left there.For example, after you did the CTRL-C, it quit right there and stayed CD-ed to the image. In that case, it will not eject, either under program control or manually. The solution is to make sure there is no process or shell that is CD-ed to the image. jerry 72-STABLE. Yuri messages acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request acd0: WARNING - TEST_UNIT_READY taskqueue timeout - completing request directly acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request aaccdd00:: WWAARRNNIINNGG -- PRREEAVDE_NTTO_CA LtLaOsWk qtuaesukeq uteiumee otuitm e-o ucto m-p lceotmipnlge trienqgu ersetq udeisrte cdtilryec tly acd0: WARNING - PREVENT_ALLOW freeing taskqueue zombie request acd0: WARNING - TEST_UNIT_READY taskqueue timeout - completing request directly acd0: WARNING - READ_TOC freeing taskqueue zombie request ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reporter on deadline seeks comment about reported security bug in FreeBSD
On Tue, 15 Sep 2009 23:47:10 -0700 per...@pluto.rain.com wrote: Jerry ges...@yahoo.com wrote: Waiting until someone is harmed is tantamount to being an accomplice to the act. And providing details of a currently-undefendable vulnerability to a black hat who did not previously know about it, thereby enabling the black hat to perpetrate harm that would otherwise not have occurred, isn't? The simple act of publishing the fact that a know exploit exists for a given program compromises nothing. Example: WARN: The following program(s) have known exploits. PROGRAM: prog-name PROGRAM VERSION: 2.4 OS: FreeBSD-7.2+ EXPLOIT: Potential to render HD inaccessible PATCH: NONE AVAILABLE SUGGESTION: If prog-name is not imperative to system performance, remove it and consider using a similar product by another author. A simple solution that affords the end user the right to make an informed decision. I realize that governments, especially socialistic/fascists ones use the terms 'censorship' and 'secret' with the term 'For their own good' interchangeable. I would hate to see the open-source community, especially FBSD embracing that philosophy. -- Jerry ges...@yahoo.com Progress is impossible without change, and those who cannot change their minds cannot change anything. George Bernard Shaw ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade broken
On Wed, 16 Sep 2009 11:18:39 +0200 DA Forsyth d.fors...@ru.ac.za wrote: [snip] I saw someone ask about this in Google Groups on the 14th but he has not got an answer yet, so I am not the only one. How do I fix this? You could try the following; 1) Update your ports tree. 2) Remove: /var/db/pkg/pkgdb.db 3) Run: /usr/local/sbin/pkgdb -Ffuv 4: Run: /usr/local/sbin/portsdb -fUu 4) Run: /usr/sbin/pkg_version -vIL= Now run portupgrade as you normally do and see what transpires. If that still fails, install /usr/ports/ports-mgmt/portmanager Then run it as thus: portmanager -u -l -y -p I have had great success in getting updates completed successfully with portmanager when portupgrade and portmaster both crapped out. I would suggest that you consider deleting the contents of the /usr/ports/distfiles prior to running any of the above port utility programs. -- Jerry ges...@yahoo.com There is no comfort without pain; thus we define salvation through suffering. Cato ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reporter on deadline seeks comment about reported security bug in FreeBSD
On Tue, 15 Sep 2009 07:18:26 -0400 Bill Moran wmo...@potentialtech.com wrote: Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: On Monday 14 September 2009 23:46:42 David Kelly wrote: On Mon, Sep 14, 2009 at 05:13:54PM -0400, ill...@gmail.com wrote: Am 2009/9/14 Dan Goodin dgoo...@sitpub.com writhed: Hello, Dan Goodin, a reporter at technology news website The Register. Security researcher Przemyslaw Frasunek says versions 6.x through 6.4 of FreeBSD has a security bug. He says he notified the FreeBSD Foundation on August 29 and never got a response. We'll be writing a brief article about this. Please let me know ASAP if someone cares to comment. Has anyone submitted a PR about this? Przemyslaw Frasunek has PR's posted but none recent. IMO if a PR is not submitted then one has *not* informed the Powers That Be. Wrong. Security bugs should be reported to the security team, not PR'd. It's typical for security issues to be kept hushed until a fix is ready. As a result, there are usually no PRs, and in the case where the person who discovered the problem is amenable, there is no public discussion at all until a fix is available. Apparently, Mr. Frasunek started out down that path, which is admirable. It seems as if he doesn't have much patience, however, since he thinks that only 2 weeks is enough time to fix a security problem and QA the fix. I usually discover security problems with updates I receive from http://www.us-cert.gov/. Aren't FreeBSD security problems reported to their site? If not, why? IMHO, keeping users in the dark to known security problems is not a serviceable protocol. -- Jerry ges...@yahoo.com If there is a possibility of several things going wrong, the one that will cause the most damage will be the one to go wrong. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reporter on deadline seeks comment about reported security bug in FreeBSD
On Tue, 15 Sep 2009 11:13:31 -0400 Bill Moran wmo...@potentialtech.com wrote: In response to Jerry ges...@yahoo.com: On Tue, 15 Sep 2009 07:18:26 -0400 Bill Moran wmo...@potentialtech.com wrote: Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: On Monday 14 September 2009 23:46:42 David Kelly wrote: On Mon, Sep 14, 2009 at 05:13:54PM -0400, ill...@gmail.com wrote: Am 2009/9/14 Dan Goodin dgoo...@sitpub.com writhed: Hello, Dan Goodin, a reporter at technology news website The Register. Security researcher Przemyslaw Frasunek says versions 6.x through 6.4 of FreeBSD has a security bug. He says he notified the FreeBSD Foundation on August 29 and never got a response. We'll be writing a brief article about this. Please let me know ASAP if someone cares to comment. Has anyone submitted a PR about this? Przemyslaw Frasunek has PR's posted but none recent. IMO if a PR is not submitted then one has *not* informed the Powers That Be. Wrong. Security bugs should be reported to the security team, not PR'd. It's typical for security issues to be kept hushed until a fix is ready. As a result, there are usually no PRs, and in the case where the person who discovered the problem is amenable, there is no public discussion at all until a fix is available. Apparently, Mr. Frasunek started out down that path, which is admirable. It seems as if he doesn't have much patience, however, since he thinks that only 2 weeks is enough time to fix a security problem and QA the fix. I usually discover security problems with updates I receive from http://www.us-cert.gov/. Aren't FreeBSD security problems reported to their site? If not, why? IMHO, keeping users in the dark to known security problems is not a serviceable protocol. Because releasing security advisories before there is a fix available is not responsible use of the information, and (as is being discussed) the fix is still in the works. I disagree. If I have a medical problem, or what ever, I expect to be informed of it. The fact that there is no known cure, fix, etc. is immaterial, if in fact not grossly negligent. Being keep ignorant of a security problem is as foolish a theory as Security through Obscurity. I find the http://www.us-cert.gov/ updates invaluable. The fact that apparently FBSD does not encompass them I find discomforting. BTW, please do not CC: me. I am subscribe to the list and do not need multiple copies of the same post. -- Jerry ges...@yahoo.com There is no sin but ignorance. Christopher Marlowe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reporter on deadline seeks comment about reported security bug in FreeBSD
On Tue, 15 Sep 2009 13:18:29 -0400 Bill Moran wmo...@potentialtech.com wrote: On Tue, 15 Sep 2009 13:03:50 -0400 Jerry ges...@yahoo.com wrote: On Tue, 15 Sep 2009 11:13:31 -0400 Bill Moran wmo...@potentialtech.com wrote: In response to Jerry ges...@yahoo.com: I usually discover security problems with updates I receive from http://www.us-cert.gov/. Aren't FreeBSD security problems reported to their site? If not, why? IMHO, keeping users in the dark to known security problems is not a serviceable protocol. Because releasing security advisories before there is a fix available is not responsible use of the information, and (as is being discussed) the fix is still in the works. I disagree. If I have a medical problem, or what ever, I expect to be informed of it. The fact that there is no known cure, fix, etc. is immaterial, if in fact not grossly negligent. This is a stupid and non-relevant comparison. A better comparison would be if I realized that you'd left your car door unlocked in a less than safe neighborhood. Would you rather I told you discreetly, or just started shouting it out loud to the neighborhood? Wait, I know the answer, if I see _your_ car unlocked, I'll just start shouting. The fact is, that you do in fact notify me. Keeping important security information secret benefits no one, except for possibly those responsible for the problem to begin with who do not want the knowledge of the problem to become public. A multitude of software, such as Mozilla, publish known security holes in their software. The ramifications of allowing a user to actively use a piece of software when a known bug/exploit/etc. exists within it is grossly negligent. Being keep ignorant of a security problem is as foolish a theory as Security through Obscurity. No, it's not. And I don't even want to hear your ill-fitting metaphor for how you arrived at that conclusion. I find the http://www.us-cert.gov/ updates invaluable. The fact that apparently FBSD does not encompass them I find discomforting. You're missing the fact that FreeBSD's security issues _are_ listed there, when appropriate. Your obvious ignorance of how things operate absolves you of any right to complain. BTW, please do not CC: me. I am subscribe to the list and do not need multiple copies of the same post. Whine me a river, for crying out loud. List policy on this list since the Dawn of Time has been to CC the list and the poster. I'm not going to check with everyone on the list to see if they're subscribed or not. Don't like it? Get off the list. I just check the FreeBSD list web page, http://lists.freebsd.org/mailman/listinfo/freebsd-questions and failed to find any indication that CC:ing was the desired posting response. In fact, except for a few, perhaps one or two others, I am not aware of any perpetual CC:'s on this list. Then again, I doubt that they feel as threatened when their beliefs are questioned. Perhaps you should seek professional help for your anger issues. Now, if you don't like that, KISS MY ASS. -Bill -- Jerry ges...@yahoo.com If it doesn't smell yet, it's pretty fresh. Dave Johnson, on dead seagulls ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reporter on deadline seeks comment about reported security bug in FreeBSD
On Tue, 15 Sep 2009 20:51:40 +0200 Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: Please inform yourself properly before assuming you're right. Mozilla does not by default publish vulnerabilities before a fix is known. In some cases publishing has been delayed by months. The exception is when exploits are already in the wild and a work around is available, while a real fix will take more work. This is also why vulnerabilities are typically not disclosed till a fix is known, because it does not protect the typical user, but puts him in harms way, which is exactly what you don't want. In theory, if I know the details of this particular exploit, I can patch my 6.4 machines myself, but more realistically, if developers take all this time to come up with a solution that doesn't break functionality the chances that I and more casual users can do this are slim. Meanwhile, the exploit will be coded into the usual rootkits and internet scanners and casualties will be made. That doesn't help anyone. Assume that I have discovered a vulnerability in a widely used, or even marginal for arguments sake, program. I now start to exploit that vulnerability. Now assume that you are responsible for maintaining, that program. Use any job description that suits you for this purpose. Are you claiming that since it may take several months to fix, it is better to let users be exploited rather than inform them that there is an exploitable problem in said software? I fine that extremely disturbing. As you can no doubt tell, I am not a believer in the Ignorance is bliss theory. -- Jerry ges...@yahoo.com In the days of old, When Knights were bold, And women were too cautious; Oh, those gallant days, When women were women, And men were really obnoxious. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reporter on deadline seeks comment about reported security bug in FreeBSD
On Tue, 15 Sep 2009 15:28:59 -0400 DAve dave.l...@pixelhammer.com wrote: Jerry wrote: On Tue, 15 Sep 2009 20:51:40 +0200 Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: Please inform yourself properly before assuming you're right. Mozilla does not by default publish vulnerabilities before a fix is known. In some cases publishing has been delayed by months. The exception is when exploits are already in the wild and a work around is available, while a real fix will take more work. This is also why vulnerabilities are typically not disclosed till a fix is known, because it does not protect the typical user, but puts him in harms way, which is exactly what you don't want. In theory, if I know the details of this particular exploit, I can patch my 6.4 machines myself, but more realistically, if developers take all this time to come up with a solution that doesn't break functionality the chances that I and more casual users can do this are slim. Meanwhile, the exploit will be coded into the usual rootkits and internet scanners and casualties will be made. That doesn't help anyone. Assume that I have discovered a vulnerability in a widely used, or even marginal for arguments sake, program. I now start to exploit that vulnerability. Now assume that you are responsible for maintaining, that program. Use any job description that suits you for this purpose. Are you claiming that since it may take several months to fix, it is better to let users be exploited rather than inform them that there is an exploitable problem in said software? I fine that extremely disturbing. As you can no doubt tell, I am not a believer in the Ignorance is bliss theory. I believe the point that others are trying to make is this. Your example requires that the exploit is known to the blackhats and in use currently. Their example assumes that exploit is only known to those who discovered it. This particular exploit is not believed to be known to the black hats, and not known to be in use currently. Is it better for an exploit to remain a secret and not is use, protecting those that may not get their systems patched in time (as the blackhats *will* most certainly put the exploit to use as soon as they are told about it). Or, let the exploit remain a secret until it is either fixed and a patch made available or discovered in use by blackhats. I think you are both right. If the exploit is not being used, keep it a secret and let the developers design a permanent fix. If the exploit is discovered publicly before the fix is out, warn everyone loudly and provide a workaround. I believe all software I am aware of handles exploits with that method. I am not aware of any infallible method of determining if an exploit is in use. By the time the exploit become common knowledge it is usually too late. Lacking same, I believe in the For Warned is For Armed policy. Waiting until someone is harmed is tantamount to being an accomplice to the act. -- Jerry ges...@yahoo.com Never buy from a rich salesman. Goldenstern ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dump/Restore?
On Sun, Sep 13, 2009 at 06:15:55PM -0700, Chris Maness wrote: I level 0 dump of my server. I lost a file that I need back. Is it possible to use restore like tar and explode it into a directory instead of a pristine partition/mount? Or even better, is it possible to just extract a single file without exploding the whole tape dump? Yes, it is easily done. Just use the 'interactive' option. First, be clear where you want the restores file[s] to go. The official way to do the interactive option is to cd in to the bottom level of the filesystem it is in and do it from there. Restore will then put the files in the directories where they were when the dump was made. So, if the file[s] were in /home/joes/files/ cd to /home and do the restore. It will take care of knowing about the joes and files subdirectories and build them if they are not there. But, really the general recommended way (and the way I do it) to do an interactive restore is to create a designated directory for it and cd in to that. It can be anywhere there is room for the files. So, for example, on some systems I have a large amount of extra space in a filesystem I mount as /work. Within that I create a directory I can recover (for lack of any more imaginative name). I cd to the /work/recover directory and do the interactive restore. eg do: cd /work/recover restore -if dump_device/file Then fish around amongst the directories. When you find the one[s] you need to restore, just do add filename You can keep going and add several files and directories. When you have all that you want/need, then type extract It will ask you what tape to start with. If the dump is a file or of there is only one tape or other device, type 1 If there are more than one tape, type in the number of the last tape. It will search backward through the list of tapes/devices until it finds the files. eg. if there are 7 tapes in the level 0 dump set, start with 7, then give it 6 and then 5, etc. It will quit asking when it finds the files. Finally, it will ask if you want to set ownership of . Say no unless you have a good reason for doing otherwise. Now, if you have used a separate directory as I suggest above, tell restore to quit and then look at the file[s] to make sure they are all right and then manually move then to whichever directory you want. You can then delete them from /work/recover but leave that directory around for when you need it again. This is good for any circumstance when you want to pull just one of a few files out of a dump (or a tar file). I do a similar thing when I untar stuff I have moved over. I make a /work/unroll directory and untar stuff in there and move whay I want to where I want it. This may seem to be an extra unnecessary step, but it cuts down on errors, in my handling directories and file locations. jerry Sorry if the question seems stupid. Chris KQ6UP ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
