Re: error message, what does this mean?
May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, flags 0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, ... This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. Both disks are on seperate SCSI buses. Is this because the cp -R tries to copy /proc ?? Probably. Procfs has bugs that cause bad things to happen when some files in it are copied. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
On Wed, May 26, 1999 at 03:50:21AM -0700, Jordan K. Hubbard j...@zippy.cdrom.com wrote: Unless I hear unanimous fierce outcry against it, I'm strongly considering making FTP_PASSIVE_MODE obsolete by virtue of being the default for all tools/libraries which currently examine it. FTP_ACTIVE_MODE will be the new flag for toggling the previous behavior. Given the state of the Internet today, I think this is purely a sensible change in defaults. Comments? - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Yay! This is awesome. I guess in addition to ftp, the tools and libraries you talk about would also include fetch, and other firewall not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE by doing '-P -' too). -- Yan P.S. - Everyone knows allowing connections from other side's port 20 is silly since root can control src port. Hell, nmap even does port scan with source port of 20 if you ask it to. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: error message, what does this mean?
As Bruce Evans wrote ... May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, flags 0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, ... This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. Both disks are on seperate SCSI buses. Is this because the cp -R tries to copy /proc ?? Probably. Procfs has bugs that cause bad things to happen when some files in it are copied. Hmm. Never seen it before. But doing a cd / ; find . -fstype ufs -print | cpio -pudm /mnt works like a charm without the vnode_pager messages. So looks like procfs alright. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: error message, what does this mean?
As Matthew Dillon wrote ... :etc : :This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. :Both disks are on seperate SCSI buses. Is this because the cp -R :tries to copy /proc ?? : :| / o / / _Arnhem, The Netherlands- Powered by FreeBSD - :|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org It seems to me that a cp command like is probably trying to cp -R /mnt to /mnt ... /* will include /mnt, right? I'm not sure what would be causing the errors, though, unless the cp is recursing endlessly due to the cp of /mnt on top of /mnt and running the filesystem out of space... In the end that happens, but not after a couple of seconds already. I'm quite sure it is the copying of /proc that triggers the messages. The VT_PROCFS like in May 28 10:04:15 p100 /kernel: tag VT_PROCFS, type 6, pid 193, mode 180, flags 0 also seems to indicate this. If I do: cd / ; find . -fstype ufs -print | cpio -pdum /mnt it works just fine without messages (of course until /mnt becomes full like you mention above). I've never seen this procfs behaviour before BTW. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Jordan K. Hubbard j...@zippy.cdrom.com writes: Unless I hear unanimous fierce outcry against it, I'm strongly considering making FTP_PASSIVE_MODE obsolete by virtue of being the default for all tools/libraries which currently examine it. FTP_ACTIVE_MODE will be the new flag for toggling the previous behavior. I agree that passive mode should be the default. I do not agree that the tools should be changed to reflect this. I suggest that we instead set FTP_PASSIVE_MODE to YES in some suitable place (e.g. /etc/profile, /etc/cshrc). DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Doug White dwh...@resnet.uoregon.edu writes: I second the suggestion to 'autoprobe' PASV support, and revert to active mode (w/ an appropriate msg) if PASV is refused. No. Ncftp tries to do this, and provides adequate proof that it is not practical. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Dan Langille junkm...@xtra.co.nz writes: For the argument that some ftp servers don't accept passive mode, I say it's a question of numbers: which default setting will satisfy the greatest number of people? which setting will reduce the number of questions how do I do X? FTP servers which do not accept passive mode are, IMHO, broken. Their loss. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Jan B. Koum j...@best.com writes: Yay! This is awesome. I guess in addition to ftp, the tools and libraries you talk about would also include fetch, and other firewall not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE by doing '-P -' too). CVSup uses multiplexed mode by default, which means it multiplexes its various data channels over a single TCP connection. The server does not (should not) attempt to connect back to the client. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
On 28 May 1999, Dag-Erling Smorgrav wrote: Jan B. Koum j...@best.com writes: Yay! This is awesome. I guess in addition to ftp, the tools and libraries you talk about would also include fetch, and other firewall not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE by doing '-P -' too). CVSup uses multiplexed mode by default, which means it multiplexes its various data channels over a single TCP connection. The server does not (should not) attempt to connect back to the client. No. $ /usr/local/bin/cvsup /usr/src-supfile -g -L 2 ... Establishing active-mode data connection Timed out waiting for connection from server. Check your firewall setup or try the -P m option And it never gets there (firewall is 3 hops down the road). '-P m' does change the behaviour. Nick To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Nick Hibma nick.hi...@jrc.it writes: On 28 May 1999, Dag-Erling Smorgrav wrote: CVSup uses multiplexed mode by default, which means it multiplexes its various data channels over a single TCP connection. The server does not (should not) attempt to connect back to the client. No. Yes, it does. If your version doesn't, you're way overdue for an upgrade :) The documentation for CVSup 16.0 says The modes provided for this are multiplexed mode, passive mode, SOCKS mode, and active mode. All but multiplexed mode are deprecated. Multiplexed mode can handle any situation that the other modes can handle. By default the channels are established in multiplexed mode, if the server is new enough to support it. I can't remember how long multiplexed mode has been the default, but I'm sure it was already the default in 15.4 or whatever was the last version before 16.0. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
CVSup uses multiplexed mode by default, which means it multiplexes its various data channels over a single TCP connection. The server does not (should not) attempt to connect back to the client. No. $ /usr/local/bin/cvsup /usr/src-supfile -g -L 2 ... Establishing active-mode data connection Timed out waiting for connection from server. Check your firewall setup or try the -P m option And it never gets there (firewall is 3 hops down the road). '-P m' does change the behaviour. You're probably still running cvsup 15.4 or earlier. As of version 16, multiplexed mode is the default. Upgrade, if it's that important. I'm still running 15.4 at a lot of places... works well enough for cvsup make world, even with the (petty) annoyance of '-P m'. ==Michael To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: splash screen broken??
Whenever I try to load the splash screen (300x200 256 colors) the modules seem to load right, however, when the kernel boots, it gives me an error about mod_register_init or something of that nature, I was just testing the config... I tried these commands at the boot loader. Here it is... I typed the exact same lines into the bootloader that I showed you in my last mail, and here is my dmesg output... I also have the line pseudo-device splash in my kernel so I know that's not the problem. ... module_register_init: MOD_LOAD (splash_bmp, c028162c, 0) error 19 That's what we needed to see. Error 19 is ENODEV; this means you either don't have VESA support compiled in, haven't loaded the VESA module, or your VESA BIOS doesn't support a mode that allows a 300x200x8 image to be displayed. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msm...@freebsd.org \\-- Joseph Merrick \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
On 28 May 1999 at 14:05, Dag-Erling Smorgrav d...@flood.ping.uio.no wrote: FTP servers which do not accept passive mode are, IMHO, broken. Their loss. I'll second that opinion. Netscape and Microsoft browsers, at least, have been using passive FTP for years (1994 or earlier). One could argue that these are the most used FTP clients in the world, and has made passive mode a de facto requirement for public FTP servers. Jacques Vidrine / n...@nectar.cc / nec...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -Current still leaking mbuf's
On Thu, 27 May 1999, Kevin Day wrote: I tried doubling whatever it was that putting maxusers at 256 set it at. (I can get the exact number later). I'm running with no NMBCLUSTERS setting, just with maxusers at 128 at the moment. Okay, you may want to bump NMBCLUSTERS. You might want to collect some netstat -m stats as time goes on. In addition to being easier to read, it may give you some hints as to how high you want to go with mbuf clusters. I added a cron job to to netstat -m every half hour... Right now, after 10 hours of being up: 130/1686/2560 mbuf clusters in use (current/peak/max) This is what you care about. If the peak pops above 1670 (2/3 of 2560), you should try bumping NMBCLUSTERS to 4096 or maybe 8192. This didn't happen in 2.2.8 or 3.1, so I'm trying to figure out what's causing it. :) NFS could be a little less efficient than in previous versions. [...] #11 0xc015c382 in m_retryhdr (i=0, t=1) at ../../kern/uipc_mbuf.c:297 297 panic(Out of mbuf clusters); Doug White Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
According to Dag-Erling Smorgrav: FTP servers which do not accept passive mode are, IMHO, broken. Their They're broken with respect to RFC-959, not only to your opinion :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Announcing a new cvsup server - cvsup6.freebsd.org
A florida ISP recently donated a T3 connection and a beefy SMP box to us, so I took advantage of this to create another cvsup mirror which allows up to 32 connections. Folks are encouraged to use this site in preference to some of our more loaded cvsup servers (like cvsup1 and cvsup2) and it updates from freefall once an hour, so the bits are nice and fresh. :) This site is also set to become an FTP and www mirror, but we need a bit more disk space first. Those of you who are experienced DNS sleuths as well as hardened baseball fans might also find this site interesting for other reasons (and that's the only clue you guys get). That is all! - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Announcing a new cvsup server - cvsup6.freebsd.org
Just a warning -- it does not appear to have reverse DNS set up on it. This could be a problem if you try to ever send mail from it. host cvsup6.freebsd.org cvsup6.freebsd.org is a nickname for hitter.freebsd.org hitter.freebsd.org has address 207.192.64.20 nslookup 207.192.64.20 Server: ns2-snfc21.pbi.net Address: 206.13.28.12 *** ns2-snfc21.pbi.net can't find 207.192.64.20: Non-existent host/domain On Fri, 28 May 1999, Jordan K. Hubbard wrote: A florida ISP recently donated a T3 connection and a beefy SMP box to us, so I took advantage of this to create another cvsup mirror which allows up to 32 connections. Folks are encouraged to use this site in preference to some of our more loaded cvsup servers (like cvsup1 and cvsup2) and it updates from freefall once an hour, so the bits are nice and fresh. :) This site is also set to become an FTP and www mirror, but we need a bit more disk space first. Those of you who are experienced DNS sleuths as well as hardened baseball fans might also find this site interesting for other reasons (and that's the only clue you guys get). That is all! - Jordan 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
Re: FTP passive mode - a new default?
On Fri, May 28, 1999 at 02:09:19PM +0200, Dag-Erling Smorgrav d...@flood.ping.uio.no wrote: Jan B. Koum j...@best.com writes: Yay! This is awesome. I guess in addition to ftp, the tools and libraries you talk about would also include fetch, and other firewall not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE by doing '-P -' too). CVSup uses multiplexed mode by default, which means it multiplexes its various data channels over a single TCP connection. The server does not (should not) attempt to connect back to the client. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no I know how CVSup works. If you are behind firewall, you need to use -P - command line switch. What I am saying, is that it would be nice if CVSup would use passive mode by default now also (like ftp/fetch will). -- Yan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
On Fri, May 28, 1999 at 03:13:55PM -0700, Jan B. Koum jkb wrote: On Fri, May 28, 1999 at 02:09:19PM +0200, Dag-Erling Smorgrav d...@flood.ping.uio.no wrote: Jan B. Koum j...@best.com writes: Yay! This is awesome. I guess in addition to ftp, the tools and libraries you talk about would also include fetch, and other firewall not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE by doing '-P -' too). CVSup uses multiplexed mode by default, which means it multiplexes its various data channels over a single TCP connection. The server does not (should not) attempt to connect back to the client. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no I know how CVSup works. If you are behind firewall, you need to use -P - command line switch. What I am saying, is that it would be nice if CVSup would use passive mode by default now also (like ftp/fetch will). -- Yan Never mind me. I go upgrade now ;) -- Yan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
* From: Dag-Erling Smorgrav d...@flood.ping.uio.no * FTP servers which do not accept passive mode are, IMHO, broken. Their * loss. No. The losers will be our users who can't talk to them. I don't have a problem with changing the default as long as there are ways to turn them off easily (read: on a per-port basis). Can we cancel an environment variable set in /etc/login.conf from a Makefile? -PW To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Jan B. Koum j...@best.com writes: I know how CVSup works. If you are behind firewall, you need to use -P - command line switch. [...] No. I use CVSup from behind a firewall daily (actually, 23 times a day on one box and 24 times a day on another) without any fancy switches. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
as...@freebsd.org (Satoshi - Ports Wraith - Asami) writes: * From: Dag-Erling Smorgrav d...@flood.ping.uio.no * FTP servers which do not accept passive mode are, IMHO, broken. Their * loss. No. The losers will be our users who can't talk to them. I don't have a problem with changing the default as long as there are ways to turn them off easily (read: on a per-port basis). Can we cancel an environment variable set in /etc/login.conf from a Makefile? If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO before trying to fetch the port. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
* From: Dag-Erling Smorgrav d...@flood.ping.uio.no
* I don't have a problem with changing the default as long as there are
* ways to turn them off easily (read: on a per-port basis). Can we
* cancel an environment variable set in /etc/login.conf from a Makefile?
*
* If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or
* /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO
* before trying to fetch the port.
No. This is from libftpio/ftpio.c:
===
static void
check_passive(FILE *fp)
{
if (getenv(FTP_PASSIVE_MODE))
ftpPassive(fp, TRUE);
}
===
Satoshi
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
as...@freebsd.org (Satoshi - Ports Wraith - Asami) writes: No. This is from libftpio/ftpio.c: Libftpio will shortly be deprecated. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Anybody working on dset utility for ELF?
Is there anybody out there working on making /sbin/dset recognize ELF kernel files? I need it, so if there is nobody, I'm going to work on it myself. If you are familiar with this, please give me pointers or hints as to how best to do this. Carlos C. Tapang http://www.genericwindows.com
Re: FTP passive mode - a new default?
If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO before trying to fetch the port. Heh, no. UTSL. All the code which checks this, checks to see if it's set to anything at all, not if it's set explicitly to YES. :) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Jordan K. Hubbard j...@zippy.cdrom.com writes: If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO before trying to fetch the port. Heh, no. UTSL. All the code which checks this, checks to see if it's set to anything at all, not if it's set explicitly to YES. :) In that case, the source is wrong. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
* From: Dag-Erling Smorgrav d...@flood.ping.uio.no * Libftpio will shortly be deprecated. Fine. Just make sure /etc/login.conf is not updated too early then. Satoshi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Well, if we're replacing it with libfetch then either fetch(1) or libfetch(3) need to check it too. At the moment, neither does - I just checked. :-) - Jordan as...@freebsd.org (Satoshi - Ports Wraith - Asami) writes: No. This is from libftpio/ftpio.c: Libftpio will shortly be deprecated. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no 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
Re: FTP passive mode - a new default?
No, you're the one who's wrong, the source is simply the source. :-) My only point was that you should make sure something is a certain way before you offer advice for dealing with its *current* behavior since, otherwise, that's just confusing to everyone. Either way, I don't think that *any* of the current sources, from libfetch to libftpio, are currently doing anything right with FTP_PASSIVE_MODE and hence this debate is also 100% academic for the time being. :-) - Jordan Jordan K. Hubbard j...@zippy.cdrom.com writes: If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO before trying to fetch the port. Heh, no. UTSL. All the code which checks this, checks to see if it's set to anything at all, not if it's set explicitly to YES. :) In that case, the source is wrong. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Anybody working on dset utility for ELF?
On Fri, May 28, 1999 at 06:12:33PM -0700, Carlos C. Tapang ctap...@easystreet.com wrote: Is there anybody out there working on making /sbin/dset recognize ELF kernel files? I need it, so if there is nobody, I'm going to work on it myself. If you are familiar with this, please give me pointers or hints as to how best to do this. Carlos C. Tapang http://www.genericwindows.com Uhm.. I thought that is what /sbin/kget does, no?! -- Yan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP passive mode - a new default?
Jordan K. Hubbard j...@zippy.cdrom.com writes: Well, if we're replacing it with libfetch then either fetch(1) or libfetch(3) need to check it too. At the moment, neither does - I just checked. :-) Umm, I'm kinda embarassed. The 19990529 patchkit fixes that :) URL:http://www.freebsd.org/~des/software/fetch-19990529.tgz DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Interesting bogons from last night's 4.0 snapshot.
Bogon #1: Userconfig doesn't appear to work - change anything at all and you're looking at a kernel panic when you exit. Hmmm! Bogon #2: Correcting Natoma for non-SMP configuration message on SMP boxes is now printed twice (once for each CPU? :). Bogon #3: bt_isa_probe: Probe failed for card at 0xNNN Where NNN is 6 different addresses. The driver should never be this chatty unless bootverbose is set. JFYI - don't want us getting *too* complacent with -current now, do we? :-) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Anybody working on dset for ELF? (resend)
Sorry I had to do this again. I sent the first one in html format, which most mail readers don't support. Is there anybody upgrading dset to work with ELF kernels? If not, I'd like to work on it myself. If you are familiar with this, please give me pointers or hints. Thanks. Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Invocating as at gcc -pipe filename.s
On my 3.1-REL and 3.1-STABLE-19990331 systems, invocation of gas at gcc
-pipe is not treated correctly.
For example, on my 2.2.8-STABLE system says,
-
moon: {101} touch test.s
moon: {102} gcc -v -pipe test.s
gcc version 2.7.2.1
/usr/bin/as -o /var/tmp/ccsU37121.o test.s
/usr/bin/ld -e start -dc -dp /usr/lib/crt0.o -L/usr/libdata/gcc
/var/tmp/ccsU37
121.o /usr/lib/libgcc.a -lc /usr/lib/libgcc.a
/usr/lib/crt0.o: Undefined symbol `_main' referenced from text segment
moon: {103}
-
gcc doesn't use -pipe option when passes test.s to /usr/bin/as. But on
my 3.1-RELEASE system,
-
leda: {100} touch test.s
leda: {101} gcc -v -pipe test.s
gcc version 2.7.2.1
/usr/libexec/elf/as -v -o /var/tmp/ccjoC3551.o test.s -
GNU assembler version 2.9.1 (i386-unknown-freebsdelf), using BFD version
2.9.1
^C
leda: {102}
-
gcc passes test.s and - to /usr/libexec/elf/as. With these arguments,
/usr/libexec/elf/as waits source from stdin (but - should be --).
Does anyone know that this problem may occur on recent -current system?
# Sorry, I have no -current system for testing now.
--
Jun Kuriyama // kuriy...@sky.rim.or.jp
// kuriy...@freebsd.org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Announcing a new cvsup server - cvsup6.freebsd.org
On Fri, 28 May 1999 14:44:58 -0700, Jordan K. Hubbard j...@zippy.cdrom.com said: [...] create another cvsup mirror which allows up to 32 connections. Folks are encouraged to use this site in preference to some of our more loaded cvsup servers (like cvsup1 and cvsup2) and it updates from freefall once an hour, so the bits are nice and fresh. :) cvsup3 allows 24 connections (max 3 per /24, unlimited within MIT). If you're connected to the vBNS, it's probably your best choice as we're only four 100-Mbit/s hops away from MIT's vBNS connection. Likewise ESnet (hi, Guy!). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Anybody working on dset for ELF? (resend)
dset is no longer required for ELF kernels - see kget instead. - Jordan Sorry I had to do this again. I sent the first one in html format, which most mail readers don't support. Is there anybody upgrading dset to work with ELF kernels? If not, I'd like to work on it myself. If you are familiar with this, please give me pointers or hints. Thanks. Carlos C. Tapang http://www.genericwindows.com 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
savecore too (Re: kvm_getswapinfo is broken)
On Thu, May 27, 1999 at 02:09:14AM +0400, Dmitrij Tejblum wrote: This is a known problem. It is because dev_t in kernel and dev_t and userland are now different things. This is worse on the alpha, where they also have different sizes. So, on the alpha, the numbers are broken too, not just device names. Just found that savecore is broken in the same way. What is proper procedure to fix it? I.e. is it must be fixed in the kernel, leaving userland programs as is or in userland, leaving kernel as is? -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Anybody working on dset utility for ELF?
On 29-May-99 Jan B. Koum wrote: Uhm.. I thought that is what /sbin/kget does, no?! It would appear so (I didn't even know kget existed sigh :) But it isn't in any .rc files, so presumably it isn't automagic. Presumably it would be trivial to add though, ie have 'kget /boot/kernel.conf' somewhere in /etc/rc.* ie in /etc/rc.local have - echo -n 'saving boot -c changes..' /sbin/kget /boot/kernel.conf echo 'done' --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
NFS diskless on -current
I tried to upgrade my diskless router this afternoon to -current as
cvsupped last night.
I can't make it boot, though.
The configuration it has been using since it was last rebuilt
from Feb 24's -current (and which has been working for longer than
I care to remember) is:
- /etc/bootptab features:
yeahwhatever:\
:ha=21409773:\
:ip=YYY.YYY.YYY.YYY:\
:sm=255.255.255.240:\
:ht=ether:\
:sa=XXX.XXX.XXX.XXX:
- /tftpboot/freebsd.YYY.YYY.YYY.YYY specifies:
hostname yeahwhatever
netmask 255.255.255.240
rootfs XXX.XXX.XXX.XXX:/export/root/dotat
swapfs XXX.XXX.XXX.XXX:/export/swap/dotat
swapsize 20480
- kernel config mentions NFS_ROOT and NFS.
- kernel built with KERNFORMAT=aout ('cos loader is too stupid to
do NFS just now).
It now panics with Can't mount root when I boot it. And yes, I have
updated the kernel config for new-bus.
I noticed the BOOTP stuff in LINT, but that's been there for a while and
I've never needed to use it before. I turned it on anyway just to see
what happens, but tcpdump doesn't show it sending any bootp requests.
I'm obviously missing something really stupid. Would anyone care to
educate me about changes to diskless booting with NFS root filesystems
since February 24?
- mark
Mark Newton Email: new...@internode.com.au (W)
Network Engineer Email: new...@atdot.dotat.org (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
Network Man - Anagram of Mark Newton Mobile: +61-416-202-223
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
