Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 16:17:06 -0700 Chuck Swiger cswi...@mac.com wrote: There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. The code that's being run does the following: 1. Finds all network interfaces. 2. Finds all CDROM, floppy, disk and network devices that might be needed for installation. 3. Finds all partitions on the disks to register. I'd guess it's hanging on a syscall somewhere, but there really isn't much debugging output in usr.sbin/sysinstall/devices.c to know where, unless the kernel has printed some errors to the debug console. -- Bruce Cran ___ 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: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 11:09 PM, Bruce Cran br...@cran.org.uk wrote: On Mon, 19 Jul 2010 16:17:06 -0700 Chuck Swiger cswi...@mac.com wrote: There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. The code that's being run does the following: 1. Finds all network interfaces. 2. Finds all CDROM, floppy, disk and network devices that might be needed for installation. 3. Finds all partitions on the disks to register. I'd guess it's hanging on a syscall somewhere, but there really isn't much debugging output in usr.sbin/sysinstall/devices.c to know where, unless the kernel has printed some errors to the debug console. -- Bruce Cran ___ 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 This is why I suspected #3 - maybe querying the disk and hanging because of bad disk? Hard to say without debug logs. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Emacs splash screen went to textmode only
Markus Hoenicka writes: Ashish SHUKLA writes: Can you upload the screenshot of what you're getting ? Hi, I've uploaded a screenshot right here: http://www.abload.de/img/emacs-splashaws1.png The image shows four incarnations of Emacs. These are, clockwise starting from upper left: 1) Emacs started remotely on my laptop through ssh. This Emacs is slightly older (23.1.1) than the one on my desktop (23.2.1). This is what an unfiddled-with splash screen is supposed to look like in recent versions. 2) Emacs started on my desktop, using -q -no-site-file as per your suggestion. There are no graphics and no colors. Can you please provide output of following: 1. xrdb -q|grep '^Emacs' from an terminal running in X11. 2. (display-grayscale-p) in *scratch* buffer in GNU Emacs running in X11. 3. system-configuration-options in *scratch* buffer in GNU Emacs. Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ “I find the whole business of religion profoundly interesting. But it does mystify me that otherwise intelligent people take it seriously.” (Douglas Adams) pgp4a7JqOhmI1.pgp Description: PGP signature
Re: system hangs on; Probing devices, please wait (this can take a while)...
I had this problem trying to install FreeBSD on my old computer: Cx486DX2 CPU at 66 MHz; 20 MB RAM; 1.2 GB IDE hard drive; 2x Texel, now Plextor, CD-ROM on Trantor T130B SCSI (NCR5380 chip; no support in FreeBSD = 3.0); Iomega Zip 250 on same SCSI card. That was in the days of FreeBSD 4.x. No such problem on my newer computer with FreeBSD 7.x and now 8.0. I wondered if this part had been revamped with FreeBSD 5.x. If you could boot a FreeBSD live file system, for which downloadable iso images are now available, you might be able to look at the sysinstall scripts, and after partitioning/disklabeling (bsdlabel), you might be able to newfs and make mount points, and untar the pieces (base.aa, base.ab, etc) onto the desired FreeBSD target slice. I've wondered why FreeBSD installation sets (base, etc, games, comp, man and others) are broken into pieces of 1392 KB each as opposed to each installation set in a single .tgz or .tbz (base.tgz, etc.tgz, comp.tgz, and others: that's how NetBSD does it). NetBSD installation CD also offers a utility shell (sh). With floppy disks and floppy drives showing their age, I wouldn't be able to get enough good floppy disks together to install FreeBSD from floppies, and I believe others would have the same problem. I never actually did this, so I can't be sure if I'd succeed: decidedly not user-friendly but might be interesting to try in a pinch. Tom ___ 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: sockets stuck in use
On Mon, Jul 19, 2010 at 11:04 PM, Adam Vande More amvandem...@gmail.com wrote: On Mon, Jul 19, 2010 at 3:12 AM, Jim stapleton...@gmail.com wrote: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. sockstat(1) will tell you process that has the socket open, can you kill it from there? -- Adam Vande More Thanks... That told me who to kill ___ 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
Dtrace ustack status
Hi, Does anyone know what the status of dtrace being able to trace userland processes is? I see there are few patches out there but am unsure of the reliability etc. ___ 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
custom log in website folder
Dear all, All my website logs are in /var/log but one user would like to have access to a custom log specific to his site. Sites are in /usr/local/v/ How can I make /var/log/custom.log available to him in /usr/local/v/site/logs/? Does it need a symlink? But will he be able to read the log if it is only a symlink to /var/log/custom.log? I'd appreciate your suggestions and sorry for asking a basically non-freebsd related question but this community has always been a wonderul source of inspiration and help. Thank you! Zbigniew Szalbot ___ 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
HP proliant ML 150 G6 Server
Hi, I'm in looking for FreeBSD server for my employer. The server will be our main server. At the moment we are looking at 'HP proliant ML 150 G6 server' and are keen on hearing about users experience. Any advice or personal experience on this matter would be most welcomed. http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/15351-15351-241434-241646-3328424-3884323.html Yours, Alex P.S. Please CC me, as I am not on the list. ___ 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: custom log in website folder
On Tue, Jul 20, 2010 at 01:18:50PM +0200, Zbigniew Szalbot wrote: Dear all, All my website logs are in /var/log but one user would like to have access to a custom log specific to his site. Sites are in /usr/local/v/ How can I make /var/log/custom.log available to him in /usr/local/v/site/logs/? Does it need a symlink? But will he be able to read the log if it is only a symlink to /var/log/custom.log? I'd appreciate your suggestions and sorry for asking a basically non-freebsd related question but this community has always been a wonderul source of inspiration and help. You can probably configure your web server to write separate logs for each site you host. That way, you don't need to expose the entire log data to each user - each will see only what's relevant to their site. How you do this depends on the web server you use, of course. You should also be able to have the log files written to your preferred location. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpe2SmC47hsK.pgp Description: PGP signature
Re: Dtrace ustack status
On Tue, 20 Jul 2010 12:03:09 +0100 krad kra...@googlemail.com wrote: Does anyone know what the status of dtrace being able to trace userland processes is? I see there are few patches out there but am unsure of the reliability etc. http://freebsdfoundation.blogspot.com/2010/06/dtrace-userland-project.html -- Bruce Cran ___ 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: nautilus crashing on right click properties
Joe Marcus Clarke mar...@freebsd.org writes: On 7/19/10 9:49 AM, Jerry wrote: FreeBSD 8.1-PRERELEASE / amd64 Platform Version 4.4.5 (KDE 4.4.5) I installed nautilus via the /usr/ports/sysutils/eiciel port. I can start nautilus successfully, however, whenever I right click on a file or directory and choose properties, nautilus crashes. I tried to build it with debug support; however, I am not getting much info back. [...] Eel:ERROR:eel-wrap-table.c:494:wrap_table_get_num_fitting: assertion failed: (max_child_size 0) Sometime ago I tried to use nautilus with fluxbox. Nautilus (launched at xterm) crashed with similar error. I didn't have full gnome2 installation at that host. [...] I am not sure if the problem is actually with nautilus or eiciel. Most likely eiciel given the errors. Remove it, and see if the crash persists. I don't think that it's an eiciel fault. Since nautilus works with gnome I assume that not all dependencies are build/installed for pure nautilus port. -- WBR, bsam ___ 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
Help with setting up a mail server
I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job ___ 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: Help with setting up a mail server
On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ I kind of want to slay the dragon. Let's go to work. Angel's final words. ___ 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: Help with setting up a mail server
On Tue, 20 Jul 2010 09:33:28 -0400 Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. We had also tried sendmail and couldn't get that working either so I suspect it is a general config issue not a MTA one. (I have set sendmail up about 30 times in the past so I know a little bit about it) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: custom log in website folder
Assuming you're running apache make the virtualhost directive for the domain look something like this: VirtualHost *:80 ServerName domain.com ServerAlias www.domain.com DocumentRoot/usr/local/v/site/logs/domain.com/htdocs/ CustomLog /usr/local/v/site/logs/domain.com/logs/access_log combined ErrorLog/usr/local/v/site/logs/domain.com/logs/error_log /VirtualHost Make the changes to the * if you need to and the domains. -- Ryan On Jul 20, 2010, at 6:18 AM, Zbigniew Szalbot wrote: Dear all, All my website logs are in /var/log but one user would like to have access to a custom log specific to his site. Sites are in /usr/local/v/ How can I make /var/log/custom.log available to him in /usr/local/v/site/logs/? Does it need a symlink? But will he be able to read the log if it is only a symlink to /var/log/custom.log? I'd appreciate your suggestions and sorry for asking a basically non-freebsd related question but this community has always been a wonderul source of inspiration and help. Thank you! Zbigniew Szalbot ___ 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: Help with setting up a mail server
On Tue, 20 Jul 2010 09:46:09 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: On Tue, 20 Jul 2010 09:33:28 -0400 Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. We had also tried sendmail and couldn't get that working either so I suspect it is a general config issue not a MTA one. (I have set sendmail up about 30 times in the past so I know a little bit about it) Might I suggest that you supply some log entries that support your claims. It is hard to help you without actual facts. By the way, did you also try Postfix? -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ They spell it da Vinci and pronounce it da Vinchy. Foreigners always spell better than they pronounce. Mark Twain ___ 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: Help with setting up a mail server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh M. Friedman wrote: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job Hi Aryeh, Here are some things that I do to troubleshoot problems like this: - - Check if there are any firewalls (client-side or server-side) that block the ports, tcp 25/587 and tcp 110/143 in this case. If you're using POP3 or IMAP over SSL, check tcp 993 and tcp 995, too. - - Check if the listening ports are ready to accept connections with the command netstat -an | grep LISTEN. Do you see the ports you expect? - - Dumb question - are the mail server processes running? - - Assuming the processes are running and the ports are listening, what happens when you telnet to them from within the machine, e.g.: telnet localhost 25 telnet localhost 110 telnet localhost 143 - - Can you ping the mail server hostname? - - Use dig to do lookups on your A and MX records. Did you bump the DNS serial number and reload the DNS server after you added the records? - - If that works, now try telnetting to the same ports from an outside network using the DNS hostnames, e.g.: telnet my.mail.server.com 25 ... - - Please send me your hostname privately, if you like, and I can check DNS and ports from here. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMRa/E0sRouByUApARAsZwAJwIB6hXWwi2x2Wys94WyjHUJfF4fgCglmiR RYfOIA1ePOLwXcWj1xRrdFk= =j2tU -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: system hangs on; Probing devices, please wait (this can take a while)...
Ok I booted on the 8.0 live CD and pressed Alt-F2 when it gets hung. In verbose mode it says this: DEBUG: ioctl(3, TIOCCONC, NULL) = 0 (success) DEBUG: MADT: Found CPUAPIC ID 1 enabled DEBUG: MADT: Found CPUAPIC ID 2 enabled DEBUG: MADT: Found CPUAPIC ID 3 enabled DEBUG: MADT: Found CPUAPIC ID 4 enabled DEBUG: Notify: Probing devices, please wait (this can take a while)... DEBUG: Found a network device named re0 DEBUG: Found a network device named re1 DEBUG: Found a network device named fwe0 DEBUG: Found a network device named fwip0 DEBUG: deviceTry: attempting to open /dev/cd0 DEBUG: deviceTry: open of /dev/cd0 failed. DEBUG: deviceTry: attempting to open /dev/cd1 DEBUG: deviceTry: open of /dev/cd1 failed. DEBUG: deviceTry: attempting to open /dev/cd2 DEBUG: deviceTry: open of /dev/cd2 failed. DEBUG: deviceTry: attempting to open /dev/cd3 DEBUG: deviceTry: open of /dev/cd3 failed. DEBUG: deviceTry: attempting to open /dev/mcd0 DEBUG: deviceTry: open of /dev/mcd0 failed. DEBUG: deviceTry: attempting to open /dev/mcd1 DEBUG: deviceTry: open of /dev/mcd1 failed. DEBUG: deviceTry: attempting to open /dev/mcd2 DEBUG: deviceTry: open of /dev/mcd2 failed. DEBUG: deviceTry: attempting to open /dev/mcd3 DEBUG: deviceTry: open of /dev/mcd3 failed. DEBUG: deviceTry: attempting to open /dev/scd0 DEBUG: deviceTry: open of /dev/scd0 failed. DEBUG: deviceTry: attempting to open /dev/scd1 DEBUG: deviceTry: open of /dev/scd1 failed. DEBUG: deviceTry: attempting to open /dev/scd2 DEBUG: deviceTry: open of /dev/scd2 failed. DEBUG: deviceTry: attempting to open /dev/scd3 DEBUG: deviceTry: open of /dev/scd3 failed. DEBUG: deviceTry: attempting to open /dev/acd0 DEBUG: deviceTry: open of /dev/acd0 succeeded on first try. DEBUG: deviceTry: attempting to open /dev/acd1 DEBUG: deviceTry: open of /dev/acd1 failed. DEBUG: deviceTry: attempting to open /dev/acd2 DEBUG: deviceTry: open of /dev/acd2 failed. DEBUG: deviceTry: attempting to open /dev/acd3 DEBUG: deviceTry: open of /dev/acd3 failed. DEBUG: deviceTry: attempting to open /dev/fd0 DEBUG: deviceTry: open of /dev/fd0 failed. DEBUG: deviceTry: attempting to open /dev/fd1 DEBUG: deviceTry: open of /dev/fd1 failed. DEBUG: deviceTry: attempting to open /dev/fd2 DEBUG: deviceTry: open of /dev/fd2 failed. DEBUG: deviceTry: attempting to open /dev/fd3 DEBUG: deviceTry: open of /dev/fd3 failed. DEBUG: deviceTry: attempting to open /dev/scd0 DEBUG: deviceTry: open of /dev/scd0 failed. DEBUG: deviceTry: attempting to open /dev/cuad0 DEBUG: deviceTry: open of /dev/cuacd0 failed. DEBUG: deviceTry: attempting to open /dev/cuad1 DEBUG: deviceTry: open of /dev/cuacd1 failed. DEBUG: deviceTry: attempting to open /dev/cuad2 DEBUG: deviceTry: open of /dev/cuacd2 failed. DEBUG: deviceTry: attempting to open /dev/cuad3 DEBUG: deviceTry: open of /dev/cuacd3 failed. DEBUG: deviceTry: attempting to open /dev/cuad4 DEBUG: deviceTry: open of /dev/cuacd4 failed. DEBUG: deviceTry: attempting to open /dev/cuad5 DEBUG: deviceTry: open of /dev/cuacd5 failed. DEBUG: deviceTry: attempting to open /dev/cuad6 DEBUG: deviceTry: open of /dev/cuacd6 failed. DEBUG: deviceTry: attempting to open /dev/cuad7 DEBUG: deviceTry: open of /dev/cuacd7 failed. DEBUG: deviceTry: attempting to open /dev/cuad8 DEBUG: deviceTry: open of /dev/cuacd8 failed. DEBUG: deviceTry: attempting to open /dev/cuad9 DEBUG: deviceTry: open of /dev/cuacd9 failed. DEBUG: deviceTry: attempting to open /dev/cuad10 DEBUG: deviceTry: open of /dev/cuacd10 failed. DEBUG: deviceTry: attempting to open /dev/cuad11 DEBUG: deviceTry: open of /dev/cuacd11 failed. DEBUG: deviceTry: attempting to open /dev/cuad12 DEBUG: deviceTry: open of /dev/cuacd12 failed. DEBUG: deviceTry: attempting to open /dev/cuad13 DEBUG: deviceTry: open of /dev/cuacd13 failed. DEBUG: deviceTry: attempting to open /dev/cuad14 DEBUG: deviceTry: open of /dev/cuacd14 failed. DEBUG: deviceTry: attempting to open /dev/cuad15 DEBUG: deviceTry: open of /dev/cuacd15 failed. DEBUG: deviceTry: attempting to open /dev/da0 DEBUG: deviceTry: open of /dev/da0 failed. DEBUG: deviceTry: attempting to open /dev/da1 DEBUG: deviceTry: open of /dev/da1 failed. DEBUG: deviceTry: attempting to open /dev/da2 DEBUG: deviceTry: open of /dev/da2 failed. DEBUG: deviceTry: attempting to open /dev/da3 DEBUG: deviceTry: open of /dev/da3 failed. DEBUG: deviceTry: attempting to open /dev/da4 DEBUG: deviceTry: open of /dev/da4 failed. DEBUG: deviceTry: attempting to open /dev/da5 DEBUG: deviceTry: open of /dev/da5 failed. DEBUG: deviceTry: attempting to open /dev/da6 DEBUG: deviceTry: open of /dev/da6 failed. DEBUG: deviceTry: attempting to open /dev/da7 DEBUG: deviceTry: open of /dev/da7 failed. DEBUG: deviceTry: attempting to open /dev/da8 DEBUG: deviceTry: open of /dev/da8 failed. DEBUG: deviceTry: attempting to open /dev/da9 DEBUG: deviceTry: open of /dev/da9 failed. DEBUG: deviceTry: attempting to open /dev/da10 DEBUG: deviceTry: open of /dev/da10 failed. DEBUG: deviceTry: attempting to open /dev/da11
Re: system hangs on; Probing devices, please wait (this can take a while)...
Disks are not bad. Works with other OSes. Problem is with FreeBSD. I've tried versions 4.6, 7.2, 8.0 and 9.0. Only FreeBSD 4.6 boots without hanging. I've not tried 5 or 6 but I guess I could if it would help to narrow down what the changes were in those versions. Something obviously changed along the way to cause it to hang. From: Randi Harper ra...@freebsd.org To: Bruce Cran br...@cran.org.uk Cc: Chuck Swiger cswi...@mac.com; FreeBSD - freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 11:19:06 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Mon, Jul 19, 2010 at 11:09 PM, Bruce Cran br...@cran.org.uk wrote: On Mon, 19 Jul 2010 16:17:06 -0700 Chuck Swiger cswi...@mac.com wrote: There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. The code that's being run does the following: 1. Finds all network interfaces. 2. Finds all CDROM, floppy, disk and network devices that might be needed for installation. 3. Finds all partitions on the disks to register. I'd guess it's hanging on a syscall somewhere, but there really isn't much debugging output in usr.sbin/sysinstall/devices.c to know where, unless the kernel has printed some errors to the debug console. -- Bruce Cran ___ 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 This is why I suspected #3 - maybe querying the disk and hanging because of bad disk? Hard to say without debug logs. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dtrace ustack status
On 20 July 2010 13:02, Bruce Cran br...@cran.org.uk wrote: On Tue, 20 Jul 2010 12:03:09 +0100 krad kra...@googlemail.com wrote: Does anyone know what the status of dtrace being able to trace userland processes is? I see there are few patches out there but am unsure of the reliability etc. http://freebsdfoundation.blogspot.com/2010/06/dtrace-userland-project.html -- Bruce Cran Thanks thats good however its a letter of intent only. Does anyone know how its going, and is it likely to be delivered? September sounds like a tight time line to me as from what ive read its a fairly complex task. ___ 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: ipnat.conf - map and rdr won't work!
On Mon, Jul 19, 2010 at 12:38 PM, Erik Norgaard norga...@locolomo.org wrote: On 19/07/10 16.46, alexus wrote: Use tcpdump, you should see if your rdr/map rules work as expected. Also, pfctl -ss and similar. i don't know how to use tcpdump, can you provide exact syntax so i can run it? The man-page is excelent. tried that, unfortunately not really sure what am i doing.. still Can't help you more, really, you need to investigate where packets are dropped, tcpdump is a great tool and the man-page is excelent, can't explain it better, if you don't like tcpdump then use any other packet sniffing tool at hand, snort for example. ipmon: 20/07/2010 10:22:00.123106 @2 NAT:RDR 172.16.172.16,22 - - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] 20/07/2010 10:26:00.340436 @2 NAT:EXPIRE 172.16.172.16,22 - - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] Pkts 11/0 Bytes 640/0 tcpdump: tcpdump: listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes 11:40:07.366519 IP (tos 0x0, ttl 49, id 48580, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc05d (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387932 0,sackOK,eol 11:40:08.346575 IP (tos 0x0, ttl 49, id 19079, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc054 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387941 0,sackOK,eol 11:40:09.102442 IP (tos 0x0, ttl 49, id 28097, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc04a (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387951 0,sackOK,eol 11:40:10.108089 IP (tos 0x0, ttl 49, id 28130, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc040 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387961 0,sackOK,eol 11:40:11.104669 IP (tos 0x0, ttl 49, id 27900, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc036 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387971 0,sackOK,eol 11:40:12.110396 IP (tos 0x0, ttl 49, id 56214, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc02c (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387981 0,sackOK,eol 11:40:14.105642 IP (tos 0x0, ttl 49, id 41429, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc018 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91388001 0,sackOK,eol 11:40:18.114148 IP (tos 0x0, ttl 49, id 30423, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol 11:40:21.899739 arp who-has 64.52.58.36 tell 64.52.58.33 11:40:24.830499 arp who-has 64.52.58.36 tell 64.52.58.33 11:40:26.125568 IP (tos 0x0, ttl 49, id 25515, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol 11:40:42.157443 IP (tos 0x0, ttl 49, id 18773, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol 11:41:14.193555 IP (tos 0x0, ttl 49, id 42007, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol ^C180 packets captured 182 packets received by filter 0 packets dropped by kernel Do packets can get dropped because of your firewall default policy? For stealth it may be set to simply drop packets which result in a connection time-out rather than send a TCP-RST. su-3.2# grep ^firewall /etc/rc.conf firewall_enable=YES firewall_type=open su-3.2# ipfw show 00100 5478792380 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any 65000 869903 554820708 allow ip from any to any 65535 0 0 deny ip from any to any su-3.2# grep ^ip /etc/rc.conf ipfilter_enable=YES ipmon_enable=YES ipnat_enable=YES ipnat_flags=-d su-3.2# i even did this su-3.2# /etc/rc.d/ipfw stop net.inet.ip.fw.enable: 1 - 0 su-3.2# Do packets get dropped because of nat on the way in? or on the way out? i tried disabling map rule and leave only rdr, that didn't help What if you just disable ipnat? What if you flush the firewall rules? (disconnect from the Internet first) if i disable ipnat then map or rdr wont work as they simply disabled i disabled ipfw, and i dont have any rules inside of ipfilter Do you have any logs in the jail that indicate that the first packet is actually received? Do your
Re: Help with setting up a mail server
On 20/07/10 15.26, Aryeh M. Friedman wrote: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. First, as everybody else: If you are not satisfied with the default sendmail the most popular alternative seems to be postfix, it will probably be much easier for you to get help with postfix should the problem turn out to be the mail configuration. When you modify your DNS it may take a while before the changes propagate, depending on the TTL setting in your zone configuration. You can check if the mail server is running and can deliver mail locally by, on the mail server, do $ telnet localhost 25 You can then type in manually the smtp commands, see rfc 2821. If you can, then it may be a dns problem. Next, can you send out? You may well be able to send out while you can't receive mail from external servers for local delivery. If this is the case, either your DNS is wrong or the changes has not yet propagated. If you can't, check the error messages, if there is some dns related error look in /etc/resolv.conf to see if you use the right dns server, do some dns queries to check that it works. If you use your own dns server, check the named.conf and verify any forwarders entries. If you can't receive mail from external servers for local delivery, but local delivery works - locally. Try from a different host to telnet to your mail server using the ip address, $ telnet mail-server-ip 25 If this works, maybe your dns changes has not yet propagated. If more time than the TTL has passed and your dns does not resolve correctly, check that you updated the serial number in the zone file, it must be incremented every time you make a modification or the changes won't propagate to dns slaves. If you can't connect, maybe you have a firewall issue. This I think should get you started trouble shooting. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them If you found my advice useful, please donate a reasonable fee to the FreeBSD project, I am still endepted for the great effort of all the people involved in the project. BR, Erik ___ 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: ipnat.conf - map and rdr won't work!
alexus wrote: On Mon, Jul 19, 2010 at 12:38 PM, Erik Norgaard norga...@locolomo.org wrote: On 19/07/10 16.46, alexus wrote: Use tcpdump, you should see if your rdr/map rules work as expected. Also, pfctl -ss and similar. i don't know how to use tcpdump, can you provide exact syntax so i can run it? The man-page is excelent. tried that, unfortunately not really sure what am i doing.. still Can't help you more, really, you need to investigate where packets are dropped, tcpdump is a great tool and the man-page is excelent, can't explain it better, if you don't like tcpdump then use any other packet sniffing tool at hand, snort for example. ipmon: 20/07/2010 10:22:00.123106 @2 NAT:RDR 172.16.172.16,22 - - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] 20/07/2010 10:26:00.340436 @2 NAT:EXPIRE 172.16.172.16,22 - - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] Pkts 11/0 Bytes 640/0 tcpdump: tcpdump: listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes 11:40:07.366519 IP (tos 0x0, ttl 49, id 48580, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc05d (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387932 0,sackOK,eol 11:40:08.346575 IP (tos 0x0, ttl 49, id 19079, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc054 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387941 0,sackOK,eol 11:40:09.102442 IP (tos 0x0, ttl 49, id 28097, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc04a (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387951 0,sackOK,eol 11:40:10.108089 IP (tos 0x0, ttl 49, id 28130, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc040 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387961 0,sackOK,eol 11:40:11.104669 IP (tos 0x0, ttl 49, id 27900, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc036 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387971 0,sackOK,eol 11:40:12.110396 IP (tos 0x0, ttl 49, id 56214, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc02c (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91387981 0,sackOK,eol 11:40:14.105642 IP (tos 0x0, ttl 49, id 41429, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc018 (correct), 208454974:208454974(0) win 65535 mss 1380,nop,wscale 3,nop,nop,timestamp 91388001 0,sackOK,eol 11:40:18.114148 IP (tos 0x0, ttl 49, id 30423, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol 11:40:21.899739 arp who-has 64.52.58.36 tell 64.52.58.33 11:40:24.830499 arp who-has 64.52.58.36 tell 64.52.58.33 11:40:26.125568 IP (tos 0x0, ttl 49, id 25515, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol 11:40:42.157443 IP (tos 0x0, ttl 49, id 18773, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol 11:41:14.193555 IP (tos 0x0, ttl 49, id 42007, offset 0, flags [DF], proto TCP (6), length 48) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0x8b0d (correct), 208454974:208454974(0) win 65535 mss 1380,sackOK,eol ^C180 packets captured 182 packets received by filter 0 packets dropped by kernel Do packets can get dropped because of your firewall default policy? For stealth it may be set to simply drop packets which result in a connection time-out rather than send a TCP-RST. su-3.2# grep ^firewall /etc/rc.conf firewall_enable=YES firewall_type=open su-3.2# ipfw show 00100 5478792380 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any 65000 869903 554820708 allow ip from any to any 65535 0 0 deny ip from any to any su-3.2# grep ^ip /etc/rc.conf ipfilter_enable=YES ipmon_enable=YES ipnat_enable=YES ipnat_flags=-d su-3.2# i even did this su-3.2# /etc/rc.d/ipfw stop net.inet.ip.fw.enable: 1 - 0 su-3.2# Do packets get dropped because of nat on the way in? or on the way out? i tried disabling map rule and leave only rdr, that didn't help What if you just disable ipnat? What if you flush the firewall rules? (disconnect from the Internet first) if i disable ipnat then map or rdr wont work as they simply disabled i disabled ipfw, and i dont have any rules inside of ipfilter Do you have any logs in the jail that indicate that the first packet is actually received? Do your
Re: ipnat.conf - map and rdr won't work!
su-3.2# grep ^firewall /etc/rc.conf firewall_enable=YES firewall_type=open su-3.2# grep ^ip /etc/rc.conf ipfilter_enable=YES ipmon_enable=YES ipnat_enable=YES ipnat_flags=-d This is not good. You are running 2 different firewalls at the same time. comment out firewall_enable=YES firewall_type=open and reboot your system. ___ 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 do you know that for a fact or you just guessing?? because first of all it worked before just fine with 2 firewalls second i disabled firewall, so firewall is no longer an issue third i have another system just like that that runs 2 firewall and everything working just fine! if you dont know the answer there is no need to throw just any answer as its pretty clear that this isn't the right answer -- http://alexus.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: startkde: Could not start kdeinit4. Check your installation.
hello fellas, can no one give me any ideas ? I reinstalled libthr.so.3 in the meantime but with no effect. ___ 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
Recommend ezjail.conf settings?
Hi folks, I'm looking at the ezjail.conf file, and it seems like SOME of the settings might be mandatory, but they're all commented out. For example, the: # ezjail_mount_enable=YES # ezjail_devfs_enable=YES # ezjail_devfs_ruleset=devfsrules_jail # ezjail_procfs_enable=YES # ezjail_fdescfs_enable=YES should be uncommented because they're Default options for newly created jails, right? Are there any of the other settings I might want to consider enabling? Thank you, Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipnat.conf - map and rdr won't work!
On 20/07/10 18.02, alexus wrote: On Mon, Jul 19, 2010 at 12:38 PM, Erik Norgaardnorga...@locolomo.org wrote: On 19/07/10 16.46, alexus wrote: Can't help you more, really, you need to investigate where packets are dropped, tcpdump is a great tool and the man-page is excelent, can't explain it better, if you don't like tcpdump then use any other packet sniffing tool at hand, snort for example. ipmon: 20/07/2010 10:22:00.123106 @2 NAT:RDR 172.16.172.16,22- - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] 20/07/2010 10:26:00.340436 @2 NAT:EXPIRE 172.16.172.16,22- - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] Pkts 11/0 Bytes 640/0 tcpdump: tcpdump: listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes 11:40:07.366519 IP (tos 0x0, ttl 49, id 48580, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc05d (correct), 208454974:208454974(0) win 65535mss 1380,nop,wscale 3,nop,nop,timestamp 91387932 0,sackOK,eol 0 packets dropped by kernel What tcpdump options did you use, on what interface? where did you run it? on the hosting system or within the jail? Do packets can get dropped because of your firewall default policy? For stealth it may be set to simply drop packets which result in a connection time-out rather than send a TCP-RST. i disabled ipfw, and i dont have any rules inside of ipfilter You do have the default rule. IIRC this is set when you compile ipfilter, it can be set to either block or pass. If you don't remember what it was, then you can override it by configuring two rules: pass in quick all pass out quick all Do you have any logs in the jail that indicate that the first packet is actually received? Do your firewall log connections? If not, see how you can enable logs on all rules to get more information. nothing gets to jail there for no logs inside of jail Ok, but you should be able to configure log on your firewall/nat rules. IIRC ipfilter does not permit log statement on nat rules, you can switch to packet filter it has almost same syntax and permits log. Can you connect out from the jail, to external servers? only to the jail hosting server? Did the jail's ssh log tell anything? no i can not connect out from jail, as map doesn't work either nothing gets to Nor to the hosting system? You wrote you can connect with ssh from the hosting server to the jail, but it took a long time, did you investigate this? Is there some DNS issue that times out and causes the connection to fail? what about that long time I recall you mentioned? Can you ping your jail? Can you ping out? Default route is configured? i can ping my jail within host environment once again nothing within jail works as map (nat) isn't working Are you sure you're actually ping'ing the jail? IIRC from your previous mail you have configured the jail IP both on the host environment and in the jail. So I suppose that from your host environment you can ssh into the jail? Did ssh start up, netstat -l? From the jail, can you ping the host environment? default router isn't configured in rc.conf (inside of jail) as per jail's man page its not needed it was working fine before without it There are tons of tests you can do to figure out what's failing. Do you have additional external ip addresses available? Last time I played around with jail, I had this: ifconfig_vr1=inet 172.16.0.1/23 # Hosting system ifconfig_vr1_alias0=inet 172.16.0.2/32 # Jail jail_test_ip=172.16.0.2 So that would create an alias for for the jail and bypasss the need for rdr. BR, Erik ___ 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: ipnat.conf - map and rdr won't work!
On 20/07/10 18.37, alexus wrote: You are running 2 different firewalls at the same time. comment out firewall_enable=YES firewall_type=open and reboot your system. do you know that for a fact or you just guessing?? because first of all it worked before just fine with 2 firewalls second i disabled firewall, so firewall is no longer an issue third i have another system just like that that runs 2 firewall and everything working just fine! if you dont know the answer there is no need to throw just any answer as its pretty clear that this isn't the right answer Regardless of your previous experience, it is a bad idea to have two different firewalls configured and enabled at the same time. It provides no additional security and makes debugging a mess. Have you considered the possibility of both ipfw and ipfilter doing both filtering and nat? Another thing, I think I've mentioned before, you may have to reload firewall/nat rules after the jail starts. BR, Erik ___ 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: system hangs on; Probing devices, please wait (this can take a while)...
On 07/20/2010 02:42 AM, Thomas Mueller wrote: I've wondered why FreeBSD installation sets (base, etc, games, comp, man and others) are broken into pieces of 1392 KB each as opposed to each installation set in a single .tgz or .tbz (base.tgz, etc.tgz, comp.tgz, and others: that's how NetBSD does it). NetBSD installation CD also offers a utility shell (sh). With floppy disks and floppy drives showing their age, I wouldn't be able to get enough good floppy disks together to install FreeBSD from floppies... If I were to hazard a guess, I'd say it's because not everyone who uses FreeBSD is on a broadband connection, and a 56MB download (just for base.??) is a bit too large to fetch in a single session, if for some reason you are unable to resume the transfer after interruption. But the floppy thing might be a good reason too. Especially since all you really need is one working floppy disk and two floppy-drive-equipped computers to do it. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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: new jail utility is available. announcement.
On Tue, 20 Jul 2010 12:29:56 +0800 Aiza aiz...@comclark.com articulated: This is a news announcement to inform people who have interest in jails, that a new jail utility is available. http://sourceforge.net/projects/qjail/ Has a file suitable for the pkg_add command or the port make files can be downloaded and a make install run. Qjail [ q = quick ] is a 4th generation wrapper for the basic chroot jail system that includes security and performance enhancements. Plus a new level of user friendliness enhancements dealing with deploying just a few jails or large jail environments consisting of 100's of jails. Qjail requires no knowledge of the jail command usage. It uses nullfs for read-only system binaries, sharing one copy of them with all the jails. Uses mdconfig to create sparse image jails. Sparse image jails provide a method to limit the total disk space a jail can consume, while only occupying disk space of the sum size of the files in the image jail. Ability to assign ip address with their network device name, so aliases are auto created on jail start and auto removed on jail stop. Ability to create ZONEs of identical qjail systems, each with their own group of jails. Ability to designate a portion of the jail name as a group prefix so the command being executed will apply to only those jail names matching that prefix. Qjail reduces the complexities of small and large jail deployments to the novice level. Qjail has a fully documented manpage written for easy comprehension. Details are given to felicitate the use of qjail's capabilities to the fullest extent possible. There presently does not exist a port for this, or at least I could not find one. Is someone going to create a port? -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Sadoequinecrophilia, n.: Beating a dead horse. ___ 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: [kde-freebsd] startkde: Could not start kdeinit4. Check your installation.
On Tue, 20 Jul 2010 18:51:50 +0200, claudiu vasadi wrote: hello fellas, can no one give me any ideas ? I reinstalled libthr.so.3 in the meantime but with no effect. I got it last night and simply recompiling kdelibs was sufficient: sudo portupgrade -f kdelibs Rusty Nejdl http://networking.ringofsaturn.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: Help with setting up a mail server
On Tue, Jul 20, 2010 at 4:46 PM, Aryeh M. Friedman aryeh.fried...@gmail.com wrote: On Tue, 20 Jul 2010 09:33:28 -0400 Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. We had also tried sendmail and couldn't get that working either so I suspect it is a general config issue not a MTA one. (I have set sendmail up about 30 times in the past so I know a little bit about it) Exim is a very good choice. Forget the Postfix suggestions. It's Sendmail's brother:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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: Help with setting up a mail server
On Tue, Jul 20, 2010 at 09:03:55PM +0300, Odhiambo Washington wrote: On Tue, Jul 20, 2010 at 4:46 PM, Aryeh M. Friedman aryeh.fried...@gmail.com wrote: On Tue, 20 Jul 2010 09:33:28 -0400 Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. We had also tried sendmail and couldn't get that working either so I suspect it is a general config issue not a MTA one. (I have set sendmail up about 30 times in the past so I know a little bit about it) Exim is a very good choice. Forget the Postfix suggestions. It's Sendmail's brother:-) Sendmail comes from a good family. jerry -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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: ipnat.conf - map and rdr won't work!
On Tue, Jul 20, 2010 at 12:57 PM, Erik Norgaard norga...@locolomo.org wrote: On 20/07/10 18.02, alexus wrote: On Mon, Jul 19, 2010 at 12:38 PM, Erik Norgaardnorga...@locolomo.org wrote: On 19/07/10 16.46, alexus wrote: Can't help you more, really, you need to investigate where packets are dropped, tcpdump is a great tool and the man-page is excelent, can't explain it better, if you don't like tcpdump then use any other packet sniffing tool at hand, snort for example. ipmon: 20/07/2010 10:22:00.123106 @2 NAT:RDR 172.16.172.16,22- - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] 20/07/2010 10:26:00.340436 @2 NAT:EXPIRE 172.16.172.16,22- - 64.52.58.58,22 [69.10.67.106,6346 PR tcp] Pkts 11/0 Bytes 640/0 tcpdump: tcpdump: listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes 11:40:07.366519 IP (tos 0x0, ttl 49, id 48580, offset 0, flags [DF], proto TCP (6), length 64) 69.10.67.106.9408 64.52.58.58.22: S, cksum 0xc05d (correct), 208454974:208454974(0) win 65535mss 1380,nop,wscale 3,nop,nop,timestamp 91387932 0,sackOK,eol 0 packets dropped by kernel What tcpdump options did you use, on what interface? where did you run it? on the hosting system or within the jail? 'tcpdump -n -i fxp0 -vv' was run on host fxp0 is a public interface Do packets can get dropped because of your firewall default policy? For stealth it may be set to simply drop packets which result in a connection time-out rather than send a TCP-RST. i disabled ipfw, and i dont have any rules inside of ipfilter You do have the default rule. IIRC this is set when you compile ipfilter, it can be set to either block or pass. the main reason why i have ipfilter is because it requires by ipnat If you don't remember what it was, then you can override it by configuring two rules: pass in quick all pass out quick all done su-3.2# cat /etc/ipf.rules | grep -v ^# pass in quick all pass out quick all su-3.2# Do you have any logs in the jail that indicate that the first packet is actually received? Do your firewall log connections? If not, see how you can enable logs on all rules to get more information. nothing gets to jail there for no logs inside of jail Ok, but you should be able to configure log on your firewall/nat rules. IIRC ipfilter does not permit log statement on nat rules, you can switch to packet filter it has almost same syntax and permits log. plan b is to run natd, but i'd rather run ipnat especially that ipnat used to work before no problem! Can you connect out from the jail, to external servers? only to the jail hosting server? Did the jail's ssh log tell anything? no i can not connect out from jail, as map doesn't work either nothing gets to Nor to the hosting system? i'm able to ssh out from jail to a host system as this local, no map (nat) is needed for this connection You wrote you can connect with ssh from the hosting server to the jail, but it took a long time, did you investigate this? Is there some DNS issue that times out and causes the connection to fail? what about that long time I recall you mentioned? my guess it's trying to do dns reverse look up and since map (nat) doesn't work it takes long time back in the days when nat was working, sshing it didn't take long time at all Can you ping your jail? Can you ping out? Default route is configured? i can ping my jail within host environment once again nothing within jail works as map (nat) isn't working Are you sure you're actually ping'ing the jail? IIRC from your previous mail you have configured the jail IP both on the host environment and in the jail. su-3.2# ping -c1 lama PING lama (172.16.172.16): 56 data bytes 64 bytes from 172.16.172.16: icmp_seq=0 ttl=64 time=0.075 ms --- lama ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.075/0.075/0.075/0.000 ms su-3.2# ip address tells me that this is in fact jail's IP So I suppose that from your host environment you can ssh into the jail? Did ssh start up, netstat -l? From the jail, can you ping the host environment? su-3.2# jls JID IP Address Hostname Path 1 172.16.172.16 lama /usr/jail/lama su-3.2# jexec 1 /etc/rc.d/sshd status sshd is running as pid 1085. su-3.2# ps -p 1085 PID TT STAT TIME COMMAND 1085 ?? IsJ0:00.00 /usr/sbin/sshd su-3.2# default router isn't configured in rc.conf (inside of jail) as per jail's man page its not needed it was working fine before without it There are tons of tests you can do to figure out what's failing. Do you have additional external ip addresses available? unfortunately no, if i had them i wouldn't need to do map nor rdr Last time I played around with jail, I had this: ifconfig_vr1=inet 172.16.0.1/23 # Hosting system ifconfig_vr1_alias0=inet 172.16.0.2/32 # Jail jail_test_ip=172.16.0.2 So that would create an
Re: ipnat.conf - map and rdr won't work!
On Tue, Jul 20, 2010 at 1:03 PM, Erik Norgaard norga...@locolomo.org wrote: On 20/07/10 18.37, alexus wrote: You are running 2 different firewalls at the same time. comment out firewall_enable=YES firewall_type=open and reboot your system. do you know that for a fact or you just guessing?? because first of all it worked before just fine with 2 firewalls second i disabled firewall, so firewall is no longer an issue third i have another system just like that that runs 2 firewall and everything working just fine! if you dont know the answer there is no need to throw just any answer as its pretty clear that this isn't the right answer Regardless of your previous experience, it is a bad idea to have two different firewalls configured and enabled at the same time. It provides no additional security and makes debugging a mess. that's why i disabled ipfw for now, as it's only used for traffic shapping and ipfilter used for filtering and it's part of ipnat. Have you considered the possibility of both ipfw and ipfilter doing both filtering and nat? not according to ipfw show, it's as open as it gets. su-3.2# ipfw show 00100 2894 283660 allow ip from any to any via lo0 00200 00 deny ip from any to 127.0.0.0/8 00300 00 deny ip from 127.0.0.0/8 to any 65000 56006 24726087 allow ip from any to any 65535 00 deny ip from any to any su-3.2# Another thing, I think I've mentioned before, you may have to reload firewall/nat rules after the jail starts. i tried that but that didn't really solve anything BR, Erik ___ 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 -- http://alexus.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: ipnat.conf - map and rdr won't work!
alexus wrote: su-3.2# grep ^firewall /etc/rc.conf firewall_enable=YES firewall_type=open su-3.2# grep ^ip /etc/rc.conf ipfilter_enable=YES ipmon_enable=YES ipnat_enable=YES ipnat_flags=-d This is not good. You are running 2 different firewalls at the same time. comment out firewall_enable=YES firewall_type=open and reboot your system. do you know that for a fact or you just guessing?? because first of all it worked before just fine with 2 firewalls second i disabled firewall, so firewall is no longer an issue third i have another system just like that that runs 2 firewall and everything working just fine! if you dont know the answer there is no need to throw just any answer as its pretty clear that this isn't the right answer Just because 2 firewalls at same time didn't blow up in your face before, sure don't mean they are working correctly. Thats one bad assumption to base debugging on. Jumping in my face, questioning the free advice given, sure makes you look foolish. You should read the handbook firewall section before opening your month and sticking your foot into it. People on this list will stop helping if you turn on them and bit the hand that feeds you. And another thing. Network access for a jail is not controlled by the hosts firewall. You need to look else where for your jail network access solution. If your attitude was not so XXX, I could have told you the solution, but now go learn it the hard way. ___ 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: new jail utility is available. announcement.
Jerry wrote: On Tue, 20 Jul 2010 12:29:56 +0800 Aiza aiz...@comclark.com articulated: This is a news announcement to inform people who have interest in jails, that a new jail utility is available. http://sourceforge.net/projects/qjail/ Has a file suitable for the pkg_add command or the port make files can be downloaded and a make install run. Qjail [ q = quick ] is a 4th generation wrapper for the basic chroot jail system that includes security and performance enhancements. Plus a new level of user friendliness enhancements dealing with deploying just a few jails or large jail environments consisting of 100's of jails. Qjail requires no knowledge of the jail command usage. It uses nullfs for read-only system binaries, sharing one copy of them with all the jails. Uses mdconfig to create sparse image jails. Sparse image jails provide a method to limit the total disk space a jail can consume, while only occupying disk space of the sum size of the files in the image jail. Ability to assign ip address with their network device name, so aliases are auto created on jail start and auto removed on jail stop. Ability to create ZONEs of identical qjail systems, each with their own group of jails. Ability to designate a portion of the jail name as a group prefix so the command being executed will apply to only those jail names matching that prefix. Qjail reduces the complexities of small and large jail deployments to the novice level. Qjail has a fully documented manpage written for easy comprehension. Details are given to felicitate the use of qjail's capabilities to the fullest extent possible. There presently does not exist a port for this, or at least I could not find one. Is someone going to create a port? Like the announcement said the port is available at http://sourceforge.net/projects/qjail/ And if you have ever submitted a new port for inclusion into the freebsd ports system you would know that it takes months for it to show up in the collection. So you can wait till xmas or RELEASE 9.0 to come out for the port to be in the ports collection or just fetch it form the development project site. ___ 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: Help with setting up a mail server
Message: 24 Date: Tue, 20 Jul 2010 14:05:13 -0400 From: Jerry McAllister jerr...@msu.edu Subject: Re: Help with setting up a mail server To: Odhiambo Washington odhia...@gmail.com Cc: Aryeh M. Friedman aryeh.fried...@gmail.com, freebsd-questions@freebsd.org Message-ID: 20100720180513.gb46...@gizmo.acns.msu.edu Content-Type: text/plain; charset=iso-8859-1 On Tue, Jul 20, 2010 at 09:03:55PM +0300, Odhiambo Washington wrote: On Tue, Jul 20, 2010 at 4:46 PM, Aryeh M. Friedman aryeh.fried...@gmail.com wrote: On Tue, 20 Jul 2010 09:33:28 -0400 Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. We had also tried sendmail and couldn't get that working either so I suspect it is a general config issue not a MTA one. (I have set sendmail up about 30 times in the past so I know a little bit about it) Exim is a very good choice. Forget the Postfix suggestions. It's Sendmail's brother:-) Sendmail comes from a good family. jerry -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube At the risk of starting a flame war, I think sendmail gets a bad rap. It's not been the most widely used MTA for the last few decades because it sucks. It's about personal preference. Now I know this may be redundant advice but I used to run an MTA and enjoyed having the use of it and freedom to have my own mailserver at home. But alas, the spammers have ruined that for all of us and almost every ISP out there will block port 25 by default. Even if they don't block port 25 it will only be a matter of time before they detect your outgoing mail traffic and then block you so that you're forced to purchase an add-on service to run your own MTA. They will use lame excuses that you've been blacklisted because of spam. It's simply their way of making you cough up extra dough for your service. This is one of the parts of the Internet that I really hate and long for the good old days. ___ 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: Recommend ezjail.conf settings?
Ed Flecko wrote: Hi folks, I'm looking at the ezjail.conf file, and it seems like SOME of the settings might be mandatory, but they're all commented out. For example, the: # ezjail_mount_enable=YES # ezjail_devfs_enable=YES # ezjail_devfs_ruleset=devfsrules_jail # ezjail_procfs_enable=YES # ezjail_fdescfs_enable=YES should be uncommented because they're Default options for newly created jails, right? Are there any of the other settings I might want to consider enabling? Thank you, Ed Of course their commented out. Those are the default settings hard coded in the ezjail-admin script. You have no need to ever change those. Leave the conf file alone. Messing with it will only cause you problems. And I suggest you leave that dinosaur ezjail to it death and move on to its replacement, qjail. Which is a complete rewrite of ezjail, fixing all of its long time bugs and adding many new features. ___ 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: ipnat.conf - map and rdr won't work!
On Tue, Jul 20, 2010 at 2:16 PM, Aiza aiz...@comclark.com wrote: alexus wrote: su-3.2# grep ^firewall /etc/rc.conf firewall_enable=YES firewall_type=open su-3.2# grep ^ip /etc/rc.conf ipfilter_enable=YES ipmon_enable=YES ipnat_enable=YES ipnat_flags=-d This is not good. You are running 2 different firewalls at the same time. comment out firewall_enable=YES firewall_type=open and reboot your system. do you know that for a fact or you just guessing?? because first of all it worked before just fine with 2 firewalls second i disabled firewall, so firewall is no longer an issue third i have another system just like that that runs 2 firewall and everything working just fine! if you dont know the answer there is no need to throw just any answer as its pretty clear that this isn't the right answer Just because 2 firewalls at same time didn't blow up in your face before, sure don't mean they are working correctly. Thats one bad assumption to base debugging on. i never had any problem doing so, not that i'm saying it's a smart thing to do i'm well aware of that, and as i mention before both firewall doing different purposes its not like i'm filtering packets with both firewalls at the same time. Jumping in my face, questioning the free advice given, sure makes you look foolish. You should read the handbook firewall section before opening your month and sticking your foot into it. i wasn't jumping in your face, i just outline some of the facts. i'm asking help here, there is no point for me to jump anyone. People on this list will stop helping if you turn on them and bit the hand that feeds you. And another thing. Network access for a jail is not controlled by the hosts firewall. You need to look else where for your jail network access solution. my jail has a private IP address, so in order to get to my jail you need to go through public IP and that being hosted within host environment jail itself seem like it's functional fine as i can ssh into jail from host environment so my guess i gotta look somewhere inside of ipnat, since ipnat is responsible for routing packets from/to jail If your attitude was not so XXX, I could have told you the solution, but now go learn it the hard way. i'm sorry you feel that way, surely didn't mean anything bad by outlining facts. ___ 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 -- http://alexus.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: ipnat.conf - map and rdr won't work!
On 20/07/10 20.07, alexus wrote: On Tue, Jul 20, 2010 at 12:57 PM, Erik Norgaardnorga...@locolomo.org wrote: plan b is to run natd, but i'd rather run ipnat especially that ipnat used to work before no problem! Maybe move away from what used to work and towards what is working :) Whichever you prefer, just stick to one solution only. su-3.2# ping -c1 lama PING lama (172.16.172.16): 56 data bytes 64 bytes from 172.16.172.16: icmp_seq=0 ttl=64 time=0.075 ms --- lama ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.075/0.075/0.075/0.000 ms su-3.2# ip address tells me that this is in fact jail's IP Yes and no, if you shut down your jail you should still be able to ping that ip as I read your snippet from your rc.conf. So I suppose that from your host environment you can ssh into the jail? Did ssh start up, netstat -l? From the jail, can you ping the host environment? su-3.2# jls JID IP Address Hostname Path 1 172.16.172.16 lama /usr/jail/lama su-3.2# jexec 1 /etc/rc.d/sshd status sshd is running as pid 1085. su-3.2# ps -p 1085 PID TT STAT TIME COMMAND 1085 ?? IsJ0:00.00 /usr/sbin/sshd su-3.2# OK, but you didn't check where your ssh binds. i know, i can run it that IP address as an alias on public interface, but we on purpose added another NIC to be private NIC. Well, read the man jail(8): ip4.addr A comma-separated list of IPv4 addresses assigned to the prison. If this is set, the jail is restricted to using only these address. Any attempts to use other addresses fail, and attempts to use wildcard addresses silently use the jailed address instead. ... If I understand this correctly, remove the line jail_lama_ip=172.16.172.16 from your rc.conf and your jail can then bind to port 22 on the external interface thus bypassing the need for nat. This is ok, since all you did was redirecting traffic. And the map rule shouldn't be necessary either, nor should the fxp interface. BR, Erik ___ 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: ipnat.conf - map and rdr won't work!
On 20/07/10 20.43, alexus wrote: On Tue, Jul 20, 2010 at 2:16 PM, Aizaaiz...@comclark.com wrote: Just because 2 firewalls at same time didn't blow up in your face before, sure don't mean they are working correctly. Thats one bad assumption to base debugging on. i never had any problem doing so, not that i'm saying it's a smart thing to do i'm well aware of that, and as i mention before both firewall doing different purposes its not like i'm filtering packets with both firewalls at the same time. You've never had a problem? Or maybe you didn't know: Picture this: You've got two competing firewall solutions loaded at the same time. How do you know which one handles what? In fact, all firewalls comes with a default policy which is in effect if no rules are loaded. First, they are not consulted in parallel, just how would that work? maybe some sort of load balancing? So, maybe both are consulted, but does that mean that if solution A is consulted first, then solution B only see what is passed by A? Or maybe it sees both what is passed and blocked with the power to change that? What about stateful filtering, if solution A creates a state and B don't? Maybe only one of the solutions is actually consulted and the other one just hangs around without any effect? Then how would you know which one is A and which one is B? If both are consulted you need to keep sure their rulesets are equivalent, or who knows what else might happen? And if only one, which one? OK, so you say you use ipnat for redirect and map and ipfw for packet filtering. Even if we assume that ipfilter packet filtering capabilities does not alter the anything, then the next question would be does ipfw filtering take place before or after ipnat? Because you have to write your ruleset taking this into account. Iirc, ipfilter wraps around the kernel and takes over all packet handling. That means that any other firewall solution you have configured that is more tightly integrated with the kernel just hangs around doing nothing. All that traffic shaping you've done have no effect at all. So, you said, but it worked.. or did it? Well, packets may get passed, some may get blocked, that's easy to check, but does it mean that everything works according to your design? You mentioned traffic shaping. Have you actually tested and shown that this takes place and works as expected? Mixing multiple different firewall solutions is a recipe for disaster. As for choice of firewall, chose one, whichever, but just one. It's five years since I switched from ipfilter to packet filter. I don't know if ipfilter is still actively developed, last time, last year I tried to find the source code for Solaris and only found dead ends. I recommend packet filter, it should have the traffic shaping capabilities you mentioned. BR, Erik ___ 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: new jail utility is available. announcement.
On Wed, 21 Jul 2010 02:25:32 +0800 Aiza aiz...@comclark.com articulated: Like the announcement said the port is available at http://sourceforge.net/projects/qjail/ And if you have ever submitted a new port for inclusion into the freebsd ports system you would know that it takes months for it to show up in the collection. Actually, I have submitted a few ports. I believe it averaged only approximately 10 to 14 days before they were officially committed to the ports tree. Updating them usually takes 10 days or less. So you can wait till xmas or RELEASE 9.0 to come out for the port to be in the ports collection or just fetch it form the development project site. I guess I was just lucky I did not have to wait 6 months. I am assuming, perhaps incorrectly, that you might be the maintainer of this new port. What is the PR #? -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ There are a lot of lies going around and half of them are true. Winston Churchill ___ 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: ipnat.conf - map and rdr won't work!
alexus wrote: On Tue, Jul 20, 2010 at 2:16 PM, Aiza aiz...@comclark.com wrote: alexus wrote: su-3.2# grep ^firewall /etc/rc.conf firewall_enable=YES firewall_type=open su-3.2# grep ^ip /etc/rc.conf ipfilter_enable=YES ipmon_enable=YES ipnat_enable=YES ipnat_flags=-d This is not good. You are running 2 different firewalls at the same time. comment out firewall_enable=YES firewall_type=open and reboot your system. do you know that for a fact or you just guessing?? because first of all it worked before just fine with 2 firewalls second i disabled firewall, so firewall is no longer an issue third i have another system just like that that runs 2 firewall and everything working just fine! if you dont know the answer there is no need to throw just any answer as its pretty clear that this isn't the right answer Just because 2 firewalls at same time didn't blow up in your face before, sure don't mean they are working correctly. Thats one bad assumption to base debugging on. i never had any problem doing so, not that i'm saying it's a smart thing to do i'm well aware of that, and as i mention before both firewall doing different purposes its not like i'm filtering packets with both firewalls at the same time. Jumping in my face, questioning the free advice given, sure makes you look foolish. You should read the handbook firewall section before opening your month and sticking your foot into it. i wasn't jumping in your face, i just outline some of the facts. i'm asking help here, there is no point for me to jump anyone. People on this list will stop helping if you turn on them and bit the hand that feeds you. And another thing. Network access for a jail is not controlled by the hosts firewall. You need to look else where for your jail network access solution. my jail has a private IP address, so in order to get to my jail you need to go through public IP and that being hosted within host environment jail itself seem like it's functional fine as i can ssh into jail from host environment so my guess i gotta look somewhere inside of ipnat, since ipnat is responsible for routing packets from/to jail If your attitude was not so XXX, I could have told you the solution, but now go learn it the hard way. i'm sorry you feel that way, surely didn't mean anything bad by outlining facts. Have you copied your hosts /etc/resolv.conf file to your jail? How did you create your jail? ezjail??? What application are you planing on running inside of the jail? Did you give the jail the ip address of your public network? check it again to verify the numbers are correct. Doing ssh from the host is not the way to test. You need someone from the public network to try to ssh in by using your public ip address. But the first test, is to start the jail and access the jails console from the host and them issue dug or whois command from the jails console to see if you have outbound public network access. The ping command is a security leak and not allowed from a jail by design. See man jail for details about ping. If no public network access, then the hosts /etc/resolv.conf is missing form the jail, or named wrong, or not in the correct location or the jails assigned ip address is not your public ip address, or if you created the jail without using ezjail you messed it up. And all of this is done with all your firewalls disabled. And jails do not have their own firewalls. If your jail has one disable it. Firewalls DO NOT drive network traffic to a jail, so erase that idea from your mind. Your barking up the wrong tree going down that road. Your problem is not a firewall one, but a jail config one. This debugging method is called process of elimination ___ 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
Wifi AP behind FreeBSD
Hello, I am planning to change my network a little, I need to put WiFi AP (Dlink Di-524) behind FreeBSD box, there are 2 nic in this box - one should be for internet (xl0) and another should use xl1 nic for WiFi AP. I need to know how to setup routing in FreeBSD box, could someone help? And also when someone connect via WiFi, I want to get connected to internet. Now I use 192.168.0.0/24 adresses from WiFi AP dhcp. FreeBSD 8.0 thanks regards for any advice DadAN ___ 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: Wifi AP behind FreeBSD
Hi-- On Jul 20, 2010, at 12:09 PM, DadAN wrote: I need to know how to setup routing in FreeBSD box, could someone help? And also when someone connect via WiFi, I want to get connected to internet. Now I use 192.168.0.0/24 adresses from WiFi AP dhcp. There's fine documentation available at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-routing.html Regards, -- -Chuck ___ 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: new jail utility is available. announcement.
Jerry wrote: On Wed, 21 Jul 2010 02:25:32 +0800 Aiza aiz...@comclark.com articulated: Like the announcement said the port is available at http://sourceforge.net/projects/qjail/ And if you have ever submitted a new port for inclusion into the freebsd ports system you would know that it takes months for it to show up in the collection. Actually, I have submitted a few ports. I believe it averaged only approximately 10 to 14 days before they were officially committed to the ports tree. Updating them usually takes 10 days or less. So you can wait till xmas or RELEASE 9.0 to come out for the port to be in the ports collection or just fetch it form the development project site. I guess I was just lucky I did not have to wait 6 months. I am assuming, perhaps incorrectly, that you might be the maintainer of this new port. What is the PR #? There has been the normal pre RELEASE freeze on since xmas, that is why no port activity is occurring right now. http://www.freebsd.org/cgi/query-pr.cgi?pr=148777 ___ 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: Wifi AP behind FreeBSD
On 20/07/2010, at 21.09, DadAN dad...@gmail.com wrote: Hello, I am planning to change my network a little, I need to put WiFi AP (Dlink Di-524) behind FreeBSD box, there are 2 nic in this box - one should be for internet (xl0) and another should use xl1 nic for WiFi AP. I need to know how to setup routing in FreeBSD box, could someone help? You need to enable routing in the kernel, I've forgotten the kernel variable but do sysctl -a | grep rout Enable routing setting the variable to 1. Since you have a private network connecting to the Internet you need to configure nat. There are different solutions, I prefer packet filter. And also when someone connect via WiFi, I want to get connected to internet. Now I use 192.168.0.0/24 adresses from WiFi AP dhcp. FreeBSD 8.0 That's ok just configure the internal interface in that range. It should be possible to configure the AP so it won't assign ti ip of your freebsd box. You need to configure the AP such that the clients get default gateway set to the ip on the internal interface of your freebsd box. BR Erik. thanks regards for any advice DadAN ___ 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: ipnat.conf - map and rdr won't work!
On Tue, Jul 20, 2010 at 2:54 PM, Erik Norgaard norga...@locolomo.org wrote: On 20/07/10 20.07, alexus wrote: On Tue, Jul 20, 2010 at 12:57 PM, Erik Norgaardnorga...@locolomo.org wrote: plan b is to run natd, but i'd rather run ipnat especially that ipnat used to work before no problem! Maybe move away from what used to work and towards what is working :) Whichever you prefer, just stick to one solution only. right, yet I still would like to know where problem is :)) su-3.2# ping -c1 lama PING lama (172.16.172.16): 56 data bytes 64 bytes from 172.16.172.16: icmp_seq=0 ttl=64 time=0.075 ms --- lama ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.075/0.075/0.075/0.000 ms su-3.2# ip address tells me that this is in fact jail's IP Yes and no, if you shut down your jail you should still be able to ping that ip as I read your snippet from your rc.conf. you right, i'm pinging ip that resides on another interface and doesn't really belong to jail at the first place you asked me if I can ping jail from host, I dont know how else I can test it then pinging ip is kind of pointless then, so i ssh in that seems to be working, what else can I try? So I suppose that from your host environment you can ssh into the jail? Did ssh start up, netstat -l? From the jail, can you ping the host environment? su-3.2# jls JID IP Address Hostname Path 1 172.16.172.16 lama /usr/jail/lama su-3.2# jexec 1 /etc/rc.d/sshd status sshd is running as pid 1085. su-3.2# ps -p 1085 PID TT STAT TIME COMMAND 1085 ?? IsJ 0:00.00 /usr/sbin/sshd su-3.2# OK, but you didn't check where your ssh binds. su-3.2# netstat -tan | grep LISTEN | grep 22 tcp4 0 0 172.16.172.16.22 *.*LISTEN su-3.2# would that sufficient? I just don't know how else I can see .. i know, i can run it that IP address as an alias on public interface, but we on purpose added another NIC to be private NIC. Well, read the man jail(8): ip4.addr A comma-separated list of IPv4 addresses assigned to the prison. If this is set, the jail is restricted to using only these address. Any attempts to use other addresses fail, and attempts to use wildcard addresses silently use the jailed address instead. ... If I understand this correctly, remove the line jail_lama_ip=172.16.172.16 from your rc.conf and your jail can then bind to port 22 on the external interface thus bypassing the need for nat. This is ok, since all you did was redirecting traffic. And the map rule shouldn't be necessary either, nor should the fxp interface. BR, Erik i actually like this idea, i think i'm going give that a shot... i'll let you know how that worked out... -- http://alexus.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: new jail utility is available. announcement.
On Wed, 21 Jul 2010 03:45:37 +0800 Aiza aiz...@comclark.com articulated: There has been the normal pre RELEASE freeze on since xmas, that is why no port activity is occurring right now. http://www.freebsd.org/cgi/query-pr.cgi?pr=148777 Date: Tue, 20 Jul 2010 02:47:18 GMT It was only just submitted. I would hardly expect it to be committed yet. By the way, there has been a great deal of port activity since Christmas. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ For every complex problem, there is a solution that is simple, neat, and wrong. H. L. Mencken ___ 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: Help with setting up a mail server
On Tue, 20 Jul 2010 21:03:55 +0300 Odhiambo Washington odhia...@gmail.com articulated: On Tue, Jul 20, 2010 at 4:46 PM, Aryeh M. Friedman aryeh.fried...@gmail.com wrote: On Tue, 20 Jul 2010 09:33:28 -0400 Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. We had also tried sendmail and couldn't get that working either so I suspect it is a general config issue not a MTA one. (I have set sendmail up about 30 times in the past so I know a little bit about it) Exim is a very good choice. Forget the Postfix suggestions. It's Sendmail's brother:-) At least Postfix is fully RFC compliant, as opposed to Exim. SEE: RFC 2034 (SMTP enhanced status codes), RFC 3461-4 (delivery status notifications), RFC 1652 (8-bit MIME including 8-7bit conversion) among others. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ The wise shepherd never trusts his flock to a smiling wolf. ___ 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: Emacs splash screen went to textmode only
Quoting Olivier Nicole olivier.nic...@cs.ait.ac.th: Hi, 4) Another instance of Emacs on my desktop, this time running in a terminal. The startup screen is yet another one. In this one, I clearly recognize emacs being run inside an ascii terminal. Ascii terminal do not have graphic possibility (nor mousse) so it is only normal that there is no graphic splash screen. Yes, I am fully aware of that. In my original post I wondered if Emacs for some reason *thinks* it is running in a terminal and thus displays the terminal mode splash screen. But #2 and #4 are different, thus I proved myself wrong. If it is the same version of emacs that you run on the instances 2 and 3, I would look for a X issue. Do you have an environment variable set in the xterm? In that xterm, can you launch another xterm? Well, set displays a few screens full of environment variables, so, yes, of course there are some and they have to be there. But none of these affected Emacs before upgrading to 23.2.1. BTW launching another xterm from an xterm works without problems. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 ___ 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: new jail utility is available. announcement.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aiza wrote: Jerry wrote: On Wed, 21 Jul 2010 02:25:32 +0800 Aiza aiz...@comclark.com articulated: Like the announcement said the port is available at http://sourceforge.net/projects/qjail/ And if you have ever submitted a new port for inclusion into the freebsd ports system you would know that it takes months for it to show up in the collection. Actually, I have submitted a few ports. I believe it averaged only approximately 10 to 14 days before they were officially committed to the ports tree. Updating them usually takes 10 days or less. So you can wait till xmas or RELEASE 9.0 to come out for the port to be in the ports collection or just fetch it form the development project site. I guess I was just lucky I did not have to wait 6 months. I am assuming, perhaps incorrectly, that you might be the maintainer of this new port. What is the PR #? There has been the normal pre RELEASE freeze on since xmas, that is why no port activity is occurring right now. http://www.freebsd.org/cgi/query-pr.cgi?pr=148777 Hi Aiza, Where did you get that information? Whoever told you that is mistaken. A large number of commits have entered the ports tree since the beginning of the year. Have a look at the ports CVS mailing list archive since December 2009: http://lists.freebsd.org/pipermail/cvs-ports/ The ports tree does go into a freeze or slush state around release times, but that doesn't completely stop commits either, mostly sweeping changes that affect a great number of ports or introduce some other incompatibility. Here's some more information: http://www.freebsd.org/doc/en/articles/committers-guide/ports.html#AEN1466 Hope that helps, and thank you for your new port, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMRhRg0sRouByUApARAqpqAJ9bvM5El5YXO0GjCfkmwaZwy4pXHQCgvuuc QNAOpT/EElnICj72S97QAuY= =jIkQ -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: Emacs splash screen went to textmode only
Quoting Ashish SHUKLA ash...@freebsd.org: Can you please provide output of following: 1. xrdb -q|grep '^Emacs' from an terminal running in X11. [mar...@wutz /usr/home/markus]$ xrdb -q|grep '^Emacs' Emacs*font: Bitstream Vera Sans Mono-8 2. (display-grayscale-p) in *scratch* buffer in GNU Emacs running in X11. (display-grayscale-p) t 3. system-configuration-options in *scratch* buffer in GNU Emacs. system-configuration-options '--with-x-toolkit=gtk' '--x-libraries=/usr/local/lib' '--x-includes=/usr/local/include' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=i386-portbld-freebsd8.0' 'build_alias=i386-portbld-freebsd8.0' 'CC=cc' 'CFLAGS=-O2 -pipe -fno-strict-aliasing' 'LDFLAGS=-L/usr/local/lib -lintl' 'CPPFLAGS=-I/usr/local/include' BTW I've first built the Emacs port, and after I realized there was that splash screen issue I installed the package instead, just in case I managed to misconfigure the build somehow. Didn't make a difference. Thanks Thank you! Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 ___ 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: system hangs on; Probing devices, please wait (this can take a while)...
Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? From: Thomas Mueller mueller6...@bellsouth.net To: freebsd-questions@freebsd.org Sent: Tue, July 20, 2010 12:42:09 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... I had this problem trying to install FreeBSD on my old computer: Cx486DX2 CPU at 66 MHz; 20 MB RAM; 1.2 GB IDE hard drive; 2x Texel, now Plextor, CD-ROM on Trantor T130B SCSI (NCR5380 chip; no support in FreeBSD = 3.0); Iomega Zip 250 on same SCSI card. That was in the days of FreeBSD 4.x. No such problem on my newer computer with FreeBSD 7.x and now 8.0. I wondered if this part had been revamped with FreeBSD 5.x. If you could boot a FreeBSD live file system, for which downloadable iso images are now available, you might be able to look at the sysinstall scripts, and after partitioning/disklabeling (bsdlabel), you might be able to newfs and make mount points, and untar the pieces (base.aa, base.ab, etc) onto the desired FreeBSD target slice. I've wondered why FreeBSD installation sets (base, etc, games, comp, man and others) are broken into pieces of 1392 KB each as opposed to each installation set in a single .tgz or .tbz (base.tgz, etc.tgz, comp.tgz, and others: that's how NetBSD does it). NetBSD installation CD also offers a utility shell (sh). With floppy disks and floppy drives showing their age, I wouldn't be able to get enough good floppy disks together to install FreeBSD from floppies, and I believe others would have the same problem. I never actually did this, so I can't be sure if I'd succeed: decidedly not user-friendly but might be interesting to try in a pinch. Tom ___ 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: system hangs on; Probing devices, please wait (this can take a while)...
On Tue, 20 Jul 2010 14:59:04 -0700 (PDT) Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? It looks like it's stopping/spinning at the section where it parses the slices/partitions. I don't know why it would be getting stuck there, though. -- Bruce Cran ___ 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: Recommend ezjail.conf settings?
Hi Ed, On 7/20/10 12:54 PM, Ed Flecko wrote: Hi folks, I'm looking at the ezjail.conf file, and it seems like SOME of the settings might be mandatory, but they're all commented out. For example, the: # ezjail_mount_enable=YES Uncommenting and setting to NO would disable mounting the /basejail, read-only bits. # ezjail_devfs_enable=YES # ezjail_devfs_ruleset=devfsrules_jail If you have specific devfs needs for the jail, you can enable a special rule. Have a look at devfs(8) and devfs.conf(5) if you need to modify this, though you probably won't need to. # ezjail_procfs_enable=YES Disabling this will disable procfs(5). I recommend this one if you don't need procfs(5). # ezjail_fdescfs_enable=YES Similarly to procfs above. I haven't found any reason to disable this. should be uncommented because they're Default options for newly created jails, right? Correct, they are enabled by default, and show the default value. Are there any of the other settings I might want to consider enabling? Depends on what your usage needs are. :) Regards, -- Glen Barber ___ 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: system hangs on; Probing devices, please wait (this can take a while)...
Yes I have, that's not it. It's very frustrating because every CD I can find boots up except the FreeBSD CD. If it's not a bad drive nobody seems to know what else it could be. It's deeper than that. Something in the FreeBSD code. Isn't there a developer somewhere that can tell me what his code is doing? From: Andrew Gould andrewlylego...@gmail.com To: Rich rl...@pacbell.net Sent: Tue, July 20, 2010 3:52:21 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, Jul 20, 2010 at 4:59 PM, Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? Have you tried booting up with ACPI disabled? Best of luck, Andrew ___ 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: Emacs splash screen went to textmode only
Markus Hoenicka writes: Quoting Ashish SHUKLA ash...@freebsd.org: Can you please provide output of following: 1. xrdb -q|grep '^Emacs' from an terminal running in X11. [mar...@wutz /usr/home/markus]$ xrdb -q|grep '^Emacs' Emacs*font: Bitstream Vera Sans Mono-8 2. (display-grayscale-p) in *scratch* buffer in GNU Emacs running in X11. (display-grayscale-p) t And please also evaluate following functions in Emacs (in X11) and paste their output: (use-fancy-splash-screens-p) (display-graphic-p) (display-color-p) (image-type-available-p 'xpm) (image-type-available-p 'xbm) 3. system-configuration-options in *scratch* buffer in GNU Emacs. system-configuration-options '--with-x-toolkit=gtk' '--x-libraries=/usr/local/lib' --x-includes=/usr/local/include' '--prefix=/usr/local' --mandir=/usr/local/man' '--infodir=/usr/local/info/' --build=i386-portbld-freebsd8.0' build_alias=i386-portbld-freebsd8.0' 'CC=cc' 'CFLAGS=-O2 -pipe -fno-strict-aliasing' 'LDFLAGS=-L/usr/local/lib -lintl' CPPFLAGS=-I/usr/local/include' configuration flags look fine to me. BTW I've first built the Emacs port, and after I realized there was that splash screen issue I installed the package instead, just in case I managed to misconfigure the build somehow. Didn't make a difference. Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ “Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things.” (Robert A. Heinlein, 1973) pgpHHZhECO6or.pgp Description: PGP signature
Subscription to discussion cvs
We have received a request to subscribe you to the discussion c...@phing.tigris.org. If you wish to receive email notifications from this discussion, please reply to this message. If not, ignore this email. ___ 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: Help with setting up a mail server
On Tue, Jul 20, 2010 at 11:50 PM, Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 21:03:55 +0300 Odhiambo Washington odhia...@gmail.com articulated: On Tue, Jul 20, 2010 at 4:46 PM, Aryeh M. Friedman aryeh.fried...@gmail.com wrote: On Tue, 20 Jul 2010 09:33:28 -0400 Jerry freebsd.u...@seibercom.net wrote: On Tue, 20 Jul 2010 09:26:44 -0400 Aryeh M. Friedman aryeh.fried...@gmail.com articulated: I am a consultant and was retained by my client to setup qmail or exim on a VPS running 8.0-STABLE (i386). After setting up the DNS (A record and MX record) we have been unable to send or receive mail. The client has/had a working script for installing qmail on 7.1-STABLE but it seems to not work on 8.0-STABLE. They are using the same VPS provider who this 7.1-STABLE install script worked under. I have tried everything I can think of to make it work including asking obvious questions on -questi...@. I informed the client that the task is likely beyond me capabilities but I would help recruit someone who would be able to do it at a reasonable fee paid to them (I am acting as a no cost middle man on this [I am helping the client for free since I was unable to get it done]). Please send any ideas and/or offers to do the job I would seriously suggest that you consider installing Postfix. It is in the ports tree, is well maintained and works out of the box. The Postfix forum will be glad to give you any advice you need for setting up and securing your mail server. Qmail is no longer supported by its author and can be a nightmare to maintain. We had also tried sendmail and couldn't get that working either so I suspect it is a general config issue not a MTA one. (I have set sendmail up about 30 times in the past so I know a little bit about it) Exim is a very good choice. Forget the Postfix suggestions. It's Sendmail's brother:-) At least Postfix is fully RFC compliant, as opposed to Exim. SEE: RFC 2034 (SMTP enhanced status codes), RFC 3461-4 (delivery status notifications), RFC 1652 (8-bit MIME including 8-7bit conversion) among others. I doubt anyone makes a choice on an MTA (or any other software) based on it's RFC-compliance. In my experience, it's normally boils down to: 1. It has the features that I want 2. I can swim with it in times of toruble -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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
