Upgrade succeded from 3.8 to 3.9



Ok, the first time I did some upgrades (the first one was from 3.2 to 3.3),
I ran into terrible troubles, so I have therefor just backup up data,
reinstalled with the new system, and restored data again.

But this time, I would give the upgrade from 3.8 to 3.9 a go, and in spite
of a faulty drive (read error in bsd.rd, but did an FTP on that file
afterwards), I got all the way, and system is now running 3.9. (-;

Looking at /, I get this:
boot dated jun 9
bsd dated jun 9 but...
bsd.rd is dated mar 2

Did the bsd.rd copy fail afterall? If so, how can I resolve the error?

Afterwards, I did this:
http://www.openbsd.org/faq/upgrade39.html
patch -C -p0 < upgrade39.patch

but I am not sure how to read the output. It gives me a lot of:



Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- etc/lynx.cfg Sat Sep 10 17:15:28 2005
|+++ 39/etc/lynx.cfg Wed Feb 15 19:46:16 2006
--------------------------
Patching file etc/lynx.cfg using Plan A...
Hunk #1 succeeded at 5.
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- etc/rc.conf Sat Sep 10 17:15:07 2005
|+++ 39/etc/rc.conf Wed Feb 15 19:45:58 2006
--------------------------
Patching file etc/rc.conf using Plan A...
Hunk #1 succeeded at 33.
Hunk #2 succeeded at 54.
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- etc/ssh/ssh_config Sat Sep 10 17:15:10 2005
|+++ 39/etc/ssh/ssh_config Wed Feb 15 19:46:01 2006
--------------------------
Patching file etc/ssh/ssh_config using Plan A...
Hunk #1 succeeded at 39.



that is a lot of succeded. It is not stating any errors. Can I then do a
patch -p0 < upgrade39.patch without any problems?

Is that it... is it really so simpel???

Regards, Lars.



.



Relevant Pages

  • Re: 2.6.20-rt8 patch tweaked for 2.6.20.5
    ... patching file arch/ia64/kernel/iosapic.c ... Hunk #3 succeeded at 469 with fuzz 2. ... when the 'patch' utility didnt find the 'context' of the ...
    (Linux-Kernel)
  • Re: Upgrade succeded from 3.8 to 3.9
    ... The next patch looks like a unified diff to me... ... Patching file etc/lynx.cfg using Plan A... ... Hunk #1 succeeded at 5. ...
    (comp.unix.bsd.openbsd.misc)
  • Re: [PATCH][RESEND]drivers/scsi/megaraid/megaraid_{mm,mbox}
    ... > The patch has been recreated against 2.6.11.8. ... > Please review the patch to previous driver. ... patching file Documentation/scsi/ChangeLog.megaraid ... Hunk #2 FAILED at 43. ...
    (Linux-Kernel)
  • Applying kernel patches
    ... in the kernel source directory. ... patching file arch/i386/kernel/i386_ksyms.c ... Hunk #2 FAILED at 196. ... Reversed patch detected! ...
    (Fedora)
  • Re: Regression in gdm-2.18 since 2.6.24
    ... only the second hunk of the patch seems to be making ... Sets preempt granularity for + niced tasks at 5ms ... success rate across 10 tests. ...
    (Linux-Kernel)