from 5.4-PRERELEASE -> 5.3-RELEASE-p5 error?

[Jon Noack]

On 03/11/05 15:57, Bashar wrote:
> Jon Noack wrote:
>> Bashar wrote:
>>> Doug White wrote:
>>>> On Thu, 10 Mar 2005, Bashar wrote:
>>>>> Doug White wrote:
>>>>>> On Wed, 9 Mar 2005, Bashar wrote:
>>>>>>> Hello,
>>>>>>> i was wondering just right after the downgrade been facing some 
>>>>>>> issues
>>>>>>> such as:
>>>>>>> 1. server# /usr/local/bin/strace -f ps
>>>>>>> PIOCSFL: Inappropriate ioctl for device
>>>>>>> trouble opening proc file
>>>>>>> 2. mounting ext2fs partition doesn't work unless i specify -ro or it
>>>>>>> will give operation not permitted.
>>>>>>>
>>>>>>> any idea what might be causing this?
>>>>>>
>>>>>> How did you perform the downgrade? The strace error looks like you're
>>>>>> still running the 5.3-STABLE binary.
>>>>>
>>>>> first i ran RELENG_5 and when i got the 5.4-PRERELEASE (which
>>>>> incompatible with cPanel.net software) i had to run cvsup with 
>>>>> RELENG_5_3
>>>>> after than i started getting those errors
>>>>
>>>> You're leaving out important details, like what you did after you 
>>>> cvsup'd.
>>>
>>> the usual ,cvsup'ed then cd /usr/src && make buildworld && make 
>>> installworld && cd /sys/i386/conf && config mykernel && cd 
>>> ../compile/mykernel && make depend && make && make install && reboot
>>
>> This is the usual?  You should read 
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html#AEN27432 
>> and /usr/src/UPDATING.
>>
>> The Canonical Way to Update Your System (for 5.x):
>> 1) make buildworld
>> 2) make buildkernel KERNCONF=YOUR_KERNEL_HERE
>> 3) make installkernel KERNCONF=YOUR_KERNEL_HERE
>> 4) <reboot in single user>
>> 5) /etc/rc.d/preseedrandom
>> 6) mergemaster -p
>> 7) make installworld
>> 8) mergemaster
>> 9) <reboot>
> 
> Cant do this for remote system as you know

I was merely pointing out what was the official take on "the usual". 
The general consensus for remote systems is to replace steps 4 and 5 
with "shut down as many services as possible".  This has never failed me 
for minor updates, but caution is advised for major ones.

Jon