Kernel compilation error for 7.0 ( with IPSEC )
Hi, people! I've just CvsUPed the src-all collection for RELENG_7_0 [This is a 7.0-RELEASE, as I understand, am I correct? ] trying to compile the source with IPSEC reselts in the following: --- ... xform_ipcomp.o(.text+0xcac):/usr/src/sys/netipsec/xform_ipcomp.c:570: undefined reference to `M_XDATA' xform_ipcomp.o(.text+0xcbc):/usr/src/sys/netipsec/xform_ipcomp.c:571: undefined reference to `crypto_freereq' xform_ipcomp.o(.text+0xda6):/usr/src/sys/netipsec/xform_ipcomp.c:584: undefined reference to `M_XDATA' xform_ipcomp.o(.text+0xdb6):/usr/src/sys/netipsec/xform_ipcomp.c:585: undefined reference to `crypto_freereq' *** Error code 1 Stop in /usr/obj/usr/src/sys/TKLGW_7. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- The question: what may be wrong with that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel compilation error for 7.0 ( with IPSEC )
Am Mon, 03 Mar 2008 15:15:29 +0300 schrieb Leonid Satanovsky [EMAIL PROTECTED]: Hi, people! I've just CvsUPed the src-all collection for RELENG_7_0 [This is a 7.0-RELEASE, as I understand, am I correct? ] RELENG_7_0 The release branch for FreeBSD-7.0, used only for security advisories and other critical fixes. trying to compile the source with IPSEC reselts in the following: --- ... xform_ipcomp.o(.text+0xcac):/usr/src/sys/netipsec/xform_ipcomp.c:570: undefined reference to `M_XDATA' xform_ipcomp.o(.text+0xcbc):/usr/src/sys/netipsec/xform_ipcomp.c:571: undefined reference to `crypto_freereq' xform_ipcomp.o(.text+0xda6):/usr/src/sys/netipsec/xform_ipcomp.c:584: undefined reference to `M_XDATA' xform_ipcomp.o(.text+0xdb6):/usr/src/sys/netipsec/xform_ipcomp.c:585: undefined reference to `crypto_freereq' *** Error code 1 Stop in /usr/obj/usr/src/sys/TKLGW_7. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- The question: what may be wrong with that? You are missing device crypto in your kernel config. Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel compilation error for 7.0 ( with IPSEC )
Be sure to have this stuff in kernel config file: options IPSEC options IPSEC_FILTERTUNNEL device crypto Cheers Norman Am Montag, den 03.03.2008, 15:15 +0300 schrieb Leonid Satanovsky: Hi, people! I've just CvsUPed the src-all collection for RELENG_7_0 [This is a 7.0-RELEASE, as I understand, am I correct? ] trying to compile the source with IPSEC reselts in the following: --- ... xform_ipcomp.o(.text+0xcac):/usr/src/sys/netipsec/xform_ipcomp.c:570: undefined reference to `M_XDATA' xform_ipcomp.o(.text+0xcbc):/usr/src/sys/netipsec/xform_ipcomp.c:571: undefined reference to `crypto_freereq' xform_ipcomp.o(.text+0xda6):/usr/src/sys/netipsec/xform_ipcomp.c:584: undefined reference to `M_XDATA' xform_ipcomp.o(.text+0xdb6):/usr/src/sys/netipsec/xform_ipcomp.c:585: undefined reference to `crypto_freereq' *** Error code 1 Stop in /usr/obj/usr/src/sys/TKLGW_7. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- The question: what may be wrong with that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PHP cli segfaults
Drew Sanford a écrit : Peter wrote: Drew Sanford wrote: | Command line programs for php seem to segfault on a 7.0RC1 box (yes, I | know, I should update to RC2) - for example: | | [EMAIL PROTECTED](~/bin)$ php -v | PHP 5.2.5 with Suhosin-Patch 0.9.6.2 (cli) (built: Feb 9 2008 13:03:20) | Copyright (c) 1997-2007 The PHP Group | Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies | zsh: segmentation fault (core dumped) php -v | | Any pointers? Just update and see if that fixes it? Thanks in advance. | | | uname output: | FreeBSD colossus.cotharyus.net 7.0-RC1 FreeBSD 7.0-RC1 #0: Sat Feb 9 | 11:43:37 CST 2008 Getting same thing, fresh install of 7.0 [cvsupped to rc2?], latest or not latest portsnap, I found it was the 'mhash.so' extension that was causing php to segfault - did portsnap update, and rebuilt all php stuff, still does same thing - have not tried it for last several weeks, so could be fixed by now...I did cvsup to latest sources... my emails were subjected apache coredump with 'mhash' php extension enabled - with mhash disabled, php works fine now. Will try and buildworld/reinstall php with the latest 7 sometime soon. ]Peter[ Good find Peter, I've got exactly the same system config at this point, and disabling mhash fixed it as well. Same problem with php5-mhash. I build it from the port, using FreeBSD7.0-RELEASE. I use PHP as apache module. Any ideas ? Thanks. -Nicolas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problems in ports of 7.0R
Hello, I'm preparing a fresh system with 7.0-RELEASE before updating my laptop for the daily-work; I've installed a clean 7.0-RELEASE with the ports tree but I'm running in some ports into problems, see below; until now I was thinking that even if the ports are not fully at the cutting edge, at least should be install-able without any problem, at least in 6.0R and 6.2R it has been this way; I'm wrong with that assumption? the problems are in detail: /usr/ports/emulators/qemu # make install === Vulnerability check disabled, database not found === Found saved configuration for qemu-0.9.1 === Extracting for qemu-0.9.1 = MD5 Checksum OK for qemu/qemu-0.9.1.tar.gz. = SHA256 Checksum OK for qemu/qemu-0.9.1.tar.gz. === qemu-0.9.1 depends on file: /usr/local/bin/perl5.8.8 - found === Patching for qemu-0.9.1 === qemu-0.9.1 depends on file: /usr/local/bin/perl5.8.8 - found === Applying FreeBSD patches for qemu-0.9.1 File to patch: ^C= Patch patch-PRId64 failed to apply cleanly. = Patch(es) patch-90_security patch-Makefile patch-Makefile.target applied cleanly. updating the port /usr/ports/emulators/qemu helps but ...; during the build the installation of /usr/ports/textproc/texi2html /usr/ports/lang/gcc34 /usr/ports/graphics/svgalib are failing, but work if they are done explictly by hand; /usr/ports/www/firefox # make install ... === Extracting for firefox-2.0.0.12,1 = MD5 Checksum OK for firefox-2.0.0.12-source.tar.bz2. = SHA256 Checksum OK for firefox-2.0.0.12-source.tar.bz2. === firefox-2.0.0.12,1 depends on file: /usr/local/bin/perl5.8.8 - found === Patching for firefox-2.0.0.12,1 === firefox-2.0.0.12,1 depends on file: /usr/local/bin/perl5.8.8 - found === Applying FreeBSD patches for firefox-2.0.0.12,1 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to content/canvas/src/nsCanvasRenderingContext2D.cpp.rej = Patch patch-content__canvas__src__nsCanvasRenderingContext2D.cpp failed to apply cleanly. = Patch(es) patch-Double.cpp patch-browser_app_mozilla.in patch-build_unix_run-mozilla.sh patch-config-mkdepend-imakemdep.h patch-config-rules.mk patch-config_autoconf.mk.in patch-config_mkdepend_Makefile.in patch-configure applied cleanly. *** Error code 1 Any hints? matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Variable Substitution
Hi: Forgive this basic question, but can´t figure out how to google it. If I want to substitute strings in an expression, I can use %s for string, or %d for digit. What about file? What is this process called, so I can find a howto? TIA, Victor ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dependencies in portmaster
[EMAIL PROTECTED] wrote: If you truly are just looking at the dependency list and do not wish to have make do anything, wouldn't this do the trick: http://portsmon.freebsd.org/portdependencytree.py Not quite, because it doesn't show which of the dependencies I have already got installed, and which of those would need to be updated. portmanager -s (ports-mgmt/portmanager) if I've understood your question right I don't know why people keep on ignoring this utility it is quite excellent and doesn't keep breaking things which portupgrade judging by posts to this list does. Perhaps I have something to learn here. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update and mergemaster
Chris Maness [EMAIL PROTECTED] writes: I was wondering if it was possible to use mergemaster with the binary update tool. It seemed like a much better way than freebsd-update dumping me into vi. I don't understand what it wants me to do with vi. Mergemaster is very clear. Can someone please shed light. Mergemaster just uses sdiff(1). Perhaps freebsd-update can be configured (e.g., with an EDITOR setting) to do the same? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Expanding file system
I am currently running FreeNAS on FreeBSD as a NAS device and it works great. Initially, I had a Highpoint RocketRAID card installed with 3 - 500 Gig drives attached configured in hardware as RAID 5. This gave me about 905 Gig usefull storage. The RAID card allows for adding hard drives via Online RAID Level Migration (ORLM) and this is waht I did. I added another 500 Gig drive and performed the ORLM. Everything worked great. No data was lost and I now have about 1.5 TB of storage but. The problem is, df only reports back the original 905 Gig. It seems that the RAID controller did migrate my data but left the additional space raw. What I need to know how to do now is extend my original partition (slice) to include the newly added space without loosing data. The array was originally formatted UFS in one partition (slice). I believe that using a combination of FDISK and FSGROW I should be able to do this but I am really afraid of losing my data (and I don't have a way to back up that much data). My experience is mainly in Linux and I know this is much different. I believe that I could probably boot up knoppix from CD and use gparted, but that would involve removing the NAS box from the rack and installing a CD drive and that's a real pain in the butt. I have no GUI, so everything has to be command line. Any help would be greatly appreciated. If for some reason I have sent this request to the wrong mail list I apologize and would request the correct list. Regards, Jeff Swan -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update and mergemaster
Chris Maness [EMAIL PROTECTED] writes: I was wondering if it was possible to use mergemaster with the binary update tool. It seemed like a much better way than freebsd-update dumping me into vi. I don't understand what it wants me to do with vi. Mergemaster is very clear. Can someone please shed light. Mergemaster just uses sdiff(1). Perhaps freebsd-update can be configured (e.g., with an EDITOR setting) to do the same? The mergemaster is a nice implementation as it really lets you see what is going on during the whole process. I like the the whole script as it lets you choose what version you want to keep for each and every file. Who is working on FreeBSD update? Maybe I can make a feature request. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update and mergemaster
Who is working on FreeBSD update? Maybe I can make a feature request. Or, even better, make a patch - FreeBSD is open source, everyone can work on it! Sorry, couldn't resist :-). I know the above remark is generally not very helpful for an average user; however, I was surprised to find out that the freebsd-update(8) was actually a shell script - i.e. modifying it doesn't require one to be a hard-core C hacker. freebsd-update(8) is part of the base system and is, as such, in the source tree that is freely available from the CVS repository (http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/freebsd-update/). Being a shell script also means you can go directly to /usr/sbin/freebsd-update and edit it in-place. The author, to the best of my knowledge, is Colin Percival, the current FreeBSD security officer (http://www.freebsd.org/security/index.html#sec). Regards, -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Uname borked on ??-Release...
Hello,
Been bashing myself on the head for a few days, so I'm
looking for a little help. If you've a big stick, read
on (and apologies if poor formatting, I'm using an unfamiliar
keyboard, unfamiliar mailer, and I'm not even sure if this
system is running FreeBSD anymore :-D )
I get the following from uname -a:
FreeBSD archangel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #6:
Sat Jun 2 09:22:50 CDT 2007 [EMAIL PROTECTED]:
/usr/obj/backup/src/sys/GENERIC i386
However, I rebuilt world, more or less without issues,
twice in February with RELENG_6 in the supfile. This
didn't change uname's output, and that worried me a bit.
So, to make matters bette^H^H^H^Hadder, I csup'ped
to RELENG_7_0 the day after it was release, read
/usr/src/UPDATING, and the webpage detailing the
upgrade, and did another buildworld/kernel cycle.
Now I have no idea if I'm on 6 or 7 (seems like
7, but many ports issues, and I've rebuilt them
all), and it's just becoming a major PITA.
Uname -a still shows the same string. However,
file dates in /bin, /sbin, etc., are Feb 28, and:
#cd /bin file grep
grep: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),
for FreeBSD 7.0 (700055), dynamically linked (uses shared libs),
FreeBSD-style, stripped
Manpages also show FreeBSD 7.0.
Trivia:
I blew away /usr/src and /usr/obj before the last
buildworld. They are not symlinked now, but apparently
were back last summer; /usr is at /dev/ad0s1e.
I've not yet done any of the old-libs commands; I do
have lots of ports failing with Bad system call and
I've got a lot of ports that wouldn't build because
configure was failing (C compiler cannot create
executables). There's more, but I'll wait until
something moves with this data, I think.
Question: why is uname reporting the {wrong} build?
Kevin Kinsey
--
I despise the pleasure of pleasing people whom I despise.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: looks like success
On Sunday 02 March 2008 03:50:43 am Daniel Gerzo wrote: Hello B., Thursday, February 28, 2008, 9:27:03 PM, you wrote: Hello all, make delete-old (took a long time to do by hand) and make delete-old-libs (went rather quickly) if you really want to delete all things: # yes | make delete-old While I've seen this suggestion before (and it's a very unix-y way to do it), the canonical method (from build(7)) is to run make -DBATCH_DELETE_OLD_FILES delete-old What I'd like to see (although I realize this isn't the correct forum..) is a make target that produces a list of files that _would_ be deleted, which the admin could then review and approve all or remove individual files to be preserved. But until I turn this into a useful PR or a nice request on a different list just consider it a rant. :) JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: looks like success
On Monday 03 March 2008 12:45:31 pm John Nielsen wrote: On Sunday 02 March 2008 03:50:43 am Daniel Gerzo wrote: Hello B., Thursday, February 28, 2008, 9:27:03 PM, you wrote: Hello all, make delete-old (took a long time to do by hand) and make delete-old-libs (went rather quickly) if you really want to delete all things: # yes | make delete-old While I've seen this suggestion before (and it's a very unix-y way to do it), the canonical method (from build(7)) is to run make -DBATCH_DELETE_OLD_FILES delete-old What I'd like to see (although I realize this isn't the correct forum..) is a make target that produces a list of files that _would_ be deleted, which the admin could then review and approve all or remove individual files to be preserved. But until I turn this into a useful PR or a nice request on a different list just consider it a rant. :) Heh.. I didn't read the manpage I just referred to closely enough. There's a check-old (and a check-old-libs) target that makes just such a list. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expanding file system
Jeffery Swan wrote: The problem is, df only reports back the original 905 Gig. It seems that the RAID controller did migrate my data but left the additional space raw. What I need to know how to do now is extend my original partition (slice) to include the newly added space without loosing data. You need to do three things in this order. i) update the disk partition table to match the new size of your composite drive. Essentially so long as your partition starts at the same place, you can move the partition end point to increase the size without massive breakage[*]. Use fdisk(8) to do this. ii) Update the partition table using bsdlabel(8). The same caveats apply about adding space at the end of a partition only. iii) Extend the UFS filesystem to fill up the newly available space. Use growfs(8) to do this. This is a job with a reasonably high risk of some mis-step destroying your data, so make very sure you have good backups before you begin. Cheers, Matthew [*] Ummm... assuming you're using the traditional partition / slice thing. If you're using gpt(8) then I'm not actually at all clear on how you would go about something like this. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uname borked on ??-Release...
Kevin Kinsey wrote:
Question: why is uname reporting the {wrong} build?
cd /usr/src
sudo make installkernel
--
Philip M. Gollucci ([EMAIL PROTECTED])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expanding file system
Actually, I am using GPT. -Jeff - Original Message - From: Matthew Seaman To: Jeffery Swan Subject: Re: Expanding file system Date: Mon, 03 Mar 2008 17:54:46 + Jeffery Swan wrote: The problem is, df only reports back the original 905 Gig. It seems that the RAID controller did migrate my data but left the additional space raw. What I need to know how to do now is extend my original partition (slice) to include the newly added space without loosing data. You need to do three things in this order. i) update the disk partition table to match the new size of your composite drive. Essentially so long as your partition starts at the same place, you can move the partition end point to increase the size without massive breakage[*]. Use fdisk(8) to do this. ii) Update the partition table using bsdlabel(8). The same caveats apply about adding space at the end of a partition only. iii) Extend the UFS filesystem to fill up the newly available space. Use growfs(8) to do this. This is a job with a reasonably high risk of some mis-step destroying your data, so make very sure you have good backups before you begin. Cheers, Matthew [*] Ummm... assuming you're using the traditional partition / slice thing. If you're using gpt(8) then I'm not actually at all clear on how you would go about something like this. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Maximum number established TCP connection
Hello I would like if there is a (countable) limit for the max TCP connection of a Apache web server. Suppose: 1. An apache web server serves a very big iso file. 2. 5000 people tried to connect to the apache server to get the iso file. 3. They connect to the server gradually (not 5000 people starting at the same moment). So that there will not be a problem caused by the TCP backlog limit. 4. There will be 5000 established TCP connections. Is it true that FreeBSD could handle 'unlimited' established TCP connections as long as it has enough CPU power and memory? Regards Patrick Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
telnet and rlogin problems
Rel: FreeBSD 6.2 Summary: I am unable to get either telnet or rlogin to function Details: To several of my PCs, that had been running 4.11, I have installed release 6.2. To the rc.conf, which was used for 4.11, I added: rcpbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_client_enable=YES mountd_enable=YES ftpd_enable=YES To hosts.allow, I added: rpcbind | ALL | allow To login.access, I added: +:ALL:.ursa.com I have looked in the handbook, Michael Lucas's 2nd Ed Absolute FreeBSD and in both the NOTES files for configuring the kernel, and I still am un- able to either telnet or rlogin to the box. I do not recall that I have made any changes to the kernel config file when going to 6.2 - I believe that I am using the same config file. It is my opinion that I am missing one or two specific incantations. Can anyone out there shed some light on what I am missing to get these to work? Thank you. August Grammas [EMAIL PROTECTED] If you pick up a starving dog and make him prosperous, he will not bite you; that is the principle difference bet- ween a dog and a man. Sam Clemens ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Maximum number established TCP connection
In response to Patrick Dung [EMAIL PROTECTED]: Hello I would like if there is a (countable) limit for the max TCP connection of a Apache web server. Suppose: 1. An apache web server serves a very big iso file. 2. 5000 people tried to connect to the apache server to get the iso file. 3. They connect to the server gradually (not 5000 people starting at the same moment). So that there will not be a problem caused by the TCP backlog limit. 4. There will be 5000 established TCP connections. Is it true that FreeBSD could handle 'unlimited' established TCP connections as long as it has enough CPU power and memory? The FreeBSD limit on the number of open TCP connections is significantly higher than the Apache limit on the number of concurrent HTTP sessions. I believe Apache has a hard limit of 256. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: telnet and rlogin problems
Grammas, August wrote: Rel: FreeBSD 6.2 Summary: I am unable to get either telnet or rlogin to function Details: To several of my PCs, that had been running 4.11, I have installed release 6.2. To the rc.conf, which was used for 4.11, I added: rcpbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_client_enable=YES mountd_enable=YES ftpd_enable=YES Don't believe any of these are relevant to your stated problem. To hosts.allow, I added: rpcbind | ALL | allow Again, I don't think this is relevant to your stated problem. try adding: telnetd: whatever : ALLOW Note the use of ':' - I have no idea whether the wrappers will allow you to use '|'. As a general matter, service: ALL : ALLOW is very bad if your machine is connected to the internet. You really do want your allow statements to be in the form: service: exact list of machines or networks that should be allowed :ALLOW Now then ... one last thing: DON'T USE TELENT AND RLOGIN - get out of the habit of using them even on local networks. They are painfully bad security holes. Learn to use ssh instead. HTH, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade
Is there a way to get the portupgrade to just accept all of the defaults for the configurations of the individual ports. I tried # env BATCH=yes, but it still just goes on hanging on the port configuration menus. It seems as though these time out (though I'm not sure). Chris Maness ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: looks like success
John Nielsen wrote: On Monday 03 March 2008 12:45:31 pm John Nielsen wrote: On Sunday 02 March 2008 03:50:43 am Daniel Gerzo wrote: Hello B., Thursday, February 28, 2008, 9:27:03 PM, you wrote: Hello all, make delete-old (took a long time to do by hand) and make delete-old-libs (went rather quickly) if you really want to delete all things: # yes | make delete-old While I've seen this suggestion before (and it's a very unix-y way to do it), the canonical method (from build(7)) is to run make -DBATCH_DELETE_OLD_FILES delete-old What I'd like to see (although I realize this isn't the correct forum..) is a make target that produces a list of files that _would_ be deleted, which the admin could then review and approve all or remove individual files to be preserved. But until I turn this into a useful PR or a nice request on a different list just consider it a rant. :) Heh.. I didn't read the manpage I just referred to closely enough. There's a check-old (and a check-old-libs) target that makes just such a list. JN Thanks for that. I've been using # yes no | make delete-old to get that list. Well, my way still has the claim on being more amusing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
This post hasn't appeared on the list after almost 24 hours so I'm re-posting. Apologies if it appears twice. It seems that about 50% of the posts I make to the lists (-questions and -ports) never show up. Matthew Seaman wrote: I've been doing a bunch of 6.x - 7.0 upgrades recently. Here's a few hints I've picked up along the way: [snip the gory details] Thanks for that Matthew, it confirms that I've made the right decision to do a completely clean install :-) Which leads me to ask if there are likely to be any issues with dual-booting 6.3-STABLE (as of ~1 month ago) and 7.0-RELEASE? I vaguely recall from way back there being issues with dual-booting multiple versions of FreeBSD. Maybe that was when trying to install both in the same slice? Mine will be installed on separate hard disks. The only thing I could think may possibly be an issue is the FreeBSD Boot Manager. The current setup uses the FBSD BM to boot FBSD and Ubuntu on separate disks - it's the Ubuntu disk that I will be zapping to install 7 - is there anything to watch out for (apart from the obvious stupidity of selecting the wrong disk to newfs ;-) ) Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade
Hello, On Mon, Mar 3, 2008 at 1:55 PM, [EMAIL PROTECTED] wrote: Is there a way to get the portupgrade to just accept all of the defaults for the configurations of the individual ports. I tried # env BATCH=yes, but it still just goes on hanging on the port configuration menus. It seems as though these time out (though I'm not sure). Try with portupgarde -y or portupgarde --yes Regards Rambius -- Tangra Mega Rock: http://www.radiotangra.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
audio on 5.3
I've tried compiling in support for sound on 5.3 STABLE adding 'device pcm' to /usr/src/sys/i386/conf/GENERIC but @ /usr/sbin/config -g 'pcm' generates an error - this worked fine on 4.0, 4.6, and 5.1 - with on-board and add-in sound cards. If I use 'sound' no error is generated but dmesg shows 'pci2: multimedia, audio at device 10.0 (no driver attached)' this happens if mobo soundMax is used or an add-in soundblaster live! 24 bit PCI. pciconf on the soundblaster: none2 at pci2:10:0: class=0x040100 card=0x10061102 chip=0x00071102 rev=0x00 hdr=0x00 vendor = 'Creative Labs' device = 'CA0106-DAT Audigy LS' class= multimedia subclass = audio So this card is really an Audigy LS - and no driver exists ? Please advise Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Maximum number established TCP connection
Bill Moran wrote: In response to Patrick Dung [EMAIL PROTECTED]: Hello I would like if there is a (countable) limit for the max TCP connection of a Apache web server. Suppose: 1. An apache web server serves a very big iso file. 2. 5000 people tried to connect to the apache server to get the iso file. 3. They connect to the server gradually (not 5000 people starting at the same moment). So that there will not be a problem caused by the TCP backlog limit. 4. There will be 5000 established TCP connections. Is it true that FreeBSD could handle 'unlimited' established TCP connections as long as it has enough CPU power and memory? The FreeBSD limit on the number of open TCP connections is significantly higher than the Apache limit on the number of concurrent HTTP sessions. I believe Apache has a hard limit of 256. That's a compile-time option in apache-1.3.x -- you can set APACHE_HARD_SERVER_LIMIT in /etc/make.conf to override the default of 512 if required. However in apache-2.2.x it seems the limits are imposed entirely by the MPM settings in httpd.conf -- at least, I cannot find any tunables in the port Makefiles. Generally the practical limit on the number of apache processes is the amount of available RAM. You want enough processes to fill up the memory, but no more -- so the system does not begin to swap. If the system does start swapping, performance will suffer for all users, new connections will begin to pile up and generally the whole thing will come to a grinding halt. With a maximum limit on the number of processes -- which corresponds to the total number of simultaneous active clients -- excess incoming connections are queued up until a process becomes available to deal with them. However, 5000 simultaneous apache processes is probably still too much, even if your server has oodles of RAM and you make strenuous efforts to slim down apache to the smallest possible image size. In such situations, smaller and lighter-weight HTTP servers such as nginx are more appropriate -- or else apply an aggressive inverse caching policy using such things as varnish or squid. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 and VMware tools (was Re: FreeBSD 7RC2 and VMware tools)
Dimitri Yioulos wrote: I've followed a couple of posts in other forums (or fora, if you prefer :-) ) that suggest using the e1000 NIC driver (e.g. communities.vmware.com/message/352504), but it fails. This is the last piece I need to make work. Suggestions? What's the problem you see? All I've ever needed to do was edit my .vmx file and add: ethernet0.virtualDev = e1000 MikeC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Maximum number established TCP connection
Is it true that FreeBSD could handle 'unlimited' established TCP connections as long as it has enough CPU power and memory? unlimited is too much said but 5000 doesn't seem a lot. you may need to sysctl a bit but with up to 5000 connections probably not at all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expanding file system
growfs can expand UFS filesystem. worked for me with normal partitions, if you use geli with sector size != 512 bytes, it won't, but i've patched it for that. still - it's buggy. but really don't assume it won't screw up your filesystem... if you like to try do: a)unmount this fs b) fsck it to make sure clear up new space with zeroes (yes, it will make it easier to survive after growfs) use dd if=/dev/zero of=/dev/yourpartition bs=1m seek=oldsizeinmegabytes (to obtain size, use dumpfs read blocks data, divide by 2048 to get into megs, round result up) run growfs fsck this again with -y option, preferably on screen as you'll get megabytes of error messages about screwed up inodes (growfs doesn't properly initialize new ones, used ones are ok) data will survive, i had a success just my root directory got destroyed, and all subdirs and files went into lost+found). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Maximum number established TCP connection
In response to Matthew Seaman [EMAIL PROTECTED]: Bill Moran wrote: In response to Patrick Dung [EMAIL PROTECTED]: Hello I would like if there is a (countable) limit for the max TCP connection of a Apache web server. Suppose: 1. An apache web server serves a very big iso file. 2. 5000 people tried to connect to the apache server to get the iso file. 3. They connect to the server gradually (not 5000 people starting at the same moment). So that there will not be a problem caused by the TCP backlog limit. 4. There will be 5000 established TCP connections. Is it true that FreeBSD could handle 'unlimited' established TCP connections as long as it has enough CPU power and memory? The FreeBSD limit on the number of open TCP connections is significantly higher than the Apache limit on the number of concurrent HTTP sessions. I believe Apache has a hard limit of 256. That's a compile-time option in apache-1.3.x -- you can set APACHE_HARD_SERVER_LIMIT in /etc/make.conf to override the default of 512 if required. However in apache-2.2.x it seems the limits are imposed entirely by the MPM settings in httpd.conf -- at least, I cannot find any tunables in the port Makefiles. Interesting. I found this: http://httpd.apache.org/docs/2.0/mod/mpm_common.html#serverlimit Which claims the hard limit is 20,000. So I guess my information is a bit out of date. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uname borked on ??-Release...
Kevin Kinsey wrote: Hello, Been bashing myself on the head for a few days, so I'm looking for a little help. If you've a big stick, read on (and apologies if poor formatting, I'm using an unfamiliar keyboard, unfamiliar mailer, and I'm not even sure if this system is running FreeBSD anymore :-D ) I get the following from uname -a: FreeBSD archangel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #6: Sat Jun 2 09:22:50 CDT 2007 [EMAIL PROTECTED]: /usr/obj/backup/src/sys/GENERIC i386 However, I rebuilt world, more or less without issues, twice in February with RELENG_6 in the supfile. This didn't change uname's output, and that worried me a bit. So, to make matters bette^H^H^H^Hadder, I csup'ped to RELENG_7_0 the day after it was release, read /usr/src/UPDATING, and the webpage detailing the upgrade, and did another buildworld/kernel cycle. Now I have no idea if I'm on 6 or 7 (seems like 7, but many ports issues, and I've rebuilt them all), and it's just becoming a major PITA. You didnt succeed in installing the new kernel. 'make installkernel' is the step in which this occurs. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems in ports of 7.0R
Matthias Apitz wrote: Hello, I'm preparing a fresh system with 7.0-RELEASE before updating my laptop for the daily-work; I've installed a clean 7.0-RELEASE with the ports tree but I'm running in some ports into problems, see below; until now I was thinking that even if the ports are not fully at the cutting edge, at least should be install-able without any problem, at least in 6.0R and 6.2R it has been this way; I'm wrong with that assumption? the problems are in detail: /usr/ports/emulators/qemu # make install === Vulnerability check disabled, database not found === Found saved configuration for qemu-0.9.1 === Extracting for qemu-0.9.1 = MD5 Checksum OK for qemu/qemu-0.9.1.tar.gz. = SHA256 Checksum OK for qemu/qemu-0.9.1.tar.gz. === qemu-0.9.1 depends on file: /usr/local/bin/perl5.8.8 - found === Patching for qemu-0.9.1 === qemu-0.9.1 depends on file: /usr/local/bin/perl5.8.8 - found === Applying FreeBSD patches for qemu-0.9.1 File to patch: ^C= Patch patch-PRId64 failed to apply cleanly. = Patch(es) patch-90_security patch-Makefile patch-Makefile.target applied cleanly. updating the port /usr/ports/emulators/qemu helps but ...; during the build the installation of /usr/ports/textproc/texi2html /usr/ports/lang/gcc34 /usr/ports/graphics/svgalib are failing, but work if they are done explictly by hand; /usr/ports/www/firefox # make install ... === Extracting for firefox-2.0.0.12,1 = MD5 Checksum OK for firefox-2.0.0.12-source.tar.bz2. = SHA256 Checksum OK for firefox-2.0.0.12-source.tar.bz2. === firefox-2.0.0.12,1 depends on file: /usr/local/bin/perl5.8.8 - found === Patching for firefox-2.0.0.12,1 === firefox-2.0.0.12,1 depends on file: /usr/local/bin/perl5.8.8 - found === Applying FreeBSD patches for firefox-2.0.0.12,1 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to content/canvas/src/nsCanvasRenderingContext2D.cpp.rej = Patch patch-content__canvas__src__nsCanvasRenderingContext2D.cpp failed to apply cleanly. = Patch(es) patch-Double.cpp patch-browser_app_mozilla.in patch-build_unix_run-mozilla.sh patch-config-mkdepend-imakemdep.h patch-config-rules.mk patch-config_autoconf.mk.in patch-config_mkdepend_Makefile.in patch-configure applied cleanly. Both of these patch files were present in 7.0-R but removed after the release. In both cases they apply cleanly to the release ports tree (you can verify this because the packages built for both of these ports, as found on the ftp site). Are you sure you did not attempt to update your ports tree post-install? This kind of error usually happens following an incorrect update attempt after installing a ports tree from sysinstall. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
It is safe to build ports for 7.0 from a 6.3 chroot?
Hi everybody Actually, I do the following in order to update from 6.3 to 7.0: 1) dump my actual 6.3 filesystems /, /var and /usr into three new ones: /rel70, /rel70/usr and /rel70/var (I use the dump command, of course) 2) chroot /rel70 and mergemaster -p + buildkernel + buildworld + installkernel + installworld + mergemaster -i and such stuff 3) Inside the chroot, rebuild the ports 4) Reboot the new release Will I go into problems following this approach? The step 3) is the most dangerous, I believe, as I have executing 7.0 commands on a 6.3 kernel (even though only for compilation). Best regards pgp47kcDn5bMv.pgp Description: PGP signature
Mathematica 6.01 + FBSD 6.3-release
I'm having problems getting the frontend running. The kernel seems to run fine. Initially the linux loader wasn't seeing the libraries under SystemFiles/Libraries/Linux (or at least /compat/linux/usr/bin/ldd couldn't find them when run on SystemFiles/FrontEnd/Binaries/Linux/Mathematica ) So I installed /compat/linux/etc/ld.so.conf.d/Mathematica.conf containing /usr/local/mma6/SystemFiles/Libraries/Linux and ran linux's ldconfig, which updated the cache and all was fine as far as ldd was concerned. But it still doesn't run and there are no errors. Does anyone else have this running under 6.3? Does it need to be installed under /compat/linux ? Thanks for any help! Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Compile Error
Hi there, I tried to compile an custom kernel, and i've got a lot of errors. I don't know what is the problem, even when i try to compile with GENERIC conf file i've got same link errors. So, what should i do ? Thanks for help. #uname -a FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 === conf file == # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.2.2.1 2008/02/06 03:24:28 scottl Exp $ #cpuI486_CPU #cpuI586_CPU cpuI686_CPU identMyKernel # To statically compile in device wiring instead of /boot/device.hints #hintsGENERIC.hints# Default places to look for devices. #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_4BSD# 4BSD scheduler options PREEMPTION# Enable kernel thread preemption options INET# InterNETworking options INET6# IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS# Berkeley Fast Filesystem options SOFTUPDATES# Enable FFS soft updates support options UFS_ACL# Support for access control lists options UFS_DIRHASH# Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT# MD is a potential root device options NFSCLIENT# Network Filesystem Client options NFSSERVER# Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS# MSDOS Filesystem options CD9660# ISO 9660 Filesystem options PROCFS# Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT# GUID Partition Tables. options GEOM_LABEL# Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4# Compatible with FreeBSD4 options COMPAT_FREEBSD5# Compatible with FreeBSD5 options COMPAT_FREEBSD6# Compatible with FreeBSD6 options SCSI_DELAY=5000# Delay (in ms) before probing SCSI options KTRACE# ktrace(1) support options SYSVSHM# SYSV-style shared memory options SYSVMSG# SYSV-style message queues options SYSVSEM# SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT# Giant mutex is adaptive. options STOP_NMI# Stop CPUS using NMI instead of IPI options AUDIT# Security event auditing # To make an SMP kernel, the next two lines are needed options SMP# Symmetric MultiProcessor Kernel deviceapic# I/O APIC # CPU frequency control devicecpufreq # Bus support. deviceeisa devicepci # Floppy drives devicefdc # ATA and ATAPI devices deviceata deviceatadisk# ATA disk drives deviceataraid# ATA RAID drives deviceatapicd# ATAPI CDROM drives deviceatapifd# ATAPI floppy drives deviceatapist# ATAPI tape drives options ATA_STATIC_ID# Static device numbering # SCSI Controllers deviceahb# EISA AHA1742 family deviceahc# AHA2940 and onboard AIC7xxx devices options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. deviceahd# AHA39320/29320 and onboard AIC79xx devices options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. deviceamd# AMD 53C974 (Tekram DC-390(T)) devicehptiop# Highpoint RocketRaid 3xxx series deviceisp# Qlogic family #device ispfw# Firmware for QLogic HBAs- normally a module devicempt# LSI-Logic MPT-Fusion #devicencr# NCR/Symbios Logic devicesym# NCR/Symbios
Re: Uname borked on ??-Release...
Kris Kennaway wrote: Kevin Kinsey wrote: snip I get the following from uname -a: FreeBSD archangel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #6: Sat Jun 2 09:22:50 CDT 2007 [EMAIL PROTECTED]: /usr/obj/backup/src/sys/GENERIC i386 However, I rebuilt world, more or less without issues, twice in February with RELENG_6 in the supfile. This didn't change uname's output, and that worried me a bit. So, to make matters bette^H^H^H^Hadder, I csup'ped to RELENG_7_0 the day after it was released, read /usr/src/UPDATING, and the webpage detailing the upgrade, and did another buildworld/kernel cycle. Now I have no idea if I'm on 6 or 7 (seems like 7, but many ports issues, and I've rebuilt them all), and it's just becoming a major PITA. You didnt succeed in installing the new kernel. 'make installkernel' is the step in which this occurs. Kris Thank you and Phillip for answering my post. However, I've done this 3 times now, and I don't skip that step. There have been no errors in the process, either. AAMOF, in response to Phillip's mail, I just did it again, as you can see (z* is to omit snipping): ll /boot/kernel/z* -r-xr-xr-x 1 root wheel 712006 Mar 3 15:16 /boot/kernel/zfs.ko* -r-xr-xr-x 1 root wheel 3471592 Mar 3 15:16 /boot/kernel/zfs.ko.symbols* -r-xr-xr-x 1 root wheel38175 Mar 3 15:16 /boot/kernel/zlib.ko* -r-xr-xr-x 1 root wheel58834 Mar 3 15:16 /boot/kernel/zlib.ko.symbols* I've rebooted the system, and I'm still being told I'm running 6.2 by uname. In addition, pkg_add thinks I should be looking for 6-latest packages instead of 7, and the list of annoyances continues. And, hmm, symbols? I'm guessing that knob is ON in FBSD7? Once again, proof that something's wrong, as I didn't build debugging kernels in FBSD6 ... so I'm thinking this is a 7 kernel? It just doesn't make sense to me. It *is* a Monday, after all. If installkernel didn't succeed, shouldn't there be any other evidence? Could skipping a mergemaster at some point have this effect? (I don't *always* do that, unless I'm making a pretty big move, and the first build cycle was production code IIRC) What about issues with newvers.sh (or whatever it is?) Any other think-outside-the-box stuff? What could cause an installkernel operation to fail but appear to succeed? KDK -- I just rewrote my .sig. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
7.0RC1 i386 and 7.0RC2 AMD64 major issues with mount_msdosfs
I'm prepared to workaround, and I suspect this has already been brought up if it's a 'real' issue, but I thought I'd better speak up. I have two systems: 1) 2005 HP ZE4650 laptop running 7.0RC1 i386 2) Brand-new FOXCONN 775? motherboard system running 7.0RC2 Amd64 They are both vanilla installs off of the ftp.freebsd.org ISO images, and they both behave similarly, so I know it's not the hardware. I also have two FAT devices: 1) 60GB laptop drive in USB 2.0 carrier 2) 1GB Lexar SD card in iRock cardreader In both systems, 1) The 60GB drives takes 10 seconds to mount (as opposed to 1/10 sec on my 6.3amd64 system at home). When I start rsyncing part of the 60GB to one of the 7.0 systems, it craps out after 5 minutes. If you umount, it says something to the effect that the drive is gone, and if you physically pull the USB cable, the system usually freezes up solid, until a powercycle. Once, most of the files rsync'd sucessfully, but the data was all corrupted. Age of the disk is several months, so I'd be suspicious that bad sectors are at fault. 2) The SD card appears to mount just fine, but when you cd to the mountpoint, ls -la df shows that it's empty. Putting it into my 6.3 system or a win32 box shows approx 1GB of photos, of course. Thought someone should know. Since I've been having issues with it locking up, dmesg info is hard to come by, but I'm happy to work with someone smarter than me if it results in a more stable 7.0. I finished a large copy several hours ago, and I see several of the following in dmesg: umass0: Invalid CSW: tag 242579 should be 242656. Several files are corrupted. No errors or issue when the data was placed on the drive by my 6.3amd64 system 24 hours ago. Best, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix port broken?
This is due to these lines in the Makefile (with line numbers): 187 .if defined(WITH_VDA) 188 IGNORE= Waiting for a new patch that's work with 2.5.1 189 PATCH_SITES+= http://vda.sourceforge.net/VDA/ 190 PATCHFILES+=postfix-2.4.5-vda-ng.patch.gz 191 PATCH_DIST_STRIP= -p1 192 .endif make config would enable you to turn off virtual delivery agent. I'm not a postfix expert, but I believe VDA is only needed if you run virtual domains. fred On Mar 2, 2008, at 2:57 AM, Ezat wrote: Hello all, Not sure if correct list for this. Trying to install postfix today and came across this issue. === postfix-2.5.1_1,1 Waiting for a new patch that's work with 2.5.1. *** Error code 1 Stop in /usr/ports/mail/postfix. Anyone have same issue? ezat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Compile Error
On 2008-03-03 13:00, Win32 Win32 [EMAIL PROTECTED] wrote: Hi there, I tried to compile an custom kernel, and i've got a lot of errors. I don't know what is the problem, even when i try to compile with GENERIC conf file i've got same link errors. So, what should i do ? The problem is that you trimmed / commented out too much stuff... # Wireless NIC cards #devicewlan# 802.11 support #devicewlan_wep# 802.11 WEP support #devicewlan_ccmp# 802.11 CCMP support #devicewlan_tkip# 802.11 TKIP support #devicewlan_amrr# AMRR transmit rate control algorithm #devicewlan_scan_ap# 802.11 AP mode scanning #devicewlan_scan_sta# 802.11 STA mode scanning [...] # USB support [...] devicerum# Ralink Technology RT2501USB wireless NICs linker error = linking kernel if_ural.o(.text+0x713): In function `ural_free_tx_list': : undefined reference to `ieee80211_free_node' `rum' is a wireless NIC driver. You need `wlan' options to compile into the kernel. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uname borked on ??-Release...
Kevin Kinsey wrote: Kris Kennaway wrote: Kevin Kinsey wrote: snip I get the following from uname -a: FreeBSD archangel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #6: Sat Jun 2 09:22:50 CDT 2007 [EMAIL PROTECTED]: /usr/obj/backup/src/sys/GENERIC i386 However, I rebuilt world, more or less without issues, twice in February with RELENG_6 in the supfile. This didn't change uname's output, and that worried me a bit. So, to make matters bette^H^H^H^Hadder, I csup'ped to RELENG_7_0 the day after it was released, read /usr/src/UPDATING, and the webpage detailing the upgrade, and did another buildworld/kernel cycle. Now I have no idea if I'm on 6 or 7 (seems like 7, but many ports issues, and I've rebuilt them all), and it's just becoming a major PITA. You didnt succeed in installing the new kernel. 'make installkernel' is the step in which this occurs. Kris Thank you and Phillip for answering my post. However, I've done this 3 times now, and I don't skip that step. There have been no errors in the process, either. AAMOF, in response to Phillip's mail, I just did it again, as you can see (z* is to omit snipping): ll /boot/kernel/z* -r-xr-xr-x 1 root wheel 712006 Mar 3 15:16 /boot/kernel/zfs.ko* -r-xr-xr-x 1 root wheel 3471592 Mar 3 15:16 /boot/kernel/zfs.ko.symbols* -r-xr-xr-x 1 root wheel38175 Mar 3 15:16 /boot/kernel/zlib.ko* -r-xr-xr-x 1 root wheel58834 Mar 3 15:16 /boot/kernel/zlib.ko.symbols* I've rebooted the system, and I'm still being told I'm running 6.2 by uname. In addition, pkg_add thinks I should be looking for 6-latest packages instead of 7, and the list of annoyances continues. And, hmm, symbols? I'm guessing that knob is ON in FBSD7? Once again, proof that something's wrong, as I didn't build debugging kernels in FBSD6 ... so I'm thinking this is a 7 kernel? It just doesn't make sense to me. It *is* a Monday, after all. If installkernel didn't succeed, shouldn't there be any other evidence? Could skipping a mergemaster at some point have this effect? (I don't *always* do that, unless I'm making a pretty big move, and the first build cycle was production code IIRC) What about issues with newvers.sh (or whatever it is?) Any other think-outside-the-box stuff? What could cause an installkernel operation to fail but appear to succeed? Possibly you have 6.x sources still. Or you are not actually booting /boot/kernel/kernel but some other kernel. Check sysctl kern.bootfile. You can also do strings /boot/kernel/kernel | grep 7.0-RELEASE to verify the kernel version string. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uname borked on ??-Release...
Kris Kennaway wrote: snip I get the following from uname -a: FreeBSD archangel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #6: Sat Jun 2 09:22:50 CDT 2007 [EMAIL PROTECTED]: /usr/obj/backup/src/sys/GENERIC i386 However, I rebuilt world, more or less without issues, twice in February with RELENG_6 in the supfile. This didn't change uname's output, and that worried me a bit. So, to make matters bette^H^H^H^Hadder, I csup'ped to RELENG_7_0 the day after it was released, read /usr/src/UPDATING, and the webpage detailing the upgrade, and did another buildworld/kernel cycle. Now I have no idea if I'm on 6 or 7 (seems like 7, but many ports issues, and I've rebuilt them all), and it's just becoming a major PITA. You didnt succeed in installing the new kernel. 'make installkernel' is the step in which this occurs. Thank you and Phillip for answering my post. However, I've done this 3 times now, and I don't skip that step. There have been no errors in the process, either. I've rebooted the system, and I'm still being told I'm running 6.2 by uname. In addition, pkg_add thinks I should be looking for 6-latest packages instead of 7, and the list of annoyances continues. And, hmm, symbols? I'm guessing that knob is ON in FBSD7? Once again, proof that something's wrong, as I didn't build debugging kernels in FBSD6 ... so I'm thinking this is a 7 kernel? It just doesn't make sense to me. It *is* a Monday, after all. If installkernel didn't succeed, shouldn't there be any other evidence? Could skipping a mergemaster at some point have this effect? Possibly you have 6.x sources still. Or you are not actually booting /boot/kernel/kernel but some other kernel. Check sysctl kern.bootfile. You can also do strings /boot/kernel/kernel | grep 7.0-RELEASE to verify the kernel version string. #sysctl kern.bootfile kern.bootfile: /boot/kernel/kernel #strings /boot/kernel/kernel | grep 0-RELEASE @(#)FreeBSD 7.0-RELEASE #1: Thu Feb 28 12:22:38 CST 2008 FreeBSD 7.0-RELEASE #1: Thu Feb 28 12:22:38 CST 2008 7.0-RELEASE #ls -l /boot/kernel/kernel -r-xr-xr-x 1 root wheel 9294687 Feb 28 12:22 /boot/kernel/kernel* Well, fudging around with uname's source shows that it's basically calling some sysctls, so maybe the question is, with what I have above, why do I still have: sysctl -a | grep kern.osre kern.osrelease: 6.2-RELEASE kern.osrevision: 199506 kern.osreldate: 602000 ?? Thanks in advance, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is safe to build ports for 7.0 from a 6.3 chroot?
On Mon, Mar 03, 2008 at 09:09:37PM +0100, Jose Garcia Juanino wrote: Hi everybody Actually, I do the following in order to update from 6.3 to 7.0: 1) dump my actual 6.3 filesystems /, /var and /usr into three new ones: /rel70, /rel70/usr and /rel70/var (I use the dump command, of course) 2) chroot /rel70 and mergemaster -p + buildkernel + buildworld + installkernel + installworld + mergemaster -i and such stuff 3) Inside the chroot, rebuild the ports 4) Reboot the new release Will I go into problems following this approach? The step 3) is the most dangerous, I believe, as I have executing 7.0 commands on a 6.3 kernel (even though only for compilation). Not only that, many ports have some tweaks dependent on OSVERSION; some have it ingrained into their configure shims. Personally, I got into a situation where I had to run 7.0 world on 6.3 kernel. Nothing bad happened, but I rebooted with a new kernel as soon as I could. All in all, I'd say you have a good chance to succeed, especially if you have your fingers crossed :) You won't be on the safe side, though. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade
On Mon, 3 Mar 2008 10:55:32 -0800 (PST) [EMAIL PROTECTED] wrote: Is there a way to get the portupgrade to just accept all of the defaults for the configurations of the individual ports. I tried # env BATCH=yes, but it still just goes on hanging on the port configuration menus. It seems as though these time out (though I'm not sure). It should work, is there a specific port that fails? When you say you tried env BATCH=yes did you use it properly like this: # env BATCH=yes portupgrade foo rather than # env BATCH=yes # portupgrade foo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: audio on 5.3
On Mon, Mar 03, 2008 at 11:41:08AM -0800, Robert Palambo wrote: I've tried compiling in support for sound on 5.3 STABLE adding 'device pcm' to /usr/src/sys/i386/conf/GENERIC but @ /usr/sbin/config -g 'pcm' generates an error - this worked fine on 4.0, 4.6, and 5.1 - with on-board and add-in sound cards. If I use 'sound' no error is generated but dmesg shows 'pci2: multimedia, audio at device 10.0 (no driver attached)' this happens if mobo soundMax is used or an add-in soundblaster live! 24 bit PCI. Try this: cd /boot/kernel/kldload snd*ko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Variable Substitution
On Monday 03 March 2008 15:52:51 Victor Subervi wrote: Forgive this basic question, but can´t figure out how to google it. If I want to substitute strings in an expression, I can use %s for string, or %d for digit. What about file? What is this process called, so I can find a howto? printf(1) or printf(3), pending what language you want. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix port broken?
Thanks Fred others who have replied directly, The virtual domains are actually exactly what is required in this situation so I have fallen back to 2.4 port which will do for now. Ezat Fred Condo wrote: This is due to these lines in the Makefile (with line numbers): 187 .if defined(WITH_VDA) 188 IGNORE= Waiting for a new patch that's work with 2.5.1 189 PATCH_SITES+= [1]http://vda.sourceforge.net/VDA/ 190 PATCHFILES+=postfix-2.4.5-vda-ng.patch.gz 191 PATCH_DIST_STRIP= -p1 192 .endif make config would enable you to turn off virtual delivery agent. I'm not a postfix expert, but I believe VDA is only needed if you run virtual domains. fred On Mar 2, 2008, at 2:57 AM, Ezat wrote: Hello all, Not sure if correct list for this. Trying to install postfix today and came across this issue. === postfix-2.5.1_1,1 Waiting for a new patch that's work with 2.5.1. *** Error code 1 Stop in /usr/ports/mail/postfix. Anyone have same issue? ezat ___ [EMAIL PROTECTED] mailing list [3]http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [4][EMAIL PROTECTED] References 1. http://vda.sourceforge.net/VDA/ 2. mailto:freebsd-questions@freebsd.org 3. http://lists.freebsd.org/mailman/listinfo/freebsd-questions 4. mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kern.ipc.maxpipekva
On Sunday 02 March 2008 13:36:26 Colin Adams wrote: I'm getting error messages about this when trying to run my program. As far as I know, I don't use IPC at all, although I dare say it is used in one of the libraries that are linked in. After googling for this error, I edited /boot/loader.conf to set it to 6500 (a nice big number?), and now if I do: sysctl kern.ipc.maxpipekva I see: kern.ipc.maxpipekva: 6500 but I still get the message. I also get a lot of messages saying: Fatal error `Cannot create kernel pipe' at line 294 in file /usr/src/lib/libc_r/uthread/uthread_init.c (error = 24) Why does this occur, and what can i do about it? grep 24 /usr/include/sys/errno.h: max open /files/. This signals that a thread can't be created, cause there's too many open files. Any chance your program/library loops like mad, creating threaded workers that open a socket/file and never end? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI trouble FreeBSD 7.0 STABLE
On Sunday 02 March 2008 09:19:43 budsz wrote: Hi, Yesterday, I try to CVSUP/make world from FreeBSD 6.3 STABLE to FreeBSD 7.0 STABLE: I got strange debug message here: Mar 2 14:14:14 gw-core-iixrouter kernel: acpi: suspend request ignored (not ready yet) Mar 2 14:14:14 gw-core-iixrouter kernel: acpi: request to enter state S5 failed (err 6) Mar 2 14:14:15 gw-core-iixrouter kernel: acpi: suspend request ignored (not ready yet) Mar 2 14:14:15 gw-core-iixrouter kernel: acpi: request to enter state S5 failed (err 6) Mar 2 14:14:16 gw-core-iixrouter kernel: acpi: suspend request ignored (not ready yet) Mar 2 14:14:16 gw-core-iixrouter kernel: acpi: request to enter state S5 failed (err 6) Mar 2 14:14:17 gw-core-iixrouter kernel: acpi: suspend request ignored (not ready yet) Mar 2 14:14:17 gw-core-iixrouter kernel: acpi: request to enter state S5 failed (err 6) Mar 2 14:14:18 gw-core-iixrouter kernel: acpi: suspend request ignored (not ready yet) Mar 2 14:14:18 gw-core-iixrouter kernel: acpi: request to enter state S5 failed (err 6) Mar 2 14:14:18 gw-core-iixrouter kernel: acpi: suspend request ignored (not ready yet) Mar 2 14:14:18 gw-core-iixrouter kernel: acpi: request to enter state S5 failed (err 6) Mar 2 14:14:19 gw-core-iixrouter syslogd: exiting on signal 15 That's a shutdown invoked by someone pressing and holding the powerbutton, or a loose/stuck powerbutton, that keeps sending I'm pressed to the kernel. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HDD missing from sysinstall
I had a missing hard drive on a FreeBSD box that had a single IDE drive that was incorrectly jumpered. After I switched the jumper on the disk controller, everything was correctly detected by the device probe. (This shouldn't be an issue on SATA drives though.) Something you might try before looking into hardware issues, is to use a liveCD such as Freesbie (available in the ports collection sysutils/freesbie), boot to the liveCD and use dd(1) to entirely obliterate the first few sectors of the disk, nuking the the master boot record. That is, if the device probe on the liveCD detects the disk. (Perhaps use an older version.) This will make any previous data on the disk inaccessible, but if a really corrupt master boot record in concert with a funky BIOS are at fault, this would resolve the issue. You could then use sysinstall to install a new master boot record and so forth. The command would look something like this: dd if=/dev/zero of=/dev/ad0 bs=512 count=1 # Nuke the master boot record. Replace 'ad0' with the appropriate device. # IMPORTANT: This will make the disk not bootable. Just a thought. -Modulok- On 3/1/08, comperr [EMAIL PROTECTED] wrote: Just to add I am using an MSI P6N SLI plat. motherboard On Mar 1, 10:28 pm, comperr [EMAIL PROTECTED] wrote: When I put in my fbsd 6.3 or 7.0 install disk sysinstall is unable to detect any of the hard drives in my computer. This is includes SATA and IDE HDDs in varying orders. BIOS is able to detect the the hard drives. I Previously had fbsd 6.2 installed on them and the problem started when I upgraded the kernel to 6.3 although I don't see my upgrades relevance as I have tried to reinstall from a clean disk since then. ___ [EMAIL PROTECTED] mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RAM not recognized
Hello every one, I have installed FreeBSD-7.0_RELEASE on Dell Power Edge 1950 Quad Core and 4GB of RAM. The problem is that FreeBSD does not recognize all of the RAM. This is part of the dmesg. # dmesg CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2496.28-MHz 686-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 3484745728 (3323 MB) avail memory = 3405631488 (3247 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard Can anyone give me some light in this issue? Thank you very much!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD diskless workstation boot over Linux PXE server
Thank you for the input from a couple of folks. After a few research and readings I am able to boot off a diskless client; and have a little error encountered. To clarify the environment: 1. PXE/DHCP/NFS/TFTP servers is a linux host 2. DHCP - server - dhcpd.conf file shows the following: (for my freeBSD diskless client testing scenario) filename pxeboot; next-server 192.168.16.5; option root-path 192.168.16.5:/export/images/freeBSD; -- pxeboot is the freeBSD /boot/pxeboot file I copied over to my /tftpboot directory. -- next server IP is the PXE/TFTPD/DHCP server ... -- the NFS root is exported by the NFS server as such. The client seems to boot properly - acquires an IP address; downloads and reads the /tftpboot/pxeboot file; a message also appears that indicates it mounted the root File system: (snippet of console messages:) NFS ROOT: 192.168.16.5:/export/images/freeBSD nfe0: link state change to UP Interface nfe0 IP_Address 192.168.16.5 ... . . . . .. Loading Configuration files. rc.conf: not found No Suitable dump device was found . | etc. etc. IT seems like the root is mounted but it cannot find the rc.conf file; my root contains the following directories (including nfsroot/etc/rc.conf and nfsroot/etc/defaults/rc.conf ... freeBSD# ls bin boot dev etc home lib libexec sbin swap tmp usr var I must be missing something silly or apparent. Any help and/or suggestions would be greatly appreciated. I have attempted to painstakingly google this issue, to no avail. thanks in advanced. On Sat, Feb 23, 2008 at 2:45 AM, Erik Norgaard [EMAIL PROTECTED] wrote: vincenzo romero wrote: Hello, Am new to FreeBSD and relatively new to linux; I have a CentOS 5.1 PXE/tftpd/dhcpd server; I'd like it to be the build/PXE server where a bunch of 1U clients could PXE boot and run: 1. diskless over NFS-Root In googling, seems like there is a clone script that preps and lets you generate a root file system structure and let your clients boot off the network. I found the docs I could find on the internet way obsolete back in 2005 when I played with it, and I am not aware that these has been updated. I wrote my own guide to make up for this, however, this may now also be obsolete as it's been some time since I played with this. My main problem with diskless is that FreeBSD mounts memory backed filesystems for /var and /tmp which waste a lot of precious RAM if you have restricted memory. And a feature, useless in diskless operation, prevents mounting /var and /tmp from a server. I checked the Free BSD Handbook (Chapter 29) where extensive documentation on setup is outlined, but it assumes that the PXE/TFTP/NFS/DHCPd servers are FreeBSD; mine is a CentOS; just want to support diskless PXE boot for my clients. Section 29.7.2.9.2 9Usning a Non-FreeBSD server - just indicates that do a tar/cpio of root; but ensure that special files in /dev are taken care of ... There is no problem serving files from a non-FreeBSD server, however things are easier, as you need to build all applications served via NFS for FreeBSD. This mainly affects you if you want diskless clients, you need to keep these updated. For installation this is not a concern. The /dev is not a problem, the diskless client mounts a /dev locally, it is not a real file system. - does anyone have this type of scenario setup? if so, can you please share with me your insights/cheat-sheet-how to? http://www.locolomo.org/pub/pxeboot/index.html - i'd be interested in understanding the setup of how you handled copying the /dev files into your exported ROOT directorty ... Are there any other recommendations ? If you want to do network installation rather than diskless, avoid NFS, it is much easier to set up installation over ftp. Cheers, Erik -- Erik Nørgaard Ph: +34.666334818 http://www.locolomo.org -- best, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAM not recognized
Cesar Amaya wrote: Hello every one, I have installed FreeBSD-7.0_RELEASE on Dell Power Edge 1950 Quad Core and 4GB of RAM. The problem is that FreeBSD does not recognize all of the RAM. This is part of the dmesg. # dmesg CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2496.28-MHz 686-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 3484745728 (3323 MB) avail memory = 3405631488 (3247 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard Can anyone give me some light in this issue? Thank you very much!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, se nd any mail to [EMAIL PROTECTED] Forgot to CC list This is not a problem of FreeBSD but of i386/x86 architecture which max memory limit is 4GB i theory and 3-3.5GB in practice, you can use PAE to use 36bit addressing (instead of default 32bit) for memory to get full 4GB on i386 but you will not be able to have loadable kernel modules for example, other sollution for this is using amd64/64bit FreeBSD, where you will have full 4GB and even more without any problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is safe to build ports for 7.0 from a 6.3 chroot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jose Garcia Juanino wrote: | Hi everybody | | Actually, I do the following in order to update from 6.3 to 7.0: | | 1) dump my actual 6.3 filesystems /, /var and /usr into three new | ones: /rel70, /rel70/usr and /rel70/var (I use the dump command, of | course) | | 2) chroot /rel70 and mergemaster -p + buildkernel + buildworld + | installkernel + installworld + mergemaster -i and such stuff | | 3) Inside the chroot, rebuild the ports | | 4) Reboot the new release | | | Will I go into problems following this approach? The step 3) is the most | dangerous, I believe, as I have executing 7.0 commands on a 6.3 kernel | (even though only for compilation). 0) Do I need to reinvent wheel? Joke off. Really, why would you try alternate way of upgrading, when there's straight way to do it? - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfMnD0ACgkQo6C4vAhYtCDrTwCgoHSPgIoGgltE2plO4JsQ5Bb/ R50An3hFeeBfcNIyHlRD9za8lLnI3t0v =ZGrK -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAM not recognized
Paul A. Procacci writes: AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 3484745728 (3323 MB) avail memory = 3405631488 (3247 MB) This is not a problem of FreeBSD but of i386/x86 architecture which max memory limit is 4GB i theory and 3-3.5GB in practice, you can use PAE to use 36bit addressing (instead of default 32bit) for memory to get full 4GB on i386 but you will not be able to have loadable kernel modules for example, other sollution for this is using amd64/64bit FreeBSD, where you will have full 4GB and even more without any problems. ... and not be able to run some ports; some won't run in native 64 bit mode, some won't run at all. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is safe to build ports for 7.0 from a 6.3 chroot?
On Tuesday 04 March 2008 01:48:37 Bogdan Ćulibrk wrote: Jose Garcia Juanino wrote: | Hi everybody | | Actually, I do the following in order to update from 6.3 to 7.0: | | 1) dump my actual 6.3 filesystems /, /var and /usr into three new | ones: /rel70, /rel70/usr and /rel70/var (I use the dump command, of | course) | | 2) chroot /rel70 and mergemaster -p + buildkernel + buildworld + | installkernel + installworld + mergemaster -i and such stuff | | 3) Inside the chroot, rebuild the ports | | 4) Reboot the new release | | | Will I go into problems following this approach? The step 3) is the most | dangerous, I believe, as I have executing 7.0 commands on a 6.3 kernel | (even though only for compilation). 0) Do I need to reinvent wheel? Joke off. Really, why would you try alternate way of upgrading, when there's straight way to do it? Minimize downtime of services provided by ports? Jose: take a look at Tinderbox - it does exactly what you want to do: build ports for OS release X on OS release Y, using chroot. If you're unsure about your own method, because of OSVERSION or similar, do it using Tinderbox. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade
You can try with portupgrade -a --batch Regards. Vivian On Tue, 04 Mar 2008 02:55:32 +0800, [EMAIL PROTECTED] wrote: Is there a way to get the portupgrade to just accept all of the defaults for the configurations of the individual ports. I tried # env BATCH=yes, but it still just goes on hanging on the port configuration menus. It seems as though these time out (though I'm not sure). Chris Maness ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Versioned symbols
Hi!
First, sorry if this shouldn't belong to this list. If this is the case,
please point me to the appropriate list.
I want to make versioned symbols as they work in Linux, but I had no
success with FreeBSD.
Let me say, I've app, lib1 and lib2. lib1 and lib2 have two different
functions, and I link app with both. They use the following version scripts:
lib1.vers
--
lib1 {
*;
};
lib2.vers
--
lib2 {
*;
};
Then, I rebuild lib2 to have the same lib1 function, and when app calls
that function (that nows exists in lib1 and lib2) the call go to lib2.
I suppose the app should call the lib1 function, as the imported
function is defined with lib1 namespace.
If you want, I can post a small test case.
Do exists any different on Linux and FreeBSD re. versioned symbols? Is
there a way to achieve what I want?
Thanks,
Adriano
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade
On Mon, 03 Mar 2008 10:55:32 -0800 (PST) [EMAIL PROTECTED] wrote: Is there a way to get the portupgrade to just accept all of the defaults for the configurations of the individual ports. I tried # env BATCH=yes, but it still just goes on hanging on the port configuration menus. It seems as though these time out (though I'm not sure). Chris Maness Just add BATCH=yes to your /etc/make.conf file ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAM not recognized
On Mon, 3 Mar 2008 19:51:42 -0500 Robert Huff [EMAIL PROTECTED] wrote: Paul A. Procacci writes: AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 3484745728 (3323 MB) avail memory = 3405631488 (3247 MB) This is not a problem of FreeBSD but of i386/x86 architecture which max memory limit is 4GB i theory and 3-3.5GB in practice, you can use PAE to use 36bit addressing (instead of default 32bit) for memory to get full 4GB on i386 but you will not be able to have loadable kernel modules for example, other sollution for this is using amd64/64bit FreeBSD, where you will have full 4GB and even more without any problems. ... and not be able to run some ports; some won't run in native 64 bit mode, some won't run at all. And also bear in mind that amd64 uses memory less efficiently than i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAM not recognized
RW writes: And also bear in mind that amd64 uses memory less efficiently than i386 Would you care to elaborate? (A pointer will do.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: HDD missing from sysinstall
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of comperr Sent: Saturday, March 01, 2008 7:28 PM To: freebsd-questions@freebsd.org Subject: HDD missing from sysinstall When I put in my fbsd 6.3 or 7.0 install disk sysinstall is unable to detect any of the hard drives in my computer. This is includes SATA and IDE HDDs in varying orders. BIOS is able to detect the the hard drives. I Previously had fbsd 6.2 installed on them and the problem started when I upgraded the kernel to 6.3 although I don't see my upgrades relevance as I have tried to reinstall from a clean disk since then. What is the machine model and make, please? This can happen because previously the disk driver in 6.2 was treating your disk as generic ATA devices, but then support for your IDE controller was added into the driver, and now your BIOS has it in a weird mode. A dmesg from the 6.2 system would be useful as well. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD bind performance in FreeBSD 7
Ted Mittelstaedt wrote: My beef with the DNS tests was that ISC ran out and bought the hardware FIRST, -then- they started testing. This is directly contrary to every bit of advice ever given in the computer industry for the last 50 years - you select the software FIRST, -then- you buy the hardware that runs it. In short, it said far more about the incompetence of the testers than the shortcomings of the software. This is ridiculous. ISC is one of the most fervent pro-FreeBSD companies out there (basing most of our services on the OS, and contributing to the FreeBSD community including the busiest CVSup FTP servers and have FreeBSD committers on staff) I will not stand back and watch folks on a public mailing list call us incompetent individuals with a anti-FreeBSD bias. First off the final report was published last Friday at: http://www.isc.org/pubs/tn/index.pl?tn=isc-tn-2008-1.html (the server this is served from runs FreeBSD) I was not one of the direct testers (we had a couple PhD's handling that, who I know both use FreeBSD on their personal systems), but as one of the folks who supported them in their work, I can tell you that the stats we gave the FreeBSD folks were from a test sponsored by the US National Science Foundation. We were mandated to use branded HW and we tested several models from HP, Sun, even Iron Systems (whitebox) before deciding on the HP's. The mechanism we used are all documented in the paper We were also asked to test DNS performance on several OS's. The short version was 'take a standard commercial off the shelf' server and see how BIND performs (esp. with DNSSEC) on it. We weren't asked to get hardware that was perfect for Brand X OS; that wasn't part of the remit. (We actually use the exact same HP HW for a secondary service where we host a couple of thousand zones using BIND including 30+ TLD zones. Oh and it runs FreeBSD) Yes we found FreeBSD performed poorly in our initial tests. and I talked to several folks (including rwatson and kris) about the issue. Kris had already been working on improving performance with MySQL and PgSQL and was interested in doing the same with BIND. Kris went off and hacked away and right before EuroBSDcon last September asked us to re-run the tests (on the same HW) using a 7.0-CURRENT snapshot, and the end results are shown with a 33,000 query increase over 6.2-RELEASE, bring FreeBSD just behind the Linux distros we tested. I know rwatson and kris have continually worked on the relevent network stack issues that cover BIND, and additional performance gains have been found since then, and working on this issue has been a true partnership between the FreeBSD developers and ISC. BIND isn't perfect, we admit that, we have been constantly improving it's multi-CPU performance and BIND 9.4 and 9.5 are continuing in that effort. We have several members of our dev team who use FreeBSD as their developent platform, including a FreeBSD committer. So Ted, stop spouting this ISC is spewing anti-FreeBSD bias crap, it flatly isn't true... Oh, and this email is coming to you via several of ISC FreeBSD MX servers which resolve the freebsd.org name via caching DNS servers running FreeBSD, to freebsd.org's MX server over a IPv6 tunnel supplied by ISC to the FreeBSD project to help FreeBSD eat their own IPv6 dog food... Yeah, ISC just hates FreeBSD... rolls eyes Best Wishes - Peter -- [EMAIL PROTECTED] | ISC | OpenPGP 0xE8048D08 | The bits must flow signature.asc Description: OpenPGP digital signature
RE: ndis0 panic when ifconfig inet IP address
Glenn, It doesen't help us by updating the mailing list Please run send-pr on your laptop and put in the problem description and the fix. Thanks, Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Glenn Sent: Sunday, March 02, 2008 10:12 AM To: freebsd-questions@freebsd.org Subject: Re: ndis0 panic when ifconfig inet IP address Update: I wasn't able to solve the problem so resorted to installing FreeBSD 6.3 instead, and got the wireless working without any difficulty. I guess that some of the ndis kernel code has been changed in 7.0 that is causing my system to panic. Glenn I have just upgraded my Asus A2 notebook from 6.1 to FreeBSD 7.0-RELEASE #0 by doing a full clean install. (completely repartitioned my disc prior to installing) This notebook uses the Broadcom bcmwl5 wireless drivers which worked faultlessly using ndis on 6.1 I can kldload ndis and driver bcmwl5_sys without a problem. However the system panics anytime that I try to config the ip address either through rc.conf or directly e.g. ifconfig ndis inet 192.168.0.5 netmask 255.255.255.0 Got the error on the GENERIC kernel plus my own built kernel Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instructor pointer = 0x20:0xc0a464f8 stack pointer = 0x28:0xcbfd8b04 frame pointer = 0x28:0xcbfd8b3c code segment = base 0x0, limit 0xf, type 0xib = DPL0, pres 1 def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 994 (ndis0 taskq) trap number = 12 Any idea what the problem may be? Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: HDD missing from sysinstall
URL for the board please? What disk chipset is in use? Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of comperr Sent: Saturday, March 01, 2008 9:08 PM To: freebsd-questions@freebsd.org Subject: Re: HDD missing from sysinstall Just to add I am using an MSI P6N SLI plat. motherboard On Mar 1, 10:28 pm, comperr [EMAIL PROTECTED] wrote: When I put in my fbsd 6.3 or 7.0 install disk sysinstall is unable to detect any of the hard drives in my computer. This is includes SATA and IDE HDDs in varying orders. BIOS is able to detect the the hard drives. I Previously had fbsd 6.2 installed on them and the problem started when I upgraded the kernel to 6.3 although I don't see my upgrades relevance as I have tried to reinstall from a clean disk since then. ___ [EMAIL PROTECTED] mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade
?? wrote: You can try with portupgrade -a --batch Regards. Vivian On Tue, 04 Mar 2008 02:55:32 +0800, [EMAIL PROTECTED] wrote: Is there a way to get the portupgrade to just accept all of the defaults for the configurations of the individual ports. I tried # env BATCH=yes, but it still just goes on hanging on the port configuration menus. It seems as though these time out (though I'm not sure). Chris Maness ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks, guys... Just looked at the man page a little more carefully and spotted it. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Daylight Savings time
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Lisa Casey Sent: Saturday, March 01, 2008 12:19 PM To: freebsd-questions@freebsd.org Subject: Daylight Savings time Hi, I suspect my FreeBSD 5.2 system isn't going to handle the change to Daylight Savings Time correctly next weekend: zdump -v /etc/localtime | grep 2008 /etc/localtime Sun Apr 6 06:59:59 2008 UTC = Sun Apr 6 01:59:59 2008 EST isdst=0 gmtoff=-18000 /etc/localtime Sun Apr 6 07:00:00 2008 UTC = Sun Apr 6 03:00:00 2008 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Oct 26 05:59:59 2008 UTC = Sun Oct 26 01:59:59 2008 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Oct 26 06:00:00 2008 UTC = Sun Oct 26 01:00:00 2008 EST isdst=0 gmtoff=-18000 Could someone help me remember the steps I need to take to correct this? Here's a little very hacky script I put together last year. I forget where you get the current timezone files, you can google for that. The process is explained in the script. you will need to adjust for your location, it should be obvious where. Some BSD versions uses a link. Some other unices just copy the zonefile in. I manage a number of different unices. #!/bin/sh zdump -v /etc/localtime | grep 2007 echo If sun Mar 11 and Nov 1 then OK echo Otherwise stop script now and rerun from clean temp dir echo also ls -l /etc |more and check that localtime is not a link sleep 5 fetch ftp://server.example.com/pub/tzdata2007c.tar.gz tar -xzf tzdata2007c.tar.gz zic -d zoneinfo northamerica cp -R zoneinfo/* /usr/share/zoneinfo zdump -v /usr/share/zoneinfo/PST8PDT | grep 2007 zdump -v /usr/share/zoneinfo/America/Los_Angeles | grep 2007 echo if localtime is a link then Cntl-C, stop and rm /etc/localtime then echo ln -s /usr/share/zoneinfo/PST8PDT /etc/localtime sleep 5 cp /usr/share/zoneinfo/PST8PDT /etc/localtime zdump -v /etc/localtime | grep 2007 echo If Sun Mar 11 and Nov 1 then OK echo now rm -r this temp dir Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Daylight Savings time
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Erik Trulsson Sent: Saturday, March 01, 2008 1:04 PM To: Lisa Casey Cc: freebsd-questions@freebsd.org Subject: Re: Daylight Savings time On Sat, Mar 01, 2008 at 03:18:52PM -0500, Lisa Casey wrote: Hi, I suspect my FreeBSD 5.2 system isn't going to handle the change to Daylight Savings Time correctly next weekend: zdump -v /etc/localtime | grep 2008 /etc/localtime Sun Apr 6 06:59:59 2008 UTC = Sun Apr 6 01:59:59 2008 EST isdst=0 gmtoff=-18000 /etc/localtime Sun Apr 6 07:00:00 2008 UTC = Sun Apr 6 03:00:00 2008 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Oct 26 05:59:59 2008 UTC = Sun Oct 26 01:59:59 2008 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Oct 26 06:00:00 2008 UTC = Sun Oct 26 01:00:00 2008 EST isdst=0 gmtoff=-18000 Could someone help me remember the steps I need to take to correct this? Install the misc/zoneinfo port, which will install an updated zoneinfo file on your machine, and then run tzsetup(8) to update /etc/localtime. That may work on 5, I don't know. It won't work on 4 since the ports structure is so different now. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD bind performance in FreeBSD 7
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chris Sent: Friday, February 29, 2008 6:21 PM To: Adrian Chadd Cc: [EMAIL PROTECTED]; freebsd-questions@freebsd.org Subject: Re: FreeBSD bind performance in FreeBSD 7 On 01/03/2008, Adrian Chadd [EMAIL PROTECTED] wrote: On 01/03/2008, Chris [EMAIL PROTECTED] wrote: You working round what I just said. A nic should perform equally well as it does in other operating systems just because its cheaper its not an excuse for buggy performance. There is also other good network cards apart from intel pro 1000. I am talking about stability not performance, I expect a intel pro 1000 to outperform a realtek however I expect both to be stable in terms of connectivity. I expect a realtek in freebsd to perform as well as a realtek in windows and linux. :) Patches please! Adrian -- Adrian Chadd - [EMAIL PROTECTED] Ironically the latest server I got last night has a intel pro 1000 a rarity :) I am just giving feedback as when I speak to people in the datacentre and hosting business the biggest gripe with freebsd is hardware compatability, as I adore freebsd I ignore this and work round it but its defenitly reducing take up. Of course I know current re issues are getting attention which I am thankful for, I fully understand the time and effort required to write drivers patches etc. and have got no critisicms for the people who do this my complaint is more focused on people claiming there is no issues its just the hardware. There aren't issues on hardware that is compatible. You can't run MacOS X on an off-the-shelf PC and nobody complains about it. You can't run Solaris for the Sparc on an Intel box but nobody complains about it. FreeBSD is not Java, it is not write once, run anywhere If there is any problem with FreeBSD in this respect is that it supports the poor hardware AT ALL. Of course, we can't do much about that - a code contributor who gets access to CVS can put anything they want into the FreeBSD source, and drivers are a particular problem - since few developers are going to have duplicates of the hardware, only the contributing developer really knows if his driver is solid or not. Arguably it might be better to drop support for poor hardware, then the people who had such hardware would not be tempted to run FreeBSD - thereby having a bad experience with it, and blaming FreeBSD about it. I challenge you to find an example of very high quality hardware that has a driver in FreeBSD that has a lot of problems. Yet, you can find a lot of poor quality hardware that has a FreeBSD driver with a lot of problems. That should tell you something - that the issue for the poor hardware really is just the hardware The people complaining about hardware compatibility need to pull their heads out. If they are buying brand new systems they are utter fools if they don't check out in advance what works and what doesen't. It's not like there's a shortage of experienced people on this list who could tell them what to buy. And if after the fact they find out their shiny new PC won't run FreeBSD - then they take it back to the retailer and exchange it for a different model. Why is this so difficult? My beef with the DNS tests was that ISC ran out and bought the hardware FIRST, -then- they started testing. This is directly contrary to every bit of advice ever given in the computer industry for the last 50 years - you select the software FIRST, -then- you buy the hardware that runs it. In short, it said far more about the incompetence of the testers than the shortcomings of the software. The people who have USED systems who are bitching about FreeBSD not being compatible with their stuff need to get over it. OK, so they didn't get a chance to select the hardware, they are using some retired Windows box that won't run the new version of Windows. So they come here and our stuff has a problem with some hardware part. Well, OK fine - how does this hurt them? Their old computer wasn't usable for Windows anymore, now was it? In short, their computer at that point was worthless - and why is it OUR responsibility to make our stuff compatible with their old computer? How does us being incompatible take anything away from them - their computer was scrap anyway. If there's a problem, well they can go to the computer junkyard and exchange their scrap computer for a different old scrap computer that has compatible parts. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Performance Issues on 6.3
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Natham Sent: Saturday, March 01, 2008 10:04 AM To: Mel Cc: Lyle Miller; freebsd-questions@freebsd.org Subject: Re: Performance Issues on 6.3 I made the test today and i got awesome results. One of my harddrives (RAID 1 ) goes offline. I made the test with only 1 disk trasfering a 1.7GB file trought FTP and samba. Samba got about 24mb/s and ftp got about 45mb/s from the single disk both. Samba takes the twice the time than ftp, it is my bottleneck anyone has any patch/suggestion to improve the samba performance on freebsd? Are you happy with your 45mb/s? Wern't you claiming gigabit here? Seems if it was gigabit then 45mb/s is a problem, eh? One more test for you. Map a drive on your 'doze system Drop to command line (start-run-cmd) xcopy a sample file from c: to the mapped drive xcopy a sample file from mapped drive back to c: Time it Compare the times, what are the results? What are the results in comparison with the other tests? Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Creating a custom install disk
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Doug Hardie Sent: Sunday, March 02, 2008 6:16 PM To: freebsd-questions Subject: Creating a custom install disk I have a number of servers that I am going to be updating to FreeBSD 7 from 6.2. I have built a new base system with all the configurations and ports and local code that I need. This process takes about 2 days from the distribution CDs. I need a way to clone this machine and install on the others. My first idea was a custom install disk. The make release process does not appear to do what I want. It would install a GENERIC kernel and take the config files from the distribution. LiveCD was tried, but it fails with numerous attempts to write to directories that do not exist. I expect I could manually create those directories, but I am not sure what it would actually install since it too builds a new GENERIC (but slightly modified) kernel. I tried creating a dump file of the new machine and restoring it on the old one. I did root first and was going to then do /usr, but the alterations to root were such that the system just couldn't keep going through the process. That what I had expected, but it was worth a try. I have not tried this, but perhaps it might work. Creating the dump files on the new machine, booting the old from the live filesystem cd, recreating the filesystems on disk and then restoring from the dump files on the new system. That would require a good net connection between the 2 machines. Is there a better way to do this? Yes: http://freshmeat.net/projects/g4l/ Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Maximum number established TCP connection
--- Bill Moran [EMAIL PROTECTED] wrote: In response to Matthew Seaman [EMAIL PROTECTED]: Bill Moran wrote: In response to Patrick Dung [EMAIL PROTECTED]: Hello I would like if there is a (countable) limit for the max TCP connection of a Apache web server. Suppose: 1. An apache web server serves a very big iso file. 2. 5000 people tried to connect to the apache server to get the iso file. 3. They connect to the server gradually (not 5000 people starting at the same moment). So that there will not be a problem caused by the TCP backlog limit. 4. There will be 5000 established TCP connections. Is it true that FreeBSD could handle 'unlimited' established TCP connections as long as it has enough CPU power and memory? The FreeBSD limit on the number of open TCP connections is significantly higher than the Apache limit on the number of concurrent HTTP sessions. I believe Apache has a hard limit of 256. That's a compile-time option in apache-1.3.x -- you can set APACHE_HARD_SERVER_LIMIT in /etc/make.conf to override the default of 512 if required. However in apache-2.2.x it seems the limits are imposed entirely by the MPM settings in httpd.conf -- at least, I cannot find any tunables in the port Makefiles. Interesting. I found this: http://httpd.apache.org/docs/2.0/mod/mpm_common.html#serverlimit Which claims the hard limit is 20,000. So I guess my information is a bit out of date. -- Bill Moran http://www.potentialtech.com Hello I have checked the link and dig deeper. For prefork model: One connection should be served by one httpd child process. The default limit, as most of you had said, it should be MaxClients or ServerLimit (default is 256 described in apache manual). If worker model is used, the max connection limit should still be MaxClients, but there are other related parameters which affect the limit. (ThreadsLimit, ServerLimit, ThreadsPerChild). ps: Each directive (eg. ServerLimit) may have different meanings in different MPM. I hope my understanding is correct and please correct me if I am wrong. Regards Patrick Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kern.ipc.maxpipekva
No chance at all, I would have said. On 03/03/2008, Mel [EMAIL PROTECTED] wrote: On Sunday 02 March 2008 13:36:26 Colin Adams wrote: I'm getting error messages about this when trying to run my program. As far as I know, I don't use IPC at all, although I dare say it is used in one of the libraries that are linked in. After googling for this error, I edited /boot/loader.conf to set it to 6500 (a nice big number?), and now if I do: sysctl kern.ipc.maxpipekva I see: kern.ipc.maxpipekva: 6500 but I still get the message. I also get a lot of messages saying: Fatal error `Cannot create kernel pipe' at line 294 in file /usr/src/lib/libc_r/uthread/uthread_init.c (error = 24) Why does this occur, and what can i do about it? grep 24 /usr/include/sys/errno.h: max open /files/. This signals that a thread can't be created, cause there's too many open files. Any chance your program/library loops like mad, creating threaded workers that open a socket/file and never end? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0R X.Org 1.4.0 PANIC on switching console / exit
El día Saturday, March 01, 2008 a las 02:52:41PM +0100, Matthias Apitz escribió: Hello, I'm installing 7.0R on a Fujitsu Siemens Lifebook C series X11 comes up but the box panic's on first console switch or on exit of X (fully reproduceable, also with ACPI off); I've put the Xorg.0.log and /etc/X11/xorg.conf here is someone wants to have a look: http://www.unixarea.de/Xorg.0.log http://www.unixarea.de/xorg.conf Any hints? Thanks in advance The problem is unrelated to FreeBSD because the Xorg server in Knoppix 5.3 shows the same problem on this hardware; I've filed a bug report in Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=14791 matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
