updating Kernel 3.3 to 3.4

updating Kernel 3.3 to 3.4

Post by Douglas A. Mask » Sun, 20 Feb 2000 04:00:00



I had a lot of luck removing the 3.3 source, and downloading the 3.4
STABLE source, and doing a buildworld; installworld; and then
recompiling my kernel.  I have had serious trouble getting the compat22
working properly with Netscape, it only works right on one machine, I
recompiled the src twice on there, rebuilt XFree86 3.3.6 twice and then
it worked without library errors.

Thanks,
Doug


> hi,
> i've had freebsd for about 2 months now.  i'm ready to upgrade to
> kernel 3.4, but i'm not quite sure what i need to download.  do i need
> to download the whole ./sys/ folder or what?  or is there an update
> feature.
> thanks

> ---
> drwxrwxrwx
> *******
> * from this mic device i spit non fiction
> * who got tha power this be my question
> * the mass or the few in this torn nation
> * the priest the book or the congregation
> * the politricks who rob and hold down your zone
> * or those who give the thieves the key to their homes
> * the pig who's free to * one shucklack
> * or SURVIVORS WHO MAKE A MOVE AND * ONE BACK
> *******

--
Douglas A. Maske
CEO/President
Thin Blue Communications, Inc.
Management/Information Systems

Simple Solutions For The Small Business, & Home.

Address: 640 Anthony Trail Northbrook IL. 60062
Web: http://www.veryComputer.com/
Home: (847) 776-1606
Work: (847) 562-1886
Fax: (847) 562-1895
Cellular: (847) 452-0709

 
 
 

updating Kernel 3.3 to 3.4

Post by Ray Kohl » Sun, 20 Feb 2000 04:00:00



>hi,
>i've had freebsd for about 2 months now.  i'm ready to upgrade to
>kernel 3.4, but i'm not quite sure what i need to download.  do i need
>to download the whole ./sys/ folder or what?  or is there an update
>feature.

