Re: RESOLVED: Problem upgrading ports - libintl.so.8 not found
I found a more elegant way of doing this, thanks to google on my 7.3 system. I added: ldconfig_paths=/usr/lib/compat /usr/X11R6/lib /usr/local/lib /usr/local/lib/compat/pkg to rc.conf and rebooted (I couldn't shutdown to single user then exit as I don't have physical access at the moment). Scott___ 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
Problem upgrading ports - libintl.so.8 not found
I'm trying to upgrade ports and they keep choking. In particular gpg is one of them: echo '#!/bin/sh' ./gpg_dearmor echo ../../g10/gpg2 --no-options --no-greeting \ --no-secmem-warning --batch --dearmor ./gpg_dearmor chmod 755 ./gpg_dearmor ./gpg_dearmor ./pubring.gpg ./pubring.asc /libexec/ld-elf.so.1: Shared object libintl.so.8 not found, required by libgcrypt.so.16 gmake[3]: *** [pubring.gpg] Error 1 gmake[3]: Leaving directory `/usr/ports/security/gnupg/work/gnupg-2.0.14/tests/openpgp' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/security/gnupg/work/gnupg-2.0.14/tests' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/security/gnupg/work/gnupg-2.0.14' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/security/gnupg. *** Error code 1 Stop in /usr/ports/security/gnupg. Another one this happened to was ghostscript8-nox11 What do I need to do to fix this problem? 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
RESOLVED: Problem upgrading ports - libintl.so.8 not found
On Jun 15, 2010, at 3:26 PM, Scott Schappell wrote: I'm trying to upgrade ports and they keep choking. In particular gpg is one of them: echo '#!/bin/sh' ./gpg_dearmor echo ../../g10/gpg2 --no-options --no-greeting \ --no-secmem-warning --batch --dearmor ./gpg_dearmor chmod 755 ./gpg_dearmor ./gpg_dearmor ./pubring.gpg ./pubring.asc /libexec/ld-elf.so.1: Shared object libintl.so.8 not found, required by libgcrypt.so.16 gmake[3]: *** [pubring.gpg] Error 1 gmake[3]: Leaving directory `/usr/ports/security/gnupg/work/gnupg-2.0.14/tests/openpgp' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/security/gnupg/work/gnupg-2.0.14/tests' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/security/gnupg/work/gnupg-2.0.14' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/security/gnupg. *** Error code 1 Stop in /usr/ports/security/gnupg. Another one this happened to was ghostscript8-nox11 What do I need to do to fix this problem? Thanks! After digging through /usr/ports/UPDATING, I copied all .so.8 and .so.16 libraries to /usr/local/lib and /usr/local/lib/compat/pkg and those ports are now compiling. I'm assuming that's the approved solution until ports are updated? My apologies for bugging the list, I missed that info the first time I read through UPDATING. At least now this will be archived if someone else has the problem, I suppose. Scott___ 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: Problem upgrading ports - libintl.so.8 not found
On Jun 15, 2010, at 3:43 PM, Eitan Adler wrote: 20100530: AFFECTS: users of devel/gettext (i.e.: YOU) AUTHOR: a...@freebsd.org I did do the make clean, make deinstall and make instal clean and it was still throwing that error. The only way I got the gnupg and ghostscript8-nox11 ports to update was by copying the .8 libraries over from a backup. ___ 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
FIXED: idled not disconnecting idle users on 7.2
I enabled UseLogin in sshd_config. Scott ___ 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
idled not disconnecting idle users on 7.2
I liked using idled on 4.11 to kick off idle users as it allowed me to specify which users can stay connected indefinitely, whereas sshd_config options ClientAliveCountMax 0 and ClientAliveInterval 60 would kick everyone off after an hour. I do have a couple of users that have a legitimate need to keep their SSH tunnel open as long as they need it. However, on 7.2 idled logs that it's disconnecting a user for idle, but it doesn't actually happen. Is there a kernel parameter or something other than idled that does the same thing (namely excluding users or groups from being idled disconnected)? Thanks! Scott___ 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: Wake up time
On Sep 21, 2009, at 14:16:53, Rolf G Nielsen wrote: Roland Smith wrote: There are such timers, that run over a week rather than just 24 hours, and they can have different times each day. And make sure you set in the BIOS (if able) to power on after power fail and test it to make sure it works. ___ 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: hard disk failure - now what?
On Aug 26, 2009, at 14:14:51, George Davidovich wrote: I believe you. I saw a similar scene in a movie, so I already knew it had to be true. Bonus points for anyone that can add to this thread's collection of off-topic but semi-interesting trivia and name the movie. What is The Abyss for 1000, Alex? :) Scott ___ 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: howto alias a stty erase?
If you use sh or bash, you can add to .profile or .bash_profile: stty erase ^h That should do it. Type the caret (^) and (h). On Aug 25, 2009, at 6:30 PM, Gary Kline wrote: is there a way of setty'ing stty erase to [backspace key? pretty sure that is the delete key. i'm tired of having to hand set it every time when i use the Konsole term. thanks, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 5.67a 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 ___ 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: Problem mounting EXT2FS
Judging by your uname output, the #0 should be #1 if it's reading a re- compiled kernel. I would double check that you used the proper KERNCONF for make buildkernel and make installkernel. For example, I recompiled my kernel and note the output: [r...@arthur /var/account]# uname -a FreeBSD arthur.silvertree.org 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #1: Fri Aug 14 13:27:47 PDT 2009 r...@arthur.silvertree.org:/usr/ obj/usr/src/sys/ARTHUR i386 See the #1? That shows me that the kernel has been recompiled once. The fact it says MYKERNEL for the kernel config, make sure that you copied GENERIC to MYKERNEL in /usr/src/sys/i386/conf/ I used the handbook and actually put ARTHUR in /root/kernels and in / usr/src/sys/i386/conf: [r...@arthur ~/kernels]# ls -la /usr/src/sys/i386/conf/ARTHUR lrwxr-xr-x 1 root wheel 20 Jul 29 07:57 /usr/src/sys/i386/conf/ ARTHUR - /root/kernels/ARTHUR I'd suggest that you didn't compile the right kernel config file. Another suggestion I used was to add in /etc/make.conf: KERNCONF=ARTHUR So add KERNCONF=MYKERNEL then copy /usr/src/sys/i386/conf/GENERIC to /usr/src/sys/i386/conf/MYKERNEL then edit MYKERNEL as needed and with that line in /etc/make.conf: cd /usr/src make buildkernel make installkernel shutdown -r now I may be off base, but I'd start with double checking the kernel config file used for buildkernel and installkernel. Scott On Aug 24, 2009, at 13:20:29, Jeronimo Calvo wrote: Hi folks, im migrating from Linux to BSD, and i found my first problem... First of all, i did save my /home from my old Linux distribution on another HD, ext2fs partition /dev/ad6s1... I can correctly see the drive from sysinstall. I read about compiling the KERNEL in order to add Ext2fs support under Freebsd, wich I did... Adding the line: Quote: options EXT2FS looking like this: Quote: options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing #options KDTRACE_FRAME # Ensure frames are compiled in *options EXT2FS* #options KDTRACE_HOOKS # Kernel DTrace hooks After this i recompiled the kernel and installed... Quote: # uname -a FreeBSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Mon Aug 24 18:59:43 UTC 2009 iscariote@:/usr/obj/usr/src/sys/MYKERNEL amd64 Well... everything should be ready now to mount my ext2fs partition... Using the following command... Quote: # mount /dev/ad8s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad8s1e on /tmp (ufs, local, soft-updates) /dev/ad8s1f on /usr (ufs, local, soft-updates) /dev/ad8s1d on /var (ufs, local, soft-updates) /dev/ntfs/DATOSWIN on /media/DATOSWIN (ntfs, local, nosuid) # mount -t extfs2 /dev/ad6s1 /ext2 mount: /dev/ad6s1 : Operation not supported by device I tried several times, with not luck, one of those times i was able to mount it, but not to access it, when i tried to cd /ext2 (folder when is mounted) system tells me that ext2 is not a folder... any ideas??? Thanks in advance!! ___ 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: Remounting a drive as read/write crashes the system and no dmesg.boot
Looking at info.0 I see: Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 155131904B (147 MB) Blocksize: 512 Dumptime: Fri Aug 21 08:27:45 2009 Hostname: arthur.silvertree.org Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.2-RELEASE-p3 #1: Fri Aug 14 13:27:47 PDT 2009 r...@arthur.silvertree.org:/usr/obj/usr/src/sys/ARTHUR Panic String: ffs_sync: rofs mod Dump Parity: 2778312054 Bounds: 0 Dump Status: good This is interesting: Panic String: ffs_sync: rofs mod It looks I'm guessing this is saying read only file system modified. So it looks like the problem is with mount? If there's anything you want me to pull from the vmcore.0 let me know. Again, this happens with the drive mounted RO from fstab. Unmounted then mount -o rw /backup. Something is amiss, and first blush doesn't seem to be hardware related. Scott ___ 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: Remounting a drive as read/write crashes the system and no dmesg.boot
On 8/20/2009 4:31 PM, Mel Flynn wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html OK, /backup was mounted read only, I did the following umount /backup mount -o rw /backup [r...@arthur ~]# dd if=/dev/zero of=/backup/testfile bs=1024 dd: /backup/testfile: end of device 21122+0 records in 21121+0 records out 21627904 bytes transferred in 2.215991 secs (9759924 bytes/sec) [r...@arthur ~]# You can see by that snippet it barfed at 21627094 bytes (21 megabytes, ish). /backup has 100s of GiB free. Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a9.7G453M8.5G 5%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad0s1d 15G481M 13G 4%/var /dev/ad0s1e 15G3.1G 10G23%/usr /dev/ad0s1f 15G1.4G 12G10%/usr/local /dev/ad0s1g216G3.5G195G 2%/home /dev/ad2s1d226G 32G176G15%/backup I cannot get the system to generate a dump, even though dumpon verified it's set to the swap drive but /var/crash stays empty. I have dumpdev=AUTO in rc.conf and dumpdir=/var/crash as well. Could this have anything to do with how I added the drive? I followed the handbook instructions but maybe I messed it up. ___ 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: Remounting a drive as read/write crashes the system and no dmesg.boot
On 8/20/2009 7:36 PM, Scott Schappell wrote: On 8/20/2009 4:31 PM, Mel Flynn wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html OK, /backup was mounted read only, I did the following umount /backup mount -o rw /backup [r...@arthur ~]# dd if=/dev/zero of=/backup/testfile bs=1024 dd: /backup/testfile: end of device 21122+0 records in 21121+0 records out 21627904 bytes transferred in 2.215991 secs (9759924 bytes/sec) [r...@arthur ~]# As of now, the dd command above has not crashed and it's past 3 GiB, using the mount -u -w syntax versus unmount, mount -o rw. This is puzzling. ___ 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 rid of X
In a parallel sort of thread to the current desktop thread, when I installed FreeBSD 7.2 since I had plenty of disk space and memory I installed X, however, I don't need it or really want it. How can I pare that out of the system short of doing a complete rebuild? Scott ___ 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: Getting rid of X
On Aug 19, 2009, at 09:19:56, Glen Barber wrote: Hi, You can deinstall the x11/xorg metaport. (Or, pkg_delete -x xorg.) The leftovers can be removed with ports-mgmt/pkg_cutleaves. HTH -- Glen Barber Thanks, Glen and John. I pared out 72 packages. I kept ones that seemed ambiguously related to X just to be on the safe side. Scot ___ 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
Remounting a drive as read/write crashes the system and no dmesg.boot
I have a drive (/dev/ad2s1d) mounted to /backup that I want to be read only until the backup scripts run and then it will be read/write. If I set /etc/fstab to: /dev/ad2s1d /backup ufs ro 0 0 to mount it read only most of the time then do: umount /backup mount -o rw /backup the system crashes, it just reboots about 10 seconds into writing data. The system is perfectly stable with it mounted read/write. Also, dmesg.boot has completely disappeared from the system, and touch /var/log/dmesg.boot it does not get populated. # uname -a FreeBSD arthur.silvertree.org 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #1: Fri Aug 14 13:27:47 PDT 2009 r...@arthur.silvertree.org:/usr/ obj/usr/src/sys/ARTHUR i386 Any suggestions on the remounting drive and dmesg.boot? Thanks! Scott P.S. It's good to be off of FreeBSD 4.11 :) ___ 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: Remounting a drive as read/write crashes the system and no dmesg.boot
On Aug 18, 2009, at 13:11:10, Tim Judd wrote: On my CF-based devices (firewalls.. nagios boxes, etc), I run: mount -uw / to update the mount (not mount again) the filesystem. If you're trying to mount again, I could understand why the box panics. Try in your script: mount -u -w /backups or shorter by a little: mount -uw /backups do your stuff, then go back to read-only: mount -ur /backups HTH We have a winner. I am sheepish in admitting I didn't read the man page well enough for mount. Thanks for the answer! Scott ___ 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
It's time to bite the bullet and do a major upgrade from 4.11 to 6.0
The writing is on the wall and all that stuff. I've put this off long enough. What needs to be done to upgrade from 4.11 to 6.x? I have an extensive amount of ports installed and in googling and searching the list, it seems I need to make a jump to 5.2 then from there to 6. My thinking is the best way to do this would be to cvsup, do the rebuilding of the world thing boot it to the 5 version then cvsup to 6. The server is continuously backed up so rolling back won't be a problem if I need to. Am I on the right track by doing source upgrades? If so, what intermediate jump(s) do I need to make to get from 4.11 to 6? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Seeking advice for new server: 4.8-REL vs. 4.9-BETA
Doug Poland wrote: Hi, On Monday, 29 Sep, I'll be building an apache/mysql server. I usually install from the latest release on CD then cvsup to -STABLE. My questions: Can I start with 4.9-BETA ISOs? My thinking is that what's in 4.9-BETA will not be much different from -STABLE. What do others when building servers and we're on the cusp of a new -RELEASE? Speaking for myself, since I have people hosting on my server and what not, I'm sticking with 4.8 until it's passed EOL and patch as necessary then evaluate if the latest RELEASE offers any substantial improvements, if so, then I'll CVSup to the next RELEASE in the same branch I'm in (4.8 4.9). The BETA is just that, and following -stable has revealed that while it's getting close to RELEASE, there's still some bugs. It's depends on what you want. If you want stability, install the 4.8 ISO and CVS to 4.9 when it's RELEASEd, if you want to help bug hunt, grab BETA. I always build with the latest RELEASE as I put stability ahead of being on the bleeding edge. Hope my opinion helped :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Seeking advice for new server: 4.8-REL vs. 4.9-BETA
Doug Poland wrote: I guess I have some confusion between what's -STABLE and -RELEASE and when one becomes the other. Better read up on it. The way I understand it is there are three branches CURRENT - the cutting edge source, use at your own risk, etc (5.x). This is a branch that is in development. STABLE - this is the development branch for a current dot release. For example 4.9 right now is in the STABLE branch and has gone through a certain level of testing in CURRENT. 4.9 right now is PRERELEASE, but it's still considered STABLE. Since it's still a dvelopment branch, it's prone to bugs (but not as many as CURRENT) as used primarily for contributors to the project or folks who want to stay as absolutely current in their current RELENG version (4). RELEASE - this is a branch that is the most stable, it's only updated to fix security or system issues. If you're tagging *default tag release=. (that's a literal . not a punctuation mark) then you're tracking CURRENT (5.x) If you're tagging *default tag release=RELENG_4 you're tracking 4.x STABLE If you're tagging *default tag release=RELENG_4_8 you're tracking 4.8 RELEASE (security branch) - this is what I'm following in my cvsupfile. Again, this is how I see it after reading the handbook, and I may be a bit off the mark :). Cheers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice re mail
David Bear wrote: I need to write a program the grabs mail from a standard mail folder and processes it. The trouble is I have no idea what mail file format FreeBSD uses by default. I am using postfix, and currently postfix is my mta and mda. I will be adding procmail as the mda. I'm guessing procmail writes the same kind of file the postfix does... but here I'm showing my ignorance. I will be using python as my language and there are modules for MH, maildir, mbox, and mailbox... Anyone have any recommended reading for me to better understand what I need to do? More than likely it's mbox format. Since you're running postfix Maildir has to be enabled in the config file by the entry home_mailbox=Maildir/. If you don't have that configured, you're using mbox formatted mailboxes. HTH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Default route dissapears constantly
John Straiton wrote: Hello, I'm having a doozy of a problem keeping a default route set up on a box I just upgraded today from 4.8-RC to 4.9-PR. After the upgrade, the machine will come up but quickly it will lose it's default route. The only way I can keep it from dropping the default route now is to continuously ping across it. If I stop for more than about 15 seconds, it'll get removed from the netstat -rn results. I don't mind researching possible means to fix it, but it's kinda hard when you have to hammer someone else's IP with pings to keep the link up or type route add default xx.xxx.xxx.xx every 15 seconds in order to surf... Are there any ways I can nail a route up without giving FreeBSD the ability to back it out automagically so I can fix this long enough to fix it the right way? Here's the relavent info: FreeBSD calefaction.clickcom.com 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #2: Wed Sep 24 16:36:22 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CALEFACTION i386 Default kernel except for options QUOTA, options IPFILTER and options IPFILTER_LOG rc.conf: network_interfaces=xl0 lo0 sis0 gateway_enable=YES defaultrouter=209.198.22.1 firewall_type=OPEN Ipfilter rules (for now) pass in all pass out all Ipnat rules (for now) map xl0 xx.xxx.xxx.0/24 - 209.198.22.19/32 Thanks in advance, John Straiton jks@ clickcom.com Clickcom, Inc 704-365-9970x101 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This has been discussed heavily in the -stable list. It seems the arp patch (incorporated into the world of 4.9, 4.8, et al) caused a loss of default routes on some systems. It was just mentioned that there seems to be an update addressing this issue. To fix it, you may want to roll back to 4.8 and wait for the fix for the arp advisory to be placed into a patch and the source tree. Cheers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PERLIO=stdio error message- newbie doesnt have a clue
suleyman wrote: I am trying to get dvdrip to run. This is the error message I get bash-2.05b$ dvdrip You're using Perl 5.8.0 without PERLIO set to 'stdio'. Most Perl 5.008 installations currently have a bug. dvd::rip doesn't work with them if PERLIO isn't set. I will set PERLIO=stdio for you and restart dvd::rip... You can get rid of this messages, by setting PERLIO=stdio in your ~/.profile, or whatever your shell uses. I have added this line PERLIO=stdio in my .login .cshrc and my .profile files I usually get this in term $ then type bash to get bash-2.05b$ either way after typing dvdrip i get the same message. Could someone please direct me to info about this. Thanks, Suleyman p.s.-In the last 3 months I have used redhat, suse, gentoo debian. Finally I tried FreeBSD 4.8- I love it so far though I have a lot to learn :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You're running bash, and that has to be in the environment. in your .bashrc and .bash_profile (or equivalent) use PERLIO=stdio; export PERLIO Try that. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Default route dissapears constantly
Rob Lahaye wrote: It looks like a fix got committed into the tree. snip R. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Yah, I noticed that, just waiting for a new patch now, though so far my system has been unaffected (using dc0) as I don't want to build world just yet :). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading to 4.9 CVS vs. binary?
It seems that 4.9 is rapidly on its way to becoming RELEASE, which is a good thing. I'm currently running 4.8-p3 on my production server, and I don't have a spare to build then move over, so it will be an in place upgrade. Which upgrade path would be the best? CVS or installing from a binary ISO CD? If CVS, I'm assuming I need to add *default tag=RELENG_4_9 when it's released to my cvsup file to grab it, or do I need to start tracking stable RELENG_4? My hunch is CVS will be the better way to do it, and the last time I tried upgrading the system with a binary, it exploded (learned then don't do a binary upgrade when it's running the kernel and multiuser, thank god for backups). What is the recommendation of folks on this list? Thanks :) -- PGP Key: http://archon.silvertree.org/pgp.txt Compassion and retribution are two sides of the same coin. Necessity dictates on what side the coin will fall. Firearms stand next in importance to the Constitution itself. They are the American people's liberty teeth and keystone under independence. -George Washington ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cvsup refuse confusion
Charles Howse wrote: Hi, I'm trying to eliminate all the non-English ports and documentation. I've deleted the relevant directories in /usr/ports and /usr/share/doc, But they reappear on subsequent cvsups. Where have I gone wrong? * /etc/cvsupfile * *default host=cvsup11.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_4_8 *default delete use-rel-suffix src-all *default tag=. ports-all doc-all * /usr/local/etc/cvsup/sup/ports-all/refuse * doc/da_* doc/de_* doc/el_* doc/es_* doc/fr_* doc/it_* doc/ja_* doc/nl_* doc/no_* doc/pl_* doc/pt_* doc/ru_* doc/sr_* doc/zh_* ports/INDEX ports/chinese ports/french ports/german ports/hebrew ports/hungarian ports/japanese ports/korean ports/polish ports/portuguese ports/russian ports/ukranian ports/vietnamese Thanks, Charles Got a computer with idle CPU time? Join [EMAIL PROTECTED] and help make history! http://setiathome.ssl.berkeley.edu/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] The refuse file goes in /usr/local/etc/cvsup/sup/refuse as mentioned in the handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Section A.5.3.1 The refuse file essentially tells *CVSup* that it should not take every single file from a collection; in other words, it tells the client to /refuse/ certain files from the server. The refuse file can be found (or, if you do not yet have one, should be placed) in /base//sup/. /base/ is defined in your supfile; by default, /base/ is /usr/local/etc/cvsup, which means that by default the refuse file is /usr/local/etc/cvsup/sup/refuse. Cheers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cvsup refuse confusion
The refuse file goes in /usr/local/etc/cvsup/sup/refuse as mentioned in the handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Section A.5.3.1 The refuse file essentially tells *CVSup* that it should not take every single file from a collection; in other words, it tells the client to /refuse/ certain files from the server. The refuse file can be found (or, if you do not yet have one, should be placed) in /base//sup/. /base/ is defined in your supfile; by default, /base/ is /usr/local/etc/cvsup, which means that by default the refuse file is /usr/local/etc/cvsup/sup/refuse. Cheers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cvsup refuse confusion
Charles Howse wrote: OK, the OP is getting confused. ;-) I have moved my refuse file to /usr/sup/refuse I have deleted the directories in /usr/ports and /usr/share/doc that I don't want. I will cvsup when we get this straightened out in my mind. Dr. Seaman says run 'make index' *OR* portsdb -Uu after cvsup. Kent says run 'portsdb -u' *AFTER* make index. What is our consensus? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I /think/ but I haven't confirmed this, that portsdb -Uu as part of its deal does a make index. In my update ports script, I jsut do portsdb -Uu. Then again, someone else has already pointed out my brain is a bit foggy this morning :). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Updating SSH, patch failed?
Greetings:
I ran the patch process exactly as listed in the advisory. I'm currently
running 4.8p3 built from source.
After running the instructions verbatim, sshd shows the following version
string:
OpenSSH_3.5p1 FreeBSD-20030201, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
Also the command to restart sshd gives me an error:
arthur# (. /etc/rc.conf ${sshd_program:-/usr/sbin/sshd} ${sshd_flags})
Bad : modifier in $ (-).
Is my ssh patched? Or should I remake the world?
Thanks for the help!
--
PGP Key: http://archon.silvertree.org/pgp.txt
Compassion and retribution are two sides of the same coin. Necessity
dictates on what side the coin will fall.
Firearms stand next in importance to the Constitution itself. They are the
American people's liberty teeth and keystone under independence.
-George Washington
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Forcing users to use unique passwords?
I've did a google search on this, and an archive search. For an extra measure of completeness, I scanned the handbook. Here's the question: I currently make my users reset their passwords every 90 days. However, nothing stops them from reusing the same password. passwd happily allows users to reuse a password. Since that's the case, what's the point of enabling password expiration, since most users will probably reuse their password (after all, it's convenient to do so). Is there a way to change login.conf to force unique passwords? Or would I have to wrap passwd in a shell script of some sort? Thanks in advance for your help! -- PGP Key: http://archon.silvertree.org/pgp.txt Compassion and retribution are two sides of the same coin. Necessity dictates on what side the coin will fall. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
realpath advisory question
I have a question regarding whether or not I need to upgrade my system, and if so, what's the best way to do it to minimize downtime. If this should have gone to the security list, I apologize. uname output: bash-2.05b$ uname -a FreeBSD arthur.silvertree.org 4.8-RELEASE FreeBSD 4.8-RELEASE #1: Sat Aug 2 15:57:20 PDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARTHUR0 i386 Does anything in the uname suggest I'm OK, or do I need to upgrade? I'm a bit nervous about doing a make world update, but only for downtime concerns. Is there another command I can run to verify whether or not I'm OK? Thanks in advance for your help, and if I left something out, please feel free to let me know. I have my asbestos suit on :). Thanks! Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
