Re: unabe to install linux compatibility on freebsd 8.0-R
Hi, thanks for replying On Sun, Feb 21, 2010 at 03:10:05AM +0100, Pieter de Goeje wrote: Somehow your linux.ko is broken, do you perhaps have WITHOUT_LINUX= in /etc/src.conf or /etc/make.conf? I have no src.conf make.conf looks like this: $ cat /etc/make.conf | less CPUTYPE?=athlon64 WITH_MUTT_IMAP_HEADER_CACHE=yes WITH_MUTT_SMTP=yes WITH_MUTT_CYRUS_SASL2=yes # added by use.perl 2009-11-27 15:44:59 PERL_VERSION=5.10.1 Check the last modification date of /boot/kernel/linux.ko, does it correspond (roughly) to the one from /boot/kernel/kernel? Yes, it does: $ ls -la /boot/kernel/linux.ko -r-xr-xr-x 1 root wheel 240K Feb 20 21:50 /boot/kernel/linux.ko* $ ls -la /boot/kernel/kernel -r-xr-xr-x 1 root wheel 6.8M Feb 20 21:08 /boot/kernel/kernel* About the kernel option, try COMPAT_LINUX32. It's a documentation bug. OK I'll try that now, thanks edit: I got this error: ../../../amd64/linux32/linux32_sysvec.c:38:2: error: #error Unable to compile Linux-emulator due to missing COMPAT_IA32 option! mkdep: compile failed *** Error code 1 so I'll add that one, too - seems to be building now cheers -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 ___ 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: Problems With K3b
On Sat, 20 Feb 2010 22:00:10 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: I've already added the necessary line to /boot/default/loader.conf for enabling dma) The file /boot/loader.conf is the file you should edit. The defaults file is read prior to the normal config file, it is overriden by different settings. Using pkg_add for k3b isn't working because I'm using a newer version of some of it's dependencies and that apparently is causing problems (I should have never installed Xv, I had to upgrade jpeg from jpeg-7 to jpeg-8 and that upgrade has caused nothing but problems). I've experienced that fun, too. :-) What error message is issued if you fake install K3B? See pkg_add -rvn (remote, verbose, no-install)? Maybe it will work with the newer version of libjpeg. I realize now that I'm going to have to learn to use the port management tools to help prevent problems like this in the future and that's ok. I've often been told that portmaster would be a good choice. I've used portinstall / portupgrade in the past, but have to say that I honestly prefer pkg_add -r for simplicity. :-) -- 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
Re: Dump questions
On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. Does this mean that a complete copy of the file system is written to .snap directory? No. The snapshot, quite incorrectly explained, is a saved delta between the file system on disk at a given state, to fixate further modifications (that are not included in the dump, of course). Is this the limiting factor that forces a user to use (single user mode) for running dump? Using SUM is for a feeling of comfort only. You can save the time needed for creating the snapshot by entering SUM - and, what's essential - unmount the partitions. This makes sure the underlying file systems aren't modified. 2. What is the worse that will happen if dump is run on live file system with out the -L flag? The dump could not be readable, which would imply that your backup is useless. Can dump recognize this situation and issue an error message? The dump program does what you tell it to do. It does not bother you with questions that you should have asked yourself already. :-) 3. Can dump be told to only dump a particular directory tree? IE /var/log or /usr/port? No. THe dump program operates on file systems. It does not have a concept of files and directories per se. If you plan to work with individual files and directories rather than partitions (file systems), check out tools like cpdup, rsync and the like. -- 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
Re: Problems With K3b
On Sunday 21 February 2010, Programmer In Training wrote: so I deinstalled qt33 and began recompiling it with the intention of enabling thread support. The compile of Qt than proceeded to fail (I've long since closed the window but could retry it to get the specific messages if needed). I need Qt back because I have quite a few apps that require Qt installed I know that this won't help your immediate problem of getting Qt back but it might help with future problems. You don't really need to deinstall any package before attempting to rebuild it, e.g. First create a log file for the task. script rebuild.log Now create a backup copy of your current working package, adjust the version number below to match your system pkg_create -b qt-3.3.8_11 /tmp/qt-3.3.8_11 Go ahead and build the new binary but don't attempt to install it yet cd /usr/ports/x11-toolkits/qt33 make clean make If you get this far then you've successfully created the binary so go ahead and install it. make deinstall reinstall make clean If everything goes pear shaped in the install stage and the new version fails to install then just cd to /tmp and use pkg_add qt-3.3.8_11.tbz to reinstall the previous version. When everything is finished hit control-D or type exit to stop logging your output. You have a full record of all output in your rebuild.log file so if things went wrong during the build you can peruse it at leisure even after you've closed the window. I realize now that I'm going to have to learn to use the port management tools to help prevent problems like this in the future It's certainly worth spending some time to familiarise yourself with portupgrade or portmaster - among other things these do all the necessary steps of creating temporary backups and reinstalling them if things go wrong. Portmaster should be adequate for most of your needs, portupgrade offers more features but at the expense of a bit more complexity -- Mike Clarke ___ 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
earlier FBSD distributions...
How can I get ahold of the earlier versions of FBSOD, up to the initial release? I have tried looking for an archive on the web, and haven't been able to find any that aren't for exclusive users only. Thankyou. _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. http://clk.atdmt.com/GBL/go/201469226/direct/01/___ 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: earlier FBSD distributions...
Ure looking for the 386BSD patch sets then I suspect. http://www.oldlinux.org/Linux.old/distributions/386BSD/ On Sun, Feb 21, 2010 at 12:17 PM, aavum meza process4...@hotmail.com wrote: How can I get ahold of the earlier versions of FBSOD, up to the initial release? I have tried looking for an archive on the web, and haven't been able to find any that aren't for exclusive users only. Thankyou. _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. http://clk.atdmt.com/GBL/go/201469226/direct/01/___ 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 -- Opportunity is most often missed by people because it is dressed in overalls and looks like work. Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ 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: earlier FBSD distributions...
On Sun, 21 Feb 2010 04:17:36 -0600, aavum meza process4...@hotmail.com wrote: How can I get ahold of the earlier versions of FBSOD, [...] What is a FBSOD, a Friendly Bluescreen of...? :-) [...] up to the initial release? They are all available in FreeBSD's FTP archive. I have tried looking for an archive on the web, and haven't been able to find any that aren't for exclusive users only. Exclusive users? I'm not sure what this means... Anyway, if you're searching for FreeBSD from 1.0-RELEASE up to 2.2.9, 3.6.1, 4.11, 5.5, 6.4 and 7.2, you'll find them here: ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ Check for local mirrors: http://www.freebsd.org/doc/handbook/mirrors-ftp.html -- 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
Re: earlier FBSD distributions...
Oh and u'll probably want a copy of the NET/2 and NET/2-lite tapes. Ive got them somewhere, will have to go dig in the garage sometime to find them though. Must be available on the net somewhere. On Sun, Feb 21, 2010 at 12:17 PM, aavum meza process4...@hotmail.com wrote: How can I get ahold of the earlier versions of FBSOD, up to the initial release? I have tried looking for an archive on the web, and haven't been able to find any that aren't for exclusive users only. Thankyou. _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. http://clk.atdmt.com/GBL/go/201469226/direct/01/___ 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 -- Opportunity is most often missed by people because it is dressed in overalls and looks like work. Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ 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
Brasero can't detect my DVD RW disc to erase and make it blank
list, I have Freebsd7.2 and have gnome2 installed by pkg_add -r option , I want to burn DVD's, someone advised me by using brasero I can erase/write CD/DVDs steps followed was 1. in rc.conf added devfs_system_ruleset=local 2. in loader.conf atapicam_load=YES 3 in /etc/devfs.conf [local=10] #DVD+RW add path 'acd*' mode 0660 group operator add path 'cd0' mode 0666 group operator #CAM passthrough add path 'pass0' mode 0666 group operator add path 'xpt*' mode 0666 group operator [r...@kk /dev]# camcontrol devlist HL-DT-ST DVDRAM GSA-4083N 1.08 at scbus0 target 0 lun 0 (cd0,pass0) I inserted my dvd rw disk which has some .avi files, then launced brasero fromgnome--applications--soundvideo--brasero disk burner but from tools --erase I cant blank my DVD RW becoz no available disc in Select a disc dialog screen in brasero. How can I make brasero to doblank and burn DVDs successfully ? Any hints most welcome from . Thanks in advance Dhanesh For your information this is the debug output r...@kk]# brasero -gb hat you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy
Re: Dump questions
Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. Does this mean that a complete copy of the file system is written to .snap directory? No. The snapshot, quite incorrectly explained, is a saved delta between the file system on disk at a given state, to fixate further modifications (that are not included in the dump, of course). Sorry, I read your words but have no clue as what you are trying to say with that statement. As i understand 'delta' to mean, the difference in file system content between a point in time 'A' and 'B' some point in time later in the future. Now just what is snapshot recording between point 'A' and 'B' and how does that apply to what dump is going to read and write? ___ 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 questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/02/2010 12:52, Aiza wrote: Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. Does this mean that a complete copy of the file system is written to .snap directory? No. The snapshot, quite incorrectly explained, is a saved delta between the file system on disk at a given state, to fixate further modifications (that are not included in the dump, of course). Sorry, I read your words but have no clue as what you are trying to say with that statement. As i understand 'delta' to mean, the difference in file system content between a point in time 'A' and 'B' some point in time later in the future. Now just what is snapshot recording between point 'A' and 'B' and how does that apply to what dump is going to read and write? In horrendously simplified terms, the way snapshots work is this. Whenever there would be a write to a disk block, instead of overwriting the original block, the content is copied and written out to a previously unused disk block. The original block is preserved temporarily while the snapshot is active -- so the snapshotted data you see is the comprised of: * All the disk blocks that haven't been altered during the lifetime of the snapshot * The original, unchanged disk blocks which have been replaced by modified copies in the live filesystem. ZFS always does the copy-on-write thing, so it's a very natural and very fast operation to create snapshots with it -- often described as 'snapshots for free' -- and you can have as many as you want. UFS doesn't do CoW by default (AFAIR) so creating a snapshot under UFS means toggling the default behaviour and initialising some data structures to keep track of the disk blocks that belong to each snapshot. This means it will take a few seconds to create and you can only have a limited number of snapshots per filesystem active simultaneously. In either case, the space used for the snapshot corresponds to the amount of changes made to the filesystem since the snapshot was created. Thus on an active fs, snapshot space usage will go up over time. However, the amount used will generally be a fairly small percentage of the total space on the device, and all the extra space is recovered when the snapshot is released. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuBNYQACgkQ8Mjk52CukIzETQCfdnu2W7BBRVrc1T2H3MPWMA1G KWsAnj6E2hZ3m2WTtMfTfqZ89sWzxaB8 =jOeb -END PGP SIGNATURE- ___ 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
BSD perspective at SCALE?
Is the anyone who attend SCALE this weekend that would be interested in writing a couple of paragraphs about the event on BSD News? Please contact me off list. Regards, Mikel ___ 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 questions
On Sun, Feb 21, 2010 at 1:52 PM, Aiza aiz...@comclark.com wrote: Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. Does this mean that a complete copy of the file system is written to .snap directory? No. The snapshot, quite incorrectly explained, is a saved delta between the file system on disk at a given state, to fixate further modifications (that are not included in the dump, of course). Sorry, I read your words but have no clue as what you are trying to say with that statement. As i understand 'delta' to mean, the difference in file system content between a point in time 'A' and 'B' some point in time later in the future. Now just what is snapshot recording between point 'A' and 'B' and how does that apply to what dump is going to read and write? A somewhat inaccurate explanation is this: When you (or dump -L) create a snapshot, the current state of the filesystem is frozen and a snapshot file is created. As soon as some process starts to modify the filesystem, the old blocks at the time of snapshot are written in the snapshot file and the new blocks are written in the (current) filesystem. Now, when you (or dump -L) read the snapshot file, the UFS filesystem does some magic behind the scenes: if the snapshot file contains the blocks you ask for, it means that the corresponding blocks in the filesystem have already been changed. That's okay: UFS will then give you the old blocks from the snapshot. If the snapshot file doesn't contain the blocks you asked for, it means that those blocks were not modified in the filesystem, so UFS gives you those unmodified blocks, right from the filesystem. When the snapshot file is deleted, the filesystem will not be monitored anymore and old blocks of modified blocks will not be saved anymore. The net result is that by reading the snapshot, you get the frozen state of the whole filesystem, while everybody else who does read the filesystem will get the current state. Well, it doesn't work exactly as outlined above, but conceptually, it comes pretty close. Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: earlier FBSD distributions...
On Sun, Feb 21, 2010 at 11:17 AM, aavum meza process4...@hotmail.comwrote: How can I get ahold of the earlier versions of FBSOD, up to the initial release? I have tried looking for an archive on the web, and haven't been able to find any that aren't for exclusive users only. Thankyou. If you're willing to go back before Jolitz' 386BSD or BSD44lite code, check out the CSRG Archives. Marshall Kirk McKusick offers a set of CD-ROMs with versions of the original BSD, up to BSD 1: http://www.mckusick.com/csrg/index.html They're not not freely available, because that ancient code was covered by a different license back then, so by buying those CD-ROMs you have to agree to those terms. But it's worth the hassle: there's very interesting code in there if you're an OS historian. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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 questions
On Sun, Feb 21, 2010 at 02:10:29PM +0100, C. P. Ghost wrote: On Sun, Feb 21, 2010 at 1:52 PM, Aiza aiz...@comclark.com wrote: Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. Does this mean that a complete copy of the file system is written to .snap directory? No. The snapshot, quite incorrectly explained, is a saved delta between the file system on disk at a given state, to fixate further modifications (that are not included in the dump, of course). Sorry, I read your words but have no clue as what you are trying to say with that statement. As i understand 'delta' to mean, the difference in file system content between a point in time 'A' and 'B' some point in time later in the future. Now just what is snapshot recording between point 'A' and 'B' and how does that apply to what dump is going to read and write? A somewhat inaccurate explanation is this: When you (or dump -L) create a snapshot, the current state of the filesystem is frozen and a snapshot file is created. As soon as some process starts to modify the filesystem, the old blocks at the time of snapshot are written in the snapshot file and the new blocks are written in the (current) filesystem. Now, when you (or dump -L) read the snapshot file, the UFS filesystem does some magic behind the scenes: if the snapshot file contains the blocks you ask for, it means that the corresponding blocks in the filesystem have already been changed. That's okay: UFS will then give you the old blocks from the snapshot. If the snapshot file doesn't contain the blocks you asked for, it means that those blocks were not modified in the filesystem, so UFS gives you those unmodified blocks, right from the filesystem. When the snapshot file is deleted, the filesystem will not be monitored anymore and old blocks of modified blocks will not be saved anymore. The net result is that by reading the snapshot, you get the frozen state of the whole filesystem, while everybody else who does read the filesystem will get the current state. Well, it doesn't work exactly as outlined above, but conceptually, it comes pretty close. Let me just add to this thread to make sure we document the intent: The point of such a snapshot is to give you a point-in-time consisent view of a filesystem. On an active system, the state of the file system may change from the time you beging the backup to the time you complete it, meaning that if you ever have to restore, you may find time skew corruption. By taking the snapshot, you at least have the point in time view of the file system. That doesn't mean it will be perfect! If there were files being updated or written at the moment the snapshot was taken, they may be internally inconsistent - part new, part old - but from a file system structure point of view, they will be uncorrupted. So - you may still have to take steps to queisce users, databases, or other applications to get everything in the file system in a known state BEFORE you take the snapshot! But, at least, you only need to do it for the few seconds it takes to instantiate the snapshot, and not the whole time it would take to do the backup. Without snapshot (to have a pefect backup): Shut down all your applications and kick off all your users If you're really paranoid, unmount the file system (so you know it's not being accessed) Run your dump remount the filesystem Restart your apps let your users back on You can have confidence when restoring from such a backup, but it may be a practical impossibility! With snapshot (and a few other gives to practicality) Alert your users of when the snapshot will begin, so they can avoid actively modifying files at the time of the snapshot Quiesce all your applications - many databases have ways that you can put them into extended logging mode or write-aside mode to give you a guaranteed, transactionally-consistent copy (and some just operate that way all the time), but if your applications don't USE transactions - well, it may be best to just shut them down for a few seconds anyway sync;sync;sync (OK - we probably don't do that anymore - I'm an old-timer) Start the snapshot Let everyone go back about their business Do your dump / backup Release the snapshot That should give you the same quality of backup, or pretty darn close, with minial interruption to your users and the services you provide. My point is, if you're simply starting the snapshot without doing anything else, you'll be in the same state after a restore as you would from a power failure or other system fault. If you are comfortable picking up from such a state and moving forward, that's fine, but if you need a more consistent state of affairs, you may want to take a few extra steps. Power outages and systems failures which stop filesystems cold are rare - but your snapshots and
Re: unabe to install linux compatibility on freebsd 8.0-R
On Sun, Feb 21, 2010 at 08:47:01AM +, John wrote: Hi, thanks for replying On Sun, Feb 21, 2010 at 03:10:05AM +0100, Pieter de Goeje wrote: Somehow your linux.ko is broken, do you perhaps have WITHOUT_LINUX= in /etc/src.conf or /etc/make.conf? I have no src.conf make.conf looks like this: $ cat /etc/make.conf | less CPUTYPE?=athlon64 WITH_MUTT_IMAP_HEADER_CACHE=yes WITH_MUTT_SMTP=yes WITH_MUTT_CYRUS_SASL2=yes # added by use.perl 2009-11-27 15:44:59 PERL_VERSION=5.10.1 Check the last modification date of /boot/kernel/linux.ko, does it correspond (roughly) to the one from /boot/kernel/kernel? Yes, it does: $ ls -la /boot/kernel/linux.ko -r-xr-xr-x 1 root wheel 240K Feb 20 21:50 /boot/kernel/linux.ko* $ ls -la /boot/kernel/kernel -r-xr-xr-x 1 root wheel 6.8M Feb 20 21:08 /boot/kernel/kernel* About the kernel option, try COMPAT_LINUX32. It's a documentation bug. OK I'll try that now, thanks edit: I got this error: ../../../amd64/linux32/linux32_sysvec.c:38:2: error: #error Unable to compile Linux-emulator due to missing COMPAT_IA32 option! mkdep: compile failed *** Error code 1 so I'll add that one, too - seems to be building now That didn't fix it, and I should have mentioned at the start that I was using a custom kernel. I was also having a problem with rar out of the ports - it gave a similar error to the kldstat. So I did this: /usr/local/bin/rar: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, for FreeBSD 7.0 (700055), stripped and then remembered I'd stripped out the compatibility 4 5 6 and 7 from the kernel. So put them back in, recompiled and now everything works. Sorry for the noise. -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 ___ 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
Question about git
Hi I am having a problem with git. I followed a tutorial[1] about managing a website hosted on a remote server with git version control. It explains to use a post-receive script to update a detached working tree. However, when ever I push from the local machine to remote server the script fails with this error: Counting objects: 5, done. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 319 bytes, done. Total 3 (delta 2), reused 0 (delta 0) refs/heads/master: 863ce61088f2b6e2f8c5ccfa755c894558b83db3 - 52e033ea3b7ef16c88e865e1dbc3c4f72ca47cc2 fatal: /usr/bin/git-checkout cannot be used without a working tree. error: hooks/post-receive exited with error code 1 To ssh://j...@sphinx.mythic-beasts.com/home/jpg/website_devel.git 863ce61..52e033e master - master I have been searching on the internet for hours and tried different things like unsetting the environment variables using env -i, or by explicitly setting the $GIT_WORK_TREE $GIT_DIR variables in the script but it just will not run. Can anyone who uses git help me to figure out how I can use this post-receive script to update a detached work tree [1] http://http://toroid.org/ams/git-website-howto Thank you. -- Jamie http://www.mythic-beasts.com/~jpg ___ 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 questions
On Sun, 21 Feb 2010 20:52:31 +0800, Aiza aiz...@comclark.com wrote: Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. Does this mean that a complete copy of the file system is written to .snap directory? No. The snapshot, quite incorrectly explained, is a saved delta between the file system on disk at a given state, to fixate further modifications (that are not included in the dump, of course). Sorry, I read your words but have no clue as what you are trying to say with that statement. As i understand 'delta' to mean, the difference in file system content between a point in time 'A' and 'B' some point in time later in the future. Now just what is snapshot recording between point 'A' and 'B' and how does that apply to what dump is going to read and write? Oh, I see I did express a bit unclear. The snapshot means that the filesystem's status of a certain point in time - here: when dump is beginning to run - is fixated in a snapshot file, representing its exact content at time A. This representation is subject to the dump. All further deltas after A are not incorporated into the snapshot, and of course not into the dump. This means that all changes after A are lost if the backup is restored. A welcome solution, especially when dumo + restore are used to transfer system and user data, is to first run dump and restore, and then use cpdup to commit changes that took place during or right after the dump to the target. -- 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
mlock within jail possible for use with proftpd and TLS
Is it possible to make applications use mlock within jails? Im trying to use proftp with tls inside an jail. If i start it as root with proftpd -d 2, it complains about locking passphrase into memory: operation not permitted. error locking passphrase into memory: Operation not permitted Im using versions FreeBSD 8.0-RELEASE-p2 ProFTPD Version 1.3.2c - mod_tls/2.2.2 here are sysctls settings for jail related settings. security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.enforce_statfs: 2 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 1 security.jail.allow_raw_sockets: 1 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 1 Anyone got any tip? Niklas ___ 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
mlock within jail possible for use with proftpd and TLS
Is it possible to make applications use mlock within jails? Im trying to use proftp with tls inside an jail. If i start it as root with proftpd -d 2, it complains about locking passphrase into memory: operation not permitted. error locking passphrase into memory: Operation not permitted Im using versions FreeBSD 8.0-RELEASE-p2 ProFTPD Version 1.3.2c - mod_tls/2.2.2 here are sysctls settings for jail related settings. security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.enforce_statfs: 2 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 1 security.jail.allow_raw_sockets: 1 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 1 Anyone got any tip? Niklas ___ 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 kernel messages using syslog-ng 3.x
I'm in need of getting help using syslog-ng 3 on FreeBSD 8.0-RELEASE.
I'm having trouble getting kernel messages. I've made a very small
config file, and this isn't working either.
@version:3.0
source local { internal(); file(/dev/klog); unix-dgram(/var/run/log); };
destination all { file(/var/log/all.log); };
log { source(local); destination(all); };
The /etc/rc.conf.local has the following options in it.
syslogd_enable=NO
syslog_ng_enable=YES
syslog_ng_pid=/var/run/syslog-ng.pid
This picks up other things, but not the kernel messages. I assume it's
a small configuration issue. Using file /dev/klog works using
syslog-ng 2.x on FreeBSD 8.0, but not using syslog-ng 3.x. Let me
know. Thanks.
Phusion
___
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
booting single user mode
Looking for conformation. On booting into single user mode all files systems are unmounted except / which is mounted read only. Is this true? Will dump/restore commands 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: Dump questions
On Sun, Feb 21, 2010 at 11:03:58AM +0100, Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. ... Is this the limiting factor that forces a user to use (single user mode) for running dump? The snapshot, as far as the dump is concerned, essentially freezes the condition of the file system so that dump does not see any changes while dump is running. Without the snapshot, files could change or be deleted during the time it takes dump to finish. Dump starts by making its own list, by inode, of all the files to dump. Then it writes out, first the list, then the directories and finally the files and links to the media. If the files change between the time that list is made and things get written to the media, you will have an inaccurate representation of the file system. This can result in error messages if files it expects to be there are missing It can mean that a mangled image of a file is written in the dump. Doing a dump in Single User Mode means stopping activity on the system so there are fewer chances of the above happening. Using -L and doing a snapshot will not prevent a dump from being technically obsolete by the time it gets done, but it will mean that what gets written to media is internally consistent. The list it made will be exactly what is on the backup media and the files are all written completely as they were when the snapshot was taken with no mangling. 2. What is the worse that will happen if dump is run on live file system with out the -L flag? The index list that is written as part of the dump will not reflect what is on the dump media. It may claim a file is there, but it really is not. A file or some files are mangled because they are open and being modified by another process as the dump is reading them. The file may be either an inaccurate image or even completely unreadable. Restore is smart enough to skip over these problems if the file[s] you are looking to restore are not the ones mangled or deleted. But, you could get in to a situation of not being able to restore some things that you have on media. Can dump recognize this situation and issue an error message? I don't remember if dump puts out any useful diagnostic. I think it might tell you if it cannot file a file whose inode is in its list to write. But, it is restore that really notices and complains. If you have room, you can use restore to 'verify' a dump just by doing a restore of it to some extra space (maybe even to /dev/null, though I have never tried that one) and seeing if it makes any complaints. This, of course, is a long way to do this, but it might be valuable if it is essential for that dump to be completely readable in a later situation where the original is not longer available. But, in this situation, then making a -L dump (using a snapshot) is really important or even a single user, filesystem unmounted -L dump. 3. Can dump be told to only dump a particular directory tree? IE /var/log or /usr/port? dump only workes on filesystems/partitions. If you know you will want to make dumps on just that directory tree, that is a reason to make a separate partition/filesystem for it and mount it up. There is no reason that /var/log cannot be in its own partition/filesystem separate from /var and just mounted that way. Of course, you have to make sure that /var gets mounted before /var/log. But, that is not strange. Many people make a separate partition for /usr/home inside of /usr or a /var/db that is mounted inside of /var. Now, you can restore just a single file, group of files or a directory tree out of a dump. You do not have to restore the whole dump. So, you can make a dump of a '/var' filesystem if that is what you have and then if you need to restore just '/var/db' out of it, that is no problem. Just make sure you understand where you are putting it and how you specifiy it in the restore. But, if you just want a backup copy of a directory tree that is not its own partition/filesystem, you must use some other tool, such as tar or possibly rsync. 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: booting single user mode
On Mon, Feb 22, 2010 at 10:39:57AM +0800, Aiza wrote: Looking for conformation. On booting into single user mode all files systems are unmounted except / which is mounted read only. Is this true? Will dump/restore commands work? Generally yes. Make sure they are in your path and available to you in whatever filesystem[s] you have mounted. I think they normally are. I believe dump and restore are in /sbin which should be part of your root filesystem and not in its own partition. ==Never put those things that should be in root in their own partitions== To check where they are use 'which' which dump or which restore will tell you where they are. When you dump a non mounted filesystem, I think you have to use the partition name, not the mount name. So, instead of dump 0afL /dev/nsa0 /usr it might be dump 0afL /dev/nsa0 /dev/ad0s1d if your mount a partition /dev/ad0s1d as /usr normaly. You don't really need to restore to an unmounted partition, though using single user might be useful. If you are restoring in single user, do something like this. fsck -a mount -u / mount -a cd /usr restore -rf /dev/nsa0 Note: I am using /dev/nsa0 as where the dump media is. that would be a tape device. You need to adjust this for where you really write the dump or have the dump stored. 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: booting single user mode
Jerry McAllister wrote: On Mon, Feb 22, 2010 at 10:39:57AM +0800, Aiza wrote: Looking for conformation. On booting into single user mode all files systems are unmounted except / which is mounted read only. Is this true? Will dump/restore commands work? Generally yes. Make sure they are in your path and available to you in whatever filesystem[s] you have mounted. I think they normally are. I believe dump and restore are in /sbin which should be part of your root filesystem and not in its own partition. ==Never put those things that should be in root in their own partitions== To check where they are use 'which' which dump or which restore will tell you where they are. When you dump a non mounted filesystem, I think you have to use the partition name, not the mount name. So, instead of dump 0afL /dev/nsa0 /usr it might be dump 0afL /dev/nsa0 /dev/ad0s1d if your mount a partition /dev/ad0s1d as /usr normaly. You don't really need to restore to an unmounted partition, though using single user might be useful. If you are restoring in single user, do something like this. fsck -a mount -u / mount -a cd /usr restore -rf /dev/nsa0 Note: I am using /dev/nsa0 as where the dump media is. that would be a tape device. You need to adjust this for where you really write the dump or have the dump stored. jerry Think mistake here dump 0afL /dev/nsa0 /usr Whole reason for doing dump in single user mode is no snapshot so no need for -L flag in your example dump command. ___ 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 questions
Jerry McAllister wrote: On Sun, Feb 21, 2010 at 11:03:58AM +0100, Polytropon wrote: On Sun, 21 Feb 2010 11:42:50 +0800, Aiza aiz...@comclark.com wrote: 1. Using the -L flag to create a snapshot of the live running file system. ... Is this the limiting factor that forces a user to use (single user mode) for running dump? The snapshot, as far as the dump is concerned, essentially freezes the condition of the file system so that dump does not see any changes while dump is running. Without the snapshot, files could change or be deleted during the time it takes dump to finish. Dump starts by making its own list, by inode, of all the files to dump. Then it writes out, first the list, then the directories and finally the files and links to the media. If the files change between the time that list is made and things get written to the media, you will have an inaccurate representation of the file system. This can result in error messages if files it expects to be there are missing It can mean that a mangled image of a file is written in the dump. Doing a dump in Single User Mode means stopping activity on the system so there are fewer chances of the above happening. Using -L and doing a snapshot will not prevent a dump from being technically obsolete by the time it gets done, but it will mean that what gets written to media is internally consistent. The list it made will be exactly what is on the backup media and the files are all written completely as they were when the snapshot was taken with no mangling. 2. What is the worse that will happen if dump is run on live file system with out the -L flag? The index list that is written as part of the dump will not reflect what is on the dump media. It may claim a file is there, but it really is not. A file or some files are mangled because they are open and being modified by another process as the dump is reading them. The file may be either an inaccurate image or even completely unreadable. Restore is smart enough to skip over these problems if the file[s] you are looking to restore are not the ones mangled or deleted. But, you could get in to a situation of not being able to restore some things that you have on media. Can dump recognize this situation and issue an error message? I don't remember if dump puts out any useful diagnostic. I think it might tell you if it cannot file a file whose inode is in its list to write. But, it is restore that really notices and complains. If you have room, you can use restore to 'verify' a dump just by doing a restore of it to some extra space (maybe even to /dev/null, though I have never tried that one) and seeing if it makes any complaints. This, of course, is a long way to do this, but it might be valuable if it is essential for that dump to be completely readable in a later situation where the original is not longer available. But, in this situation, then making a -L dump (using a snapshot) is really important or even a single user, filesystem unmounted -L dump. 3. Can dump be told to only dump a particular directory tree? IE /var/log or /usr/port? dump only workes on filesystems/partitions. If you know you will want to make dumps on just that directory tree, that is a reason to make a separate partition/filesystem for it and mount it up. There is no reason that /var/log cannot be in its own partition/filesystem separate from /var and just mounted that way. Of course, you have to make sure that /var gets mounted before /var/log. But, that is not strange. Many people make a separate partition for /usr/home inside of /usr or a /var/db that is mounted inside of /var. Now, you can restore just a single file, group of files or a directory tree out of a dump. You do not have to restore the whole dump. So, you can make a dump of a '/var' filesystem if that is what you have and then if you need to restore just '/var/db' out of it, that is no problem. Just make sure you understand where you are putting it and how you specifiy it in the restore. But, if you just want a backup copy of a directory tree that is not its own partition/filesystem, you must use some other tool, such as tar or possibly rsync. jerry Thank you for the detail insight of how dump functions. Now one more question. Is the dump -L backup file made in a multiple-user-mode environment just as dependable as dump backups made in single-user-mode? ___ 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
Plans for BIND and DNSSEC readiness
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 I've made a post to -arch regarding my plans for BIND in the base, along with some information about getting ready for DNSSEC, including the upcoming signing of the root zone. You can find the message at http://lists.freebsd.org/pipermail/freebsd-arch/2010-February/009908.html. If you have any feedback regarding any of these topics, please follow up to that thread. Regards, Doug - -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEAREDAAYFAkuCEi4ACgkQyIakK9Wy8PtaZwCdGN6NljqTwHUxSQB3lf1T59j8 jpIAn20tJdy2h0ykeJwAQ8iWc32wUQ05 =uzZ5 -END PGP SIGNATURE- ___ 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: Problems With K3b
On 02/21/10 03:58, Polytropon wrote: snip I've often been told that portmaster would be a good choice. I've used portinstall / portupgrade in the past, but have to say that I honestly prefer pkg_add -r for simplicity. :-) I'm running portmaster right now to check for new packages and (recursively) dependencies and to upgrade anything that needs upgrading (if I'm reading the man page right I believe I issued the right command). I'm hoping this will take care of my k3b issue as well. Either way, I've decided to not worry about k3b, though I do want to resolve this if for no other reason than for if someone else runs into this problem, the archive will have the solution. I'd give you the output of pkg_add -rvn k3b but it'd be pointless because at some point I think I might have forced its install. pkgdb -f (to handle the stale dependency for mDNSResponder-108) flakes out on mDNSResponder, I think. I have more important issues right now than k3b (such as searching out docs for accessing my internal IOmega ZIP100 drive, seeing as the handbook only deals with USB, Optical (CD and DVD) and Floppy drives). I'll keep the list updated with my progress in getting k3b working (right now I get the following: [us...@hostname]k3b /libexec/ld-elf.so.1: Shared object libkparts.so.3 not found, required by k3b which I'm hoping portmaster will fix). -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
if this is a stupid q...
Excuse me, butthis IS a stupid question. I've tried to figure it out logically and by experimentation; just want to see if my findings jib with the unix wizards onlist. Now/then i do a portupgrade; I probably should just cron this, but it has given me problems before, so I do it while I can monitor the run. I'll do # portupgrade -akOPv then go ahead and work on other things. Question is What do I renice the run at [ruby] to set it to low at very low-power? I've tried like -17 and +17 (or just 17) because I learned that nice'ing the prio level higher than 0 was giving it a lower prio. Thus the rest of what I was doing could run anmost unaffected. Sometimes I'll be running a vi or two with portupgrade the Only other thing running [compiling, usually], and my editing is extremely slow. So what renice value should i use [normally]? Another question is for if i ever decide to cron portupgrade every week or so. What nice values is best? thanks, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.79a release of Jottings: http://jottings.thought.org/index.php ___ 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: if this is a stupid q...
In the last episode (Feb 21), Gary Kline said: Excuse me, butthis IS a stupid question. I've tried to figure it out logically and by experimentation; just want to see if my findings jib with the unix wizards onlist. Now/then i do a portupgrade; I probably should just cron this, but it has given me problems before, so I do it while I can monitor the run. I'll do # portupgrade -akOPv then go ahead and work on other things. Question is What do I renice the run at [ruby] to set it to low at very low-power? I've tried like -17 and +17 (or just 17) because I learned that nice'ing the prio level higher than 0 was giving it a lower prio. Thus the rest of what I was doing could run anmost unaffected. Sometimes I'll be running a vi or two with portupgrade the Only other thing running [compiling, usually], and my editing is extremely slow. Output of vmstat or top during the slowdown might be useful here. If editor responsiveness is bad, you're either running dozens of cpu-hogging processes, or running the system so far out of memory that your editor is being swapped out while you're typing. Certain ports may require a lot of ram to build (the jdk*/openjdk* ports possibly), but none should launch more processes than you have CPUs. -- Dan Nelson dnel...@allantgroup.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: earlier FBSD distributions...
aavum meza process4...@hotmail.com writes: How can I get ahold of the earlier versions of FBSOD, up to the initial release? I have tried looking for an archive on the web, and haven't been able to find any that aren't for exclusive users only. Thankyou. ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ or thereabouts has what looks like a fairly complete collection of FreeBSD releases. For older stuff including 386bsd and 4.4BSD-lite there's the archive at ftp://minnie.tuhs.org/BSD/ -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. ___ 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
