CVSup Delete failures
FYI, over the last few days, I've been seeing this error while doing a CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: Delete src/contrib/gcc/INSTALL Cannot delete /usr/local/src/freebsd/5.0/src/contrib/gcc/INSTALL: Directory not empty If I manually delete that directory, it gets recreated, and then this error pops back on the next run. Permissions on the directories aren't the issue, that I can tell -- nothing really changes manually here in the src directories. F To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Redundant network connections load balancing
In a Sysadmin (Jan 2002) article, there is explained how to use Linux as a router using redundant network connections (DSL + dialup), as well as load balancing between the two. I recall this required some special kernel configuration directives: CONFIG_IP_ADVANCED_ROUTER=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y and the iproute toolset, which must be installed separately; and a few other changes. I wonder if the same (if not more advanced) could be accomplished with FreeBSD. Take for example, Company A who wants to provision a few sDSL lines. Creating a FreeBSD gateway/router and load balancing the traffic amoungst that (with some careful ipf or ipfirewall rulesets) could be very effective, and a lot cheaper than provisioning a single pipe in some cases. I wonder if anyone has accomplished this with FreeBSD-4.x or 5.x; and if they could share that info. Thanks, Forrest To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
DHCP options in /etc/rc.conf
The problem reported earlier, whereby the default installation does not provide for DHCP configuration of interfaces (as 4.5 does), can be resolved by placing in /etc/rc.conf: ifconfig_xxx=DHCP BUT, you cannot have any options such as dhcp_program, etc., as it will fail. This can be duplicated consistently with new installations, on 5.0 using the latest DP1 ISO image. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0-CURRENT dhcp configuration failure
The 5.0-CURRENT installation and configuration (cvsup/buildworld this evening) does not correctly support dhcp configuration, even when manually placed in rc.conf. The system comes up with the default name Amnesiac. Is this a known bug. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
I've experienced this same problem today; but only after installing 5.0-current on the system in question. It compiled fine with FreeBSD_4.5. This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things (large compile projects with 4.5 before). _F From: Jose M. Alcaide [EMAIL PROTECTED] Date: Tue, 30 Apr 2002 11:28:48 +0200 To: [EMAIL PROTECTED] Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 I am getting this error while building XFree86-Server-4.2.0_2 on a recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): [snip] cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much cc1 dying on a long complex source module when you've overclocked beyond what your silicon can handle is so reliable a test that it's the first thing I use when trying to find the true speed a new system will run at. If you're not overclocking, then bad ram would make a good second suspect, I had a failing DIMM a couple years ago first manifest as signal 10 and 11 errors in cc1. -- Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
Found that cc1 also has a problem with this on a buildworld for FreeBSD-5.0-CURRENT. FYI. I can reinstall 4.5 and attempt the same, but I recall no problems with 4.5. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
To follow up on my previous post: I did reinstall FreeBSD-4.5 (updated with cvsup), did a buildworld etc., then build XFree86-4 with no troubles at all. So looks like the problem may be with FreeBSD-5.0-CURRENT. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
MFC of Perl 5.6?
I searched the archives, and found this question asked, but no responses. I wonder when (if) Perl 5.6 will be MFC'd to 4.x. Thanks, _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Package installation location
Within the scope of this problem, would it not be simple to code in a configuration diretive in the build process, such that a simple entry in /etc/make.conf would tell the ports build where to install ($prefix)? Then, the local admin can make that decision.. whether or not to default to /usr/local. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Package installation location
Haha... okay, then what's the argument about. You're about six years late. The ports system has used $PREFIX for precisely this purpose since October 1994. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/defaults/rc.conf
At 09:30 AM 11/7/2000 +, Konstantin Chuguev wrote: If xinetd has a startup script, why don't you just set inetd_enable="NO" and let the /usr/local/etc/rc.d/xinetd.sh start normally? You need to edit no /etc/rc.* files (except for rc.conf.local, obviously). [ .. ] Sure that would work, but for the type of service it is, this seems rather ambiguous. I would rather see this service handled in the rc.* scripts, where other similar services are handled. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/etc/defaults/rc.conf
It would be useful to have back the program specification variable for inetd. Currently we have: inetd_enable="YES" # Run the network daemon dispatcher (or NO). inetd_flags="-wW" # Optional flags to inetd and the /etc/rc.* files assume the use of the stock inetd. Where some people choose to use alternative inetd-like programs such as xinetd. We'd do better to have in /etc/defaults/rc.conf: inetd_enable="YES" # Run the network daemon dispatcher (or NO). inetd_program=-"/usr/local/sbin/xinetd" # Location of inetd/service daemon inetd_flags="-wW" # Optional flags to inetd .. or something similar, rather than manually editing the core rc.* scripts. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CVSUP access
What's the latest scoop on cvsup access? Yesterday, I started up the process in the early AM, returning late in the evening to find that it still wasn't able to connect (connection limit exceeded). I recall some conversation on, a while back, about this. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Release of 5.0
Just curious on the potential release of 5.0 -- which I presume won't be until next year.. ? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current.freebsd.org FTP wedged
FYI, you get the FTP login prompt, but it hangs thereafter. Looks like something is wedged. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Options for IPFilter
Since IPFilter is integrated as an option into the OS, can we get a better config in the rc.* scripts so that we can define which filter to use (ipfw or ipfilter) and appropriate options. Thx/_F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to use RSA with USA_RESIDENT=NO?
I thought they were going to get rid of this dependency, eventually, due to the change in RSA patent status, et al. On Thu, Sep 14, 2000 at 10:59:08AM +0900, Jun Kuriyama wrote: After installworld, I can not use ssh with RSA. Does someone know how to fix this problem? - % ssh white ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 DH_generate_key % - I have these variables in make.conf - CFLAGS= -O -mpentiumpro -pipe USA_RESIDENT= NO MAKE_IDEA= YES WITH_RSA= YES MAKE_RSAINTL= YES PERL_THREADED= true - -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA decrypt problems
FWIW, I've had a weird (perhaps related) problem, only in the reverse. After creating a certificate (ie: 'make certificate' in apache), I was unable to connect to the server from a Netscape 4.72 browser. It only told me there was a decryption error in the apache logs. ? On Fri, May 05, 2000 at 08:10:27PM -0700, Kris Kennaway wrote: On Fri, 5 May 2000, Steve Price wrote: [Fri May 5 20:46:19 2000] [error] OpenSSL: error:1E06D401:RSAref routines:func(109) :reason(1025) You can interpret these error codes by looking up the defines in openssl/rsaref.h - for example, these two are: #define RSAREF_F_RSA_REF_PRIVATE_DECRYPT 109 #define RSAREF_R_DATA0x0401 which doesn't tell you much in itself. However: Doing 2048 bit private rsa's for 10s: RSA private encrypt failure 14674:error:1E065406:RSAref routines:func(101) :reason(1030):/usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto/../rsaref/rsaref.c:125: 14674:error:1E065406:RSAref routines:func(101) :reason(1030):/usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto/../rsaref/rsaref.c:125: 1 2048 bit private RSA's in 0.00s #define RSAREF_F_RSAREF_BN2BIN 101 #define RSAREF_R_LEN 0x0406 RSARef can't handle keys 1024 bits long. This is a design limitation which the license forbids us from fixing. Does your webserver use a long key? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA decrypt problems
I understand, from private correspondence, that OpenSSH will have SSH2 protocol support, thus allowing people to not use RSA. Can someone confirm as it applies to use on FreeBSD. I personally find the RSARef licensing to be a sham, in the light of everything else on the internet, an would rather not have to use it. But SSH1 requires it in the protocol. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA decrypt problems
Duh :) It didn't occur to me to try another browser: Okay, I just did, using MS Explorer 5 and it worked with no problems. So, this is related to Netscape-4.72. But is it a bug on their part, or something else? Forrest On Fri, May 05, 2000 at 10:49:04PM -0500, Steve Price wrote: On Fri, 5 May 2000, Forrest Aldrich wrote: # FWIW, I've had a weird (perhaps related) problem, only in the # reverse. After creating a certificate (ie: 'make certificate' in # apache), I was unable to connect to the server from a Netscape # 4.72 browser. It only told me there was a decryption error in the # apache logs. I see the same thing in my apache error logs so it probably is related. Did you by chance try another browser and did it work? -steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: db 1.85 -- 2.x or 3.x?
Then, with the problems associated with the Sleepycat license, is there some other alternative to this particular DB product? Surely ours is not the only area that has experienced frustration with this point. What other DB-like projects are out there, etc. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: db 1.85 -- 2.x or 3.x?
I've been curious about this. Would someone clarify what in this license prevents FreeBSD from including it, at some level? _F Sleepycat Software Product Licensing Berkeley DB is an Open Sourcetm product, and complete source code is available from our Web site. If you build an application that you do not redistribute outside of your site, or if you build an application and your source code is freely available and redistributable by others, you may use Berkeley DB at no charge. You must, of course, abide by the terms of the copyrights that apply to the Berkeley DB software. If you redistribute your application outside of your site and your source code is not freely available and redistributable by others, then you require a commercial license from Sleepycat Software. Contact us for commercial licensing terms and pricing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
How will this affect this /etc/mail/mailer.conf "thing" (and I wonder why that was put there to begin with). If we're going to use a mailer.conf, then it should be able to work with other MTAs; which it probably won't because they perform their respective tasks differently. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 sysinstall fails to recognize disks
I tend to think there is something wrong with sysinstall... obviously, the OS works as the internal drives (also LVD 10KRPM drives) work. Sysinstall just tells me there aren't any disks in the system. So, hope whomever maintains sysinstall is monitoring this conversation. I will attempt another rebuild of the system. I've not had a chance to check the cvs logs to see if someone committed any changes/fixes with serendipity. _F At 09:56 AM 3/23/00 -0800, Eric Sabban wrote: I normally wouldn't recommend it. But the same situation with a different (not to be mentioned) OS happened to me. After hours of being frustrated, I decided the scsi controller went south. A cow-orker told me to LL the drive, and voila, magic. These were IBM LVD 10kRPM drives, brand spankin new. I'd recommend updating sysinstall first, if that doesn't work, LL the drives. -eric Matthew Dillon wrote: : : Why not? The drives are empty LVD Drives, nothing bad'll happen. : :Apart from screwing up the factory format. : : I mean, it may very well be sysinstall being massively out of sync, but it shouldn't hurt to LL the drives. : :It should, and will. : :-- :\\ Give a man a fish, and you feed him for a day. \\ Mike Smith I get scared when lay-prorammers talk about Low-Leveling a disk :-). There are virtually no programmers outside of RAID-land (and those are usually considered insane anyway :-)) who should ever have to LL a disk. I think I've LL'd maybe one SCSI disk in the last fifteen years. That said, today's disks are far less likely to blow up if you LL them then older (over 7 years) disks since there isn't a clock track any more. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 sysinstall fails to recognize disks
Is not sysinstall built and installed with a typical make buildworld/installworld? Anyways, I rebuilt it and it works now. Sysinstall was the culprit. _F At 10:08 AM 3/23/00 -0800, Mike Smith wrote: I tend to think there is something wrong with sysinstall... obviously, the OS works as the internal drives (also LVD 10KRPM drives) work. Sysinstall just tells me there aren't any disks in the system. So, hope whomever maintains sysinstall is monitoring this conversation. Sysinstall works fine _IF_IT_IS_IN_SYNCH_WITH_THE_REST_OF_YOUR_SYSTEM_. I will attempt another rebuild of the system. I've not had a chance to check the cvs logs to see if someone committed any changes/fixes with serendipity. Just rebuild sysinstall, like I told you to start with. Or just bring the disks up by hand, which is much faster. Or even try Warner's 'diskprep' tool. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 sysinstall fails to recognize disks
Sorry: da4 at ahc0 bus 0 target 1 lun 0 da4: QUANTUM ATLAS 10K 36SCA UCHD Fixed Direct Access SCSI-3 device da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da4: 34732MB (71132998 512 byte sectors: 255H 63S/T 4427C) _F At 02:47 PM 3/22/00 -0500, Bill Fumerola wrote: On Wed, Mar 22, 2000 at 02:42:44PM -0500, Forrest Aldrich wrote: Since this is a fairly current issue, I'm posting this appropriately. I have a DELL server that has hooked up to it a PowerVault, with 8 36gb 10krpm LVD drives. The system has recognized these previously and dmesg shows them present; however, /stand/sysinstall says that I don't have ANY disks installed when using Label or Fdisk. The PowerVault is connected to a controller. Knowledge of which one would help. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Streamlining FreeBSD Installations
There was mentioned that someone was "appointed" (perhaps unwillingly :) to look into this one... who? I was also curious about what people do to keep a fleet of FreeBSD machines up-to-date with CVSup and buildworld. I can't imagine manually going to more than 100 machines and doing the same thing manually... how time consuming. To summarize again, we are deploying status monitoring machines into POPs, across the US. Those machines are identical in terms of hardware, et al. We were hoping to find a means by which to streamline the installation process, such that we could create (say) custom boot floppies where you'd input minimum information (IP address, hostname, domain, etc.) and it would then go off and perform the installation (from fdisk, newfs... to editing packet filters appropriately, which make require a "template" of sorts). The idea of doing all of this manually makes carpal tunnel syndrome sound like a vacation, compared to what condition one might be in afterward :) Anyone got some ingenious hack to perform this? Someone made a comment about one procedure we were doing which involved using "dd" to mirror a base installation onto another disk. As far as I know, there haven't been any gotchyas with that method. The disks are WD "pluggable" drives. So, we have a master machine that we simply do our mirror from. It's hacky as hell. Someone mentioned that sysinstall could be scripted... is this the way to go, then? TIA... _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD Installations
Yes, making this process easier with Sysinstall would be a Good Thing(tm). Especially I see the need here due to the widespread use of FreeBSD in enterprise environments. This topic will certainly come up again and again. What I would like to see is a customized boot disk that, after loading the kernel etc, goes into a script where you input the critical info (IP, DNS, ... ). It's required to ask the Crypto Questions, I understand -- however, we could "answer" those in the *.cfg file, to avoid the prompts. IMHO, this shouldn't be too difficult to implement. But it would be great to pool in everyone's ideas, so that everyone's needs are considered before commiting such changes. Anyone else have some feedback on this? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD Installations
Another issue here, at least in our application of it, is about adding users and setting passwords.With well over 100 machines, we want to also have installed user accounts for our engineers. Again, nightmareish to consider doing manually. Such a script used at startup could contain also the account name and perhaps the "crypted" form of the password, and some other utility would need to do the magic from there. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD Installations
This wouldn't work in our situation, where we are needing to modify data... so if there were a power outage, imagine the hassle. Good idea, though. Most of our systems have 64 - 128mb of ram. They are doing distributed status monitoring and secondary DNS. So, there would be a bit of changes happening from time-to-time. But again, I doubt this would work for us. From the private emails I've received on this topic, it seems that the consenus is to spiff up sysinstall, which is probably the right place to begin with some of this stuff. Not sure who maintains it. _F At 06:56 PM 3/17/00 +, Andrew Gordon wrote: On Fri, 17 Mar 2000, Forrest Aldrich wrote: I was also curious about what people do to keep a fleet of FreeBSD machines up-to-date with CVSup and buildworld. I can't imagine manually going to more than 100 machines and doing the same thing manually... how time consuming. To summarize again, we are deploying status monitoring machines into POPs, across the US. Those machines are identical in terms of hardware, et al. We were hoping to find a means by which to streamline the installation process, such that we could create (say) custom boot floppies where you'd input minimum information (IP address, hostname, domain, etc.) and it would then go off and perform the installation (from fdisk, newfs... to editing packet filters appropriately, which make require a "template" of sorts). If the job they are doing is fairly simple, and they have (or could have) plenty of RAM, have you considered scrapping the disc drives and having a CD-boot system? Although CD drives are not very reliable for heavy-duty use, you should be able to arrange that the working set gets loaded at start-up and the CD is then idle in all normal use - this may "just work" through normal caching, or you may need to copy active files onto an MFS filesystem (you'll need an MFS for various things anyhow). This has the advantage over pico-BSD style installations that you can fill the rest of the CD with a fairly complete FreeBSD installation: in normal use the CD drive is idle, but you have the full set of tools available for use on rare occasions when they are needed. Obviously the machines need to pick up their identities from somewhere, as you want to just duplicate a stack of identical CDs. If the machines can rely on their environment, DHCP is the obvious way to go; if not, one technique I've used is to key it on the MAC address of the ethernet card (in /etc/rc I pick up the MAC address with ifconfig and then have a big case statement to set up the different characteristics of the machines). Obviously this doesn't suit every application, but I have found it highly advantageous when I want to put down a BSD machine in a location with no local BSD skills to fix things if they go wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0?
On Wed, Mar 15, 2000 at 02:53:57PM +0100, Alexander Langer wrote: Thus spake Bill Fumerola ([EMAIL PROTECTED]): (4) The developers all dropped FreeBSD and are now running Redhat. That's it, I believe. [ ... ] And Joan Rivers is now a Kernel hacker... (smirk) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0?
I noted the tag on the kernel today was updated to 5.0-CURRENT... where is 4.0-RELEASE? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0?
Oh, it MUST be #4:-) (hide) At 04:19 PM 3/13/00 -0500, Bill Fumerola wrote: On Mon, Mar 13, 2000 at 03:57:18PM -0500, Forrest Aldrich wrote: I noted the tag on the kernel today was updated to 5.0-CURRENT... where is 4.0-RELEASE? Multiple choice test: (1) There's a secret consipiracy going around to keep the release of it really, really quiet. (2) The consipiracy is to keep _you_ from knowing about it. (3) It hasn't been released yet because the rough edges are still being taken care of and polished of. (4) The developers all dropped FreeBSD and are now running Redhat. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current.freebsd.org (FTP)
Is not allowing anonymous ftp logins. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Streamlining FreeBSD installations across many machines
Perhaps this would be of interest in CURRENT issues: We have several servers that we plan on deploying across the US. Their purpose in life is network status and monitoring. The hardware profiles are exactly the same... Currently, we're using DD to mirror a disk image onto a new installation, and them nanually tweaking all the necessary configurations. It's tedious, and is going to get hellish with the amount we plan on deploying. I'm wondering if there might not be a way to streamline this install process, such that a boot floopy and script could be created to take a minimum amount of information, and then "do the right thing" as for the install. Things like putting in the packet filters, the kernel, IP config, etc. Surely someone has done this before...? Any pointers would be greatly appreciated. Thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USA_RESIDENT= in latest current
Even though I have USA_RESIDENT="YES" in /etc/make.conf (this is how it was installed), I get: !! You must define the value of USA_RESIDENT as 'YES' or 'NO' as appropriate, in the environment or /etc/make.conf before building can proceed. !! *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USA_RESIDENT= in latest current
Perhaps, but take a look at the installation... it sets it to USA_RESIDENT="YES" (note WITH quotes). _F The proper format is USA_RESIDENT= YES in make.conf. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Megahertz pccard
I'm using the floppies from the 01/27 CURRENT (as that's all they provide now, on current.freebsd.org)... and I can't get it to recognize the cards. Period.When it goes to initialize, and time for installation, nothing shows up for NICs... just ppp, lp0, etc. Is very frustrating! For what it's worth, here are the card numbers I have: 3CCFEM556 B 3CCFE574BT At 09:11 AM 2/8/00 -0800, Frank Mayhar wrote: Gerald Abshez wrote: I thought that I'd heard that the 3CCFE574BT (10/100) from 3com/Megahertz was supported, but it seems like it isn't. I've tried Actually, it is. I'm running one in my laptop right now, in fact, and it works fine. What problems are you seeing? -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Megahertz pccard
Patel, you're a life saver!This is exactly what was needed, change the IRQ. In my case, I chose option 2 and walla. Amazing, so simple. Note this is using the snapshot that is 02/08/2000, latest (floppies). Thank you. Forrest At 11:56 AM 2/8/00 -0800, Parag Patel wrote: On Tue, 08 Feb 2000 14:22:25 EST, Gerald Abshez wrote: There is only the ethernet card plugged in. After the boot probe completes, I get: ep0: No irq?! I also have one of these cards, and it's working fine under 4.0-CURRENT. Seems like the default IRQs used by pccard are being used by something else on your laptop. The default line in /etc/pccard.conf.sample is irq 3 5 10 11 13 15 I needed to add "-i13 -i15" to my /etc/rc.conf's pccard_flags entry as all other IRQs on my laptop were in use. I could have also edited the pccard.conf file. If there's some point at bootup where you can add these flags to pccardd or edit its default pccard.conf.sample file, it's worth a shot. I installed 3.4-STABLE from 3.4's floppies and CDs onto my laptop, hacked /etc/pccard.conf to create an entry for my Megahertz, then updated it to 4.0-CURRENT via NFS. I never tried the 4.0 boot floppies since I needed to run "make installworld" from a build on another box. -- Parag Patel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Snapshots?
Why have there not been any snapshots of 4.0-CURRENT since 01/27/2000? (current.freebsd.org). Just curious... _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Megahertz pccard
Has anyone gotten the Megahertz pccards to work with the boot floppies? I don't believe the correct entry is there for them. I recall there being a discussion here, indicating that the modification wouldn't be difficult. Is there any way we can get this fixed? Thanks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
More breakages
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel textdata bss dec hex filename 1807056 139340 115448 2061844 1f7614 kernel chflags noschg /kernel mv /kernel /kernel.old install -c -m 555 -o root -g wheel -fschg kernel /kernel /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 This is from a cvsup I just performed minutes ago, FYI. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Today's buildworld breakages
Here's the latest fault, from a cvsup just performed: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/net/rcmd.c -o rcmd.o /usr/src/lib/libc/../libc/net/rcmd.c: In function `rresvport_af': /usr/src/lib/libc/../libc/net/rcmd.c:337: too many arguments to function `bindresvport_sa' *** Error code 1 Stop in /usr/src/lib/libc. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCCARD support
Where are we with getting PCCARD support, such as the 3COM MegaHertz (3CCFEM556 B) card in the mainstream distribution? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMP detection
I have a Dell PowerEdge 1300 with dual Pentium II / 400mhz processors installed. However, upon installing today's snapshot of 4.0, the dmesg output doesn't seem to detect the second processor. I wonder if there is a problem here, or if I might have a hardware issue. Thx. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Breakage in FreeBSD-4.0-CURRENT
Got this error, just now after a CVSUP: /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choos e-temp.o) : In function `choose_temp_base': choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mkt emp.o): I n function `mktemp': mktemp.o(.text+0x1e1): undefined reference to `_libc_open' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cpp. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
config tool breaks
Is this a bug, or did I miss something on the list that changed this procedure: cd /usr/src/sys/i386/conf) bash-2.03# config MYMACHINE config: files.i386: No such file or directory bash-2.03# exit The files.* is missing, etc. No changes after a cvsup. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Installation bug (4.0-19991227-CURRENT)
Did a test install against the latest snapshot. The network configuration comes up with "dc0" (we have de0), this "works" in that we were able to perform the network install (so it must be a typo somewhere). However, it results in multiple entries in /etc/rc.conf (three, total), which have to be removed before the network will come up correctly after rebooting. NB, this was an install over a previous 4.0 instance, so there's the possibility that the rc.conf file was edited rather than written over -- though I would doubt that (?). FYI. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Archive mirror problem
I'm trying to get a snapshot from current.freebsd.org and keep getting this error all morning: Failure at end of remote directory () because: timed out This is using mirror.pl. It's worked flawlessly in the past, and for everything else I do. Has something changed on current.freebsd.org? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Today's make world breakage
FYI just CVSup'd and got this: X-UIDL: 495287ccf607850cc65e4c59c7b49751 cd /usr/src/lib/librpcsvc; make beforeinstall cd /usr/src/lib/libskey;make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libskey/skey.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libstand; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libstand/stand.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libtacplus; make beforeinstall sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 /usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libcom_err; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libss; make -B hdrs beforeinstall test -e ss_err.et || ln -s /usr/src/lib/libss/ss_err.et . compile_et ss_err.et test -h ss_err.et rm -f ss_err.et sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/ss.h ss_err.h /usr/obj/usr/src/i386/usr/include/ss sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/copyright.h /usr/obj/usr/src/i386/usr/include/ss/mit-sipb-copyright.h cd /usr/src/lib/libutil;make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libutil/libutil.h /usr/obj/usr/src/i386/usr/include sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libutil/login_cap.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libvgl; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libvgl/vgl.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libwrap;make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libwrap/../../contrib/tcp_wrappers/tcpd.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libz; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zconf.h /usr/obj/usr/src/i386/usr/include sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zlib.h /usr/obj/usr/src/i386/usr/include cd /usr/src/usr.bin/lex;make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 644 /usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/i386/usr/include/g++ -- Building libraries -- cd /usr/src; COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 MAKEOBJDIRPREFIX=/usr/obj DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/home/forrie/bin make -f Makefile.inc1 -DNOINFO -DNOMAN libraries cd /usr/src/lib/csu/i386-elf; make depend; make all; make install rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S cpp: }: No such file or directory cpp: }: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
I have one request for whatever becomes of sysinstall. And that is to make it technically consistent with the command line utilities capabilities. For example, I ran into (on several different occasions) problems where i would label a disk, allocate paritions, change parition types, etc., and it didn't really get done. Doing it manually would generally resolve the problem. However, it's a Good Thing(tm) to have a gui of one form or another to cater to less-experienced users. That's just very sensible. Thanks. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Make world breakage (12/09/99)
Getting this from this morning's make world (after doing a make clean, just for good measure): -- Rebuilding dependencies -- cd /usr/src; COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/ bin LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib OBJFORMA T_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" PERL5LIB=/usr/l ibdata/perl/5.00503 PATH=/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/loca l/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/ X11R6/bin :/usr/local/samba/bin:/usr/local/home/forrie/bin make DESTDIR=/usr/obj/usr/src/tmp I NSTALL="sh /usr/src/tools/install.sh" -f Makefile.inc1 par-depend === share/info === include === include/rpcsvc === lib === lib/csu/i386-elf rm -f .depend mkdep -f .depend -a -nostdinc -I/usr/obj/usr/src/tmp/usr/include/usr/src/lib/cs u/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S mkdep -f .depend -a -nostdinc -I/usr/obj/usr/src/tmp/usr/include /usr/src/lib/csu/ i386-elf/crt1.c /usr/src/lib/csu/i386-elf/crtbegin.c /usr/src/lib/csu/i386-elf/crtend .c In file included from /usr/src/lib/csu/i386-elf/crt1.c:32: /usr/obj/usr/src/tmp/usr/include/stddef.h:39: machine/ansi.h: No such file or directo ry In file included from /usr/src/lib/csu/i386-elf/crt1.c:33: /usr/obj/usr/src/tmp/usr/include/stdlib.h:39: sys/cdefs.h: No such file or directory /usr/obj/usr/src/tmp/usr/include/stdlib.h:41: machine/ansi.h: No such file or directo ry /usr/src/lib/csu/i386-elf/crtbegin.c:28: sys/cdefs.h: No such file or directory /usr/src/lib/csu/i386-elf/crtend.c:28: sys/cdefs.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Compiler looping
Someone recently posted a note about a compiler error (loop?) when compiling mysql. I just did buildworld/installworld from today's cvsup and still get the same problem when it goes to: c++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/mysql\""-DHAVE_CONFIG_H -I./../include -I./../regex-I. -I../include -I.. -I.-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DDBUG_OFF -O -pipe -fno-implicit-templates -c sql_yacc.cc This is compiled directly out of the ports collection. Has anyone identified (and fixed) the bug? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PAM problems
I'm trying, in vain, to get pam_mysql.so working on FreeBSD-4.0-CURRENT. This is in use with Cyrus 1.6.x. I'm running into these errors: Dec 6 19:59:34 inbound pop3d[36251]: unable to dlopen /usr/lib/sasl/libdigestmd5.so: /usr/lib/sasl/libdigestmd5.so: Undefined symbol "RC4_set_key" Dec 6 19:59:38 inbound pop3d[36251]: unable to resolve symbol: pam_sm_authenticate Dec 6 19:59:38 inbound pop3d[36251]: unable to resolve symbol: pam_sm_setcred I'm using the CMU RC4 library, and ./configure locates it. The other symbols are unknown to me. Has anyone else gotten this lot/combo to work? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ps on 4.0-current
Why does ps not show the full path on 4.0 as in 3.3? (for non-root users) ie: 4.0 ps -ax 134 v2 Is+0:00.00 (getty) 135 v3 Is+0:00.00 (getty) 136 v4 Is+0:00.00 (getty) 137 v5 Is+0:00.00 (getty) 3.3 ps -ax 312 v0 Is+0:00.01 /usr/libexec/getty Pc ttyv0 313 v1 Is+0:00.01 /usr/libexec/getty Pc ttyv1 314 v2 Is+0:00.01 /usr/libexec/getty Pc ttyv2 ?? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps on 4.0-current
I seem to recall that conversation here in the mailing list. How about a system configuration variable that determines what info like ps (and friends) can access? Personally, I would just prefer to leave it be. There are too many other potential problems with scripts and such that depend upon the info PS provides. *shrug* :) _F At 12:54 AM 11/24/99 +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Brian Somers writes: In the last episode (Nov 23), Brian Somers said: $ ps jtva USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 222 1 222 9dac400 Is+ va0:00.01 (getty) $ sudo ps jtva USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 222 1 222 9dac400 Is+ va0:00.01 /usr/libexec/getty Pc tt $ head -1 /etc/motd FreeBSD 4.0-CURRENT (HAK) #9: Mon Nov 22 01:09:55 GMT 1999 This looks a bit wrong Now that does look weird. After a bit more investigation, it looks like you can only get the full commandline of your own processes. Root can see all commandlines. Any comments Poul ? Is this anything to do with the recent command line buffering ? Yes, I changed it to this behaviour at warners asking (I think he had the security-meister hard-hat on at the time). I'm personally leaning towards the opinion that the argv is public property and should be visible, but then again, I can see the point in hiding it in some circumstances. I'll stick a sysctl in there which defaults to the "open" position and people who need to hide it can set it to "close" to do so. Will this satisfy everybody ? Warner ? -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BIND update
So wouldn't be the impact if a server was compromized in the absence of an available fix :) At 02:46 PM 11/16/99 +0800, Peter Wemm wrote: Ben Rosengart wrote: On Mon, 15 Nov 1999, Forrest Aldrich wrote: Will we be updating 4.0-current to the latest BIND-8.22-P5? Or -stable for that matter? I believe these changes are eminently qualified, being bugfixes. The changes are most definately not "just" bugfixes. The impact is rather large. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
Same here, no problems. _F At 03:36 PM 11/15/99 -0500, Kenneth Wayne Culver wrote: I just successfully compiled the world and the kernel (defaut optimizations on everything) with gcc 2.95.2, and so far all is well :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BIND update
Will we be updating 4.0-current to the latest BIND-8.22-P5? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Nov 9 Snapshot boot floppy failure
Just tried installing a 4.0-current system from Nov 9 snapshot, on a DELL 6350, 3 18g drives, 512m RAM, Got Signal Trap 12 while in kernel mode. This happened (each time) after it probed the CD drive. I've installed previous 4.0 snaps on this platform without incident. FYI. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Nov 9 Snapshot boot floppy failure (FOLLOW UP)
I backed to Nov 01 snapshot and the install went fine; however it appears it's not writing out partition information correctly. We performed 3 installs, and went over each step judiciously, and when you reboot after the install, it complains about invalid parition information. At 12:26 PM 11/10/99 -0500, Forrest Aldrich wrote: Just tried installing a 4.0-current system from Nov 9 snapshot, on a DELL 6350, 3 18g drives, 512m RAM, Got Signal Trap 12 while in kernel mode. This happened (each time) after it probed the CD drive. I've installed previous 4.0 snaps on this platform without incident. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Release schedule of 4.0
We're building a few new systems. I wondered what the status was of the 4.0 project (stability VBG and release date estimate). Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Pcmcia support
I'm still at 3.2; however, I wonder what plans there are (if any) to have pcmcia support in 4.x (like the 3com 3c574, etc). Might be a good idea to include a pcmcia floppy in the installation media (like Linux already has). Thanks. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Floppies and laptops
I realize there are only so many drivers you can crunch on a floppy... with that in mind, and with the advent of many laptops comnig about that people would like to net-install, would it not be more practical to provide an alternate mfsroot that would be more apt to find your PCMCIA card? Would be a really handy tool/option to have. -F To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
I've a feeling that somewhere there is a memory problem. Netscape-specific perhaps, but I suspect otherwise due to what I've seen. For example: the one machine that I have which will constantly dump core when Netscape is run is an HP Vectra. I've tried 3.0, 2.2.8, all current patches, etc. Core dump. Yet when I loaded Linux, it worked without incident. I have not yet tried Linux emulation, but will give it a shot. I suspected that perhaps the netscape binary needed to be recompiled against a current system. Why? System calls are updated, etc. There might be something really funky going on. The fact that it's stripped of debugging symbols doesn't help much -- but perhaps someone more adept at debugging might take a moment to look into it. Forrest To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
My setup is about the same. I just modified all my login.conf defaults to be unlimited/infinity. Still the same crappy core dumps. Forrest On Mon, Jan 25, 1999 at 08:47:29PM -0500, Luke wrote: Aha! That figures. Since I upgraded to CURRENT, with its login.conf which defaults to unlimited resources, my frequent netscape core dumps have gone away. I hadn't realized why until now. Suggestion: wwhen people complain about Netscape, ask them to mail us back the output of ``ulimit -a''. My login.conf has unlimited for everything for myself and netscape still crashes/locks up. And I have 64M/175swap so I dont think its running out of memory. --- E-Mail: Luke l...@aus.org Sent by XFMail -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
