On Thu, Aug 27, 2009 at 12:33:03AM -0700, scott mc wrote: > On Thu, Aug 27, 2009 at 12:30 AM, Stephan Assmus<superstippi@xxxxxx> wrote: > > > > On 2009-08-27 at 03:31:06 [+0200], Michael Lotz <mmlr@xxxxxxxx> wrote: > >> Hi Pete > >> > >> > I guess all one really needs to make sure is erased is the previous > >> > system hierarchy (which is what I did this time, and it seems OK). > >> > >> > Maybe the Installer could do that (warning the user first), as > >> > update-installs are likely to be fairly frequent with Haiku for a while! > >> > >> There was a discussion about that once. Not sure about the exact outcome, > >> but wipeing system is always safe (as the user is not supposed to mess > >> with it and if he does he's at fault; of course it'd still be > >> documented), wiping common and develop could be done after asking IMO. > > > > Hm. I really thought I implemented wiping the /system. And even tested > > that... I need to check, this is supposed to work. > > > > If you made that change since May, then it may just be that Pete was > using the older Installer that was on the system. And if you did make > the fix, then his next update should be smoother. Yep... Sorry to be so slow on the update (and the suggestions)... (:-/) The fix *is* in place in the newer image -- I checked. Unfortunately the update process is pretty slow with my setup (a couple of hours usually by the time I do the download, unpack it, copy it to stick, and run an Install), so I tend to put it off. And then of course I have to fix those broken links and overwritten settings from my custom changes. I'm in action again now, anyway. Cheers, -- Pete --