Once apon a time we were talking about things that were not 10 times more painful than using reg-edit I thought that was the line in the sand and we had agreed to not go below that...
OK then, the least OS in the world, MSDOS 3.1 you could edit binary using debug so there And I bet there were some people who could stuff up the machine and then use debug to trace through and fix everything... but I didn't. How many times have you mucked up your dpkg files and not had any tools available to you to edit bin. I am not trying to suggest that BIN is a good replacement for script files.. .ie you can't boot up propperly and need to fix a bootup script.. but there are some things that should be robust enough that the likelyhood of being able to muck them up is very small. The problem with the registry is that dam near everthing mucks with it how often do you muck with the dpkg files and what level of privilage is required.. When I do an apt upgrade I am root and while I am doing the update I am not doing questionable thing to make the archive fail. It appears that in DOZE every second app want's to write it's own little graffiti in the registry like it is environment space. This isn't the same as the dpkg files. Dave Nathan writes: > You only need a shell to edit a text file. Or _any_ text editor, including one running under a different OS on the same or a different machine (or a hex debugger or a disk editor, for that matter). -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null ***************************************************************** This email has been checked by the e-Sweeper Service *****************************************************************
