ctm
I'm working on restoring ctm finally (now the disk is working, and the extra room is terrific!) I am going to do things manually for a short while, so the interval of things is going to be unpredictable, but I'd consider it a favor if, when you get a ctm, you email me directly. Keep the ctm stuff off this list as much as possible, please. +------- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ctm
As most of you know by now, ctm is back, but ftp of ctm is temporarily still broken. If you want something, tell me and I'll stick it in http://www.freebsd.org/~chuckr. It's short of room there too, so don't ask for what you don't need. Thanks, I'll try not to post about ctm on current anymore. +------- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
anoncvs
I have anoncvs working now (straight anoncvs, not pserver): setenv CVSROOT [EMAIL PROTECTED]:/cvs cvs get [some path] I wasn't aware of anyone using pserver method. Any users of anoncvs, could you please test this for me? IMPORTANT!! Reply directly to me, anyone scragging the list will be anathematized!! +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can I obtain 'int-cvs-cur' by CTM ?
On Tue, 17 Aug 1999 [EMAIL PROTECTED] wrote: > Last CTM delta in > ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur > is 'int-cvs-cur.0114.gz' from May 15 1999. There isn't any "int-cvs-cur", so are you referring to maybe the International Crypto Repository run by Mark Murray out of SA? If not, then please try again, because you've lost me, and I fix ctm stuff (so I should know your answer). +------- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can I obtain 'int-cvs-cur' by CTM ?
On Tue, 17 Aug 1999, Nickolay N.Dudorov wrote: > On Tue, Aug 17, 1999 at 12:13:33AM -0400, Chuck Robey wrote: > > On Tue, 17 Aug 1999 [EMAIL PROTECTED] wrote: > > > > > Last CTM delta in > > > ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur > > > is 'int-cvs-cur.0114.gz' from May 15 1999. > > > > There isn't any "int-cvs-cur", so are you referring to maybe the > > And what is (or was earlier) at the URL I post here ? > > > International Crypto Repository run by Mark Murray out of SA? > > I refer to the "CTM interface" to "International Crypto > Repository run by Mark Murray...". (More precisely about "ftp-ing" > CTM deltas from some servers - f.e. 'ctm.freebsd.org'). I thought I knew about all the FreeBSD ctm distributions, but Mark told me about the one he does himself, which surprised me! > > I can't ftp CTM deltas from internat.freebsd.org directly - > there are some problems to connect from Siberia to SA ;-) > > N.Dudorov > > > > > If not, then please try again, because you've lost me, and I fix ctm > > stuff (so I should know your answer). > > > +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "The Matrix" screensaver, v.0.2
On Sun, 22 Aug 1999, Ollivier Robert wrote: > According to Narvi: > > "Falling letters like in the movie with red bills" > > Pill :) > > That very important... The screensaver triggered me to see the movie > again. A. I love it. Yeah, it's gotta be the perfect hacker's movie. Maybe we *should* go approach the producers? I have gone to that movie several times, and I keep on enjoying it, so this is GOOD PR for them. +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "The Matrix" screensaver, v.0.2
On Sun, 22 Aug 1999, Rodney W. Grimes wrote: > > On Sun, 22 Aug 1999, Ollivier Robert wrote: > > > > > According to Narvi: > > > > "Falling letters like in the movie with red bills" > > > > > > Pill :) > > > > > > That very important... The screensaver triggered me to see the movie > > > again. A. I love it. > > > > Yeah, it's gotta be the perfect hacker's movie. > > > > Maybe we *should* go approach the producers? I have gone to that movie > > several times, and I keep on enjoying it, so this is GOOD PR for them. > > Good idea, the approach for approval to distrubute this presented to > the marketing department has a strong leverage on the legal department, > in that they can't just take the easy road of saying ``no'' when > the marketing department is going ``yes, yes.. this would be > good for revenue''. OK, then, I'll do it "with unofficial but general approval of many FreeBSDers" (which is what I'll tell the folks). Too bad I don't live in LA anymore, I used to know the right folks to go to. +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
multiple cd devices
I've been doing a lot of neatening up here, and one of the tasks was to get both of the cdrom drives I have (one per machine) moved over so that they are on the same machine. This was so I can use the one that's a writer in conjuntion with a reader, and do duplication. Anyhow, getting the kernel to recognize cd1 was no problem, but getting /dev/MAKEDEV to do that was a hairy PITA. I couldn't locate, in either cd(4) or cd(9), the information on the maj/min numbers, so that I could just do the mknod's manually, and MAKEDEV would simply do nothing if I entered './MAKEDEV cd1'. After *much* screwing about, in desperation (trying wierd combinations) I did a './MAKEDEV cd2', and *that* made my cd1 devices (not the cd2 ones, but I didn't have a cd2, I didn't care). This sounds pretty wrong, I think MAKEDEV is busted for this, right? And, if you don't want to have the actual maj/min numbers for the cd devices in the man pages (because you want Unix unfriendly), well, shouldn't there be a pointer to a include file that would be up to date with that info, so at least the info is available somehow? BTW, all the other MAKEDEV combinations, like cd*, cd1*, cd1a, etc, all failed noisily, like: ROOT:/dev:113 >sh MAKEDEV cd1a [: 1a: bad number [: 1a: bad number -------- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: multiple cd devices
On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote: > The way certain devices, like cd with its monotonically increasing counter > where devices are probed in order and assigned device based on precedence > and not hardwiring/controller connection, work is consistent between > the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1, > so MAKEDEV accepts "cd2" for "two cd devices". All CD devices work > that way. Disks don't, because there is potential for hard-wiring > there, and will often be gaps. Why are "certain" devices wildly different than all other ones? I've never encountered that kind of syntax before, and I can't see that it's documented anywhere at all. Certainly, MAKEDEV itself (in it's comments) treats cd* just like all the others, specifying that the number following is a unit number, and *not* a quantity. I don't know when this happened, but it's surely not obvious. Not one word in the handbook, either. In fact, according to cd(4), you *can* specify the unit number: ... Prior to FreeBSD 2.1, the first device found will be attached as cd0 the next, cd1, etc. Beginning in FreeBSD 2.1 it is possible to specify what cd unit a device should come on line as; refer to scsi(4) for details on kernel configura- tion. That makes this odd setup even odder. Can't understand why this was done. > > Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: multiple cd devices (MAKEDEV)
On Fri, 31 Dec 1999, Wilko Bulte wrote: > > > Why are "certain" devices wildly different than all other ones? I've > > > never encountered that kind of syntax before, and I can't see that it's > > > documented anywhere at all. Certainly, MAKEDEV itself (in it's > > > comments) treats cd* just like all the others, specifying that the number > > > following is a unit number, and *not* a quantity. I don't know when this > > > happened, but it's surely not obvious. Not one word in the handbook, > > > either. > > > > *shrug* This is the only rationality I could think of. Obviously, this > > breaks POLA, so it should be changed (with ample warning). > > As for ample warning: I've seen MAKEDEVs display a list of the devices > they are creating. I think the Tru64 version does this. I myself think this > is a good behaviour (and hope people won't start yelling 'bloat' for once) I'd like to hack about a bit on MAKEDEV, but I was wondering, does sysinstall, in any way, use MAKEDEV? I *don't* want to mess with sysinstall! I think the idea of making MAKEDEV print the devices it's creating ought to be easy enough to hack ... Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, 2 Jan 2000, Karl Denninger wrote: > > If you intend to keep up this "sour grapes" attitude, despite all > > the helpful answers you have gotten so far, you should consider > > stopping before you have worn out your welcome. > > > > -- > > Poul-Henning Kamp FreeBSD coreteam member > > > > Yes, the "F-word". > > You have no ability to determine "my welcome". Karl, you've now managed to irritate a lot of folks. Jumping on Steve, who is normally a huge worker, and totally inoffensive, was really pushing things, but then jumping on Poul, who is somewhat easier to touch off, well, you have been just about advertising "I want a fight!", although no one's really given you much reason for it. Poul's response was right, you should come back in a few days, when you've had time to cool off. No one else really wants to keep the fight going. Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Karl's day off
OK, enough of this, let Karl be on his own for a while. Stop responding, Karl's too mad to think clearly, and you guys are just baiting him. Anyone responding is asking for addition to the kill-file. I already posted this to ports, where the other part of this has unfortunately spilled into. I won't post again. -------- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
On Sun, 2 Jan 2000, Amancio Hasty wrote: > I have to say that PHK has become the MASTER at pissing > people off, ensuring that his opponent goes the deep end > and staying calm so the blame obviously does not fall on > him. Got to admit his formula is very very nice 8) > > > By a long shot the problem is NOT Karl. It takes at least > TWO to engage in a combatitive conflict -- that is if > you are not schizophreniac. > > The proper tactic to resolve the conflict should have > been to wait a cool off period and then slug it off > technically. Nevertheless, instead of waiting for > Karl to cool off and attempt to ration with him , > it was much easier to drive him further down: hence > thru censorship the "technical" argument was won > with virtually no technical effort at all -- Like I said > earlier very very nice tactic ! Amancio, you are making assumptions, ones that are completely incorrect here. Karl's frothing started with a lot of raging at Steve on the ports list, and at the entire structure of ports. Poul didn't get into it until quite a bit later, and it was Karl who went after Poul, not vice versa. Poul reacted to someone accusing him of a complete lack of integrity (with no more evidence than McCarthy had in the 50's) merely by asking him to step back a little ways before he really annoyed folks. I wonder if I would react as well? What's more, while you're right that Poul's sometimes been abrasive in the past, his behaviour has been so above reproach here that I felt it necessary to jump in, just to highlight the fact, and maybe to avoid having people jump at the assumption you made (I referenced that directly in my post). I've never met Poul personally, but I *have* met Jonathan Bresler. That last post of Karl's, well, if that doesn't categorize him in your eyes, then I guess nothing will. Believe me, Amancio, Jonathan didn't deserve that. I think everyone really should let this darn thread die Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The mails from dev-null
On Sun, 2 Jan 2000 [EMAIL PROTECTED] wrote: > Congratulations, Karl. You just proven to the world what a complete > asshole you really are. > > Now get out of here. We don't want you. Will whoever this is, please stop? There is no valid reason for anonymity here (and to be honest, in this situation, it rather strikes me as cowardly) and we don't need the sentiments, because you're only going to provoke this further. -------- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
On Sun, 2 Jan 2000, Matthew Dillon wrote: > --> enters stage right > > ... opens door ... > heyy a party! And nobody invited me! > > U, Why's the piano broken in two and all the tables > overturned? Ahhh, whats with all the stares? guys? > Guys! > > exits stage left (at a run) --> > > -Matt Aww, you missed it! We had a broken bottle with your name on it! :-) -------- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No cvs-cur CTM deltas
On Tue, 4 Jan 2000, Peter Jeremy wrote: > The last cvs-cur CTM delta I received was cvs-cur.5961, which arrived > just over 24 hours ago. Is there a problem with the CTM generation? Right. Login problem. Fixed real quick now. > > Peter > -------- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No cvs-cur CTM deltas
On Tue, 4 Jan 2000, Peter Jeremy wrote: > The last cvs-cur CTM delta I received was cvs-cur.5961, which arrived > just over 24 hours ago. Is there a problem with the CTM generation? Fixed that problem (security thing) found another. Still working on it. > > Peter > -------- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
On Mon, 3 Jan 2000, Brian Beattie wrote: > Having read, the first article or so on this subject, I decided that it > had absolutely no merit. However; seeing an article by you I figured that > it would be at least interesting. I was not disapointed. > > Thank you. Please, I know you meant well, but THIS THREAD MUST DIE!!! Please give it a rest! > > Brian Beattie| The only problem with > [EMAIL PROTECTED] | winning the rat race ... > www.aracnet.com/~beattie | in the end you're still a rat > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > ---- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i want to join the mailing list.!
On Tue, 11 Jan 2000, °í¹ü¼® wrote: > how do i.? :) http://www.freebsd.org/support.html#mailing-list ---- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
On Mon, 17 Jan 2000, Kris Kennaway wrote:
> > No, you meant ${RM}
>
> I couldn't find this defined in /usr/share/mk/* - it's only in
> bsd.port.mk, AFAICT.
I'm note sure mine's up to date, where the definition is on line 876 of
bsd.port.mk ... but I'm *sure* it's in there, it has been for ages!
>
> Kris
>
>
> "How many roads must a man walk down, before you call him a man?"
> "Eight!"
> "That was a rhetorical question!"
> "Oh..then, seven!" -- Homer Simpson
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
Chuck Robey| Interests include C & Java programming,
New Year's Resolution: I | electronics, communications, and
will not sphroxify gullible| signal processing.
people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and
fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)|
dictionary.|
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
On Mon, 17 Jan 2000, Kris Kennaway wrote:
> On Tue, 18 Jan 2000, Chuck Robey wrote:
>
> > > > No, you meant ${RM}
> > >
> > > I couldn't find this defined in /usr/share/mk/* - it's only in
> > > bsd.port.mk, AFAICT.
> >
> > I'm note sure mine's up to date, where the definition is on line 876 of
> > bsd.port.mk ... but I'm *sure* it's in there, it has been for ages!
>
> Reread the above. I know it's in bsd.port.mk, but that doesn't help me
> when I'm building in /usr/src/secure/lib/libcrypto ;-)
Oops. Damn.
>
> Kris
>
>
> "How many roads must a man walk down, before you call him a man?"
> "Eight!"
> "That was a rhetorical question!"
> "Oh..then, seven!" -- Homer Simpson
>
>
Chuck Robey| Interests include C & Java programming,
New Year's Resolution: I | electronics, communications, and
will not sphroxify gullible| signal processing.
people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and
fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)|
dictionary.|
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
breakage
Sure would be nice if some folks would start testing before committing. I'm starting to wonder how long it'll be before it builds again. I understand screwups (god know I better!) but if you don't test before commit, that's taking things a step too far. ---- Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
On Fri, 21 Jan 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Chuck Robey >writes: > : I would think using a fixed order would be a really bad thing, causing > : overload of the first server in line. Did I misunderstand you? How about > : doing a script (say in perl, it has random numbers) that randomly picks > : the server from a list? That way, the list could even be weighted, so as > : to allow for greater or lesser machine resources (like net access). > > That's one of the things I have to fix up. This script is good for > me, but bad for everyone. Enhancements like this would be a good > thing. Got time? I don't know perl. Darn. Yes, I will learn perl. Now. > > Warner > -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
On Fri, 21 Jan 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> John Polstra writes: > : > Can you make cvsup accept multiple servers to try in it's configuration > : > file? > : > : I'll add that to the to-do list. > > I have a very crude script that does its own (fixed) round robin of > multiple servers. It tries three times fast (yes, I know that's > likely bad) and then goes to the next one on the list. If all else > fails, it will try the first one on the list in "forever" mode (with > the nice random retries). > > I'll have to see about puitting into good shape and posting it. I would think using a fixed order would be a really bad thing, causing overload of the first server in line. Did I misunderstand you? How about doing a script (say in perl, it has random numbers) that randomly picks the server from a list? That way, the list could even be weighted, so as to allow for greater or lesser machine resources (like net access). ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
On Fri, 21 Jan 2000, David O'Brien wrote: > I have to agree with Amancio. Otherwise how are we to determine if > cvsup8 is worth our time? I personally will not be switching to it until > I can determine it is a better path for me. > > Possibly, being ping'able should be be a requirement to being a CVSup > mirror. I don't know ... I think it might be a good idea for the cvsup client to make a connection to a cvsup master, get redirected from that master to the actual handler of the connection, and then work. That way, a config file on the master could be set up to know the capabilities of the other machines (network availability, machine speed, etc) and dole out connections weighted on that. If a new machine comes on line, no one really needs to know about it except whoever does the config file for the master. Any slave machine, when connected, if it was overloaded, could send the client back to the master with a packet telling the master of the slave's overload condition. A little cryptography would make that hard to cheat on. That way, the master could stay updated on the various slaves conditions (to react to overload). This would need, tho, new clients that would be able to receive a redirection, to work. And, obviously a new master. > > ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: when is FreeBSD-4.0 up for release ?
On Fri, 21 Jan 2000, Will Andrews wrote: > On Fri, Jan 21, 2000 at 03:33:19PM -0800, David O'Brien wrote: > > What do you mean? JKH said there would be a Feature Freeze on Jan 15 and > > it happened. What more did JKH need to say on the topic? > > I lost some mail from early this week, but I didn't get anything from > Jordan saying the FF was in effect. He said it would be in effect > January 15th - not necessarily that it went into effect. > > Perhaps I'm just twisting words a little bit. You really must not have been listening, Will. Jordan did everything *including* falling down laughing at about 3-4 different sets of folks who misinterpreted feature freeze to mean code freeze. I could understand, somewhat, you making that mistake, but missing the fact of the feature freeze itself? I think it was David O'Brien, in fact, who posted it here in 2 inch high letters! No kidding. You must have been hitting the delete key too fast, on several different days. ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
On Fri, 21 Jan 2000, David O'Brien wrote: > On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote: > > I don't know ... I think it might be a good idea for the cvsup client to > > make a connection to a cvsup master, get redirected from that master to > > the actual handler of the connection, and then work. That way, a config > > file on the master could be set up to know the capabilities of the other > > machines (network availability, machine speed, etc) and dole out > > connections weighted on that. > > How is a cvsup master to know anything about the path from me to any > given cvsup mirror? Knowing something about the path from me to the > master and the path from the master to the mirror tells zero about the > path from me to the mirror. > > Being on an .EDU network, I have a *very* different path to other .EDU > machine participating in Inetnet2. My path to cvsup3 is a prime example. > This "cvsup master" will have no idea about this. I guess it means, is the main component trying to be balanced the server resources or the network resources. I may be wrong, but I think that the server resources are more likely to be the most important bottleneck, and this method detects that, with minimal network effects. If you think that it's really the network that's going to be the bottleneck, then you wouldn't want to use this method. I don't think I'm wrong, but I'm willing to listen to arguments on it. > > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2support for distribution patches)
On Sat, 22 Jan 2000, Will Andrews wrote: > On Sun, Jan 23, 2000 at 12:44:46AM +0900, [EMAIL PROTECTED] wrote: > > Truely, I wish to import bzip2 to -current src tree. :) > > Is there a problem about some restriction for distributing bzip2? > > # I'm sorry I don't know about that. > > <2 5003-0> (00-01-22 12:27:37) [will@shadow /usr/ports/archivers/bzip2]% > cat pkg/DESCR > This is bzip2, a advanced block-sorting file compressor. It is > believed to be free from any patents. > > WWW: http://sourceware.cygnus.com/bzip2/ > > Nope - looks like it could be a candidate for importing to the source > tree. However, I'm not sure everyone on current@ is going to agree, > since we already have something for compression (gzip) that is pretty > standard around the world. You guys better understand, having software be legally *able* to be in the source tree is a *very* far way from needing it in the source tree. A very strong case would have to be built that we cannot really do without it. Seeing as gzip fills the requirement with undeniably maximum compatibility, the mere fact that bzip2 compresses smaller doesn't sound like a good reason in of and itself. We would not be able to get rid of gzip anyhow (for compatibility reasons) so we'd end up having to have two tools where one does the job well enough now. A case would have to be built that bzip2 does something critical that cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs is a fine port too, but it'll never get into the base system. > > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2support for distribution patches)
On Sun, 23 Jan 2000, Juergen Lock wrote: > In article <[EMAIL PROTECTED]> you write: > >... > >A case would have to be built that bzip2 does something critical that > >cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs > >is a fine port too, but it'll never get into the base system. > > Very true, but i can actually think of one thing were bzip2 would > really be useful: to better compress the kernel on install floppies > so you could keep more things in it. (like ptys and pass which > would make fixit more useful, or pppoe which was thrown out too > recently if i'm not mistaken.) > > Btw you could probably also kgzip the loader, that would free up > some space too. Juergen Lock: It's Better! Chuck: Better doesn't count, only need, functionality and compatibility. Juergen Lock: It's Better! How come I get the feeling that you didn't read the post? > > Regards, > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches)
On Sun, 23 Jan 2000, David O'Brien wrote: > On Sun, Jan 23, 2000 at 10:26:48AM +0100, Oliver Fromme wrote: > > > > Saving 10% or 20% on disk space is not worth wasting >= 10 times more > > CPU time than gzip. Disk space is cheap nowadays, but upgrading to a > > CPU that is 10 times faster is not. > > And just how do I increase the space on a CDROM??? > Go look how many port distribution files on your last CDROM set were in > bzip2 format -- there is a reason for that. David, no one is arguing if bzip2 is or is not a good tool, nor are they arguing if it's good for ports. The answer to both those arguments is very obviously "yes". The argument was whether, currently, bzip2 should be placed in the source tree for the base system. We *don't* need two compressors, and (again currently) gzip is overwhelmingly more popular at ftp sites than bzip2. Furthermore bzip2 has drawbacks for running on the core system, most especially for small ones. I don't need to go over those, you already know them. Lifting those restrictions is not necessary for the base system, seeing as it would have fatal drawbacks for small systems which would see no help from bzip2 (small systems don't have ports). It is a very good thing to have bzip2 on your system, but it's *not* a requirement. Like I said before, most of the same arguments apply to, say, emacs. You'd have to be nuts (if you ran a good sized system) not to have bzip2, but it's just not a requirement. Having a compressor at all is the requirement, and gzip currently is better for that. Ask me again in 18 months, maybe bzip2 will use less memory and be faster, and it's quite likely that it will be far more popular at ftp sites. > > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2support for distribution patches)
On Sun, 23 Jan 2000, Alex Zepeda wrote: > On Sun, 23 Jan 2000, Chuck Robey wrote: > > > Ask me again in 18 months, maybe bzip2 will use less memory and be > > faster, and it's quite likely that it will be far more popular at ftp > > sites. > > Have you looked at the memory usage when you use the -s flag? No, I said ask me again in 18 months, not NOW. Even if it didn't have the memory problem, gzip has greater compatibility and does the minimum job. It's not required for the base system. It's stupid not to have it in a larger system, but *that's the reason for ports*. Ports are optional, right? > > - alex > > -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
On Mon, 24 Jan 2000, Warner Losh wrote: > Agreed. The making lots of connections was a bad idea. However, I've > rarely seen low latency and low bandwidth go together. I've also > problems connecting accross high loss links more often. Sure, it is a > statistical argument. > > I still think that the n connections wouldn't be that expensive. The > cost, iirc, of a connection that drops is very low. I can certainly > see enough problems with it to encourage jdp to not implement it, > despite being the person that proposed it... That's the precise reason I suggested a system that used no probing, had feedback, and forced shared load in spite of user misconfiguration. Got shouted down. -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
On Mon, 24 Jan 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Chuck Robey
>writes:
> : That's the precise reason I suggested a system that used no probing, had
> : feedback, and forced shared load in spite of user misconfiguration. Got
> : shouted down.
>
> One reason I think that you've been shouted down (and me too, since I
> had similar ideas) is that people in the past have had problems with
> different cvsup servers being at different points in time and have
> been screwed to som eextent or another by this time skew.
Oh. If that's a problem, it would be a fatal problem (would be for me,
sometimes).
>
> There is a large resistance to automatically switching cvsup servers.
>
> It is my perception that the cvsup servers are much better now than
> they were even 6 months ago (well, cvsup{1,2} do seem to be much more
> heavily used than 6,7,8).
>
>
> Warner
>
----
Chuck Robey| Interests include C & Java programming, FreeBSD,
[EMAIL PROTECTED] | electronics, communications, and signal processing.
New Year's Resolution: I will not sphroxify gullible people into looking up
fictitious words in the dictionary.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
On Mon, 24 Jan 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Chuck Robey >writes: > : Oh. If that's a problem, it would be a fatal problem (would be for me, > : sometimes). > > It used to be a big problem. When cvsup was first getting mirrors, > some seemed to update every 15 minutes, while others updated what > seemed like every two days. A big part of the problem was contention > at the main cvsup server. Since cvsup has gone to cvsup-master this > problem has all but disappeared. The mirrors all have good > connectivity and can get updates on a timely basis. [some deletions] > For people updating 2x a day or less often, I doubt that switching > between responding cvsup servers would cause great pain, or any > effects at all. > > It is a hard problem to get right all the time Well, I really hate the idea of lots of network pinging, both because it's not reliable for network probing, not reliable for machine load probing, and causes more congestion, so I wanted a way to force loadsharing, one that allowed some feedback so that real backups could be adjusted to. OTOH, there's no way I will try to fight folks with elephantine memories. I even began looking at Modula-3, seeing if I could offer a diff set to jdp. You know what I realized, and (for some reason) no one in my memory has ever written: modula-3, in features, looks a lot like Java. It's not a stylistic descendant of C like Java is, but featurewise, it is. > > Warner > > ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Possible CTM problem
On Tue, 25 Jan 2000, Peter Jeremy wrote: > Looking at my CTM logs, I seem to be missing some pieces in the last 3 > cvs-cur postings (cvs-cur 6021, 6022, 6023). I get two pieces > simultaneously and then nothing until the next part. Is anyone else > seeing this? Chuck isn't sure if it's anything he's done. > > Looking back, the `first two pieces simultaneously' seems to be the > normal behaviour, but I'd expect to see the 3rd piece 30-60 minutes > later, followed by successive parts every hour. The last delta > with more than 3 parts was cvs-cur.5999 (arrived 18 Jan), so the > problem (if there is one) has occurred since then. If you need to, you can fetch them via ftp. Like I said, I was generating a large amount of extra (very small) deltas while I was testing the upgrade to allow PGP signing, I didn't think I'd caused any lossage, but it's *possible*. I announced on the ctm-announce list that I would be generating those extra deltas. Anyhow, all the testing is over, I'm just waiting on some admin stuff before I start sending the CTM pieces (of deltas, the pieces are the mailed version of the binary gzipped deltas) out. Probably be tomorrow or the next day. > > Peter > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvsup8
What happened, it fell off the edge of the earth? Nslookup can't find it anymore. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup8
On Wed, 26 Jan 2000, Matthew Hunt wrote: > On Wed, Jan 26, 2000 at 01:38:44PM -0500, Chuck Robey wrote: > > > What happened, it fell off the edge of the earth? Nslookup can't find it > > anymore. > > I seem to recall an announcement from John yesterday or so, saying > that it was going to fall off the edge of the earth temporarily. Yeah, now I remember, thanks guys. I'd thought that huge cvsup thread was about 8 coming on line, not going off. > > -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sun, 30 Jan 2000, David Gilbert wrote: > >>>>> "Sean" == Sean O'Connell <[EMAIL PROTECTED]> writes: > > Sean> On 2000 Jan 29, David Gilbert opined: > >> >>>>> "Sean" == Sean O'Connell <[EMAIL PROTECTED]> writes: > >> > Sean> lptcontrol -p > >> I will try this. It still seems that there's a misfeature that it > >> just doesn't work by default. > > Sean> Yep. It is odd that it completely locks your box waiting for > Sean> paper. I have seen other printers which end up printing garbage > Sean> after this but never a locked box. And notice it's not for everyone. I don't know why yours locks up and mine doesn't, but my printer, in the last month, has begun to occaisonally fail to pick up a sheet of paper. It stops the print, but nothing worse than that. I haven't really investigated it, and for me, since I don't see your problem, the fix is a couple of suitably applied alcohol wipes, probably. What I'm saying is, don't start trying to over-generalize your problem. It'll make it harder for you to find, and give FreeBSD an unnecessarily bad rep over that. BTW, that lptcontrol -p means you have something wrong with your parallel interface, because it's not responding to interrupts. This often means you have some IO card you forgot (like a sound card) sitting unbeknownst to you on IRQ 7, messing up the printer. The -p means it just polls the printer to pass in new characters, instead of reacting by interrupt. If the -p thing works for you, I would go looking at hardware, myself. Sheesh. This is a FreeBSD-questions type thing, not current. > > That's a different problem... That problem has something to do with > flow control... and I've had that happen, too. > > Dave. > > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
On Sun, 30 Jan 2000, Brian Somers wrote: > > I'm quite happy to DTRT(tm); I'm unsure that backing this change out > > _is_ the right thing however. Can we discuss it some more first please? > > I think that getflags()/setflags() should stay where they are, but I > can't comment on the namespace pollution issue. If/When the > functions are renamed, they'll probably break make world again > (because the new libc and old install will be there for a while), but > to be honest, this *is* current. > > I think the issue to focus on is the function names. I agree that folks should read current, and be able to do fixes. Do the fix, though, in a way that *doesn't* require yet another fix later on, and post the extraordinary steps clearly here, in a "HEADS-UP" mail that folks will definitely see, and maybe stick something in UPDATING too? At least, give everyone a fair chance, don't embed the fix as the end of a 1,000 words of context email, at the end of a long thread. That wouldn't be fair. Not for extraordinary breakage. ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Wed, 2 Feb 2000, Max Khon wrote: > hi, there! > > On Tue, 1 Feb 2000, Warner Losh wrote: > > > In message <[EMAIL PROTECTED]> Max Khon writes: > > : actually xinstall cannot be built before make world or make buildworld > > : because of undefined symbols `setflags'. > > > > What's the right thing then? > > make buildworld; cd /usr/src/usr.bin/xinstall; make depend all install > and then, make installworld Nope. If buildworld completed right, then only need the make install in xinstall. xinstall will already be built. > > /fjoe > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING - kernel fails to compile
On Sun, 6 Feb 2000, Dan Langille wrote: > After a make -k -DNOFSCHG installworld and a make installworld, I'm > getting this: > > install -c -s -o root -g wheel -m 555 genassym /usr/bin > install: genassym: No such file or directory > *** Error code 71 It's a do-once type of thing, like the xinstall stuff. Go install genassym once, it won't bother you again. It was discussed in the lists, and doesn't affect most build intervals. You got *lucky*. -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING - kernel fails to compile
On Sun, 6 Feb 2000, Dan Langille wrote: > > It's a do-once type of thing, like the xinstall stuff. Go install > > genassym once, it won't bother you again. It was discussed in the > > lists, and doesn't affect most build intervals. You got *lucky*. > > Ahh yes, and it's in UPDATING. my bad. Sorry. > > I tried that. Then did a make installworld. Then I found that conifig > wasn't installed either. so I did a That's ALWAYS true. ALWAYS when building a kernel, make very sure that your config is from the same sources as the kernel. *very* often with current, config changes things, and an old config just won't cut it. That kind of thing doesn't belong in UPDATING, either. I think it's already in the handbook, and an up-to-date config will notice for you when your kernel sources are newer than your config sources, and issue you a warning. ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ifconfig hang
I'm trying to get current up on another test box, and this one has a CNET AX8814 equipped network card. One second after I do a ifconfig: ifconfig dc0 inet (somaddr) netmask (somemask) it hangs. It does this with a completely static kernel (shouldn't be loading any modules), even if I start up in single-user. My config has: device isa device eisa device pci device miibus # MII bus support device dc0 as far as network. My dmesg on the machine shows what I take to be a normal dc0 entry, but something I don't recognize for "amphy0" (I added cariage returns 'cause I know my mailer will do a worse job if I don't): dc0: port 0x6100-0x617f mem 0xf0201000-0xf020107f irq 12 at device 19.0 on pci0 dc0: Ethernet address: 00:80:ad:41:4a:95 miibus0: on dc0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Any idea why my hang might be happening? -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ifconfig hang
On Sun, 6 Feb 2000, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Chuck Robey had to > walk into mine and say: > > > I'm trying to get current up on another test box, > > Who's exact CPU type and hardware configuration must be a state secret, > since you didn't describe them here. > > Come _on_ people, how often do I have to keep harping on this? Don't just > tell me "I have a box." Tell me about it! OK, I'm pasting in the dmesg for this Pentium 120 box. Summarizing, it's a machine with no IDE drives, one NCR controller, one scsi main disk, one scsi cdrom, one vga card, and the CNET controller. Has 128M of RAM. I've been gazing at the mobo, but I can't yet spot who made it, at least not without taking it out and looking on the flip side. Intel processor, AMI bios. But. I don't honestly think it's your problem, Bill. I have the same card on my Alpha, solid as a rock, which is why I stuck the new CNET card to replace the noname NE2000 clone it started with. This was running a 5 year old BSDi, and now I'm trying to get current on it. It doesn't hang until *after* ifconfig has returned, maybe a second later. I have time to hit return a couple times, get a couple of new prompts back; the DDB trace seems to be from the shell. I've duplicated this about 10 times now with no variation, trying little config file changes. I'm trying not to have to hand-copy that darn stack trace; if you can't do without it, I guess I will have to make a null-modem cable and try remote debugging, I sure don't want to type all that stuff in. Outside of doing network stuff, the box seems very stable. I wonder if some module is being loaded that I am not aware of, and that's the source of the hang. If you guys don't trip to this, that's what I'll try next (remote debugging), so if you want, just don't respond, I'll have to get the soldering iron out and make the cable next. == the dmesg === Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Feb 1 00:44:19 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/OEARTH Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 12541 Hz CPU: Pentium/P54C (120.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 126976000 (124000K bytes) Preloaded elf kernel "kernel" at 0xc02e7000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0x3000-0x300f at device 7.1 on pci0 sym0: <825a> port 0x6000-0x60ff mem 0xf020-0xf0200fff,0xf0202000-0xf02020ff irq 15 at device 18.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking dc0: port 0x6100-0x617f mem 0xf0201000-0xf020107f irq 12 at device 19.0 on pci0 dc0: Ethernet address: 00:80:ad:41:4a:95 miibus0: on dc0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vga-pci0: mem 0xf000-0xf01f at device 20.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:da0s1a cd0 at sym0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [319360 x 2048 byte records] da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [ID 20000124.004] "perl in malloc(): warning: recursive call"on
On Mon, 24 Jan 2000, Lars Eggert wrote: > Ilya, > > thanks for the quick response. > > > Signals and Perl do not mix. Please do not use signals if a segfault > > is not a desirable form of output. > > Never? After reading perlipc I was under the impression that using signals > was okay if you keep your handlers simple. I may have to use to another form > of IPC if signals cannot be made safe. Our malloc can't be used in a signal handler. > > Lars > > Lars Eggert <[EMAIL PROTECTED]> Information Sciences Institute > http://www.isi.edu/~larse/ University of Southern California > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [ID 20000124.004] "perl in malloc(): warning: recursive call"on
On Tue, 25 Jan 2000, Ilya Zakharevich wrote: > On Tue, Jan 25, 2000 at 02:44:05PM -0500, Chuck Robey wrote: > > On Mon, 24 Jan 2000, Lars Eggert wrote: > > > > > Ilya, > > > > > > thanks for the quick response. > > > > > > > Signals and Perl do not mix. Please do not use signals if a segfault > > > > is not a desirable form of output. > > > > > > Never? After reading perlipc I was under the impression that using signals > > > was okay if you keep your handlers simple. I may have to use to another form > > > of IPC if signals cannot be made safe. > > > > Our malloc can't be used in a signal handler. > > One can write a signal handler in such a way that no mallocs are going > to be called (see my example). But this would not help: segfaults > will happen anyway. Do you know for a fact that perl, in the signal handler code, is not calling malloc? Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
On Wed, 9 Feb 2000, Matthew Dillon wrote: > > :> a target "overview" into each /usr/ports/*/Makefile to list all available > :> subdiretories. Then, with some other command, one could fetch the > :> current port's directory from the cvs server to install the port. > :> > :> Do these thoughts make any sense? > : > :Yes, this has been desired for some time, but without an actual > :implementation we're kinda stuck. :) > : > :-Alfred > > It's a nice problem to have, I guess :-) I really like the idea of > having a target overview. It would be utterly trivial to have a > module list in the Makefile and to change the dependancies to run > 'make modulename' in the parent directory rather then in the subdirectory > (which might not exist). There's only one person who can make > something like this happen. Flattening out the unecessarily deep ports directory structure would help, too. Probably, 98 percent of it could be done with a script, and it would greatly decrease cvsup time and space. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kdelibs port broken?
On Sat, 26 Feb 2000, Alex Zepeda wrote: > On Fri, 25 Feb 2000, Will Andrews wrote: > > > If you're gonna use a port, use ports for its dependencies too. You'd be > > stupid not to use the ports whenever you can. No one has ever provided > > me a convincing reason why this is not true. > > Well when you want to keep multiple versions of kde or qt around.. and > want to be able to remove them in one fell swoop.. and the "packing > lists" aren't for sure known.. yes it helps to have its own directory. > > For a normal desktop user you're perhaps right. But not using the ports > for some things does not make one stupid, as quite possibly there's a good > reason behind it. Also, for several ports, our ports break build compatibility with any other package of that type. I'm not sure if that's clear ... tcl is a fine example, tho. We break the location of the config files that all tcl packages rely upon to build, for the purpose of allowing folks to run multiple versions simultaneously. Tcl isn't the only one like that, either. Anyone who wants to be able to build other tcl software that isn't derived from a port would be well advised to avoid using our port. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kdelibs port broken?
On Sun, 27 Feb 2000, Daniel O'Connor wrote: > > On 27-Feb-00 Chuck Robey wrote: > > fine example, tho. We break the location of the config files that all > > tcl > > packages rely upon to build, for the purpose of allowing folks to run > > multiple versions simultaneously. Tcl isn't the only one like that, > > either. Anyone who wants to be able to build other tcl software that > > isn't derived from a port would be well advised to avoid using our port. > > This is done because none of those programs/libs developed a system on > their own which allowed multiple versions to be on the same machine OR > made SURE that they where backward compatible.. > > Its not the ports collection thats at fault, the people who did it this > way are cleaning up the mess made by other coders. > > This happens for tcl, gtk, qt.. There are quite a number. (at least 3! ;) Can I ask you, why could this not have been done through a system of symlinks and a little batch-file to switch them? Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD RC-4.0 Issues
On Tue, 15 Feb 2000, Steve wrote: > Steve > Hi > > I Installed a fresh copy of RC-4.0 recently and here are a few more little things I >noticed (these are 'straight out of the box' kind of errors): > > 1. While attempting to add in linux support: > > bash-2.03# make install > ===> Installing for linux_base-6.1 > ===> linux_base-6.1 depends on executable: rpm - not found > ===>Verifying install for rpm in /usr/ports/misc/rpm > ===> Extracting for rpm-2.5.6 > >> Checksum OK for rpm-2.5.6.tar.gz. > ===> rpm-2.5.6 depends on executable: gmake - found > ===> rpm-2.5.6 depends on executable: autoconf - found > ===> rpm-2.5.6 depends on shared library: gdbm.2 - not found > ===>Verifying install for gdbm.2 in /usr/ports/databases/gdbm > ===> Extracting for gdbm-1.8.0 > >> Checksum OK for gdbm-1.8.0.tar.gz. > ===> gdbm-1.8.0 depends on executable: libtool - not found > ===>Verifying install for libtool in /usr/ports/devel/libtool > ===> Building for libtool-1.3.3 > make: don't know how to make ./libtool.m4. Stop > *** Error code 2 > > 2. I installed netscape communicator 4.7 (not the USA one) and I get: > > bash-2.03# ./communicator-4.7 > ld.so failed: Can't find shared library "libXt.so.6.0" That version of netscape seems to want the aout XFree86 stuff. I think a XFree86 binary distribution prepared for FreeBSD 2.X will fix you up nicely. I installed mine in /usr/X11R6/lib/aout. Don't forget to take care of ldconfig, because it makes a big difference when dealing with the old aout stuff. > > > Hope that helps :) This is looking like a kick ass release. > > Steve > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing
On Thu, 17 Feb 2000, Joao Pedras wrote: > eheh > > I mean dead frozen, like if I was watching at a screeshot of a X session ]:) I used to get this on a game, which was trying somehow to load a font that wasn't correct. I found it wasn't really frozen, though, because you *could* telnet in (very slow). Are you *really* sure it's frozen? Do you have a network connection you can test telnet or ping with, or maybe a serial terminal you could hook to it? > > Alfred Perlstein wrote: > > > > Do you mean dead frozen, as in needs a reboot? or frozen for a second or > > so? > > > > The first one I haven't seen recently, the second I have noticed. > > > > -Alfred > > > ^\ /^ > O O > o00-(_)-00o-- > > Common sense is the collection of prejudices acquired by age eighteen. > -- Albert Einstein > > - > PGP key available upon request or may be cut at > http://pedras.webvolution.net/pgpkey.html > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: .gdbinit for kernel
On Fri, 11 Feb 2000, Greg Lehey wrote: > On Thursday, 10 February 2000 at 23:28:14 -0500, Chuck Robey wrote: > > I was wondering if anyone had a .gdbinit that one could use, in remote > > debugging a kernel, that had a working kldstat in it? I found one in > > Greg's vinum directory, but it's a little broken here and there (although > > much of it does work). I want to invoke some of the ddb functions > > remotely, and be able to look at the module status. > > The .gdbinit.kernel in the vinum directory *should* work. If there's > any problem with it, I'll try to fix it. What's the problem? When I try to do a kldstat, it tells me there's no file variable to set. It's too late now, I gotta go, but if you wait until I get home tomorrow, I'll give you the exact error. I'm doing remote debugging into another current box. I really appreciate the work you went to, to create that tool to begin with; it oughta be pointed to by some README, don't you think? Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kdelibs port broken?
On Mon, 28 Feb 2000, Daniel O'Connor wrote: > > On 27-Feb-00 Chuck Robey wrote: > > > This happens for tcl, gtk, qt.. There are quite a number. (at least 3! ;) > > Can I ask you, why could this not have been done through a system of > > symlinks and a little batch-file to switch them? > > How could you run multiple applications which use different versions of the > same library? A lot of them have support files which are loaded by the > library when ITs loaded by the app. You would end up with all sorts of nasty > race conditions when people run multiple apps etc.. The config files that I would be controlling aren't used during program runtime, only during build. The stuff would link just as it is now, but you'd use a short "versioning" script to set up the config file symlinks, so that if you wanted to build a app that wasn't a FreeBSD port, it would find it's correct config file, right where it expects to find it. Some stuff, like tclsh, could have a default link, say from tclsh to tclsh8.2, or allow a user to set that. That could be a local option, but it's icing on the cake as far as I'm concerned. The only real thing I would be after is the ability to stick the config file locations in the places that the original developers (and the configuration scripts they build with) expect them to be. Anything done as far as executeable names, I don't really care too much about. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: which(1), rewritten in C?
On Thu, 2 Mar 2000, Alfred Perlstein wrote: > * Dan Papasian <[EMAIL PROTECTED]> [000302 18:17] wrote: > > While this may sound crazy, I was tired of 'which' taking a long > > time to complete on my 486 dx4/100 when it was under extereme > > pressure, so I rewrote it in C :) > > > > ...snip > > > NOTE: > > This version of which has exactly the same behavior. > > Also, the above test was not performed when the box was > > under load.. and on slower machines/under load, the > > differences are of course, more noticable. > > You may all go ahead and call me crazy now. > > > > ...I've got the fear of posting the source, but what the heck, > > getting nitpicked is good education :) > > > > http://bugg.strangled.net/which.c > > > > Any flames^Wthoughts? > > It doesn't seem to handle multiple arguments. File a PR and fix > the issues and I'll look at getting it into post 4.0. Hey Alfred, what Perl program is he talking about? Which is a builtin for csh and tcsh (my shells). Or is he talking about some other 'which'? > > -Alfred > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: which(1), rewritten in C?
On Thu, 2 Mar 2000, Laurence Berland wrote: > Which is also a perl script, which sh uses (since it's not a builtin > there). It does the same thing as the which that's built in to bash and > tcsh and csh Oh, then it does it dynamically? That must be why it's slow. OK, thanks. > > Chuck Robey wrote: > > > > On Thu, 2 Mar 2000, Alfred Perlstein wrote: > > > > > * Dan Papasian <[EMAIL PROTECTED]> [000302 18:17] wrote: > > > > While this may sound crazy, I was tired of 'which' taking a long > > > > time to complete on my 486 dx4/100 when it was under extereme > > > > pressure, so I rewrote it in C :) > > > > > > > > > > ...snip > > > > > > > NOTE: > > > > This version of which has exactly the same behavior. > > > > Also, the above test was not performed when the box was > > > > under load.. and on slower machines/under load, the > > > > differences are of course, more noticable. > > > > You may all go ahead and call me crazy now. > > > > > > > > ...I've got the fear of posting the source, but what the heck, > > > > getting nitpicked is good education :) > > > > > > > > http://bugg.strangled.net/which.c > > > > > > > > Any flames^Wthoughts? > > > > > > It doesn't seem to handle multiple arguments. File a PR and fix > > > the issues and I'll look at getting it into post 4.0. > > > > Hey Alfred, what Perl program is he talking about? Which is a builtin for > > csh and tcsh (my shells). Or is he talking about some other 'which'? > > > > > > > > -Alfred > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > Chuck Robey| Interests include C & Java programming, FreeBSD, > > [EMAIL PROTECTED] | electronics, communications, and signal processing. > > > > New Year's Resolution: I will not sphroxify gullible people into looking up > > fictitious words in the dictionary. > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM deltas
On Sat, 11 Mar 2000 [EMAIL PROTECTED] wrote: > The latest CTM delta for -CURRENT on ftp.freebsd.org is 4257 (March > 6). Because all of the mirrors for CTM are in countries other than the US, > would there be any differences between the deltas they have and the ones > that ftp.freebsd.org should have? (I don't understand this crypto thing > all too well.) Also, is there some reason that CTM deltas aren't on the > FTP servers? The deltas stop at 4257 on one of the mirrors in Taiwan too, > and I can't contact either of the other two Taiwanese mirrors or the South > African mirror listed on http://www.freebsd.org/handbook/mirrors-ctm.html > (the one in Germany is fine, and has all the deltas through 4265 at this > point). So many points to address here ... 1) please, bring ctm problems to the attention of [EMAIL PROTECTED] If you think they are general in nature, you can use ctm-announce, which is a public list. Don't use current, they're mostly uninterested in CTM stuff. 2) Archive site has changed, try ftp.freesoftware.com. You *should* have read that on logging into ftp.freebsd.org. 3) I don't see the numbers you see. On current, the latest delta is cvs-cur.6161.gz. I checked the src-3 one also, in case you maybe meant that, it's also a long way off of 4257. I think you must have your numbers messed up; please recheck them. 4) As long as you're not talking about Mark Murray's CTM of int'l crypto, there's only *one* source of ctm deltas, and I'm it. They are all now signed with GNU's gpg, and any you get are identically the same. Doesn't matter where you pick them up from. Most folks get them from the mailing lists from [EMAIL PROTECTED] 5) Just checked with the new ftp site; ftp.freesoftware.com isn't correctly mirroring ctm deltas. The other sites are OK. I'll get right on that, thanks for pointing me at it. The last ctm delta that ftp.freesoftware.com has is a week or two old: cvs-cur.6147.gz. Any more questions, send them to [EMAIL PROTECTED], not this list. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNP ids missing in sio.c
On Sat, 4 Sep 1999, Doug Rabson wrote: > On Fri, 3 Sep 1999, Steve Price wrote: > > > Can anyone think of a good reason why I can't migrate the > > old PNP ids to the new sio.c? I just rebooted my box with > > a fresh kernel and much to my shagrin (sp?) my USR PNP > > modem didn't work anymore. The following patch got it > > working again. > > The reason I didn't move the old ids wholesale is that the old system > matched against the vendor id (which is bogus for multifunction cards). > The new system matches with the logical device id which is often different > from the vendor id. Some simple single function cards use the same id for > both (as yours does) but I can't tell this without seeing the pnpinfo > output. > > > > > Now that we can't use the pnp command from 'boot -c', what > > has (if anything) replaced it? I seem to be remember this > > being discussed recently but I'll be darned if I can find > > it in the mailing list archives. > > The pnp command should no longer be needed (crossed fingers) since the new > code automatically detects devices and assigns resources to them. Does the sio driver know about PCI? Can it run PCI sio cards, like those sold by SIIG? > > -- > Doug Rabson Mail: [EMAIL PROTECTED] > Nonlinear Systems Ltd.Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > ---+--- Chuck Robey| Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770| picnic.mat.net: FreeBSD/i386 (301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha ---+--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make update
My make update isn't working anymore, and I can't figure out why. I know the recent stuff regarding Id->FreeBSD, and I've closely watched all the files that Doug talked about, and they're all the way he said they should be, but after I get done with the cvsup part of make update, and it looks to be real near the end of the "cvs -q update -d -P", it dies, no core. I have gone in afterwards and tried to do a cvs update without the -q flag so I could spot just where it was failing, but (and this astonished me) it always works when I invoke it directly (not via make). I am using the same cwd, and I've tried the manual cvs update with and without the -q flag, it always works without the makefile, and always fails as part of make update. I've checked Makefile, Makefile.inc0 and Makefile.inc1, they're all in fine condition (cvs diff shows no problems). Any idea why this should be so? ---+--- Chuck Robey| Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, Unix and 213 Lakeside Drive Apt T-1 | carpentry. It's all in the design! Greenbelt, MD 20770| picnic.mat.net: FreeBSD/i386 (301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha ---+--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with cvs-cur 5642
On Mon, 13 Sep 1999, Peter Jeremy wrote: > This is a bit old because I'm still catching up on a mail backlog... > > Last Wednesday, CTM reported: > > 1999-09-08 09:05 checksum: read 31757, calculated 6124 > 1999-09-08 09:05 cvs-cur.5642.gz 8/8 discarded > > I've had a look at the piece in question and there's nothing obviously > wrong with it. Later updates have arrived OK. Has anyone else seen > this? One other user reported this, but it was already drained out of the short time spool here, so I couldn't give him just the little part he wanted. He was able to get the whole ~500K delta via ftp and go on, so I guess that I'd ask you to do the same. But let me know if that isn't doing it for you. ---+--- Chuck Robey| Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, Unix and 213 Lakeside Drive Apt T-1 | carpentry. It's all in the design! Greenbelt, MD 20770| picnic.mat.net: FreeBSD/i386 (301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha ---+--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ports/13729: strip(1) exits with an error on script file - causessevere portability problems
On Mon, 13 Sep 1999 [EMAIL PROTECTED] wrote: This kind of thing, where there is no bug ... where the subject is a request for a new feature, isn't this kind of thing the wrong way for folks to be using the trouble reporting system? Or is this the way we want it to happen? It seems to me that allowing such use of gnats makes it miserably hard for folks to close some PRs. > > >Number: 13729 > >Category: ports > >Synopsis: strip(1) exits with an error on script file - causes severe >portability problems > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible:freebsd-ports > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon Sep 13 09:30:01 PDT 1999 > >Closed-Date: > >Last-Modified: > >Originator: Patrick Powell > >Release:3.2-Release, 4-Current > >Organization: > Astart Technologies > >Environment: > >Description: > strip(1) fails with an error when asked to strip shell > scripts. This behavior is documented as follows: > > DESCRIPTION >GNU strip discards all symbols from the object files >objfile. The list of object files may include archives. >At least one object file must be given. > > >strip modifies the files named in its argument, rather >than writing modified copies under different names. > > In many install scripts for code you have: > $(INSTALL) -s > ^^^ -s specified for ALL installable executable > objects including perl scripts, shell, scripts, > etc. > > > This requires a huge amount of effort when porting to FreeBSD because > you now have to determine which executables can or cannot be stripped. > > I strongly recommend you do a test in the strip code for ALLOWABLE > magic numbers, strip those, and ignore the rest.I > >How-To-Repeat: > strip a shell script - you get an error. > More seri > >Fix: > 1. modify man page to indicate that strip only works on object > files or executable files, and ignores others > 2. modify action so that it checks to see if it has an allowable > item to strip and then does it. > > In the strip code, find the place where it checks for 'magic numbers' > of allowable executables, and rather than exiting with a non-zero > error code, simply exit with a 0 error code or continue to the > next file to strip. > > >Release-Note: > >Audit-Trail: > >Unformatted: > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-ports" in the body of the message > ---+--- Chuck Robey| Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, Unix and 213 Lakeside Drive Apt T-1 | carpentry. It's all in the design! Greenbelt, MD 20770| picnic.mat.net: FreeBSD/i386 (301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha ---+--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loss of Functionality with newpnp
On Sun, 26 Sep 1999, Mike Smith wrote: > > This is only partially related, but I still can't even boot a kernel with > > the pnp0 controller enabled. It just hangs after probing the soundcard. > > You seem to have accidentally deleted all of the details related to > this bug report from your email before sending it. Please try again. Mike, I'm checking into this on my own, so this isn't a question, but you might want to know that I have a Turtle Beach PCI audio card, setup with controller pnp0 and device pcm0, and getting about the same responses. Things have stopped working (the mixer totally). This is just data if you wanted it. I can see the answer isn't laying at your fingertips, so I will continue to read code. > ---- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Linux emulation
I just tried to use my copy of WordPerfect 8 to decode an rtf document, like I've done before the signal change, and boy was I surprised. The machine locked up for 10 seconds, then spontaneously rebooted. Anyone else have this experience with Linux emulation? Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
COMMAND_SET ?
I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled, and I found something called a COMMAND_SET, and I can't figure out what it means. Any takers? -------- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The eventual fate of BLOCK devices.
On Tue, 12 Oct 1999, David Scheidt wrote: > On Tue, 12 Oct 1999, Kirk McKusick wrote: > > > I would like to take a step back from the debate for a moment and > > ask the bigger question: How many real-world applications actually > > use the block device interface? I know of none whatsoever. All the > > filesystem utilities go out of their way to avoid the block device > > and use the raw interface. Does anyone on this list know of any > > programs that need/want the block interface? If there are none, or > > It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated > disk devices. There may be other RDBMSes that do this. Informix, should a miracle occur and they decide to suport FreeBSD, definitely want the same. ---- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The eventual fate of BLOCK devices.
On Tue, 12 Oct 1999, Warner Losh wrote: > In message <[EMAIL PROTECTED]> David >Scheidt writes: > : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated > : disk devices. There may be other RDBMSes that do this. > > EVERY RDBMS that I've ever seen or had to make work with my drivers > has been on the raw partition. This is because the database writers > DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic > nature of disk writing. Are you sure that Sybase uses BLOCK devices > and not CHAR devices? Gawd, now that I think of it, about my Informix post, you're right, they use a raw partition, and their own buffering. > > Warner > > -------- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation broken..
On Thu, 14 Oct 1999, Kenneth Wayne Culver wrote: > This is weird, I use linux netscape and word perfect all the time, and the > only problems I see are memory leaks I knew were there (in the > applications, not FreeBSD) > I had equal problems a little while back. Make sure you have the linux_base port installed, it has a far more up to date set of libs. > > On Thu, 14 Oct 1999, Marc van Woerkom wrote: > > > > (im)perfect. I was using the linux version of netscape, until > > > recently when it began hanging for long periods of time during > > > network or disk activity. > > > > Calling up linux-netscape-4.61 causes my system to freeze for a > > couple of seconds, then it reboots. > > > > This is either related to some recent changes, or my system being > > not in a consistent state. > > > > Regards, > > Marc > > > > > > 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 > Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
call graph
I was wondering, is there any way to get a call-graph of the startup of FreeBSD (current) up until, say, the end of signle-user startup? One annotated with file/line info regarding funciton location? Not a line by line thing, but function call by function call? I was wondering if maybe there could be such a thing arising from the profiling code, or something like that. Sure would do me a *whole* lot of good, if I could get such a thing. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
On Sat, 23 Oct 1999, Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. > > I don't think any of the authors would mind if it went into /usr/games, > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. > > I've included the docs below. Remembering from ancient history, didn't this make the rounds to just about anyone who wanted to learn code? I think it was even in a DEC games book. I think putting this into games is safe, but there's another trek in games already ... I haven't played trek in a looong time, is this one better in some way than the one already there? If it doesn't get into /usr/games, anyhow, it can certainly go into ports. ---- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
lsof broken
It's broken trying to work with the name cache, and dies because it can't find the name NCACHE. Where is this guy? -------- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation broken.. (solution)
On Mon, 25 Oct 1999, Chris Csanady wrote: > > I *know* someone else said it wasn't so, but just 3 weeks ago I had this > > very problem, with word perfect, and it works just fine now. Are you sure > > you have a really up to date linux_base port installed? It was recently > > changed, a *lot* of new libs added, and I'd really like an answer on this, > > whether I'm right or wrong. > > Well, I found a solution to my problems with running linux-netscape and word > perfect. It looks like it was not the linux emulation code that was at fault. > > I recently installed a real redhat 6.1, and mounted it on /compat/linux. Now > all is well--so I can only assume it is some weird interaction between the > linux_base port and my system. Maybe it is related to using XFree86 3.9.15, > but I don't have the time to test that theory right now. > > Certainly not a great solution, but if things are broke for you this at least > works. No, like I said, when I *really* updated my Linux libs (and the linux_base port had very newly updated libs when I posted this) my problems evaporated, which is why I urged others to do it. I don't know why it didn't work for you, but at least it's done for you now. > > Chris Csanady > Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
lsof + namecache
Lsof is broken. It looks like it was broken because of a commit that PHK did, on namei.h, which removed the definition of the namecache struct from public visibility. According to the comments, the commit was the first part of some larger plan, but I don't see what it is. It's been 3 weeks now since the commit. I already wrote Poul about it, but he hasn't seen my email yet, I guess. Does anyone know the direction this was going in, and what visibility the namecache is intended to have? -------- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM-deltas generation sptopped ?
On Thu, 4 Nov 1999, Peter Jeremy wrote: > On 1999-Nov-03 23:58:00 +1100, [EMAIL PROTECTED] wrote: > > There are no new CTM-deltas on 'ctm.freebsd.org' > >at least 22 hours. > > The last e-mail delta I have is cvs-cur.5804, which arrived here at > 0808UTC (about 5 hours before your message). I would have expected to > receive 5805 (or at least an initial part) about 5 hours ago now, so I > suspect something is wrong. I stopped reading the list for a few days (letting my mail pile up) while I handled a panic situation at the University, sorry. I can't traceroute or ping the source of ctm's, and I have mail out to the owner of the system. Now that I'm aware, I will follow this as fast as I can. > > Peter > ---- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM-deltas generation sptopped ?
On Fri, 5 Nov 1999, Chuck Robey wrote: > On Thu, 4 Nov 1999, Peter Jeremy wrote: > > > On 1999-Nov-03 23:58:00 +1100, [EMAIL PROTECTED] wrote: > > > There are no new CTM-deltas on 'ctm.freebsd.org' > > >at least 22 hours. > > > > The last e-mail delta I have is cvs-cur.5804, which arrived here at > > 0808UTC (about 5 hours before your message). I would have expected to > > receive 5805 (or at least an initial part) about 5 hours ago now, so I > > suspect something is wrong. > > I stopped reading the list for a few days (letting my mail pile up) while > I handled a panic situation at the University, sorry. I can't traceroute > or ping the source of ctm's, and I have mail out to the owner of the > system. > > Now that I'm aware, I will follow this as fast as I can. Replying to my own mail, I want to give an update: the machine that generates ctm has crashed, and the vinum volume doesn't fsck cleanly on startup. It's not a disaster, this can all be fixed, nothing critical *could* have been lost, because I've copies of everything critical right here. The likelihood, tho, is that it'll be a couple days at least until ctm comes back up, because I think I'm going to have to recreate it. Be patient, I'll announce when it gets back up. Oh, yeah, anoncvs is down too, same reasons, same response. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mount problems after lockup
On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > > It is really a good idea to read the current mailing list > if you run current on your machine. > > copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate > your disk devices. > > Poul-Henning Excuse me, Poul, I have to switch back and forth for a day on one machine, can I run MAKEDEV to prepare for the new devs without ruining the system for a kernel that's about 4 months old? [No, it's not my machine, I run current -- real current]. -------- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mount problems after lockup
On Mon, 6 Dec 1999, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Chuck Rob > ey writes: > >On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > > > >> > >> It is really a good idea to read the current mailing list > >> if you run current on your machine. > >> > >> copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate > >> your disk devices. > >> > >> Poul-Henning > > > >Excuse me, Poul, I have to switch back and forth for a day on one machine, > >can I run MAKEDEV to prepare for the new devs without ruining the system > >for a kernel that's about 4 months old? > > No, 4 months is too old. Then if I have to do this in multiple steps, can I upgrade to current as it was before you changed out the bdevs-cdevs (I'll hunt down the commit) and do that in one step, get it working, then MAKEDEV and do another step taking it the rest of the way to current? I don't want to move it with no ability to fall back on an old kernel, as I step it towards current. > > -- > 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 > Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
On Thu, 9 Dec 1999, Daniel C. Sobral wrote: > Motoyuki Konno wrote: > > > > I think we don't need "a.out world" any more, but a.out support > > (a.out lib/shared lib, etc.) is still needed. Some commercial > > programs such as Netscape are in a.out only, so we still have to > > make a.out binaries. > > > > Please see Netscape plugin port (ports/www/flashplugin) to find > > out why we still have to need a.out support. > > Current is not a general use platform. And if we want them (third > party) to support FreeBSD-elf by the time 4.x becomes -stable, we > better lock them out of it *now*. > > The main reason for removing the legacy support is forcing people to > switch. This isn't taking the execution of aout binaries out, just stopping a world build. This is only going to stop 3rd party developers from making a 4.0 aout platform to create *more* aout binaries. They'll probably hang on for dear life on 2.2, just as long as they can. Looking at copious examples from real life, forcing 3rd party developers to upgrade is a good way to lose 3rd party developers. It just *sounds* like a good way to go. As long as this is a change for building world, and not making changes to the kern/imgact things (so we keep on executing aout binaries) then this is probably the best way to go. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
On Fri, 10 Dec 1999, Daniel C. Sobral wrote: > What Motoyuki-san is complaining about is that applications that > depend on a.out libraries will suffer. Alas, I don't think that's > the case, since all these libraries are (or ought to be, anyway) in > compat. > > > Looking at copious examples from real life, forcing 3rd party developers > > to upgrade is a good way to lose 3rd party developers. It just *sounds* > > like a good way to go. As long as this is a change for building world, > > and not making changes to the kern/imgact things (so we keep on executing > > aout binaries) then this is probably the best way to go. > > OTOH, going the other way around is the reason why we (users) had to > deal with things like 1 Mb RAM and 64 Kb segments in the age of > 486s, one generation after the introduction of the 80386. As a free > operating system supported by volunteer effort, we are interested in > driving the hardware to it's limits instead of being limited by the > ways we once did things. Absolutely, but (here's the caveat) if it *doesn't* hold up any new development, and there's a significant base of users actually deriving benefit from it, then I wouldn't agree. I'm kinda binary about that test, because I fully agree that, if it holds up technology in a project like ours, it's out the door! Stopping the new aout world builds doesn't injure users of aout software, it only *really* strongly discourages new development in aout. I think it just needed to be emphasized that the aout imgact stuff isn't being tossed, so aout executables will still work (those that aren't otherwise incompatible). Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux /proc and vmware.
On Thu, 16 Dec 1999, Andrew Gallatin wrote: > > Julian Elischer writes: > > > > might I suggest that we make a decision to allow procfs to be mounted with > > a -linux flag and act more like the linux programs expect.? > > (particularly we could mount it at /compat/linux/proc with the -linux > > flag). > > > > That would be wonderful. > > I'd also like to see us have enough information in /proc to be able to > divorce ps & friends from libkvm. It would be nice to be able to have > most tools continue to work if you have mismatched kernels & > userlands. I thought the work was going in precisely the opposite way, so that jail could work without any visibility to /proc. ---- Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
On Thu, 23 Mar 2000, Kris Kennaway wrote: > Any objections to the following? I don't mind at all ... I was wondering about just taking out the ability to even USE -O2 in the compiler, but there're probably *some* non-kernel related reasons for using it, and we shouldn't block it at that point. Not for FreeBSD, but for some users doing their own code on FreeBSD. > > Index: make.conf > === > RCS file: /home/ncvs/src/etc/defaults/make.conf,v > retrieving revision 1.101 > diff -u -u -r1.101 make.conf > --- make.conf 2000/03/22 00:49:20 1.101 > +++ make.conf 2000/03/23 23:33:13 > @@ -9,7 +9,13 @@ > # You have to find the things you can put here in the Makefiles and > # documentation of the source tree. > # > -# One, and probably the most common, use could be: > +# CFLAGS controls the compiler settings used when compiling C code. > +# Note that optimisation settings above -O (-O2, ...) are not recommended > +# or supported for compiling the world or the kernel - please revert any > +# nonstandard optimisation settings to "-O" before submitting bug reports > +# to the developers. > +# Note also that at this time the -O2 setting is known to produce BROKEN > +# CODE on the Alpha platform. > # > #CFLAGS= -O -pipe > # > > > 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 > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Wed, 29 Mar 2000, Matthew Dillon wrote: > time make -j 20 buildworldbuild FreeBSD-current using 4.0 kernel > > 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w > > time make -j 20 buildworldbuild FreeBSD-current using 5.0 kernel > > 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w > > Difference: 19 minutes, or a 21% improvement. Bob Bishop got 7% with an > earlier patch (hopefully his system is no longer locking up and he can > repeat his test with the current stuff). Goddamn. That's significant! Congratulations, Matt. Did it again! -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: > Are there any plans to merge perl-5.6.0 into current? I don't have any > plans for using it currently, but I curious. Hmm. What with the nightmarish build structure of perl, I'm sure that reading this is just going to wreck Mark's day. In light of that, and in the absence of both any real software that needs the upgrade, and lack of confidence in a really squeaky new release, why don't we all grant Mark a little slack on this, at least for a while. Else we're going to have a drooling Mark on our hands :-) Unless, of course, you want to do it *for* Mark? > > Thanks, > > Tom Veldhouse > [EMAIL PROTECTED] > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
On Mon, 3 Apr 2000, Christopher Masto wrote: > On Sun, Apr 02, 2000 at 05:56:22PM -0400, Chuck Robey wrote: > > On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: > > > > > Are there any plans to merge perl-5.6.0 into current? I don't have any > > > plans for using it currently, but I curious. > > > > Hmm. What with the nightmarish build structure of perl, I'm sure that > > reading this is just going to wreck Mark's day. In light of that, and in > > the absence of both any real software that needs the upgrade, and > > lack of confidence in a really squeaky new release, why don't we all grant > > Mark a little slack on this, at least for a while. > > I've been running Perl 5 since before it was included with FreeBSD, and > I've never noticed anything nightmarish about the build process. I > tried 5.6 a couple of days ago, and it built and tested out of the > box. It's the way that perl builds itself. Isn't perl the only thing we build that *doesn't* use make alone to guide the build process? Isn't perl the only thing in the tree that uses itself to build it's manpages? Have you looked at the make files for perl, say the one in gnu/usr.bin/perl/perl? It works *real* slickly, but it sure wouldn't have been easy to piece together. Maybe you misinterpreted what I said to mean "the build is screwed up". I think the job done was great, but I wouldn't want to get the job of modifying it, say moving it's local library location. > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installworld to /some/where/...
On Thu, 6 Apr 2000, Yu Guo/PEK/Lotus wrote: > > Just do a > make DESTDIR=/mnt/installdir installworld > Or remotely mount /usr/obj and /usr/src, and do 15 make installworlds on 15 machines. In fact, I'm not totally sure that first method works, because I think that perl, at least, records the name of DESTDIR during the 'make buildworld' so moving DESTDIR only in installworld, that might bomb later when you ran it. In fact, I think that will happen, and to cc1 (of gcc) also, because the 'specs' get set during buildworld, don't they? The above would only be safe, I think, if you did the make buildworld with the same DESTDIR. Anyone know if that's true? > > Hi, > > Is it possible to do an installworld not to / of existing system, but to, > say, subdirs somewhere, which could be mountpoints for another disk? > Something like: > > /mnt/installdir/ > /mnt/installdir/compat > /mnt/installdir/etc > /mnt/installdir/usr > /mnt/installdir/var > /mnt/installdir/ > > The reason I'm asking is that I'm looking for a method to easily > clone/upgrade a bunch of servers without having to do 'make world' on all > of them. I'm not satisfied either with using dd - the machines are not > identical, there are some bits and pieces of config specific to each > machine. So far the best method was to do a make world, but it becomes > more and more a nuisance and waste of time... > > > Andrzej Bialecki > > // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) > // --- > // -- FreeBSD: The Power to Serve. http://www.freebsd.org > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ > > > > > 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 > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Fri, 14 Apr 2000, Joe Greco wrote: > > In other words, if we're going to be replacing sendmail with an > > alternative MTA, I'd prefer postfix over qmail, and I believe I can > > marshall some pretty strong arguments for that position. > > Perhaps it's time to revisit something I proposed several years ago. > > Remove Sendmail from the base system - or, at least, make it a "package" > that is removable with the package management tool. Then be able to add > another mailer (or an updated Sendmail) in its place. Ideally, Sendmail > would be available as a package for installation as part of the base > system, just like games or info or proflibs. > > I would love to see this happen with other components of the system as > well, such as BIND. > > While it is fantastic that FreeBSD comes out of the box so fully > functional, it does make it a bit of a pain for those of us who intend > to build servers - we have to disable the original before installing a > new package. :-/ I always keep hearing the same line. You guys *know* perfectly well how to do it, and it's not a big thing to you, you even admit it's only "a bit of a pain". To most of the rest of the world, it's a huge thing, and they don't have the least clue how to do it. If you guys want so desperately to make things 1% easier, why have I never seen anyone bring out a parallel "sparse" FreeBSD? It wouldnt' be a large thing to do, and you who keep on asking for it, you know that very well. Just have a reasonable bit of compassion for everyone else. That's not to say the huge hurt it would do to FreeBSD to all reviewers and the public at large, just to save you "a bit of a pain". > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: > Uh, Chuck, can you tell me how many BIND and Sendmail advisories there have > been in the last five years? > > Wouldn't it be nice if we could just tell newbies, "hey, yeah, that Sendmail > has a known security issue, pkg_delete it and then add this new one here". > Or would you prefer to explain to someone who doesn't "have the least clue > how to do it" how to upgrade BIND and Sendmail to the latest? > > The concept is beneficial from _many_ angles, not just the one I gave. > > Despite my tendency to promote the traditional BSD distribution style, that > does not mean that I feel that everything in FreeBSD should arrive as it did > on the 4.4BSD tape. I think that the ability to be able to select modules > for inclusion or exclusion would be particularly useful. If you want to pick another one and by default install that, fine. If you want to force new users to read all about mailers just to get their first mail working, no, that's just too much, Joe, you're asking too much of folks. If you've got a bone to pick with sendmail, that's ok, but you have to pick a better one. If you can't decide on the best one, then how in the heck do you expect Joe Public to do better? ALWAYS provide sensible default values, not a bunch of expert questions. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: > Chuck, > > Please go back and read what I _wrote_. Your response assumes I made I've got your message, I quoted it fully in my first response. You asked to "Remove Sendmail from the base system", and that's a direct quote, Joe. > statements that I certainly did not, and suggests to me that you missed > every third word in my previous messages. :-( In particular, I advocated > including Sendmail in the base system in a manner that would allow it to > be trivially removed (or, alternatively, not including it but making it > a selectable package, like X11). No, you said remove it, or at least make it removeable. I responded that you can't just remove it. Go to your sent mail message folder, I'm not making this up. I said don't remove it (not "don't make it removeable"). You're the one who's sticking new words in. > This could, for example, be done in the very same way that we currently > do loads of other crap, like /usr/games, proflibs, etc. More ideally, it > would be done in a format compatible with the package management system, > so that one could simply "pkg_delete" Sendmail and install a new one. > > Am I getting through now? :-) You asked in your mail to remove it, I said you can't leave ordinary users without a good default. Your context in what you said was that it was a minor pain to have to remove the default mailer. I stand by what I said. You changed your message, and if you want, I can send your message back to you. If you argue *only* that some easier method be arranged so that mailers can be swapped out, that I fully approve of. I never said otherwise, and I don't like much the way you changed things. In fact, what the heck, here's your original message, cut out of my reply (where I quoted all of your part of the exchange): > Perhaps it's time to revisit something I proposed several years ago. > > Remove Sendmail from the base system - or, at least, make it a "package" > that is removable with the package management tool. Then be able to add > another mailer (or an updated Sendmail) in its place. Ideally, Sendmail > would be available as a package for installation as part of the base > system, just like games or info or proflibs. > > I would love to see this happen with other components of the system as > well, such as BIND. > > While it is fantastic that FreeBSD comes out of the box so fully > functional, it does make it a bit of a pain for those of us who intend > to build servers - we have to disable the original before installing a > new package. :-/ > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup crash
On Wed, 19 Apr 2000, Alexander N. Kabaev wrote: > Actually, it seems that Java borrowed a whole lot of ideas from Modula-3. And > C++ experience can even hurt instead helping when switching to Java. Java > inherits some parts of C++ syntax but is based on rather different design. That statement, about "C++ experience can even hurt instead helping when switching to Java" is pretty specious. I've heard it said that knowing C ruins you for learning C++, and your statement holds about the same amount of water. If you think the latter is right, you might believe the former, but I sure don't buy it, it sounds awfully conceited. C++ and Java are *quite* similar. There are differences, and personally, I think Java is quite a bit better for them, but they aren't based on radically different designs, and quite often, code parts will look identical. Yes, there are differences, and Yes, some of those differences are major, but they are from the same tree, and knowing C++ isn't going to hurt you one bit in learning Java ... it'll just make you appreciate Java all the more. One think I like about Modula-3, I have to agree, is that it has some of the nicer features or Java. I think interfaces are great, and I have very dire opinions about the quality of most template code (from C++). ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone have OpenSSH + X11-fwd working?
On Fri, 21 Apr 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Andrew Reilly" writes: > : Have you got "X11Forwarding yes" > > Ahem. "ForwardX11 yes" is what's documented and is known to work. While this whole thing is being discussed, does anyone know of either a configuration variable or environmental variable that ssh reads, that will give the same effect as the -q flag, so that I can stop seeing those stupid warnings about the size of the key being off by one? Thanks. ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Archive pruning
I want to bring up a suggestion. I just want a little bit of argument on it ... and if you're violently opposed, just say so, that's fine. I want to suggest that, once a year, we go thru the cvs archive, and prune away all history more than 3 (or maybe 2, maybe 4) years old. This could be done without too much pain, I think, in a script. The purpose is to put some kind of cap on growth of the FreeBSD source archive. While folks do sometimes go hunting for hugely old materials in the tree, I normally couldn't care less (when browsing) about history that old. Do we really need 5 year old history? -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Mon, 24 Apr 2000, David O'Brien wrote: > On Mon, Apr 24, 2000 at 08:15:45PM -0400, Chuck Robey wrote: > > I want to bring up a suggestion. I just want a little bit of argument on > > it ... and if you're violently opposed, just say so, that's fine. > > I'm "violently opposed". :-) > > > While folks do sometimes go hunting for hugely old materials in the > > tree, > > I've often traced files back to the begining of FreeBSD time (and then > continued in the CSRG SCCS tree). I've done this numerious times, > especially the contributed sources like GCC and GNU grep. > > > Do we really need 5 year old history? > > Yes. OK. Thanks, I wanted some opinions, and I guess I have enough to satisfy me. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Mon, 24 Apr 2000, Bakul Shah wrote: > > Do we really need 5 year old history? > > That really depends on your point of view. > > "Those who cannot remember the past are condemned to repeat it" > -- Santayana > > "The only thing we learn from history is that we learn nothing from history." > -- Hegel > > I am with Hegel in the very long term but what is the rush > about pruning? Set a cron job to ask this in the year 2037! > In the short term it is valuable to trace back the genesis of > various features/bugs. With cvs annotate you can even find > out who put in a feature or bug and bug that person about it > (as I was just this past week about something I had written > over four years back). The networking code is so convoluted > that having all the history (which we don't) can be very > valuable in unravelling all the development strands. Well, I wasn't talking about a harsh pruning, but I haven't seen much support for the idea, so maybe it better drop. The idea came when I was making room for vmware ... boy, I wish that the new generation of 18G Ultra160 disks would come out already ... the only reasonably priced one is the Seagate, but it could be aptly nicknamed the "data furnace" from just how hot it runs. I need more disk! Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Tue, 25 Apr 2000, Richard Wackerbarth wrote: > On Tue, 25 Apr 2000, you wrote: > > > I told myself I wouldn't get into this debate with you again, Richard, but > > you're not listening. The vast majority (all? I might have missed one) of > > the other respondants > > Actually, I didn't start this. Someone else brought up the idea. I did. I wanted to test the opinions. I said I had enough responses, about 40 messages ago. Damn, people, if you're *really* tired of hearing from Richard on this, for god's sake control your keyboards, they're running amuck! Let's see if you guys can just let it die, ok? > The quiet majority that might benefit are not very likely to speak up when > they are told some is impossible. Quiet majority hehe! Right -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Sat, 29 Apr 2000, gh wrote: > For an opinion from a reasonably new-comer and non-developer, I think at > least the main source tree should remain *completely* complete. > As someone mentioned, why not have "lite" mirrors? Oh, for god's sake, PLEASE let this drop! I don't want to insult a newcomer, but you've picked a very poor thing to comment on. Try another, maybe one that's a bit fresher. -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: a better idea for package dependencies
On Tue, 9 May 2000, David O'Brien wrote: > On Mon, May 08, 2000 at 06:30:17PM -0400, Kenneth Wayne Culver wrote: > > Actually, it has to do with the pkg_ commands, which I believe are built > > when you make world... > > yes. > > > and aren't part of the ports, > > And are only used for Ports. Thus their behavior defines the behavior of > the Ports Collection. Thus it is a Ports issue. IF the pkg_* utils were > ports, how would you install them?? Oh, will you get off it? Finally someone posts something about a *technical* issue, it's got at least some reasonable claim to be on the list (it's sure involving sysinstall, if obliquely) and it's not giving a lot of noise. There must be better things to complain about. I could offer you maybe a dozen if you're not feeling particularly investigatory right now. > > ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make(1) patches to bypass quietness prescribed by @-prefixedcommands in Makefiles
On Sun, 14 May 2000, Will Andrews wrote:
> Hi all,
>
> Some time ago I was complaining about how there is no way to force make(1)
> to display the commands executed by @-prefixed commands in Makefiles. So I
> went around and talked to a few people and one guy clued me in on how I
> would add something like this (sorry, I don't remember the name right now
> as this was a few weeks ago..).
>
> This option is useful for people with complex Makefile hierarchies who
> cannot simply insert a `@${ECHO} "SOMEVAR = ${SOMEVAR}"` as needed in their
> Makefiles or remove all the @'s in their Makefiles. In particular, I would
> use this feature to debug ports.
>
> Attached is the patch. If I can get permission, I'd like to commit this to
> code on -current, with a possible MFC in a few weeks (?). I'd like to hear
> any complaints about this code, including any style(9) mistakes, whether
> this option would be considered bloat, and whether the variable name
> ``beLoud'' is appropriate in this context. ;-)
Oh, what a nice present! Thanks!
>
> Thanks,
>
Chuck Robey| Interests include C & Java programming, FreeBSD,
[EMAIL PROTECTED] | electronics, communications, and signal processing.
New Year's Resolution: I will not sphroxify gullible people into looking up
fictitious words in the dictionary.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make(1) patches to bypass quietness prescribed by @-prefixedcommands in Makefiles
On Sun, 14 May 2000, Will Andrews wrote: > On Sun, May 14, 2000 at 01:25:16PM -0600, Lyndon Nerenberg wrote: > > I like the idea, but the -l flag conflicts with a different usage for > > SVR4 derived makes (on at least AIX, Irix, and Solaris): > > > > -l load > >Specifies that no new jobs (commands) should be started > >if there are others jobs running and the load average > >is at least load (a floating-point number). With no > >argument, removes a previous load limit. Compatibility with those other makes is pretty low to begin with, but it doesn't hurt, I guess, to allow for this. -dl is ok with me. I just wouldn't consider the compatibility thing a real issue if it weren't this easy to satisfy. -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP Re: cvs commit: src/crypto/openssh/pam_ssh pam_ssh.c src/gnu/usr.bin/binutils/gdb freebsd-uthread.c src/include mpool.h src/lib/libc/net name6.c src/lib/libc_r/uthread pthread_private.h uthread_file.csrc/lib/libncp ncpl_rcfile.c src/lib/libstand if_ether.h ...
On Tue, 23 May 2000, Jake Burkholder wrote: > > jake2000/05/23 13:41:02 PDT > > Log: > > Change the way that the queue(3) structures are declared; don't assume that > > the type argument to *_HEAD and *_ENTRY is a struct. > > > > Suggested by: phk > > Reviewed by: phk > > Approved by: mdodd > > > > HEADS UP > > Possible action required! > > Some drivers use headers from the installed system during the kernel build, > and a make world, or at least make includes, is necessary before a new kernel > can be built. > > LINT is affected by this. Is anyone else having trouble compiling the libpam things, because of this? I couldn't compile a kernel because of the the assembler changes, so I went to do a buildworld, and now I can't get thru a buildworld. I tried the suggestion above (do a make includes) but that didn't seem to do the trick. Here's about the first 5 of the 30 (or so) errors I see: cc -O -pipe -mpentium -Wall -I/usr/src/lib/libpam/modules/pam_ssh/../../../../cr ypto/openssh -c /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/p am_ssh/pam_ssh.c -o pam_ssh.o /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c :89: syntax error before `env_entry' /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c :93: syntax error before `env_entry' /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c : In function `env_new': /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c :116: structure has no member named `slh_first' / It all seems to do with the new queue.h, which is indeed installed in my /usr/include/sys (newly installed, I checked, after the make includes). Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vmware
I fianlly have vmware2 working on my current box, but I have noticed a couple things in my log, and I wanted to ask about them. Here's a little bit at the end: sio1: 3 more silo overflows (total 1268) /dev/vmmon: Vmx86_DestroyVM: unlocked pages: 359971, unlocked dirty pages: 217740 I guess I can understand the large number of silo overflows. I noticed that I can't seem to get any mails when I have vmware working, and I wish that wasn't so. The part that really worries me, tho, is the virtual memory warning. I was doing a lot of Windows software installation (which dragged on *really* slowly), but is there anything to be worried about in that warning above? -------- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Destabilization due to SMP development
On Wed, 21 Jun 2000, Mark Murray wrote: > > Has anyone given any thought to what it would take to create an > > open source version of something similar to perforce? ;-) > > Clearly you have. :-). We await your submissions with baited breath... I have mixed feelings about that. The Perforce people have been willing for FreeBSD to use it free. They're really nice about that, it seems more than a bit discourteous to try to copy it. If you'd asked to duplicate MSWord, they're a unethical monopolist, I wouldn't have any scruples attacking them, but I don't like attacking folks who've been displaying towards free software such a friendly attitude. Makes me (and I sure support free software!) feel like a predator when you go after folks who've been doing good. I think, if you want it fixed, you should go fix cvs. ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Config problems
I am getting a config error with the new gethints.pl stuff: unrecognized config token 1 This is with a newly cvsupped system, and I checked the version of gethints.pl: ROOT:/usr/src/sys/i386/conf:472 >cvs status gethints.pl === File: gethints.pl Status: Up-to-date Working revision:1.4 Sun Jun 18 01:43:22 2000 Repository revision: 1.4 /home/ncvs/src/sys/i386/conf/gethints.pl,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) So I think that's right. My config file before had worked just fine, but as a test, I went thru it and really tried to make it squeaky clean, but it didn't seem to get rid of that error. I don't know if this message indicates a fatal problem or just is a leftover printf, there's damned little in the way of info in it. I don't know, maybe that error message is referring to line 1 of my config file? Here's the start of the config file: machine i386 cpu I586_CPU cpu I686_CPU ident CH maxusers64 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O If that doesn't do it, I'm attaching the entire config file to this mail. Sure would appreciate a hint; I'm not a perl hacker, but if I gotta become one to puzzle this out, it's going to take me an long extra while trying to get me a new kernel. ---- Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