You should probably get the cvsup-bin port and use it. There's
a large section in the handbook on cvsup. (See "Staying stable with
FreeBSD".) Then do the make world sequence (See "Using make world to
rebuild your system".)

--

        KING?->

 
 
 

updating Kernel 3.3 to 3.4

Post by Ulf Kist » Wed, 23 Feb 2000 04:00:00


Hi,



> >hi,
> >i've had freebsd for about 2 months now.  i'm ready to upgrade to
> >kernel 3.4, but i'm not quite sure what i need to download.  do i need
> >to download the whole ./sys/ folder or what?  or is there an update
> >feature.

> You should probably get the cvsup-bin port and use it. There's
> a large section in the handbook on cvsup. (See "Staying stable with
> FreeBSD".) Then do the make world sequence (See "Using make world to
> rebuild your system".)

I scripted a framework which automates the following tasks (based on
3.3 STABLE):

- synching the "src" tree (should be installed, otherwise will be
  completely downloaded)
- synching the "crypto" tree (dito)
- synching the "doc" tree (english only)
- remake world
- remake and install kernel

Nothing very big, but maybe helpful for people who want to play safe.
Feel free to ask for it!

If the respective scripts are invoked by cron, you should not need to
care for them again.

Hope that helps,

Ulf

 
 
 

updating Kernel 3.3 to 3.4

Post by drwxrwxr » Wed, 23 Feb 2000 04:00:00




>Hi,



>> >hi,
>> >i've had freebsd for about 2 months now.  i'm ready to upgrade to
>> >kernel 3.4, but i'm not quite sure what i need to download.  do i need
>> >to download the whole ./sys/ folder or what?  or is there an update
>> >feature.

>> You should probably get the cvsup-bin port and use it. There's
>> a large section in the handbook on cvsup. (See "Staying stable with
>> FreeBSD".) Then do the make world sequence (See "Using make world to
>> rebuild your system".)

>I scripted a framework which automates the following tasks (based on
>3.3 STABLE):

>- synching the "src" tree (should be installed, otherwise will be
>  completely downloaded)
>- synching the "crypto" tree (dito)
>- synching the "doc" tree (english only)
>- remake world
>- remake and install kernel

>Nothing very big, but maybe helpful for people who want to play safe.
>Feel free to ask for it!

>If the respective scripts are invoked by cron, you should not need to
>care for them again.

>Hope that helps,

>Ulf

post it if ya dont mind..

*****-----
drwxrwxrwx
*****-----
from this mic device i spit nonfiction
who got tha power this be my question
the mass or the few in this torn nation
the priest the book or the congregation
the politricks who rob and hold down your zone
or those who give the thieves the key to their homes
the pig who's free to * one shucklack
or survivors who make a move and * one back
*****-----

 
 
 

updating Kernel 3.3 to 3.4

Post by Ulf Kist » Wed, 23 Feb 2000 04:00:00


Hi 777,

On Tue, 22 Feb 2000 15:11:39 GMT, drwxrwxrwx wrote:
> >I scripted a framework which automates the following tasks (based on
> >3.3 STABLE):

> >- synching the "src" tree (should be installed, otherwise will be
> >  completely downloaded)
> >- synching the "crypto" tree (dito)
> >- synching the "doc" tree (english only)
> >- remake world
> >- remake and install kernel

> >Nothing very big, but maybe helpful for people who want to play safe.
> >Feel free to ask for it!

> >If the respective scripts are invoked by cron, you should not need to
> >care for them again.

> >Hope that helps,

> >Ulf

> post it if ya dont mind..

I dont, but it's a little work - and the tarball I made contains a lot
of additional documentation (the cvsup tutorial by Ben Fennema,
<bfenn...@galaxy.csc.calpoly.edu> and the cvsup FAQ by John D. Polstra
<cvsup-b...@polstra.com>) - look at

http://www.freebsd.org/handbook/synching.html#CVSUP

(this can/should be on your HDD, too!) or / and

http://www.polstra.com/projects/freeware/CVSup/

OK, here we go:

0) - First make sure you have the complete sources installed. In the
     following they are assumed to be in "/usr/src". The first sync
     might take a longer time, subsequent syncs take not too much time
     - clickedy-click, ok, *my* last one was 10 min at a maximum rate
     of 64 MBit/s, and I update once a week).
   - Note that the documentation for 3.3 is installed in /usr/share/doc,
     so you have to use two supfiles.
   - Make sure your /var/log can bear about 15 MB of extra data -
     otherwise you could log somewhere else or direct output to
     /dev/null (IMO *not* a good idea, since you cannot trace down the
     cause of errors if they appear).

1) Copy the following files into a directory of your choice (if you
   *don't* use /etc/local/sbin, you *must* change the respective
   paths:

-----------------------------------------------------------------------

#!/bin/sh
#
# /etc/local/sbin/rebuild_system
#
# calls a set of scripts for peacefully remaking
# everything in the background, complete logging
# is provided in /var/log/remake_*
#

echo "====== $(date) ====== rotate /var/log/remake_doc =========="
mv /var/log/remake_doc /var/log/last_remake_doc
echo "====== $(date) ====== call remake_doc ====================="
echo " "
/etc/local/sbin/remake_doc > /var/log/remake_doc 2>&1

echo "====== $(date) ====== rotate /var/log/remake_cvsup ========"
mv /var/log/remake_cvsup /var/log/last_remake_cvsup
echo "====== $(date) ====== call remake_cvsup ==================="
echo " "
/etc/local/sbin/remake_cvsup > /var/log/remake_cvsup 2>&1

echo "====== $(date) ====== rotate /var/log/remake_world ========"
mv /var/log/remake_world /var/log/last_remake_world
echo "====== $(date) ====== call remake_world ==================="
echo " "
/etc/local/sbin/remake_world > /var/log/remake_world 2>&1

echo "====== $(date) ====== rotate /var/log/remake_kernel ======="
mv /var/log/remake_kernel /var/log/last_remake_kernel
echo "====== $(date) ====== call remake_kernel =================="
echo " "
/etc/local/sbin/remake_kernel > /var/log/remake_kernel 2>&1

echo "====== $(date) ====== locate.updatedb (no logging) ========"
echo " "
/usr/libexec/locate.updatedb > /dev/null 2>&1

echo "====== $(date) ====== makewhatis ==== (no logging) ========"
echo " "
/usr/bin/makewhatis $manpath > /dev/null 2>&1

##################################################################
##### Start: This will *not* work on your system !!! #############
##################################################################

echo "====== $(date) ====== rotate /var/log/remake_daemons_stop ="
mv /var/log/remake_daemons_stop /var/log/last_remake_daemons_stop
echo "====== $(date) ====== call local_daemons stop ============="
echo " "
/etc/local/sbin/local_daemons stop > /var/log/remake_daemons_stop 2>&1

##################################################################
##### Stop: This will *not* work on your system !!!  #############
##################################################################

echo "====== $(date) ====== done = complete logs in /var/log/ ==="
echo " "

-----------------------------------------------------------------------

#!/bin/sh
#
# /etc/local/sbin/remake_doc
#
# sync the documentation - english only
# please refer to /usr/sup/doc-all/refuse
# for details

echo "====== $(date) ====== updating sourcetree by cvs ======"
/usr/local/bin/cvsup -g -L 2 /etc/doc-supfile
echo "====== $(date) ====== done ============================"

-----------------------------------------------------------------------

#!/bin/sh
#
# /etc/local/sbin/remake_cvsup
# sync the source tree via cvsup

echo "====== $(date) ====== updating sourcetree by cvs ======"
/usr/local/bin/cvsup -g -L 2 /etc/stable-supfile
echo "====== $(date) ====== done ============================"

-----------------------------------------------------------------------

#!/bin/sh
#
# /etc/local/sbin/remake_world
#
# sic.

echo "====== $(date) ====== make a new world  ==============="
cd /usr/src
make world
echo "====== $(date) ====== done ============================"

-----------------------------------------------------------------------

#!/bin/sh
#
# /etc/local/sbin/remake_kernel
#
# sic. the string "ULFBSD" should be
# changed to whatever you call your
# config.

echo "====== $(date) ====== make a new kernel ==============="

echo "====== $(date) ====== backup old kernel ==============="
cp /kernel /kernel.yesterday

echo "====== $(date) ====== cd /usr/src/sys/i386/conf/ ======"
cd /usr/src/sys/i386/conf/

echo "====== $(date) ====== config ULFBSD ==================="
config ULFBSD

echo "====== $(date) ====== cd /usr/src/sys/compile/ULFBSD =="
cd /usr/src/sys/compile/ULFBSD/

echo "====== $(date) ====== make depend ====================="
make depend

echo "====== $(date) ====== make ============================"
make

echo "====== $(date) ====== make install ===================="
make install

echo "====== $(date) ====== done ============================"

-----------------------------------------------------------------------

2) copy these files to /etc:

