Re: login.conf: passwordtime not enforced?
On Tue, Jul 13, 2010 at 10:19 PM, b. f. bf1...@googlemail.com wrote: after reading some docs about hardening freebsd installations, I decided to enforce password expiration after 90days. I've added the corresponding line to /etc/login.conf and ... after quite some time (way more than 3 months already!) nothing happens ... If you want help, you'll have to be more specific. Thanks bf1783, I'm sorry about that. My apologies. I just assumed that you assumed that I was doing the right thing(TM). :) Exactly what changes did you make to login.conf, in what sections? I've changed only the default login class, and added and/or changed these lines: :passwd_format=blf:\ :minpasswordlen=8:\ :mixpasswordcase=true:\ :passwordtime=90d:\ :idletime=30:\ :umask=027: Did you run 'cap_mkdb /etc/login.conf' afterwards? Of course I did. Did you then reset your account passwords Of course. Now they all begin with $2a, as expected for blowfish-hashed passwds. and check the sixth colon-delimited field in /etc/master.passwd with 'date -r' for each account changed, to see if the appropriate expiration date was registered? I don't quite get what 'date -r' does here ... but yes I've checked the 6th field in /etc/master.passwd, all accounts (regular users and system accounts) have a '0' in that field. Next time you make a change like this, test it with a short expiration time (a minute or two, say) on a non-critical account to see if works instead of waiting three months to discover that it does not. I usually assume that the docs are correct, and don't go about checking and re-checking that everything works as expected ... unless not for these trivial config tweaks. Of course I've checked that the newly created passwords (now using blf instead of md5) worked, but I just assumed that the rest of the config settings for this login class didn't require further checking ... if the blf change worked, why not the rest? Do you suggest that I should now go and check if the 'mixpasswordcase', 'minpasswordlen', 'idletime' or the 'umask' settings are honored? I just hope I don't need to ... :) Any ideas on how to enforce this? Do I have to manually use pw(1) every 90 days? No, you shouldn't have to if you use the feature properly. You'll be prompted immediately after login for a new password if your old one has expired. b. I just added a new class in login.conf: test:\ :tc=default:\ ::passwordtime=2m: And then added a new user 'testaccount', using adduser(1). I've verified that its login class was OK in /etc/master.passwd (BTW again the 6th field is '0'). And I never got any message about the password being expired, after several succesful login attempts that, obvioulsy, spanned more than 2 minutes. Who is responsible for filling in the password expiration time/date in master.passwd, according to the login class config? passwd(1)? adduser(1)? Myself, manually? I guess this is the question I wanted answered in my first email. After reading, again the man page for master.passwd(5), saying that The expire field is the number of seconds from the epoch, UTC, until the account expires. It's now clear to me that i) I can do it manually, eg. by running something like %date -j -f %a %b %d %T %Z %Y `date -v+90d` +%s 1286895815 and entering that value into the 6th field of /etc/master.passwd. But then, I'll have to do this regularly using a script, because, ii) passwd(1) fails to read the setting in login.conf and then add the corresponding expiration time (in seconds since the epoch) in /etc/master.passwd Unless, of course, I'm missing something ... after setting the expiration time to %date -j -f %a %b %d %T %Z %Y `date -v+2M` +%s 1279120340 And then waiting until this time has passed, nothing happens (I'm logging in remotely using SSH) ... no warning, no refuse to log me in, nothing. Is it at all possible to enforce password expiration times in FreeBSD? -- fernan ___ 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: login.conf: passwordtime not enforced?
On Wed, Jul 14, 2010 at 1:25 PM, b. f. bf1...@googlemail.com wrote: On 7/14/10, Fernan Aguero fernan.agu...@gmail.com wrote: On Tue, Jul 13, 2010 at 10:19 PM, b. f. bf1...@googlemail.com wrote: I'm sorry about that. My apologies. I just assumed that you assumed that I was doing the right thing(TM). :) That would be a very bad assumption to make, when attempting to track down a problem. ... Right, I thought it was simpler than it really is ... this is getting scary. Next time you make a change like this, test it with a short expiration time (a minute or two, say) on a non-critical account to see if works instead of waiting three months to discover that it does not. I usually assume that the docs are correct, and don't go about checking and re-checking that everything works as expected ... unless not for these trivial config tweaks. Of course I've checked that the newly created passwords (now using blf instead of md5) worked, but I just assumed that the rest of the config settings for this login class didn't require further checking ... if the blf change worked, why not the rest? Do you suggest that I should now go and check if the 'mixpasswordcase', 'minpasswordlen', 'idletime' or the 'umask' settings are honored? I just hope I don't need to ... :) The docs can be outdated, incomplete, or misinterpreted. Or your system could be misconfigured or broken. How much time and energy you put into your testing is up to you. If you're serious about security, you'll check your changes. Some of the above-mentioned are fairly easy to check. Right, should have checked before talking ... see below, I just added a new class in login.conf: test:\ :tc=default:\ ::passwordtime=2m: And then added a new user 'testaccount', using adduser(1). I've verified that its login class was OK in /etc/master.passwd (BTW again the 6th field is '0'). And I never got any message about the password being expired, after several succesful login attempts that, obvioulsy, spanned more than 2 minutes. Bravo. The above is more of the kind of thing that needs to be done when trying to diagnose a problem. But I think you want: test:\ :passwordtime=2m:\ :tc=default: See the default login.conf and getcap(3). OK, changed this, but got mixed results, see below. Who is responsible for filling in the password expiration time/date in master.passwd, according to the login class config? passwd(1)? adduser(1)? Myself, manually? The first time you have to change it manually for each account, with passwd(1); Sorry if I'm getting dense but do you mean 'manually' as in editing master.passwd with vipw? Or do you really mean 'manually with passwd(1)? My passwd(1) only allows me to change the user password and even doing this doesn't update the expiration time in master.passwd. Is there a hidden functionality in passwd that allows me to set the expiration time for the password? BTW, this is on FreeBSD-6.4-p10. And so far all my tests fail to make passwords expire. But I just tested the same changes on a recent 7.3-STABLE. And: i) the first time, passwd(1) doesn't update the expiration time in master.passwd, I have to enter it manually using vipw ii) using ssh and trying to log in after the expiration period makes the system prompt for a new password, with no further explanation about what's going on, i.e.: [fer...@localhost] ssh testacco...@otherhost Password: New Password: So, the password is getting expired. However, iii) the 6th field in master.passwd for this account is reset to '0' after setting the new password. This happens if I set the new password as prompted using ssh, or if I run passwd(1) on a terminal. And, iv) I was able to enter a 5 character password, no mixed case, all letters, completely ignoring the other settings in the default login class (minpasswordlen=8, mixpasswordcase=true). thereafter pam_unix(8) checks for expiration at login time: if a password has expired, you are prompted to change it, correct in FreeBSD-7.3-STABLE and the new password will have the appropriate expiration time. not in my case. It works for me locally, with the default security settings; I've never tried it over a remote connection. which FreeBSD version are you using? You may have some configuration settings that are causing problems. Have you tinkered with /etc/pam.d/* ? No. What other configuration changes have you made? Some mentioned in http://tuxtraining.com/2009/04/26/how-to-harden-freebsd After using cap_mkdb, have /etc/pwd.db and /etc/spwd.db changed? Do they have the right timestamps? After using cap_mkdb on /etc/login.conf, /etc/login.conf.db gets changed, yes. And after editing master.passwd with vipw, all of /etc/pwd.db, /etc/spwd.db and /etc/passwd all get changed. Timestamps are OK and reasonable. Does the password change mechanism work properly if you are logging in locally, as opposed to remotely via ssh? Yes in FreeBSD
login.conf: passwordtime not enforced?
Hi, after reading some docs about hardening freebsd installations, I decided to enforce password expiration after 90days. I've added the corresponding line to /etc/login.conf and ... after quite some time (way more than 3 months already!) nothing happens ... Just googled around, and noticed this functionality seems to be absent from the base system ... only passwd(1) seems to honor this value, but truth is, when I need to use passwd(1) it's because I want to change the password myself! There is a post that mentions that having blowfish (instead of md5) as a 'passwd_format' works ... http://www.daemonforums.org/showpost.php?s=41d1e0ba423c94357afe805dbe0b2730p=17826postcount=5 However, I wonder if it worked for the author of the post, only because he manually set the password expiry date using 'pw usermod [username] -p [date]' Any ideas on how to enforce this? Do I have to manually use pw(1) every 90 days? -- fernan PS: other references to this problem: http://markmail.org/message/f5b5o3vsyo7pcozf http://lists.freebsd.org/pipermail/freebsd-security/2008-September/004934.html ___ 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
discrepancies in disk usage between df and du
Hi, I have a box (7.2-STABLE, amd64) that is currently showing some disk usage problems. It all started with apache generating huge logs from one of the mod_perl applications that is undergoing testing. So the /var partition was getting full. We removed all logs that were causing the problem, but even though du shows some 700 Mb of usage, df shows that the disk is full (-1.5 Gb): [fer...@omega ~] sudo du -hc -d1 /var/ Password: 2.0K/var/.snap 423M/var/account 6.0K/var/at 2.0K/var/audit 18K/var/backups 4.0K/var/crash 6.0K/var/cron 53M/var/db 2.0K/var/empty 2.0K/var/heimdal 219M/var/log 14M/var/mail 4.0K/var/msgs 48K/var/named 2.0K/var/preserve 44K/var/run 2.0K/var/rwho 16K/var/spool 76K/var/tmp 24K/var/yp 2.0K/var/games 710M/var/ 710Mtotal [fer...@omega ~] df -h FilesystemSizeUsed Avail Capacity Mounted on /dev/mirror/gm0s1f 18G 18G -1.5G 109%/var I've been googling around, and I understand why df and du might be reporting disk usage differently. However, I can't solve this issue and reclaim unused disk space ... applications (apache, mod_perl) are prevented to write to /var and this is causing us problems. We've already tried rebooting the box, restarting the syslog, newsyslog daemons, to no avail. df keeps showing 100% disk usage (-1.5 Gb of remaining disk space) in all cases. We've even rebooted the box with all apache instances turned off in rc.conf ... i.e. without any but the most basic services running (sshd) ... This box is essentially a web server, no other services are being run. Any suggestions as to what to try next? Thanks in advance, -- fernan ___ 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: discrepancies in disk usage between df and du
On Fri, Feb 12, 2010 at 8:53 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: You have a file locking problem. du shows disk in use, but df shows disk committed. Use lsof to identify the file that has disk space reserved but no longer exists. man (8) lsof Thanks Paul for the suggestion. I've tried both lsof and fstat, and can't really see anything wrong in the output ... 1. Can't install lsof from ports, apparently === Registering installation for lsof-4.83C,4 /var: write failed, filesystem is full cp: /var/db/pkg/lsof-4.83C,4/+MTREE_DIRS: No space left on device *** Error code 1 I say 'apparently' because in spite of the error message, /var/db/pkg gets written anyway: omega# ls -l /var/db/pkg/lsof-4.83C,4/ total 6 -rw-r--r-- 1 root wheel57 Feb 13 01:22 +COMMENT -rw-r--r-- 1 root wheel 1435 Feb 13 01:22 +CONTENTS -rw-r--r-- 1 root wheel 386 Feb 13 01:22 +DESC -rw-r--r-- 1 root wheel 0 Feb 13 01:22 +MTREE_DIRS And lsof is installed at /usr/local/sbin/lsof, as expected. 2. Let's see what lsof shows: omega# lsof +D /var/ COMMANDPID USER FD TYPE DEVICE SIZE/OFFNODE NAME devd 464 root4u unix 0xff0005d03b40 0t0 /var/run/devd.pipe devd 464 root5w VREG 0,943 47122 /var/run/devd.pid sendmail 804 root cwd VDIR 0,94 512 1295363 /var/spool/mqueue sendmail 804 root5w VREG 0,94 78 47115 /var/run/sendmail.pid sendmail 808 smmsp cwd VDIR 0,94 512 1295366 /var/spool/clientmqueue sendmail 808 smmsp4w VREG 0,940 1295368 /var/spool/clientmqueue/sm-client.pid cron 814 root cwd VDIR 0,94 512 23552 /var/cron cron 814 root3w VREG 0,943 47117 /var/run/cron.pid csh 6741 paula cwd VDIR 0,94 4096 117760 /var/log syslogd 70526 root3w VREG 0,945 47111 /var/run/syslog.pid syslogd 70526 root4u unix 0xff0024a00b40 0t0 /var/run/log syslogd 70526 root5u unix 0xff0013ee9870 0t0 /var/run/logpriv syslogd 70526 root 11w VREG 0,9451176 117901 /var/log/messages syslogd 70526 root 12w VREG 0,94 60 117771 /var/log/security syslogd 70526 root 13w VREG 0,9486008 117780 /var/log/auth.log syslogd 70526 root 14w VREG 0,94 2036 117877 /var/log/maillog syslogd 70526 root 15w VREG 0,94 60 117767 /var/log/lpd-errs syslogd 70526 root 16w VREG 0,94 60 117773 /var/log/xferlog syslogd 70526 root 17w VREG 0,9434783 117859 /var/log/cron syslogd 70526 root 18w VREG 0,94 93 117766 /var/log/debug.log syslogd 70526 root 19w VREG 0,94 60 117772 /var/log/slip.log syslogd 70526 root 20w VREG 0,94 60 117770 /var/log/ppp.log 3. fstat comes built-in, omega# fstat -f /var/ USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root syslogd705263 /var 47111 -rw--- 5 w root syslogd70526 11 /var 117901 -rw-r--r-- 51176 w root syslogd70526 12 /var 117771 -rw--- 60 w root syslogd70526 13 /var 117780 -rw--- 86008 w root syslogd70526 14 /var 117877 -rw-r-2036 w root syslogd70526 15 /var 117767 -rw-r--r-- 60 w root syslogd70526 16 /var 117773 -rw--- 60 w root syslogd70526 17 /var 117859 -rw--- 34783 w root syslogd70526 18 /var 117766 -rw--- 93 w root syslogd70526 19 /var 117772 -rw-r- 60 w root syslogd70526 20 /var 117770 -rw-r- 60 w paulacsh 6741 wd /var 117760 drwxr-xr-x4096 r root cron 814 wd /var 23552 drwxr-x--- 512 r root cron 8143 /var 47117 -rw--- 3 w smmspsendmail 808 wd /var 1295366 drwxrwx--- 512 r smmspsendmail 8084 /var 1295368 -rw--- 0 w root sendmail 804 wd /var 1295363 drwxr-xr-x 512 r root sendmail 8045 /var 47115 -rw--- 78 w root devd 4645 /var 47122 -rw--- 3 w I can see nothing here ... 4. But still, disk is full ... or is it? omega# df -h FilesystemSizeUsed Avail Capacity Mounted on /dev/mirror/gm0s1f 18G 18G -1.5G 109%/var Thanks for any further advice, -- fernan --On February 12, 2010 5:39:44 PM -0300 Fernan Aguero fernan.agu...@gmail.com wrote: Hi, I have a box (7.2-STABLE, amd64) that is currently showing some disk usage problems. It all started with apache generating huge logs from one of the mod_perl applications
arrange files and directories in CD-sized bins?
Hi! I'm trying to help a FreeBSD user with a slow (dialup) link by providing him with CDs containing distfiles. My /usr/ports/distfiles directory holds 3.0Gb of data, and although I can generate a tarball and split it in multiples of 650MB or 700MB (the CD capacity) using split(1), I would much rather like to generate ~ 5 ISO images each containing the files. This way it'll be much easier for him to access it. Now, I can go on and manually arrange the distfiles so as to minimize the number of CDs needed ... but I thought that perhaps this could be automated in some way? Anyone know of a tool that given a list of files and directories with their sizes arranges them in lists of MAX XXX bytes? Fernan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mouse dead on FreeBSD but not on Windows
Hi! I've a dual boot machine, which was running FreeBSD-5.4 (now 6.0p1) and WinXP. It has a cheap PS/2 mouse (Biswal is the brand, but I guess it's just a generic mouse, details at the bottom). In Windows it works flawlessly ... wheel included. It's been running for months. In FreeBSD it never worked. I don't know if I'm doing something wrong ... this machine is the first box in which I installed 5.x so perhaps there are some configuration differences from 4.x tham I'm unaware of? Any help would be appreciated (of course I can go buy another cheap mouse ... but I'm intrigued now). The details: dmesg says: psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT LOCKED] psm0: model Intellimouse, device ID 3 moused says: moused -i all -p /dev/psm0 /dev/psm0 ps/2 sysmouse Intellimouse I've tried to run 'vidcontrol -m on' and then 'moused -p /dev/psm0 -t auto/sysmouse' and I never get an arrow on the screen. I've got X installed with gnome and when booting I always get a black arrow in the xdm login screen that I cannot move with the mouse. I also tried to tweak my Xorg.conf file to no avail. My custom kernel has the following (I quote what I guess it's relevant, do ask for more detail if neccessary): device atkbdc device atkbd device psm I just cvsuped against RELENG_6_0 and rebuilt the world and kernel. All the base system is now 6.0p1, and now I need to rebuild all ports ... but apart from that the mouse is still dead on FreeBSD. Again thanks for any help, fernan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mouse dead on FreeBSD but not on Windows
+[ Frank Laszlo [EMAIL PROTECTED] (03.Jan.2006 12:10): | | Fernan Aguero wrote: | Hi! | | I've a dual boot machine, which was running FreeBSD-5.4 (now | 6.0p1) and WinXP. It has a cheap PS/2 mouse (Biswal is the | brand, but I guess it's just a generic mouse, details at the | bottom). | | In Windows it works flawlessly ... wheel included. It's been | running for months. In FreeBSD it never worked. I don't know | if I'm doing something wrong ... this machine is the first | box in which I installed 5.x so perhaps there are some | configuration differences from 4.x tham I'm unaware of? | | Any help would be appreciated (of course I can go buy | another cheap mouse ... but I'm intrigued now). | | The details: | | dmesg says: | psm0: PS/2 Mouse irq 12 on atkbdc0 | psm0: [GIANT LOCKED] | psm0: model Intellimouse, device ID 3 | | moused says: | moused -i all -p /dev/psm0 | /dev/psm0 ps/2 sysmouse Intellimouse | | I've tried to run 'vidcontrol -m on' and then 'moused -p | /dev/psm0 -t auto/sysmouse' and I never get an arrow on the | screen. | | I've got X installed with gnome and when booting I always | get a black arrow in the xdm login screen that I cannot move | with the mouse. I also tried to tweak my Xorg.conf file to | no avail. | | My custom kernel has the following (I quote what I guess | it's relevant, do ask for more detail if neccessary): | device atkbdc | device atkbd | device psm | | I just cvsuped against RELENG_6_0 and rebuilt the world and | kernel. All the base system is now 6.0p1, and now I need to | rebuild all ports ... but apart from that the mouse is still | dead on FreeBSD. | | Again thanks for any help, | | fernan | | | Are you using moused, or Xorg's mouse daemon? please send the applicable | section from your xorg.conf. Thanks | +] Frank, thanks for your reply, this is not just a problem in xorg, it is also the mouse not working in the console (without X). I don't get an arrow cursor that I can use in the console to copy/paste text. I've tried using moused (moused_enable=YES in rc.conf) and then using /dev/sysmouse in xorg.conf and also disabling moused and using /dev/psm0 in xorg.conf. Identifier Mouse1 Driver mouse Option ProtocolPS/2 Option Device /dev/psm0 Option ZAxisMapping 4 5 (I've done tests with and w/o the ZAxisMapping line, and as mentioned with psm0 or sysmouse after /dev/ in the Device option. None worked). When using /dev/psm0 in xorg.conf I got the typical X cursor instead of the arrow, and I could move it with the mouse, although the movement was erratic ... most of the movement of the mouse was not recognized and sometimes the cursor would move to the bottom left corner of the screen Using moused and /dev/sysmouse in xorg.conf resulted in a black arrow as a cursor, as mentioned, but the cursor would not move at all. I exchanged the mouse, and now the same setup works (only tested the mouse in the console since I'm now rebuilding the xorg from ports). This is also a generic mouse (Noganet, PS/2) but it has three buttons instead of two and a wheel. Maybe the other mouse is defective, but it works without a hitch in WinXP ... or perhaps I'm missing some essential flags that need to be added for a wheel mouse? Also, I've tried different combinations of ports/types using /stand/sysinstall (post-install configurarion-mouse) and I never got an arrow shown in the screen when activating the mouse daemon with the wheel mouse. Fernan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: maximum hard drive capacity supported?
+[ Wojciech Puchar [EMAIL PROTECTED] (30.Aug.2004 17:55): | | | Upon trying to buy a new hard drive (80 GB) I was asked | about the capabilities of my system, and I just thought that | these were needed to tell what kind the IDE (ATA) | capabilities. However, the vendor said that depending on the | BIOS the system might not be able to recognize a large disk. | | BIOS is only needed to boot. | FreeBSD then drives it without BIOS Thanks for pointing this ... that's what I originally thought! | there are 3 possibilities: | | 1) BIOS just supports whole drive. nothing special needed | | 2) BIOS can't support the whole drive, it detects as much smaller one. actually, from what I've read there are other possibilities. I'm providing two URLs that seem to say essentially the same thing: http://storagereview.com/guide2000/ref/hdd/bios/sizeHandling.html See section How a BIOS handles Oversized Hard Disks in: http://www.dewassoc.com/kbase/hard_drives/hard_drive_size_barriers.htm | solution: | | install system with separate /boot partition that fits in the range that | BIOS supports. after booting FreeBSD will get whole disk OK, that's what I remember reading when I first installed FreeBSD ... but that was a long time ago. This is the disadvantage of using an OS you don't need to reinstall :) Now, in my case I don't need the new and bigger disk to be the bootable disk (i.e. I already have two drives that are sliced, partitioned and working fine). I just need it to be another disk to hold a /home or /scratch partition ... so does it really matter what the BIOS sees? | 3) BIOS hangs completely trying to drive your disk. | rare case but i have this with P133 machine with 80GB disk. OK, in this case it might matter. But I also read it is rare. Perhaps it's also less probable to happen if the big disk is not bootable (i.e. does not contain a MBR)? (I'm not knowledgeable enough on this issue, so perhaps it does not matter whether it has an MBR or not ...) | machine runs NetBSD, and i boot kernel from floppy, then NetBSD supports | whole drive. | | with FreeBSD it could be difficult to fit kernel on floppy but it is | possible if you will compile yours with minimal set of drivers (but | including disk) and then load modules from disk by startup scripts. | | my custom kernel compresses to 977000 bytes, loader takes 237568 bytes so | it could fit. | unfortunately i don't have enough FreeBSD knowledge now to tell you how | prepare such floppy. | +] Let's hope I'm not in this situation ... my custom kernel (2.6 MB) compresses to 1214598 bytes. Thanks for your reply! Fernan -- Fernan Aguero - fernan at iib.unsam.edu.ar Phone: +54 11 4580-7255/7 ext 310, Fax: +54 11 4752-9639 Check http://genoma.unsam.edu.ar/~fernan for more info. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB Storage devices (Cigar/Pen) in FreeBSD?
Hi! I'd like to buy one of those USB storage devices that come in different aspects (cigar/pen) and sizes (64/128/256/512 MB). My main machine does not have USB 2.0 ports (but does have USB 1) and is running FreeBSD-4.9 Do these devices work with FreeBSD-4.9? What kernel options should I enable? From reading the archives I see that there are some problems if you want to boot from the device. Otherwise I've not found anything interesting. Perhaps this is just because they work 'out of the box' and there are no quirks or issues that merit attention. I'd appreciate positive/negative user experiences to decide my purchase. Thanks, Fernan PS: please CC me since I'm not subscribed to the list. -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: explain annoying You have XXX mail messages
+[ Lowell Gilbert [EMAIL PROTECTED] (03.Oct.2003 20:44): | | Fernan Aguero [EMAIL PROTECTED] writes: | | The default mailbox (/var/mail/fernan) is empty, since I | use procmail to deliver messages to several different | mailboxes under ~/mail. | | Still, I keep receving this message all the time. Right now | it says I have 50 messages. What are they? Where are they? | | # echo $MAIL | | should tell you... | +] Hi! Thanks for your reply, [EMAIL PROTECTED] echo $MAIL /var/mail/fernan [EMAIL PROTECTED] ls -l $MAIL -rw-rw 1 fernan mail 0 Oct 4 09:56 /var/mail/fernan As I said, the default mailbox (/var/mail/fernan, aka $MAIL) is empty, since I use procmail to deliver to ~/mail/inbox (default) and other mailboxes under ~/mail. I've just sent a reply to another suggestion I got. I've CC'ed @questions. Fernan, still intrigued. -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: explain annoying You have XXX mail messages
+[ Mailing Lists Catcher [EMAIL PROTECTED] (03.Oct.2003 19:53): | | I don't know if this applies now but before I ran my own mail server I | used to see that sort of thing after I su'd so another account. For | instance if I logged in as user but su'd to a root it would tell me I | had mail but when I used the mail command it said no mail for user. I | forget how I was able to read root mail but I think it had something to | do with using su -m... Hi! Thanks for the reply. Yes I know this happens ... I can su to other users and see the 'You have mail.' message. However if I read mail for that user, and say, delete all messages, after I exit (/var/mail/user is now an empty file) and reenter I don't see this message anymore. | Anyhow root normally gets mail all the time from crontab and periodic | daily/weekly/monthly/security runs. | | Or Have a look in var/mail/root and others to see who has the mail. | Also use the mail command on the account you get the messages from next. I'm using the default sendmail that comes with freebsd. All mail to root gets redirected to me (alias root: [EMAIL PROTECTED]). And yes, I receive all the mails from root's cron jobs and periodic scripts. Still, /var/mail/fernan is empty all the time (I use procmail to deliver to ~/mail/inbox), and there's no /var/mail/root (since it is redirected to myseldf). All other users in the system have empty /var/mail/$USER files, since I'm the only user in the system :) So ... I'm still intrigued: i) I don't get 'You have mail.' but 'You have 50 mail messages.' That is to say ... the message is different, perhaps someone out there can identify the program that produces this kind of messages upon entering the shell? ii) ~/mail/inbox does not have 50 mail messages, it has thousands. Also, there are no new or unread messages ... iii) if I type 'mail', right after receiving the message, I get 'No mail for fernan.' as a reply. Thanks for any tip or suggestion, Fernan | | | On Fri, 2003-10-03 at 17:08, Fernan Aguero wrote: | Hi! | | I'd like to understand why every time I open a new terminal | (or just type 'csh' in a terminal) I get a message similar | to: | | You have XXX mail messages. | | The default mailbox (/var/mail/fernan) is empty, since I | use procmail to deliver messages to several different | mailboxes under ~/mail. | | Still, I keep receving this message all the time. Right now | it says I have 50 messages. What are they? Where are they? | | I've already read the man pages for csh(1), looked in | sourced rc files (~/.cshrc, /etc/csh.cshrc, ~/.login, | /etc/csh.login) and, as far as I can see, there is nothing | that looks like checking on available messages. | | It's been also difficult to google a common phrase like 'you | have mail messages' to look for already answered questions. | | I apologize is this is a FAQ. | | Thanks in advance, | | Fernan | -- | Mailing Lists Catcher [EMAIL PROTECTED] | MGM Communications LLC kibserv | | +] -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
explain annoying You have XXX mail messages
Hi! I'd like to understand why every time I open a new terminal (or just type 'csh' in a terminal) I get a message similar to: You have XXX mail messages. The default mailbox (/var/mail/fernan) is empty, since I use procmail to deliver messages to several different mailboxes under ~/mail. Still, I keep receving this message all the time. Right now it says I have 50 messages. What are they? Where are they? I've already read the man pages for csh(1), looked in sourced rc files (~/.cshrc, /etc/csh.cshrc, ~/.login, /etc/csh.login) and, as far as I can see, there is nothing that looks like checking on available messages. It's been also difficult to google a common phrase like 'you have mail messages' to look for already answered questions. I apologize is this is a FAQ. Thanks in advance, Fernan -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
booting a different kernel each time
Hi, I need to send my everyday machine (pentiumIII) to repair. I will take the disks and move them to a spare pentiumI so I can keep working meanwhile. The problem is I need to have a kernel that will work with a different processor and with a different ethernet card. My question: are there any issues in having two different kernels and booting from the alternatively? I mean switching kernels before booting so I don't have to 'unload' a kernel at boot time and then load a diffent one. And: should I backup both the kernel and the kernel modules under a different name (kernel.p3, modules.p3/) so I can then boot from it later? Thanks in advance, Fernan PS: please CC me since I'm not subscribed to the list -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installing python2 on linux_base-7.1
+[ Esto dijo paul ([EMAIL PROTECTED]): | | Fernan Aguero wrote: | | Can I safely ignore these and force python2 to install? | | | any reason why you can't just use the ports version? You mean /usr/ports/lang/python20 or python21? No ... I need the linux one. I have a linux software package that installs a web interface and all cgi scripts are written in python. In the past I just got along with linux_base 6 and linux-python15, and I'm now upgrading this package which now needs python2. For some reason that I don't understand it just don't work with a native FreeBSD python (I had already gone the path of changing all '#!/usr/bin/env python' to either '#!/path_to_FBSD_binary' or ''#!/usr/bin/env path_to_FBSD_binary' to no avail. Pointing all scripts to '#!/usr/bin/env /compat/linux/usr/bin/env python' just works). But then I need the linux binary installed under /compat/linux/. Fernan | | +] -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
installing python2 on linux_base-7.1
--- I am sending this message to questions since I got no --- reply from freebsd-emulation, which I supposed was the --- correct mailing-list for this topic. I am also CCing --- freebsd-ports which is the maintainer of the linux_base --- port. Hi! I am trying to install python2 from rpm over a recently updated linux_base-7.1 (linux_base-6 - lihux_base-7). I am invoking rpm with the following command line options: pi# rpm --allfiles --ignoreos --root /compat/linux --dbpath /var/lib/rpm --replacepkgs -i python2-2.2.1-2.i386.rh7.3.rpm I get several failed dependencies, they are mostly shared libraries. I search rpmfind.net with each one and downloaded the rpm package corresponding to RedHat-7.3 i386, as I guessed that this is the closer I can get. Is my reasoning here correct? Now after installing and cleaning most dependencies I still have these ones to fulfill: error: failed dependencies: libdb-3.2.so is needed by python2-2.2.1-2 libdb.so.3 is needed by python2-2.2.1-2 libreadline.so.4 is needed by python2-2.2.1-2 However, libreadline apparently is installed by linux_base (distinfo lists it as readline-4.1-9.i386.rpm). My rpmfind.net search says that libreadline.so.4 is installed by readline-4.2a-4.i386.rpm. Upon trying to install this one I get the following: file /usr/lib/libhistory.so.4 from install of readline-4.2a-4 conflicts with file from package readline-4.1-9 file /usr/lib/libreadline.so.4 from install of readline-4.2a-4 conflicts with file from package readline-4.1-9 file /usr/share/info/history.info.gz from install of readline-4.2a-4 conflicts with file from package readline-4.1-9 file /usr/share/info/readline.info.gz from install of readline-4.2a-4 conflicts with file from package readline-4.1-9 file /usr/share/info/rluserman.info.gz from install of readline-4.2a-4 conflicts with file from package readline-4.1-9 file /usr/share/man/man3/readline.3.gz from install of readline-4.2a-4 conflicts with file from package readline-4.1-9 So why does python2 still complains about a failed dependency? Also with libdb, apparently it is already installed by linux_base. However in this case, I get a failed dependency on db3x-3.2.9-4.i386.rpm (from rpmfind.net): error: failed dependencies: libtcl.so.0 is needed by db3x-3.2.9-4 However I cannot seem to find any rpm providing this library on rpmfind.net Can I safely ignore these and force python2 to install? Any tips or suggestions are welcome. Fernan -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
linux_base vs linux_base-6?
I have recently finished a clean installation of FreeBSD-4.6.2. Since I run linux binaries I chose to install the linux-compatibility packages from the install media. This currently is linux_base-6, if I read it right. Now many ports have their dependencies listed as linux_base-7.1 or something similar. This means that my linux-compatibility tree got updated when I installed some of this ports? or should I do this manually by going to /usr/ports/emulators/linux_base and doing a 'make install'? Now, what are the pros and cons of -7.1 and -6? Suggestions? Fernan -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
