Upgrading from a not-very-current current
If you want to complain that I shouldn't be running -current in the first place, don't bother. I upgraded because -stable doesn't support SMP + fork with shared memory. I want to upgrade from a pre-signal changes -current to -current (I'm having problems with a pnic card getting corrupted mbufs and I want to see if Bill Paul's new driver works better), and I have a simple question: I know that I need to build the tools for config, and build a new kernel, and reboot it before doing a make world. My question is, after booting the new kernel, do I run MAKEDEV immediately, or do I run make world before runnning MAKEDEV? Would it be prudent to disable softupdates until after I'm done upgrading? Would it be simpler to install from the latest -current snap? Thanks, Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current build fails
Chris Costello writes: On Sat, Oct 30, 1999, Vincent Poy wrote: Well, I try to stay up to date but there are times when I am busy so things do get behind... I've ran -current since 1993. There is no real reason to use -STABLE. Give me one single reason why there is on real reason to use -STABLE and I'll give you 10 reasons to use -STABLE. Can -STABLE run applications that use shared memory on an SMP kernel? No? I didn't think so. I think a lot of the people who run older versions of -current, and upgrade sporadically, have done so because there are particular things missing out of -STABLE that they need (or want). For various reasons, they're not inclined to install a new version of -current daily, or even weekly, and wait until they feel that -current is relatively stable. Most of them have no interest in doing major OS internals development, but are capable of generating kernel dumps after a panic. They also know that nobody's going to spend a lot of time on any problems they encounter unless they're running a very current -current. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why do FreeBSD mailing lists ignore MX preference?
Ben Smithurst writes: Bruce Albrecht wrote: Non-authoritative answer: zuhause.mn.org preference = 150, mail exchanger = minuet.skypoint.net zuhause.mn.org preference = 100, mail exchanger = 205.215.217.178 "205.215.217.178." almost certainly does not have an address (A) record. Mail exchangers must be host names, not IP addresses. Unfortunately, I don't have control over the MX record. When I asked them to change it to my new static IP I gave them a valid PTR address (FQDN) and the new static IP, and they used the static IP instead of the FQDN. I've asked them to correct it, now that I know that it's wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Matthew Dillon writes: And to head off another question: When you are recording to a CD-RW you can do a 'quick erase' of the media using 'cdrecord blank=fast'. This does not actually erase the data, so if you have used say 100MB you will only have 550MB left. You can actually erase the media using 'cdrecord blank=all', which takes a while. In my experience, this is not true. I have used blank=fast on a CDRW that has over 500 MB written, and then written another 500 MB without a problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: colour 'ls'
Dag-Erling Smorgrav writes: Oleg Ogurok o...@ogurok.com writes: I put ls as a symbolic link to gnuls, but every time I make world, the old 'ls' puts back ;-) Don't do that. Instead, do: # cd /usr/local/bin # ln -s gnuls ls and fix your PATH so /usr/local/bin comes before /bin. Better yet, set up an alias of ls = ls --color when the shell is an interactive shell, and then you don't get the color escape sequences when running scripts or if you escape ls with \ls when outputting to a file. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Chuck Robey writes: If that were true, but it's not. Older versions of the config files and libraries can very easily cause the ports to fail to build. Every time I upgrade stuff, I have to go about doing search and destroy on old stuff. On top of that, there are various mistakes in dependencies; there's one lib (I forget which) which installs under one name, but all of the dependencies on it are under another name. The stuff seems to change it's mind on whether it wants to install under /usr/local or /usr/X11R6, so finding stuff is pretty complicated, and very dependent on version, because the darn install dirs change, just to make things worse. I'll bet the library you're thinking of is libtix. David O'Brien just committed fixes for it yesterday. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Ne2000 PCI Card
Rod Taylor writes: I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset (from the best that I can tell). Both are PCI. I've attempted to use both cards in several PCI slots, under 2.2.8 and 3.0 boot floppies, and a 3.0-stable (updated 2 days ago). None of these releases found either card in any situation. I believe the card should be detected as Ed0 (possibly ed1). I have used 3com pci cards in both machines under freebsd sucessfully and the ne2000 cards function under windows and os/2. The RealTek 8139 chipset is supported with the rl0 driver, and has been supported since 3.0 was released. Bill Paul is the maintainer of the driver. I think the GENERIC kernel should have been able to find them. I've got a 8139 based NIC, and I have no complaints about its performance at 10 Mbps, but it's a real dog at 100 Mbps. I'm only able to achieve 45-50 Mbps throughput with a dual P6-200 machine, and it uses nearly 30% of the CPU to do it. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: removing f2c from base distribution
Garrett Wollman writes: On Wed, 27 Jan 1999 20:44:33 +0900, Daniel C. Sobral d...@newsguy.com said: A lot of people use a lot of things out of ports. Why should Fortran be different? Because Berkeley Unix has /always/ included a FORTRAN compiler. So FreeBSD v12.4, released in 2026, had better include a FORTRAN compiler, because Berkely Unix has /always/ included a FORTRAN compiler? I'm sure there are a fair number of ways FreeBSD has diverged from the way Berkeley Unix has always done things (for example, to conform to POSIX), is that such a bad thing? If it's a port, and sysinstall gives the user an option to install a FORTRAN compiler, is that so radically different from Berkeley Unix /always/ including a FORTRAN compiler? Is it wrong to move things that most people installing FreeBSD don't use out of the core and into ports? I've never used the FreeBSD FORTRAN compiler, but I do use something that a lot of other people single out as being in this category (uucp), but if uucp were to move to the ports, I'd still use it and FreeBSD. Are there any programs in the base sources for FreeBSD that are written in FORTRAN? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
