PNA?
Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. 3com 3c410, or D-Link DHN-520? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
more make release
BTW, is it considered a bug or a feature that you MUST use /usr/obj to have make release work? I went in circles for quite a while before figuring this out (I just didn't have much room in /usr, so was using the make env variable to move the obj tree. It failed in various amusing ways whilst building the crunches - in particular, the generated files for /bin/sh don't go to the right places, and the makefile setup is too tangled for my tiny brain.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: more make release
Hmmm, I'm specifically talking about when you have MAKEOBJDIRPREFIX set to something other than /usr/obj - it *almost* works, but /bin/sh uses files generated on-the-fly that get put in the wrong places (in the chroot'ed hierarchy). (ONLY when building the crunches - makeworld runs fine.) I suppose its beating a dead horse (got around it with a symlink or two) but it niggles - but that whole environment is just too twisted to follow. :( -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 29, 2000 12:10 PM To: Gray, David W. Cc: FreeBSD Current list Subject: RE: more make release On 29-Nov-00 Gray, David W. wrote: BTW, is it considered a bug or a feature that you MUST use /usr/obj to have make release work? I went in circles for quite a while before figuring this out (I just didn't have much room in /usr, so was using the make env variable to move the obj tree. It failed in various amusing ways whilst building the crunches - in particular, the generated files for /bin/sh don't go to the right places, and the makefile setup is too tangled for my tiny brain.) Feature. make release starts off by doing an installworld into the chroot'd area and using that area to do a cleanroom make world from which the release bits are rolled. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release problem
I had earlier written (to deafening silence) that I had been unable to build a release from current. Buildworlds worked OK, but make release didn't. I have since figured out what was not working, but this leads to another question. On my particular box, I don't have a whole lot of room on /usr, so I was building the world on /home, e.g. export MAKEOBJDIRPREFIX=/home/current. The world would build, but make release died compiling the boot crunch. There are a slew of derived files in /bin/sh - yacc output and such - that are not found. I discovered that just symlinking /usr/obj to the right place, and not setting MAKEOBJDIRPREFIX works just fine. I made a shot at trying to fix this, but quite frankly I must agree with the comment in the release Makefile - "You are not expected to like this." Is this considered a bug worth fixing? If not, at least this will be in the archive for the next confused person... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent make world breakages
Not to exacerbate a sore subject, but... From what I'm seeing go by, the intention is that a current make world is supposed to work from -stable. OK, what about make release? The reason I am asking, is that I'm actually running current on a laptop, and for various reasons, its far easier to be able to load it from a cdrom. My build machine is a 4.0 release box, its the only one I have that's muscular enough to do the build. Since I've been tracking -current (the last couple of weeks or so, but I've been on this list for a year or so) I have been able to build world, but building the boot crunch dies compiling /bin/sh (there are intermediate files created by yacc and such that are built in the current directory, not where the source is.) Should this work? Is it germane that I don't build in /usr/whatever, but over in /home/current, etc? Should this work? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FW: Recent make world breakages
Blasted Outhouse mailer. Grumble Lets try again. -Original Message- From: Gray, David W. Sent: Monday, July 24, 2000 11:15 AM To: 'FreeBSD Current list' Subject: Recent make world breakages Not to exacerbate a sore subject, but... From what I'm seeing go by, the intention is that a current make world is supposed to work from -stable. OK, what about make release? The reason I am asking, is that I'm actually running current on a laptop, and for various reasons, its far easier to be able to load it from a cdrom. My build machine is a 4.0 release box, its the only one I have that's muscular enough to do the build. Since I've been tracking -current (the last couple of weeks or so, but I've been on this list for a year or so) I have been able to build world, but building the boot crunch dies compiling /bin/sh (there are intermediate files created by yacc and such that are built in the current directory, not where the source is.) Should this work? Is it germane that I don't build in /usr/whatever, but over in /home/current, etc? Should this work? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release?
Is it just me, or is make release broken? I've been getting a bomb-out whilst making the boot crunch (in /bin/sh, I think. Its at home, I'm not.) I haven't seen anybody kvetching (I *do* read current...) Just to sanity check, I ran a 4.0 make release last night, that worked just fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Rc2 install
I've come to the conclusion that the -current stuff really doesn't install on an 8 Meg machine anymore. I have an old 486/66 machine I'm using to play with the current-RC's, and it consistantly dies loading the 'bin' stuff. This isn't really a complaint -- after the load boot cycle, there is only 2.4M free according to the boot messages, so I can see why this would fill up. (I wound up loading the drive on another box that usually drives my printer, 386/25 and 24M, talk about S.L.O.W). And it can't quite compile a kernel in one go, either. Perhaps the release notes, or hardware file need to note you really do need more than 8M ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Compupic - yes, it works.
A quick preface, I am using Release3.2 off the CDROM. Compupic works. I don't use the install script, just unpack everything from the innermost tar file to /usr/local/compupic. Brandelf -t Linux the compupic binary, and put a symlink in /usr/local/bin to run with. Now for the SEKIT! MOVE YOUR /usr/compat DIRECTORY aside - rename it temporarily. Run compupic once. You should now be able to move /usr/compat back into place (or /compat, if you left it there...) Why? I dunno. Found it by accident. The Prez over at Compupic said something about releasing a FreeBSD native version, in the letter on the compupic mailing list. I have'nt seen hide nor hair of it, I'd ***REALLY*** like to. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
