Re: Migration Guide

2005-05-28 Thread Bruce A. Mah
If memory serves me right, Vizion wrote:
 To
 [EMAIL PROTECTED]
 This thread from freebsd-question refers to release notes and is passed to 
 you 
 on recomendation of  Giorgos Keramidas who contributed to the dialogue on Re: 
 Migration Guide:

As Giorgos said, the release notes of 5.4 are frozen and no changes can
be made to them.

The release notes for 5-STABLE and 6-CURRENT have no references to the
Migration Guide.  There used to be some boiler-plate references to
src/UPDATING but they were probably removed during those releases where
the Migration Guide existed.  Some suitably motivated doc committer
could update them if necessary and bring them back.

Note that the Migration Guide was intended to address concerns of users
upgrading from 4.X to 5.X.  This is implied in its abstract and is
specifically stated in the introduction.

Bruce.

 On 2005-05-28 08:58, Vizion [EMAIL PROTECTED] wrote:
  On Saturday 28 May 2005 07:30,  the author Giorgos Keramidas contributed
  to
 
  the dialogue on Re: Migration Guide:
  On 2005-05-27 10:52, Vizion [EMAIL PROTECTED] wrote:
   Hi
   Have I missed something -- I do not see any notes for source upgrade
   from 5.3 to 5.4 in the Migration guide. There see notes on upgrade 4.x
   to 5.x.
  
  The usual update procedure, described in the Handbook and
  /usr/src/UPDATING works fine for 5.3 - 5.4, so there is
  no need for a special Migration Guide.
 
  I think that may be arguable but if true the release notes needs to be
  updated to reflect that position by removing all reference  to the
  presence of updating notes in the migration guide for upgrade from 5.x to
  5.4 and replace it with a handbook page reference.
 
 Certainly.  It's too late to fix the release notes of 5.4, but if you
 note such places please contact [EMAIL PROTECTED] :-)
 


signature.asc
Description: This is a digitally signed message part


Re: make release broken for -STABLE?

2003-01-23 Thread Bruce A. Mah
If memory serves me right, Igor B. Bykhalo wrote:

[kern.flp overflow again]

 I don't get it:

[snip]

  goshik# ls -l *kern*
  image.kern:
  total 1346
  drwxr-xr-x  2 root  wheel  512 22 ÑÎ× 21:19 boot
  -r-xr-xr-x  1 root  wheel  1344894 22 ÑÎ× 21:19 kernel.gz
 
  kernels:
  total 2864
  -r-xr-xr-x  1 root  wheel  2909648 22 ÑÎ× 21:19 BOOTMFS.kern
 
 Looks like kernel.gz fits to floppy, but for some reason it doesn't...
 Should i supply more info?

Well, kernel.gz will probably fit, but the release needs the entire 
contents of the image.kern directory to fit on kern.flp.  See:

freebsd-stable:stage% du image.kern
88  image.kern/boot
1434image.kern

This doesn't fit.  :-(  By my calculation, we have to get rid of about 
27K to make it fit, but I could be off.

We might be able to move the de, em, or vx drivers to the mfsroot
floppy, if there's space.  I'll try playing around with this, if I get 
some time.  (Obviously that shouldn't preclude someone else from 
working on this problem.)

Bruce.






msg16539/pgp0.pgp
Description: PGP signature


Re: make release broken for -STABLE?

2003-01-23 Thread Bruce A. Mah
I wrote:

 We might be able to move the de, em, or vx drivers to the mfsroot
 floppy, if there's space.  I'll try playing around with this, if I get 
 some time.  (Obviously that shouldn't preclude someone else from 
 working on this problem.)

I moved the em driver to mfsroot.flp and was able to build a release
successfully (see revision 1.3.2.7 of src/release/i386/drivers.conf).
Please update your tree, try the build again, and let me know how this 
works.

Good luck,

Bruce.





msg16540/pgp0.pgp
Description: PGP signature


Re: upgrading problem

2002-10-22 Thread Bruce A. Mah
If memory serves me right, Barney Wolff wrote:
 The problem appears to be that the default result of .Os is still
 FreeBSD 4.6 according to man 7 mdoc, on my RELENG4 system
 cvsupped 10/18.  mdoc.local 1.2.2.15 appears to define it that way.

Oops.  We seriously need to reorganize our version number bump list.

 It appears that RELENG_4 should be using 1.2.2.15.2.1 instead, or
 another tag that will get 4.7 as the default.

Not quite.  The correct fix is to update the file on the RELENG_4
branch, not to grab this one file from the RELENG_4_7 branch.

 Ok, ok, I'll send the PR. :)

Thanks for the PR, Barney!

I committed the update as version 1.2.2.16 of mdoc.local.

Bruce.





msg06545/pgp0.pgp
Description: PGP signature


Re: RELENG_4_6

2002-07-16 Thread Bruce A. Mah

If memory serves me right, Pete Carah wrote:
 At first I thought I may have picked up a partial cvsup but cvsup'd
 twice more at hour intervals with no fix apparent.  There appears to be 
 a missing file in the MFC for skey fixes...

From what I can tell (my local respository, commit logs, and cvsweb) it
looks like src/crypto/openssh/auth-skey.c didn't get committed to the
RELENG_4_6 branch.

Bruce.





msg00661/pgp0.pgp
Description: PGP signature