-----------------------------------------------------------------------

#
# /etc/stable-supfile
#
# tracks the 3.x STABLE sources.
#
# depending on from where you cvsup you should
# change the host and eventually the crypto settings

*default host=cvsup.de.freebsd.org
*default base=/usr
*default prefix=/usr
*default release=cvs
# The following line is for 3-stable.  If you want 2.2-stable, change
# "RELENG_3" to "RELENG_2_2".
*default tag=RELENG_3
*default delete
*default use-rel-suffix
*default compress

## Main Source Tree.
#
# The easiest way to get the main source tree is to use the
# "src-all" mega-collection.  It includes all of the individual "src-*"
# collections, except the export-restricted collections.

src-all

# The easiest way to get the export-restricted code is to use the
# "cvs-crypto" mega-collection.

cvs-crypto

# Have the ports collection synched? Yo man.

ports-all tag=.

-----------------------------------------------------------------------

#
# /etc/doc-supfile
#
# for restrictions, like *not* tracking
# russian documentation, refer to
#
# /usr/sup/doc-all/refuse
#
# personally I only track the english doc, so my
# refuse-file looks like:
#
# -----------
# doc/es*       spanish
# doc/fr*       french
# doc/ja*       japanese
# doc/ru*       russian
# doc/zh*       thai
# -----------

*default host=cvsup.de.FreeBSD.org
*default base=/usr
*default prefix=/usr/share
*default release=cvs tag=.
*default delete use-rel-suffix

doc-all

-----------------------------------------------------------------------

3) copy the following lines into a file /usr/sup/doc-all/refuse :

-----------------------------------------------------------------------
doc/es*
doc/fr*
doc/ja*
doc/ru*
doc/zh*
-----------------------------------------------------------------------

4) add a line to your crontab where rebuild_system is called
   (typically overnight, since the overall procedure takes quite a
   while - on my 200 MHz PPro with 64 MB RAM about 2 1/2 hours and
   working on the system is *no* fun then).

   Example:

   00      20      *       *       sat     root \
   /etc/local/sbin/rebuild_system | mail -s "system rebuild" root \
   && sleep 300 && shutdown -r now

   Note that the rebuild_system calls a script "local_daemons" which
   cleanly shuts down running processes like postgresql, innd, ...
   But that is another story.
   You should make sure that all processes which do not like being
   killed are shut down cleanly.

That's it. Note that the scripts are useful in another manner too:
If you change your kernel config, you simply call remake_kernel
which does the work for you.
Or, another example: If you have a longer online session, you call
remake_doc, remake_cvsup and do the remake_world, remake_kernel later.

Hope that helps, Ulf

 
 
 

1. Anybody upgraded SP System from AIX4.3.3 and PSSP 3.2 to AIX5.1 and PSSP 3.4??

Hi Experts,
is there anybody running a SP System with AIX 5.1 and PSSP 3.4???

Any known problems upgrading the CWS from AIX 4.3.3 and PSSP 3.2 to
AIX 5.1 and PSSP 3.4?

I need at least 1 SP-Node at AIX 5.1 for a SAP Appl. which is only
available on AIX 5.1.

Any known Problems running a CWS on AIX 5.1 and PSSP 3.4 and some nodes
on AIX 4.3.3 and PSSP 3.2 or PSSP 3.1 and  some nodes running AIX 4.3.2 and
PSSP 2.4 (I know it's old but it still works)?

TIA
Regards
Axel

2. JDK1.3.1p6 and NetBSD-current

3. Slackware 3.3, Slackware 3.4, SC875, n_53c8xx.s bootdisk

4. 3510 FC array - disk target IDs keep changing during rebuild

5. Upgrade Slackware 3.3 to 3.4

6. Dip "mode PPP" not working with 2.0.27

7. 3.3/3.4 installation hangs after root fs mounted on MFS

8. UMSDOS filesystem check ??

9. Slackware 3.4 == 3.3!

10. SMP freeces up after 6-14 days (3.3/3.4)

11. 3.4 is not as stable as 3.3

12. How to downgrade from 3.4 to 3.3

13. FreeBSD Power Pack 3.3 and 3.4