Issue #3197 has been updated by tse.

File upgrade added

4.8 looks good to me. Feel free to re-download and try it out

The script uses 'fetch depth=1' which reduces the initial download by ~250MB.  
But developers who want full history can do '/usr/upgrade; cd /usr/src; git 
fetch --unshallow', and sort their own lives out -- so I didn't think it was 
worth adding to the script as a flag...

If the user aborts the script in the middle of checkout, they may like to just 
delete /usr/src and try again. So I've added a warning to that effect

I realize this mini-script is unsolicited, and could easily be unwanted for 
many reasons. That's fine

My thoughts are in the future to maybe look at memory compression / malloc 
latency / auto configuring wifi. But these really are just thoughts, and not 
something for this summer

Bug #3197: DragonFly upgrades

* Author: tse
* Status: New
* Priority: Normal
* Assignee: 
* Category: Feature request
* Target version: 

I realize this is quite a simple script, and possibly misses useful features 
(?). Originally posted to @users, but mailing list line-wraping didn't keep the 
script fully intact, so copy/paste/test wouldn't of worked

Also, the response on DragonFly Digest encouraged me re-post it here

I've tested it on new installs of 4.8, 5.2, and 5.4, and with installs 
previously upgraded with `make src-create/src-create-shallow`

It takes this:
> cd /usr
> make src-create
> ...
> make buildworld
> make buildkernel
> ...
> make upgrade

To this:
> /usr/upgrade
Upgrading DragonFly BSD

For more information see:
  `man build`      `man config`
  /usr/src/README  /usr/src/UPDATING

It is possible to run this script without root privileges
Usage:  upgrade [configuration]
Configuration is "X86_64_GENERIC"

Latest releases:
  [1]  DragonFly_RELEASE_5_6
  [2]  DragonFly_RELEASE_5_4
  [3]  DragonFly_RELEASE_5_2
  [4]  DragonFly_RELEASE_5_0
  [5]  DragonFly_RELEASE_4_8

Select [1-5]:

upgrade (2.4 KB)

You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here:

Reply via email to