Re: /sys/boot, egcs vs. gcc, -Os
On Fri, 9 Apr 1999, Peter Jeremy wrote: There's no mechanism for updating a package - and it's not clear (to me anyway) how this can be done safely in a general way. Where the update is only minor (and won't affect the dependent packages), you can use something like: For an update to work, files that must be preserved (shared libraries mainly) over an update must be tagged. If libfoo-1.0 is installed and I upgrade to libfoo-2.3, the libfoo-1.0 package should be removed except /usr/local/share/libfoo.so.1.0. Then libfoo-2.3 gets installed and *inherits* /usr/local/share/libfoo.so.1.0 in its +CONTENTS so that if you want to do a wholesale removal of the libfoo package in the future, you can do it. A completely different approach to this dependency nightmare is to link statically. I know there are drawbacks to this and the costs are too great in numerous situations. But if you *can* practically do this, you can demote a runtime dependency to a build time dependency which is a Good Thing for your sanity. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: wchar.h?
On Tue, 9 Mar 1999, Archie Cobbs wrote: wcslen() wcscpy() wcsncpy() wcscat() wcscmp() wcsncmp() How come FreeBSD doesn't have these? Is there a complicated problem preventing us from adding them? I have a start at all the wc functions in the NA1 of ANSI C which includes these and wide versions of most of the stdio functions (fgetwc, fputwc and the like) as well as wide iswxxx() ctype functions. Anybody who would like to finish the job is most welcome to what I have so far. (I've also got a Unicode UTF-8 local I'd like to bring in at some point...) -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems in VM structure ?
On Tue, 16 Feb 1999, Matthew Dillon wrote: Try reducing maxusers to 128. Another person reported similar behavior to me and after a bunch of work he tried going back to a basic distribution -- and everything started working again. It turned out that a maxusers value of 256 and 512 were causing his machine to go poof, but a maxusers value of 128 worked fine. Another datapoint, Sybase goes poof with maxusers set to 64 or higher. This has been the case since before 3.0 was released. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0
On Sun, 14 Feb 1999, Jordan K. Hubbard wrote: On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote: FWIW, I would also like to see this happen. What's the deadline? I did it for -current this day. I'm waiting for some feedback before the 3.1 replica. Actually, subsequent discussions with Dag-Erling have sort of shown this to have been rather too ambitious of me and now I've major second thoughts. :( My initial comment was based on my MISperception that the old lpt driver had been removed from RELENG_3 when, in fact, it had only been removed from -current. Realizing my blunder, I retract the suggestion. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0
On 13 Feb 1999, Dag-Erling Smorgrav wrote: Nicolas Souchu nso...@teaser.fr writes: controller ppbus0 # The ppbus system device nlpt0 at ppbus? # The printer driver OBTW, when are you planning to rename nlpt0 to lpt0? Hopefully before 3.1 goes out...it would be a bummer to have one release with a different name than the rest; it confuses documentation that tries to cover multiple versions. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: adding DHCP client to src/contrib/
On Tue, 9 Feb 1999, David O'Brien wrote: On Tue, Feb 09, 1999 at 09:27:44AM -0700, Lyndon Nerenberg wrote: PlatformHas DHCP Irix 6.5Yes Solaris 2.5.1 No Solaris 2.6 Yes You should have used a more modern Solaris. It helps your argment. :-) Digital Unix 4.0Yes -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
On Tue, 9 Feb 1999, jack wrote: On Tue, 9 Feb 1999, Matthew Dillon wrote: I think it's a *BAD* idea to change rc.conf operation for the 3.1 distribution. Bad Bad Bad. I have to agree. Let's not forget that there are over 30 man pages with references to /etc/rc.conf. Lets not forget that with the latest round of changes, the rc.conf in 3.1 will behave exactly as it has in the past. Think about it. rc.conf was a touchees file in the past and it is a touchees file now. The only difference is the addition of a no touchees reference copy in /etc/defaults that gets sourced before rc.conf so any essential variables introduced in an upgrade will have a safety fallaback in case you don't properly upgrade your rc.conf. The detour with rc.conf.site *did* change the way rc.conf was used. That was Bad Bad Bad and has just been fixed. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
On Wed, 10 Feb 1999, jack wrote: If /etc/rc.conf only contains changes from the defaults when man something_or_other tells the user to find and edit something_or_other_flags in /etc/rc.conf the entry won't be there to edit. Why must it contain only changes? Is there any reason it couldn't be a copy of the default rc.conf on a new installation? Over time and upgrades it may get a little out of sync with the default file, but by then the user/admin will most likely be familiar enough with configuring the system that it won't exactly be a stumper. And how about this: stick a big comment at the top of /etc/rc.conf suggesting that the user consult /etc/defaults/rc.conf for a complete list of tunable parameters. Even in the worst case, the system behavior is exactly as it was before any of these changes came about. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: some woes about rc.conf.site
On Sun, 7 Feb 1999, Andreas Klemm wrote: What do you think ? Or what are your experiences ? It has caused a lot of grief with my recent install of 3.0-19990205, but I gather I'm supposed to install something later before complaining. The main annoyance has been that running /stand/sysinstall after installation diligently clobbered settings in rc.conf.site...things like default_route, moused_enable, and network_interfaces to name a few of the more frustrating ones. Hopefully that is now fixed. As for for all the debate on the name, if it is supposed to be an untouchable file, the name of rc.conf has GOT to change. rc.defaults, rc.conf.defaults, rc.param or some such, with rc.conf being the one you normally edit and rc.conf.local being sourced for people who need it for some reason. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3.0 vs 4.0
On Wed, 3 Feb 1999, HighWind Software Information wrote: Can someone summarize the difference and locations between all these things? Think of it as a tree where the trunk is -current and branches are -stable. There is only one -current but potentally many -stables. Each release with a new major version number creates a new branch. Old branches, starved for light, eventually wither and die. current | | | stable || | 3.1 || stable | / || / 2.2.8 | / ||/ 2.2.7 | 3.0 || 2.2.6 | || \ | 2.1 \ | \ | \| 2.0 | | 2.2.8-release is (supposedly) the end of the line for the 2.2 branch of FreeBSD but critical bugs continue to be fixed and they show up in the 2.2.8-stable branch. You can get binary snapshots of this branch to pick up the bug fixes, or you can get the source and make world to get them. Call 2.2.8-stable the trailing edge. 3.0-stable is is the actively maintained stable branch from which the next release (3.1) will come. The primary activity on this--or any stable branch--is bug fixes rather than new features, although new features will appear over time. Call 3.0-stable the cutting edge. There is only one -current at any given time and the version number just indicates what the next major release will be. Since there is only one, it is usually just called -current and this is where exciting new features and bugs are introduced to FreeBSD. Call -current the bleeding edge. Is it still true that 2.2.8 is the thing that folks get when they go to the www.freebsd.org website and grab the the latest stable thing? Speaking only for myself, I'd say that is correct. Once 3.1 comes out, then I would say 3.1 is the latest stable thing. I'm not sure that *any* dot zero release should be considered stable. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What would be useful here is the ability to compose keymaps. There would be basically two sets: one that defines the layout of the main keyboard and one that defines the layout of the other keys. That way I could pick my dvorak layout, then add on a layout that, say, swaps control and caps lock but leaves the main layout alone. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: netd in free(): warning: junk pointer, too low to make sense.
On Fri, 22 Jan 1999, Palle Girgensohn wrote: I'm experiencing some strange errors with one of our workstations. I recently moved all of our workstations to 3.0 current as of 1998-12-18. Does any of this make any sense to anyone: trumpet:~rlogin balalaika netd in free(): warning: junk pointer, too low to make sense. trumpet:~telnet balalaika Trying 1.2.3.4... Connected to balalaika.partitur.se. Escape character is '^]'. inetd in free(): warning: junk pointer, too low to make sense. There are two separate bugs that can cause this behavior, one in inetd and the other is the infamous dying daemons bug. Both have theoretically been fixed, recently. Sorry I don't have exact dates handy. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Still safe to do a remote 'installworld'?
On Fri, 15 Jan 1999, Karl Pielorz wrote: Am I still safe to do the equivalent of a 'remote' install world? - I have 2 x 3.0 boxes, one which is fresh 3.0-RELEASE, the other which is 3.0-CURRENT... If I take the /usr/src /usr/obj directories from sucsessful 'buildworld' on the -current machine can I run an 'installworld' on the -release machine? I've done that a number of times in the last month or two. Works like a charm. One thing to watch out for is that kernel's are now ELF which means you must install the new bootblocks on the -release machine first. Also check out the mergemaster port for a handy way to update /etc. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 3.0-RELEASE Apache 1.3.2 problem
On Fri, 15 Jan 1999, Igor Shulgin wrote: What I have done wrong? Is it possible to run Apache 1.3.x on FreeBSD 3.0 ? Yes but you need to install a more recent port or package. The conversion to ELF tripped up a few things like Apache that didn't know about ELF FreeBSD systems. That is all fixed now. (See the FreeBSD FAQ for more info about the ELF conversion) -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
