Re: Please consider some cosmetic changes in boot messages
On Tue, Sep 12, 2000 at 06:28:05PM -0700, Kris Kennaway wrote: I'm also not sure where the rumors about a FreeBSD 4.1.5 got started since I'd certainly never planned on such a thing, that, I think, 4.1.1 rather than 4.1.5 please. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
On that subject, can you give me a rough projection as to when 5.0-RELEASE is likely to arrive? FreeBSD 2.2.1 1997-04-xx [FBD] FreeBSD 3.0 1998-10-16 [FBD] FreeBSD 4.0 2000-03-13 [FBD] You forgot FreeBSD 4.1, 2000-07-27 (www.freebsd.org/releases). This makes FreeBSD 4.2 scheduled for 2000-11-xx since we do a release every 4 months (not that anyone asked about 4.2 in this thread, but I saw some other speculation about it which I'll conveniently answer in this one). I'm also not sure where the rumors about a FreeBSD 4.1.5 got started since I'd certainly never planned on such a thing, that, I think, being more the product of wishful thinking on certain security-minded people's behalf after RSA released their code. :-) That said, it's something I'm still contemplating. I need to see what merge-in-progress work is currently underway or certainly people will complain that 4.1.5 should have waited for their own wishlist items rather than being slaved solely to the RSA release event. As to FreeBSD 5.0, I think you can count on that being a mid-summer item for 2001 and certainly not any sooner. There's a lot of work which still needs to be done before we'll be ready for anything like 5.0, given the extent of the SMPng changes planned for that release. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
On Tue, 12 Sep 2000, Jordan Hubbard wrote: I'm also not sure where the rumors about a FreeBSD 4.1.5 got started since I'd certainly never planned on such a thing, that, I think, A certain user called jkh on IRC :-). I asked you and you agreed to it as a net-only release. Kris -- 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
Re: Please consider some cosmetic changes in boot messages
A certain user called jkh on IRC :-). I asked you and you agreed to it as a net-only release. Hmmm. I must have been on drugs. :) Very well, I'll see what can be done. A test release is actually building right now. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
Sheldon Hearn wrote: I have a plan to revamp the way that the startup process's output is presented and stored for later viewing. I need to chat to some folks first about the best way to do this, first. Be patient, and look forward to something interesting in 5.0-RELEASE. :-) Ciao, Sheldon. On that subject, can you give me a rough projection as to when 5.0-RELEASE is likely to arrive? -- "I'm entirely unaccountable for any moments of sanity contained herein." :s/Windows/UNIX John Toon | [EMAIL PROTECTED] | "Sonnilon" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
On Fri 2000-09-08 (15:19), John Toon wrote: I have a plan to revamp the way that the startup process's output is presented and stored for later viewing. I need to chat to some folks first about the best way to do this, first. Be patient, and look forward to something interesting in 5.0-RELEASE. :-) On that subject, can you give me a rough projection as to when 5.0-RELEASE is likely to arrive? FreeBSD 2.2.1 1997-04-xx [FBD] FreeBSD 3.0 1998-10-16 [FBD] FreeBSD 4.0 2000-03-13 [FBD] So we're talking 2001-07 to 2001-11, at a wild guess. We have lots of new developments, but also a much more streamlined system. It's anyone's guess when it'll be deemed stable and complete enough to roll. (and please don't quote me, since this is only my guess) Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Please consider some cosmetic changes in boot messages
Anyone else noticed how FreeBSD is inconsistent with the use of words like "Doing", "setting" and "starting" in the boot messages ? For instance, I think the following fragment of my boot should change from: Additional routing options: tcp extensions=NO TCP keepalive=YES. routing daemons:. Mounting NFS file systems. additional daemons: syslogd. checking for core dump...savecore: no core dump Doing additional network setup: portmap. Starting final network daemons: mountd nfsd rpc.statd nfsiod NFS access cache ti me=2. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout starting standard daemons: inetd cron usbd. Initial rc.i386 initialization: apm apmd. rc.i386 configuring syscons: font8x16 font8x14 font8x8 blank_time allscreens. additional ABI support:. Local package initialization: fkeys SETI@home xfstt. Additional TCP options:. To: (I've put * against the changed lines) Additional routing options: tcp extensions=NO TCP keepalive=YES. routing daemons:. Mounting NFS file systems. additional daemons: syslogd. checking for core dump...savecore: no core dump * additional network setup: portmap. * final network daemons: mountd nfsd rpc.statd nfsiod NFS access cache time=2. * ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib * a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout * standard daemons: inetd cron usbd. * rc.i386 initialization: apm apmd. rc.i386 configuring syscons: font8x16 font8x14 font8x8 blank_time allscreens. additional ABI support:. Local package initialization: fkeys SETI@home xfstt. Additional TCP options:. And finally, for filesystems with = 10^6 blocks free, the fsck -p output (second line) hits exactly 80 chars which makes syscons leave a blank line before the next line of output. Call me pedantic but could we change the word "fragmentation" to "fragmented" to give room for many more blocks in the filesystem before wrapping. I'm sure the answer is no due to histerical raisins but its worth a try ;) /dev/ad0s2e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s2e: clean, 5929804 free (2252 frags, 740944 blocks, 0.0% fragmentation) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please consider some cosmetic changes in boot messages
On Fri, 08 Sep 2000 23:07:22 +0930, Matthew Thyer wrote: Anyone else noticed how FreeBSD is inconsistent with the use of words like "Doing", "setting" and "starting" in the boot messages ? Yes, but I wouldn't worry about it at this stage. I have a plan to revamp the way that the startup process's output is presented and stored for later viewing. I need to chat to some folks first about the best way to do this, first. Be patient, and look forward to something interesting in 5.0-RELEASE. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
