On 10/17/2011 2:20 AM, Invisible wrote:
>>> Wait - YaST has documentation?
>>
>> Um, yes. man yast for starters.
>
> Surely that just tells you the command name and what switches it has?
>
>>>> OSS is big about community.
>>>
>>> That sounds very nice and all, but if I'm trying to quickly set
>>> something up, I don't really want to have to go onto the Internet and
>>> beg for help, and then spend a week or two hoping that somebody
>>> knowledgeable will just happen across my message and actually take the
>>> time to give me a helpful response. I want to read a manual that tells
>>> me how to do this RIGHT NOW.
>>
>> Right, you'd rather struggle with it for weeks and weeks and then bitch
>> about how difficult it is to do anything.
>>
>> Instead of asking a question and getting an answer within a couple of
>> days so you can actually use it.
>
> You're assuming that I'm just doing it wrong, and not that it's actually
> a poorly designed system.
>
>>>> I guess I imagined all those Technet articles that have the warning I
>>>> sited earlier about how editing the registry can screw your system up.
>>>> That must be it, because of course Microsoft would *never* recommend
>>>> you do something that might bork your system.
>>>
>>> The warning is partly there because if you're a clueless user who
>>> doesn't know how to work a computer properly, it's very easy to do a
>>> hell of a lot of damage using a registry editor. Personally, I have
>>> almost never borked my system by editing the registry. The only time
>>> it's happened is when I started deleting stuff at random in a desperate
>>> attempt to make something work. If you follow the instructions, it works
>>> fine.
>>
>> So, modifying it is dangerous. Or not. The warnings don't exist. Or
>> they do.
>>
>> Gotcha.
>
> FFS... Inexpert registry editing can screw up your system. Just like
> going into a random system folder and deleting files can screw up your
> system. If you're knowledgeable enough to not do things like that, then
> it's perfectly safe to edit the registry. (And yes, the documentation
> has warnings all over the place in case some random user types some
> stuff into Google and ends up on a technical information page telling
> you how to edit registry keys.)
>
Thankfully, you don't have to worry about this sort of thing, in the 
long run, because the lack of protections in the registry, the fact that 
everything is munged into one file, etc., pretty much makes it 
inevitable that the OS, or other products on the machine, will 
eventually edit it for you, into a state where everything stops working, 
and not even MS knows why. lol

Post a reply to this message