Re: Upgrade procedure (6.4 -> 6.5)

2019-05-08 Thread Dumitru Moldovan
On Tue, May 07, 2019 at 08:15:16PM -0400, Nick Holland wrote: On 5/7/19 8:32 AM, Dumitru Moldovan wrote: On Sun, May 05, 2019 at 05:05:11PM +0200, Ingo Schwarze wrote: Hi, Consus wrote on Fri, May 03, 2019 at 02:24:10PM +0300: Maybe it's a good idea to note this on the upgrade page?

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-07 Thread Nick Holland
On 5/7/19 8:32 AM, Dumitru Moldovan wrote: > On Sun, May 05, 2019 at 05:05:11PM +0200, Ingo Schwarze wrote: >>Hi, >> >>Consus wrote on Fri, May 03, 2019 at 02:24:10PM +0300: >> >>> Maybe it's a good idea to note this on the upgrade page? Something like >>> "the upgrade procedure may leave some

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-07 Thread Ingo Schwarze
Hi Dumitru, Dumitru Moldovan wrote on Tue, May 07, 2019 at 05:33:20PM +0300: > On Sun, May 05, 2019 at 05:05:11PM +0200, Ingo Schwarze wrote: >> Consus wrote on Fri, May 03, 2019 at 02:24:10PM +0300: >>> Maybe it's a good idea to note this on the upgrade page? Something like >>> "the upgrade

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-07 Thread Dumitru Moldovan
On Sun, May 05, 2019 at 05:05:11PM +0200, Ingo Schwarze wrote: Hi, Consus wrote on Fri, May 03, 2019 at 02:24:10PM +0300: Maybe it's a good idea to note this on the upgrade page? Something like "the upgrade procedure may leave some files behing; you can manually clean them up using sysclean

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-06 Thread Wolfgang Pfeiffer
Ingo, and Everyone, On Sun, May 05, 2019 at 02:58:18PM +0200, Ingo Schwarze wrote: Hi Wolfgang, Wolfgang Pfeiffer wrote on Sat, May 04, 2019 at 06:34:04PM +0200: On Sat, May 04, 2019 at 01:07:34AM -0400, Nick Holland wrote: Spend a little time learning OpenBSD, Yes: time needed, I

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-05 Thread Ingo Schwarze
Hi, Consus wrote on Fri, May 03, 2019 at 02:24:10PM +0300: > Maybe it's a good idea to note this on the upgrade page? Something like > "the upgrade procedure may leave some files behing; you can manually > clean them up using sysclean package"? We have worse problems with the upgrade page right

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-05 Thread Otto Moerbeek
On Sat, May 04, 2019 at 10:33:26AM +0300, Strahil Nikolov wrote: > On May 4, 2019 10:11:07 AM GMT+03:00, Nick Holland > wrote: > >On 5/3/19 2:32 PM, Strahil Nikolov wrote: > >> On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland > >> wrote: > >>> On 5/2/19 1:52 AM, Consus wrote: > Hi, >

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-05 Thread Ingo Schwarze
Hi Wolfgang, Wolfgang Pfeiffer wrote on Sat, May 04, 2019 at 06:34:04PM +0200: > On Sat, May 04, 2019 at 01:07:34AM -0400, Nick Holland wrote: >> Spend a little time learning OpenBSD, > Yes: time needed, I think: Took me a while until I got that ... :) While i don't doubt it may feel like that

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-04 Thread Wolfgang Pfeiffer
On Sat, May 04, 2019 at 01:07:34AM -0400, Nick Holland wrote: On 5/3/19 2:32 PM, Strahil Nikolov wrote: On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland wrote: On 5/2/19 1:52 AM, Consus wrote: [ ... ] I tried to update a VM (stock setup) with a 10 GB disk from 6.4 to 6.5 and thus it

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-04 Thread Strahil Nikolov
On May 4, 2019 10:11:07 AM GMT+03:00, Nick Holland wrote: >On 5/3/19 2:32 PM, Strahil Nikolov wrote: >> On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland >> wrote: >>> On 5/2/19 1:52 AM, Consus wrote: Hi, I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-04 Thread Noth
On 04/05/2019 07:07, Nick Holland wrote: On 5/3/19 2:32 PM, Strahil Nikolov wrote: On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland wrote: On 5/2/19 1:52 AM, Consus wrote: Hi, I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see that /etc/networks and some other files

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-03 Thread Nick Holland
On 5/3/19 2:32 PM, Strahil Nikolov wrote: > On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland > wrote: >> On 5/2/19 1:52 AM, Consus wrote: >>> Hi, >>> >>> I've upgraded my systems from 6.4 to 6.5 without a glitch, but I >>> see that /etc/networks and some other files (like malloc.conf.5) >>>

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-03 Thread Predrag Punosevac
Strahil Nikolov wrote: > > On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland > \ > wrote: > > On 5/2/19 1:52 AM, Consus wrote: > > > Hi, > > > > > > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see > > > that /etc/networks and some other files (like malloc.conf.5) are > >

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-03 Thread Strahil Nikolov
On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland wrote: >On 5/2/19 1:52 AM, Consus wrote: >> Hi, >> >> I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see >> that /etc/networks and some other files (like malloc.conf.5) are >still >> present, although there is no use for them

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-03 Thread Steve Williams
On 02/05/2019 6:23 a.m., Stephen Gregoratto wrote: On 2019-05-02 11:46, Noth wrote: I set up a script for sysclean: cat sysclean65.txt | while read line ; do rm -rf "${line}" ; done Nitpick, but this could be shortened to: xargs rm -rf < sysclean??.txt Just tested this on my server, so

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-03 Thread Noth
On 03/05/2019 10:48, Gonzalo L. Rodriguez wrote: On Thu, 02 May 2019 at 11:46:20 +0200, Noth wrote: On 02/05/2019 11:02, Consus wrote: On 10:27 Thu 02 May, Markus Hennecke wrote: Am 02.05.2019 um 09:52 schrieb Consus: I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-03 Thread Consus
On 15:08 Thu 02 May, Ingo Schwarze wrote: > Hi Nick, > > Nick Holland wrote on Thu, May 02, 2019 at 08:04:32AM -0400: > > > There is no promise that an upgraded machine will be file-for-file > > identical to a fresh install. Here is the list of problems this might > > cause you, as you can see,

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-03 Thread Gonzalo L. Rodriguez
On Thu, 02 May 2019 at 11:46:20 +0200, Noth wrote: > > On 02/05/2019 11:02, Consus wrote: > > On 10:27 Thu 02 May, Markus Hennecke wrote: > > > Am 02.05.2019 um 09:52 schrieb Consus: > > > > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see > > > > that /etc/networks and some

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Ingo Schwarze
Hi Chris, Chris Cappuccio wrote on Thu, May 02, 2019 at 12:08:07PM -0700: > Ingo Schwarze [schwa...@usta.de] wrote: >> It might be a good idea to do >> >> # rm -rf /usr/share/man/* /usr/X11R6/man/* >> >> immediately before an upgrade. > I go one step further, and rm -rf /usr/include

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Chris Cappuccio
Ingo Schwarze [schwa...@usta.de] wrote: > > It might be a good idea to do > > # rm -rf /usr/share/man/* /usr/X11R6/man/* > > immediately before an upgrade. > I go one step further, and rm -rf /usr/include /usr/share /usr/X11R6 before a new snapshot is applied. This is a bit overkill but

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Ingo Schwarze
Hi Nick, Nick Holland wrote on Thu, May 02, 2019 at 08:04:32AM -0400: > There is no promise that an upgraded machine will be file-for-file > identical to a fresh install. Here is the list of problems this might > cause you, as you can see, it's a long list and quite horrible: > > * If you use

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Stephen Gregoratto
On 2019-05-02 11:46, Noth wrote: > I set up a script for sysclean: > > cat sysclean65.txt | while read line ; do rm -rf "${line}" ; done Nitpick, but this could be shortened to: xargs rm -rf < sysclean??.txt Just tested this on my server, so it should work fine. -- Stephen Gregoratto PGP:

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Consus
On 09:42 Thu 02 May, Stuart Henderson wrote: > The upgrade notes only list files which are likely to cause a problem > if they're left lying around. Oh, okay.

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Nick Holland
On 5/2/19 1:52 AM, Consus wrote: > Hi, > > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see > that /etc/networks and some other files (like malloc.conf.5) are still > present, although there is no use for them in the new release. > > Is there a reason why these files are not

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Noth
On 02/05/2019 11:02, Consus wrote: On 10:27 Thu 02 May, Markus Hennecke wrote: Am 02.05.2019 um 09:52 schrieb Consus: I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see that /etc/networks and some other files (like malloc.conf.5) are still present, although there is no use

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Stuart Henderson
On 2019-05-02, Consus wrote: > On 10:27 Thu 02 May, Markus Hennecke wrote: >> Am 02.05.2019 um 09:52 schrieb Consus: >> > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see >> > that /etc/networks and some other files (like malloc.conf.5) are still >> > present, although there

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Consus
On 10:27 Thu 02 May, Markus Hennecke wrote: > Am 02.05.2019 um 09:52 schrieb Consus: > > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see > > that /etc/networks and some other files (like malloc.conf.5) are still > > present, although there is no use for them in the new

Re: Upgrade procedure (6.4 -> 6.5)

2019-05-02 Thread Markus Hennecke
Am 02.05.2019 um 09:52 schrieb Consus: > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see > that /etc/networks and some other files (like malloc.conf.5) are still > present, although there is no use for them in the new release. > > Is there a reason why these files are not