 |
 |
|
 |
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 09:15:07
Message: <4e904cdb@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 13:40:07 +0100, Orchid XP v8 wrote:
>>> Unix was explicitly designed to be an OS for computer experts. It
>>> assumes you know what you're doing. It provides no help or assistence
>>> of any kind. Commands print status messages only in the event of a
>>> problem. Success is indicated by silence. There are few warning
>>> prompts or confirmation messages.
>>
>> Well, yes and no. It was designed for people who work with computers,
>> yes. It does have plenty of warning prompts and confirmation messages,
>> but it does vary from program to program.
>
> I'm told part of this also dates back to the time before video displays,
> where command responses actually got printed on paper, and the
> communication was over a slow serial link.
Sure, but as the technology advances, some things have been updated when
it was deemed appropriate.
>>> Windows is explicitly designed to be used by morons. The kind of
>>> people who shouldn't even be let near anything more complicated than a
>>> doorbell.
>>
>> Ironically, Windows until recently has done a pretty piss poor job of
>> actually keeping people from injuring themselves. Why? Because Gates'
>> initial specifications were for no security.
>
> Well, in the days before computer networks, security was pretty much a
> moot point. The only way to compromise a computer is to gain physical
> access. If somebody has physical access, there's not much you can do in
> software.
Yes and no. I worked in a computer lab at university that had boot
diskettes for the network. I can tell you viruses we had didn't spread
because of the network. They couldn't; they didn't understand INT2F
redirection.
>> Windows since WinNT has had
>> to deal with backwards compatibility, and is *finally* getting to a
>> point where it's harder for a user to aim the bazooka at their foot and
>> pull the trigger.
>
> Yeah, they do tend to prioritise easy of use higher than security, which
> isn't particularly to my liking. But hey...
Ease of use and security often need to be balanced. More secure = harder
to use. Less secure = easier to use.
>> UAC is a pain in the ass for advanced users. It's a necessary
>> component for the average user.
>
> What's UAC? Is that new in Windows 7 or something? (I've only used
> Vista.)
User Access Controls, introduced in Vista IIRC.
>>> To configure a Unix program, you must manually edit text files. To
>>> configure a Windows program, you use an actual options screen, which
>>> does things like prevent you selecting invalid combinations of
>>> features, refering to non-existent paths, and so on. In the main, this
>>> is /easier/ than editing text files. You don't have to worry about
>>> mistyping things, for example.
>>
>> No. Many UNIX programs have GUIs now. You may well have heard of CDE,
>> KDE, GNOME, LXDE, Unity - all GUIs. You may also have heard of YaST,
>> Webmin, and other GUI-based (and web-based) admin tools that don't
>> require you edit text files and do let you select from a predefined
>> list.
>
> ...until you want to configure something that the GUI doesn't have an
> option for. Or you run some script which auto-configured your Apache,
> and now the shiny Apache front-end can't understand the config file any
> more and gets all confused. Or you do anything slightly advanced.
Just like with Windows and the registry. You can configure any settings
that you want, as long as the UI has them. The minute it doesn't, out
comes regedit.
Sorry, that's a straw man, and you know it.
> See, the configuration files are still the primary interface for
> configuring most stuff. The new GUI front-ends that most Linux
> distributions ship with now are exactly that - front-ends that make the
> thing look a bit more pretty. It's all too easy to break them though, or
> to end up with cryptic error messages and need to look under the hood to
> find the "real" error and how to fix it.
Hmm, and GUI frotn-ends for Windows configuration aren't anything more
than ways of modifying the registry (or in now the rare case, an INI file
somewhere)? Sorry, again, you've constructed a straw man.
> Windows programs tend to be designed around the GUI first and foremost.
> (Which isn't eithout drawbacks; it makes scripting harder, for example.)
Well, Microsoft programs tend to be. Windows programs as a whole - some
are, some aren't. I've seen some pretty crappy designs for Windows UIs
in my time. Blackberry Desktop comes to mind immediately.
>> Why do I want to configure something from the CLI? My server is
>> headless, and dedicating memory to the GUI sucks resources. So I have
>> a server that I run without a GUI at all. CLI editing is faster *if
>> you know what you're doing*.
>
> Right. That isn't something that is going to worry the average home user
> who's just trying to surf the 'net. That's something only a computer
> expert would care about. And there are various tools for doing it.
> (E.g., apparently Computer Management works remotely now. And you can
> script it.)
You know, the average home user surfing the net doesn't have to do diddly
with a Linux box either. It isn't rocket science to install a Linux
distribution these days (certainly not like when I started using it back
in the 90's), and if the system is preconfigured the way a Windows one is
(ie, installed by someone who knows what the hell they're doing), the
average computer user can be trained how to launch Firefox or Chrome and
surf the web.
>> CMD.EXE is quite useful. I still use it on Windows Server 2008R2 and
>> Windows 7 to perform filesystem operations. Why? Because I can do
>> many of those things faster with a command prompt than with a mouse.
>> Removing my hand from the keyboard and using the mouse slows me down.
>> Time is money. Wasted time is lost money.
>
> The CLI /is/ superior for certain tasks. That's why it exists, after
> all. I won't dispute that. (Although CMD.EXE is a fairly week
> implementation of the concept.)
But for many Windows users, it's what they're most familiar with.
>>> It is perfectly possible to programmatically edit the Registry.
>>> Indeed, it's /easier/ than manipulating text files. You don't have to
>>> figure out where the hell the file is stored and learn /yet another/
>>> file format. You just issue a couple of Win32 calls. All programs
>>> store their configuration data in a single, common format - the
>>> registry.
>>
>> Hmmm, so writing a program to edit the registry is faster than going to
>> / etc/apache2 and editing httpd.conf? I don't think so.
>
> Firing up RegEdit and going to the appropriate key is roughly as easy as
> opening up a text editor on your program's configuration file. The only
> real difference is that configuration files usually have actual
> documentation, whereas the registry typically doesn't.
Firing up regedit isn't "programming". Navigating through the hives to
find the right key is a freaking nightmare. Even when you know the key
you want to navigate to.
Give me a text editor and a config file *any day*. Most of those config
files have documentation in the comments. Show me a full description for
what any given registry key does *within regedit*, and then I *might*
believe that it's "as easy as editing a config file on Linux".
>>> On the down side, registry settings tend to be completely
>>> undocumented.
>>
>> Oh, and more than that, Microsoft routinely warns people *not* to edit
>> the registry if they don't know what they're doing, and most of the
>> Technet articles I've seen that include editing the registry include a
>> "proceed at your own risk" disclaimer in case you totally fuck the
>> system over with your change.
>>
>> I have yet to see a text file change on a Linux system that can hork
>> the system up as badly as Microsoft wants you to believe Windows can be
>> messed up with a single registry change.
>
> Looking at the registry is effectively like looking at every
> configuration file on your entire Linux box. Sure, /most/ settings that
> you could change won't do any harm. However, since the harmless ones are
> right next to the utterly critical ones, one wrong step can totally
> floor the system.
You're simply wrong about this. Been using Linux since the 90s, pretty
much daily, and *never* have brought a Linux system down *instantly* by
changing a config file. N.E.V.E.R.
> Possibly instantly.
On Linux? Highly unlikely.
> (Another thing about the registry:
> changes can take effect immediately. How many Linux programs "watch"
> their configuration file(s)?)
Several do. If I change the configuration file for vsftpd, for example,
or sshd, the change comes into play the next time a user connects to it.
xinetd is a wonderful thing.
>> Because with Linux it's pretty rare to have to reboot to affect the
>> change. It's sometimes easier, but to this day, I continue to be
>> amazed at how frequently a Windows system has to be restarted. Twice
>> during installation, and if you're applying system updates, sometimes
>> multiple times to get everything current (certainly with XP, later
>> versions are somewhat better).
>
> Ubuntu seems to contantly want me to reboot when I install updates too.
> I think the problem is more that Windows requires updating more often.
Only if there's a kernel update. Ubuntu may prompt more frequently
because it's more convenient and what users coming from Windows are used
to.
I've spent a fair amount of time recently installing Windows Server
2008R2 and SQL Server 2008R2 for some work I've been doing. The install
is smoother than Server 2000 and 2003, I'll grant. But still, it's in
the stone ages compared to Linux in terms of reboots.
>>> There are even tools to automate some of this. With just a factory
>>> default install of a Windows server OS, I can press a few buttons in a
>>> GUI and apply configuration settings to every Windows machine on the
>>> network. With Unix, I'd have to go off and script something.
>>
>> Wrong.
>>
>> With openSUSE, for example, I can do an installation and at the end of
>> the installation, the installer asks if I want to create an autoyast
>> file so I can clone the system or do identical installs for multiple
>> servers.
>>
>> Trivial. No scripting required.
>
> You mean WITH ONE PARTICULAR LINUX it's trivial.
Fedora also has a similar tool. I'm sure the Ubuntu Customization Kit
also is capable of something similar.
> That's just it. Windows is one product, with one set of management
> tools. The original Unix, as best as I can tell, has almost no
> management features at all. You're supposed to roll your own. So every
> major distro builder has built their own independent system of
> management tools.
The *original* Unix was built in the 60's, and much of what was true for
that is simply not true today. That would be like me saying Windows was
totally insecure because it was with Windows 1.0. Such a statement would
be complete bullshit; so is making statements about Linux based on Unix
developed in the 60's.
> If you wanted to compare how easy this is, you can't really compare
> "Windows" to "Linux". You'd have to compare "Windows" to "Debian",
> "Ubuntu", "OpenSUSE", "Fedora", ...
In reality, that is certainly true. Because we're talking about a
complete system, and "Linux" isn't. A distribution is.
But then a distribution includes things that Microsoft doesn't include -
office suites, several gigabytes of other applications, and so on.
>> Wrong, again on the Linux front. I personally know people who
>> administer *thousands* of Linux servers. I worked for a company that
>> has a product to apply updates on a schedule to remote Linux systems.
>
> A company that "makes a product" to enable you to do this.
>
> Yes, almost /any/ OS can have software written for it that makes remote
> management easy. The question is how widely available that is.
Sorry, I thought the Windows management software to manage thousands of
servers constituted a "product made by Microsoft to make managing large
scale Windows deployments easier" was a paid for product called SMS,
combined with some built-in directory features like GPOs (which of course
require Windows server - but wait, that's not free, is it?).
Oh, and that company I worked for? Also makes a tool for managing
Windows servers that's actually quite a lot better than the Windows
native tools (including arguably many of the paid-for add-ons).
>> Nope, and to state this is pretty much an uninformed opinion based on a
>> deep(er) knowledge of Windows and a lack of knowledge about modern
>> Linux systems and how they're deployed in corporate environments.
>
> I think we can summarise as follows:
>
> Unix gives you standard tools for building any kind of management
> infrastructure you can imagine. But it doesn't actually provide such an
> infrastructure by default.
Again, wrong. And if you want to talk about Unix, Unix and Linux, while
having some common tools, are not actually the same thing.
> Windows gives you one standard set of management tools, out of the box.
> If those tools don't quite cover what you want, you have a slightly
> harder problem then you would with Unix, but it's hardly intractable.
And Unix/Linux management is hardly intractable either. But to listen to
you, it's freakin' impossible - because if you don't know it, it MUST be
impossible, right?
> And, I would imagine, various individual Linux distros probably provide
> their own unique management tools. I doubt any of these work for more
> than one distro, however...
Webmin is an example of one that's cross-distribution. Oh, and the
cost? It's free - OSS. Works the same regardless of which supported
distribution it's put on.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> This is something Microsoft has always historically not seemed to
>> understand.
>
> Well, in defense of my friend at Microsoft, he was in the consulting
> organisation, and they ordered *15,000* laptops from a particular
> manufacturer just for their consultants.
>
> It's hard to understand why people have trouble affording a single hard
> drive when you buy in such bulk quantities.
Yeah, I guess that's what it comes down to.
> But he's a funny guy - actually quite cynical about the tech industry as
> a whole. He's called the whole thing a 'scam' for years.
He's right...
(And I don't just mean Windows, or Linux. I mean the entire software
industry.)
>> I understand /why/ this happens. It's just frustrating, is all. I don't
>> see why I should need to install Samba. Why can't I just install, you
>> know, the GTK+ widgets? It seems to me that Linux dependency chains are
>> just /way/ too coarse.
>
> That's because you've never spent time looking at those interdependencies.
>
> After all, on Windows, you have CIFS/SMB available on all systems by
> default. You take it for granted on Windows, but for the rest of the
> world, there is a choice.
I still don't see why it's necessary to install a network protocl just
to run a text editor.
>> OK, that's astonishing. Every attempt I've never made at upgrading an
>> existing Linux install from one distro release to another has /always/
>> ended in massive breakage, usually to the point that when I boot the
>> system the kernel just panics and stops. You would have thought clicking
>> "upgrade now" and waiting for the progress bar to finish would work, but
>> noooo...
>
> I've upgraded openSUSE from 11.0->11.1->11.2->11.4 (I gave 11.3 a miss).
Me and my dad tried updating OpenSUSE one time. After several days of
hell, we decided never to attempt this ever again.
> The worst upgrade hell I've ever heard of, though, was MS' own corporate
> upgrade from Windows Server 2000 to Windows Server 2003. I was told they
> upgraded to each incremental pre-release alpha, beta, and release
> candidate on several of their internal servers. It was a nightmare, and
> the basis of their recommendation to do rip-and-replace upgrades rather
> than in-place upgrades.
Uh, yeah. Updating Windows in-place isn't something I'd recommend
*either*...
>> Really, I'd just be happier if I could install just the functionallity
>> that's strictly necessary, rather than installing everything even
>> remotely related. Linux package manages seem to do a really poor job of
>> dependency management. (Don't get me started on when one random program
>> decides it wants a different version of the Linux kernel or
>> something...)
>
> Programs usually don't care about the kernel version, unless they're
> kernel modules (or provide them).
Or use features that are built into the kernel. (Stuff like
cryptographic primitives, sound support, file change monitoring...)
> RPM does a pretty good job of dependency management
Well, some distros use RPM, some use .deb, some use something else
entirely. I've yet to see a package manager where it's entirely clear
what the heck is going on, or why selecting one small application
requires a 2GB download.
> but you have to take care not to add too many repositories
I don't even know how to do that.
> But, in true Linux fashion, you'll get to choose the 2 remaining
> fingers. ;)
LOL.
>> Still, the problem escalates to a whole new level if you try to install
>> something /not/ available from your distro's package manager. Everybody
>> raves about how great it is that you can install everything from a big
>> old list. But you can't, of course. There will be packages that aren't
>> in the list.
>
> Actually, with openSUSE's Open Build Service, you can.
That's a nice idea. I can't comment on whether it works or not (given
tha I've never heard of it before). I guess it doesn't help if you have
time pressure - but hey, it's free...
>> Under Windows, if you want to install something, you just download it
>> and install it. Under Linux, you probably have to download a tarball,
>> work out how to unzip and untar it, figure out where the "install me
>> now" script is, and then watch as it directs you to install a different
>> version of gcc, asks where the kernel header files are, tries to
>> auto-detect the stuff it needs... It almost never works.
>
> Certainly if you don't know what you're doing, it almost never works. If
> you know what you're doing, then it almost never fails (and when it does,
> it's usually a dependency version issue or a bug in the code that
> prevents the compile from happening).
Last time I tried this with VMware tools, it went something like this:
- Where are the kernel headers?
- No, the headers for the *running* kernel?
- OK, now install gcc please.
- No, the version of gcc that the kernel was compiled with.
At that point, I discovered that the version of gcc in question isn't
available for this release of Ubuntu. WTF?
>> To the point
>> where which Linux I use on my VM depends mostly on which one has VMware
>> driver packages provided.
>
> VMware provides their own tools, but there are free (as in OSS) tools as
> well. ISTR they're included with openSUSE, in fact.
Yeah, I tried several distros, and some of them just had no VMware
support at all, some of them you could install packages for VMware as an
option [not that it explains WTF each package does], and some of them
automatically installed a bunch of VMware stuff without me even asking.
It's as if the software somehow "knows" it's running in a VM...
VMware Tools comes with a script that's supposed to compile and install
the necessary kernel modules, but I have never, ever seen it work. It
always fails. Not that I blame them; there are such radical differences
between distros that targetting all of them looks like a hopelessly
difficult task.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Yeah, they do tend to prioritise easy of use higher than security, which
>> isn't particularly to my liking. But hey...
>
> Ease of use and security often need to be balanced. More secure = harder
> to use. Less secure = easier to use.
Yeah, I'm aware of that. The other issue is backwards compatibility. If
you make the system more secure, old software tends to stop working.
(E.g., to this day Nero only works if you're an Administrator. No
reason, it's just poorly written.)
>>> UAC is a pain in the ass for advanced users. It's a necessary
>>> component for the average user.
>>
>> What's UAC? Is that new in Windows 7 or something? (I've only used
>> Vista.)
>
> User Access Controls, introduced in Vista IIRC.
Oh, OK. Maybe I just haven't run across that one yet then. I don't use
my Vista machine all that much.
>>> No. Many UNIX programs have GUIs now.
>>
>> ...until you want to configure something that the GUI doesn't have an
>> option for. Or you run some script which auto-configured your Apache,
>> and now the shiny Apache front-end can't understand the config file any
>> more and gets all confused. Or you do anything slightly advanced.
>
> Just like with Windows and the registry. You can configure any settings
> that you want, as long as the UI has them. The minute it doesn't, out
> comes regedit.
>
> Sorry, that's a straw man, and you know it.
>> See, the configuration files are still the primary interface for
>> configuring most stuff.
>
> Hmm, and GUI frotn-ends for Windows configuration aren't anything more
> than ways of modifying the registry (or in now the rare case, an INI file
> somewhere)? Sorry, again, you've constructed a straw man.
It's a mentality difference, not a technological one.
Under Unix, the primary way to control most software is through
configuration files. These days Linux has added pretty front-ends to
some of these systems, but they tend to be designed only for the people
who aren't smart enough to use the "real" interface - i.e., edit the
text fails manually.
Under Windows, the GUI is the "real" interface. The configuration data
is stored in the registry, but you're not supposed to edit it directly.
You're supposed to go to the GUI first. Therefore, much more effort it
put into making the GUI cover everything. (And far less effort is put
into making the registry data human-readable, or even documented.)
It's just about where the developers focus their attention. Under Unix,
the configuration file is the definite interface. Under Windows, the GUI
is. (Or possibly the COM interface. But I don't know much about that one...)
>> Windows programs tend to be designed around the GUI first and foremost.
>
> Well, Microsoft programs tend to be. Windows programs as a whole - some
> are, some aren't. I've seen some pretty crappy designs for Windows UIs
> in my time. Blackberry Desktop comes to mind immediately.
Oh yeah, but /all/ platforms have crappy software. Heck, when I tried
KLogic, its simulations sometimes GAVE THE WRONG ANSWER. And frequently,
just tweaking a few lines would crash the problem. So much for OSS
always being of high quality... In truth, crap software exists
everywhere. The interesting question is where the /good/ software is.
>>> Why do I want to configure something from the CLI? My server is
>>> headless, and dedicating memory to the GUI sucks resources.
>>
>> Right. That isn't something that is going to worry the average home user
>> who's just trying to surf the 'net.
>
> You know, the average home user surfing the net doesn't have to do diddly
> with a Linux box either.
Sure. But that isn't the point. The point is that how powerful the CLI
interface is only matters to power users. Which isn't who Windows is
primarily aimed at.
>> The CLI /is/ superior for certain tasks. That's why it exists, after
>> all. I won't dispute that. (Although CMD.EXE is a fairly week
>> implementation of the concept.)
>
> But for many Windows users, it's what they're most familiar with.
Granted.
>> Firing up RegEdit and going to the appropriate key is roughly as easy as
>> opening up a text editor on your program's configuration file.
>
> Firing up regedit isn't "programming". Navigating through the hives to
> find the right key is a freaking nightmare. Even when you know the key
> you want to navigate to.
No more nightmarish than navigating to a particular file. You just click
on a tree view. Just like a file browser.
> Give me a text editor and a config file *any day*. Most of those config
> files have documentation in the comments. Show me a full description for
> what any given registry key does *within regedit*, and then I *might*
> believe that it's "as easy as editing a config file on Linux".
Like I said, it's not the primary interface. You're supposed to use it
only as a last resort. I'll admit I'd like it a lot more if there was
more documentation for the registry.
>>> I have yet to see a text file change on a Linux system that can hork
>>> the system up as badly as Microsoft wants you to believe Windows can be
>>> messed up with a single registry change.
>>
>> Looking at the registry is effectively like looking at every
>> configuration file on your entire Linux box. Sure, /most/ settings that
>> you could change won't do any harm. However, since the harmless ones are
>> right next to the utterly critical ones, one wrong step can totally
>> floor the system.
>
> You're simply wrong about this. Been using Linux since the 90s, pretty
> much daily, and *never* have brought a Linux system down *instantly* by
> changing a config file. N.E.V.E.R.
You've misparsed what I wrote. I meant that getting the Windows registry
wrong can down Windows instantly. I very much doubt you could do
anything similar to Linux.
>> (Another thing about the registry:
>> changes can take effect immediately. How many Linux programs "watch"
>> their configuration file(s)?)
>
> Several do. If I change the configuration file for vsftpd, for example,
> or sshd, the change comes into play the next time a user connects to it.
> xinetd is a wonderful thing.
Interesting. I'm pretty sure I had to send SIG_HUP (or whatever it is)
to sshd to get it to notice that I just turned off password
authentication...
[Let's not even get into the fact that the registry is transactional,
while text files aren't. Or that it supports storing binary blobs
relatively efficiently...]
>> Ubuntu seems to contantly want me to reboot when I install updates too.
>> I think the problem is more that Windows requires updating more often.
>
> Only if there's a kernel update. Ubuntu may prompt more frequently
> because it's more convenient and what users coming from Windows are used
> to.
That's just ironic. Doing something defective because that's how Windows
does it. Ha!
> I've spent a fair amount of time recently installing Windows Server
> 2008R2 and SQL Server 2008R2 for some work I've been doing. The install
> is smoother than Server 2000 and 2003, I'll grant. But still, it's in
> the stone ages compared to Linux in terms of reboots.
AFAIK, you boot the CD, do the text-mode bit, reboot into GUI mode,
reboot one final time, and you're done. That's, like, 2 reboots. Hardly
excessive...
>> That's just it. Windows is one product, with one set of management
>> tools. The original Unix, as best as I can tell, has almost no
>> management features at all. You're supposed to roll your own. So every
>> major distro builder has built their own independent system of
>> management tools.
>
> The *original* Unix was built in the 60's, and much of what was true for
> that is simply not true today. That would be like me saying Windows was
> totally insecure because it was with Windows 1.0. Such a statement would
> be complete bullshit; so is making statements about Linux based on Unix
> developed in the 60's.
It's also true that people write software that targets "Unix". It
expects standard Unix tools like make, patch, cc and so forth, and it
builds from source. The original Unix flavour provides all these tools,
but it doesn't provide much in the way of pre-build, widely standardised
management features. (Partly, as I presume you're hinting, because when
Unix was new, PCs didn't exist yet. If you have one computer, what do
you need remote management for?)
>> If you wanted to compare how easy this is, you can't really compare
>> "Windows" to "Linux". You'd have to compare "Windows" to "Debian",
>> "Ubuntu", "OpenSUSE", "Fedora", ...
>
> In reality, that is certainly true. Because we're talking about a
> complete system, and "Linux" isn't. A distribution is.
>
> But then a distribution includes things that Microsoft doesn't include -
> office suites, several gigabytes of other applications, and so on.
That I will grant you. Originally Windows was literally just an OS with
a text editor. If you wanted to get /anything/ done, you had to pay
money to install more software. (That's slowly changing of course. Now
you have a web browser and a movie player and even video editing built
in, and everybody screaming "monopoly!"...)
>> Windows gives you one standard set of management tools, out of the box.
>> If those tools don't quite cover what you want, you have a slightly
>> harder problem then you would with Unix, but it's hardly intractable.
>
> And Unix/Linux management is hardly intractable either. But to listen to
> you, it's freakin' impossible - because if you don't know it, it MUST be
> impossible, right?
That isn't what I'm trying to say.
You said "Windows stores everything in the registry, which means you
can't do any management stuff on it like you can with Linux". I'm
demonstrating that, no, that's not the case at all. You might not be
able to grep a text file and run sed over it to effect a configuration
change, but you also don't /need/ to with Windows. There are other ways
to reach the same goal - many of them easier than Unix shell scripting...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 10:32:14
Message: <4e905eee@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 15:05:45 +0100, Orchid XP v8 wrote:
>>> Yeah, they do tend to prioritise easy of use higher than security,
>>> which isn't particularly to my liking. But hey...
>>
>> Ease of use and security often need to be balanced. More secure =
>> harder to use. Less secure = easier to use.
>
> Yeah, I'm aware of that. The other issue is backwards compatibility. If
> you make the system more secure, old software tends to stop working.
> (E.g., to this day Nero only works if you're an Administrator. No
> reason, it's just poorly written.)
Yep, backwards compatibility does become an issue as well.
>>>> UAC is a pain in the ass for advanced users. It's a necessary
>>>> component for the average user.
>>>
>>> What's UAC? Is that new in Windows 7 or something? (I've only used
>>> Vista.)
>>
>> User Access Controls, introduced in Vista IIRC.
>
> Oh, OK. Maybe I just haven't run across that one yet then. I don't use
> my Vista machine all that much.
IIRC, it's kinda forced upon you. In Win7, you can disable it pretty
easily, but it's pretty hard to miss.
>> Hmm, and GUI frotn-ends for Windows configuration aren't anything more
>> than ways of modifying the registry (or in now the rare case, an INI
>> file somewhere)? Sorry, again, you've constructed a straw man.
>
> It's a mentality difference, not a technological one.
Yes, that is certainly true.
> Under Unix, the primary way to control most software is through
> configuration files. These days Linux has added pretty front-ends to
> some of these systems, but they tend to be designed only for the people
> who aren't smart enough to use the "real" interface - i.e., edit the
> text fails manually.
Well, yes and no. Users of SUSE products (openSUSE and SLE*) often do
know how to do the manual edits, but prefer using YaST anyways.
> Under Windows, the GUI is the "real" interface. The configuration data
> is stored in the registry, but you're not supposed to edit it directly.
Except for when there's no other way.
> You're supposed to go to the GUI first. Therefore, much more effort it
> put into making the GUI cover everything. (And far less effort is put
> into making the registry data human-readable, or even documented.)
Well, again, yes and no. On Linux, some developers do put a lot of
effort into hiding the backend. Look at compizconfig, for example (not
simple-ccsm, but the full configuration tool). It can write its
configuration to the flat file config file, or to a gconf backend, which
in some ways mimics a registry. The intention is that users modify the
config through the tool and not by editing the files directly.
In openSUSE and SLE, there are in fact several files that are explicitly
commented with "DO NOT EDIT THIS FILE DIRECTLY".
> It's just about where the developers focus their attention. Under Unix,
> the configuration file is the definite interface. Under Windows, the GUI
> is. (Or possibly the COM interface. But I don't know much about that
> one...)
Well, again, on Linux it depends.
Just like on Windows it used to depend on whether the developer wrote an
INI file or used the registry.
>>> Windows programs tend to be designed around the GUI first and
>>> foremost.
>>
>> Well, Microsoft programs tend to be. Windows programs as a whole -
>> some are, some aren't. I've seen some pretty crappy designs for
>> Windows UIs in my time. Blackberry Desktop comes to mind immediately.
>
> Oh yeah, but /all/ platforms have crappy software. Heck, when I tried
> KLogic, its simulations sometimes GAVE THE WRONG ANSWER. And frequently,
> just tweaking a few lines would crash the problem. So much for OSS
> always being of high quality... In truth, crap software exists
> everywhere. The interesting question is where the /good/ software is.
Well, look at OpenOffice or LibreOffice. Those are not programs designed
for the geek, they're designed for the casual user. You can't lump all
programs on Linux in one category and all programs on Windows in the
other - there's crossover.
>>>> Why do I want to configure something from the CLI? My server is
>>>> headless, and dedicating memory to the GUI sucks resources.
>>>
>>> Right. That isn't something that is going to worry the average home
>>> user who's just trying to surf the 'net.
>>
>> You know, the average home user surfing the net doesn't have to do
>> diddly with a Linux box either.
>
> Sure. But that isn't the point. The point is that how powerful the CLI
> interface is only matters to power users. Which isn't who Windows is
> primarily aimed at.
Yes, but on the one hand you're arguing about the average home user
there. Detailed configuration isn't something they need to worry about
on *either* platform.
>>> Firing up RegEdit and going to the appropriate key is roughly as easy
>>> as opening up a text editor on your program's configuration file.
>>
>> Firing up regedit isn't "programming". Navigating through the hives to
>> find the right key is a freaking nightmare. Even when you know the key
>> you want to navigate to.
>
> No more nightmarish than navigating to a particular file. You just click
> on a tree view. Just like a file browser.
No need for a file browser with CLI in Linux (though if you want, you can
use something like mc). I've navigated the /etc directory on Linux, and
I've navigated the registry on several versions of Windows (including the
most recent non-beta releases). I'll take the /etc directory any day.
>> Give me a text editor and a config file *any day*. Most of those
>> config files have documentation in the comments. Show me a full
>> description for what any given registry key does *within regedit*, and
>> then I *might* believe that it's "as easy as editing a config file on
>> Linux".
>
> Like I said, it's not the primary interface. You're supposed to use it
> only as a last resort. I'll admit I'd like it a lot more if there was
> more documentation for the registry.
And with openSUSE, editing the files directly is a last resort as well,
with YaST being the preferred and recommended tool.
>> You're simply wrong about this. Been using Linux since the 90s, pretty
>> much daily, and *never* have brought a Linux system down *instantly* by
>> changing a config file. N.E.V.E.R.
>
> You've misparsed what I wrote. I meant that getting the Windows registry
> wrong can down Windows instantly. I very much doubt you could do
> anything similar to Linux.
OK, I guess I did. Hey, it was 7:15 AM here and I've been up all
night. ;)
>> Several do. If I change the configuration file for vsftpd, for
>> example, or sshd, the change comes into play the next time a user
>> connects to it. xinetd is a wonderful thing.
>
> Interesting. I'm pretty sure I had to send SIG_HUP (or whatever it is)
> to sshd to get it to notice that I just turned off password
> authentication...
Just like in Windows, it depends on the program, and how long ago. You
may have noticed that Linux development isn't exactly stagnant.
> [Let's not even get into the fact that the registry is transactional,
> while text files aren't. Or that it supports storing binary blobs
> relatively efficiently...]
Transactionality is a function of the filesystem, and I use a journaled
filesystem.
And I've yet to see anything more effective than a binary blob as a
file. It's just inconvenient to use binary data when the primary purpose
of configuration files is for them not to be obscured.
>>> Ubuntu seems to contantly want me to reboot when I install updates
>>> too. I think the problem is more that Windows requires updating more
>>> often.
>>
>> Only if there's a kernel update. Ubuntu may prompt more frequently
>> because it's more convenient and what users coming from Windows are
>> used to.
>
> That's just ironic. Doing something defective because that's how Windows
> does it. Ha!
Sometimes distros choose that route because it's just easier than
educating the user. I would prefer if they educated the user instead.
>> I've spent a fair amount of time recently installing Windows Server
>> 2008R2 and SQL Server 2008R2 for some work I've been doing. The
>> install is smoother than Server 2000 and 2003, I'll grant. But still,
>> it's in the stone ages compared to Linux in terms of reboots.
>
> AFAIK, you boot the CD, do the text-mode bit, reboot into GUI mode,
> reboot one final time, and you're done. That's, like, 2 reboots. Hardly
> excessive...
On an openSUSE installation, you boot the DVD, do the installation, and
then it boots the installed kernel. In most situations, it doesn't POST
the machine again before it's up and running.
But then start applying patches on Windows. To get 2008R2 current,
that's probably 2-3 more reboots.
Doing the same on my openSUSE boxes, it's one reboot. Period. *If*
there's a kernel update.
>>> That's just it. Windows is one product, with one set of management
>>> tools. The original Unix, as best as I can tell, has almost no
>>> management features at all. You're supposed to roll your own. So every
>>> major distro builder has built their own independent system of
>>> management tools.
>>
>> The *original* Unix was built in the 60's, and much of what was true
>> for that is simply not true today. That would be like me saying
>> Windows was totally insecure because it was with Windows 1.0. Such a
>> statement would be complete bullshit; so is making statements about
>> Linux based on Unix developed in the 60's.
>
> It's also true that people write software that targets "Unix". It
> expects standard Unix tools like make, patch, cc and so forth, and it
> builds from source. The original Unix flavour provides all these tools,
> but it doesn't provide much in the way of pre-build, widely standardised
> management features. (Partly, as I presume you're hinting, because when
> Unix was new, PCs didn't exist yet. If you have one computer, what do
> you need remote management for?)
You clearly haven't looked at how Linux code development is done with
modern package management.
>>> If you wanted to compare how easy this is, you can't really compare
>>> "Windows" to "Linux". You'd have to compare "Windows" to "Debian",
>>> "Ubuntu", "OpenSUSE", "Fedora", ...
>>
>> In reality, that is certainly true. Because we're talking about a
>> complete system, and "Linux" isn't. A distribution is.
>>
>> But then a distribution includes things that Microsoft doesn't include
>> - office suites, several gigabytes of other applications, and so on.
>
> That I will grant you. Originally Windows was literally just an OS with
> a text editor. If you wanted to get /anything/ done, you had to pay
> money to install more software. (That's slowly changing of course. Now
> you have a web browser and a movie player and even video editing built
> in, and everybody screaming "monopoly!"...)
Slightly different situation when the manufacturer is extorting OEMs to
pre-install Windows on every machine they ship (and charge for a license
regardless of whether they ship Windows or not). That actually is an
abuse of monopoly power; the US Antitrust trial found that, and so did
the EC's investigation.
>>> Windows gives you one standard set of management tools, out of the
>>> box. If those tools don't quite cover what you want, you have a
>>> slightly harder problem then you would with Unix, but it's hardly
>>> intractable.
>>
>> And Unix/Linux management is hardly intractable either. But to listen
>> to you, it's freakin' impossible - because if you don't know it, it
>> MUST be impossible, right?
>
> That isn't what I'm trying to say.
>
> You said "Windows stores everything in the registry, which means you
> can't do any management stuff on it like you can with Linux". I'm
> demonstrating that, no, that's not the case at all. You might not be
> able to grep a text file and run sed over it to effect a configuration
> change, but you also don't /need/ to with Windows. There are other ways
> to reach the same goal - many of them easier than Unix shell
> scripting...
You don't seem to understand that Unix shell scripting is one tool of a
variety of tools available.
If you know bash better than powershell, then how exactly is bash more
difficult than powershell?
(The converse is also true)
BTW, those management tools we were talking about my former employer
selling? Turns out there's actually a free suite as well. Relatively
recent release, so I don't know all the details. But it is cross-
distribution too IIRC.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 10:42:47
Message: <4e906167@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 14:44:07 +0100, Orchid XP v8 wrote:
>>> This is something Microsoft has always historically not seemed to
>>> understand.
>>
>> Well, in defense of my friend at Microsoft, he was in the consulting
>> organisation, and they ordered *15,000* laptops from a particular
>> manufacturer just for their consultants.
>>
>> It's hard to understand why people have trouble affording a single hard
>> drive when you buy in such bulk quantities.
>
> Yeah, I guess that's what it comes down to.
That's probably a significant part of it.
>> But he's a funny guy - actually quite cynical about the tech industry
>> as a whole. He's called the whole thing a 'scam' for years.
>
> He's right...
>
> (And I don't just mean Windows, or Linux. I mean the entire software
> industry.)
He didn't mean just Windows or Linux either. And he's been around the
software industry for longer than either of us.
>>> I understand /why/ this happens. It's just frustrating, is all. I
>>> don't see why I should need to install Samba. Why can't I just
>>> install, you know, the GTK+ widgets? It seems to me that Linux
>>> dependency chains are just /way/ too coarse.
>>
>> That's because you've never spent time looking at those
>> interdependencies.
>>
>> After all, on Windows, you have CIFS/SMB available on all systems by
>> default. You take it for granted on Windows, but for the rest of the
>> world, there is a choice.
>
> I still don't see why it's necessary to install a network protocl just
> to run a text editor.
That's because you're not grokking the similarities between Windows and
Linux.
Seriously.
Try installing Notepad on Windows without installing Windows Networking.
Oh, you can't do that. Why? Because Windows Networking is an integrated
component of the operating system.
Guess what - it's also an integrated component of GNOME, because
interoperability matters.
>>> OK, that's astonishing. Every attempt I've never made at upgrading an
>>> existing Linux install from one distro release to another has /always/
>>> ended in massive breakage, usually to the point that when I boot the
>>> system the kernel just panics and stops. You would have thought
>>> clicking "upgrade now" and waiting for the progress bar to finish
>>> would work, but noooo...
>>
>> I've upgraded openSUSE from 11.0->11.1->11.2->11.4 (I gave 11.3 a
>> miss).
>
> Me and my dad tried updating OpenSUSE one time. After several days of
> hell, we decided never to attempt this ever again.
It's a shame you didn't come over to the forums and ask for some help.
>> The worst upgrade hell I've ever heard of, though, was MS' own
>> corporate upgrade from Windows Server 2000 to Windows Server 2003. I
>> was told they upgraded to each incremental pre-release alpha, beta, and
>> release candidate on several of their internal servers. It was a
>> nightmare, and the basis of their recommendation to do rip-and-replace
>> upgrades rather than in-place upgrades.
>
> Uh, yeah. Updating Windows in-place isn't something I'd recommend
> *either*...
I generally wouldn't recommend it for any OS, but it can be a bit easier
with Linux if your /home partition is separate from the rest of the
system. Worst case, you do a fresh install of the root partition and
leave the /home data alone.
>>> Really, I'd just be happier if I could install just the functionallity
>>> that's strictly necessary, rather than installing everything even
>>> remotely related. Linux package manages seem to do a really poor job
>>> of dependency management. (Don't get me started on when one random
>>> program decides it wants a different version of the Linux kernel or
>>> something...)
>>
>> Programs usually don't care about the kernel version, unless they're
>> kernel modules (or provide them).
>
> Or use features that are built into the kernel. (Stuff like
> cryptographic primitives, sound support, file change monitoring...)
Depends on the ABI in question. Many of them are fairly stable, but some
are not.
>> RPM does a pretty good job of dependency management
>
> Well, some distros use RPM, some use .deb, some use something else
> entirely. I've yet to see a package manager where it's entirely clear
> what the heck is going on, or why selecting one small application
> requires a 2GB download.
Well, again, it comes down to understanding the interdependencies, rather
than throwing your hands up in the air and saying "it's too damned
complex for anyone to understand."
>> but you have to take care not to add too many repositories
>
> I don't even know how to do that.
In openSUSE:
sudo yast2 repositories
>> But, in true Linux fashion, you'll get to choose the 2 remaining
>> fingers. ;)
>
> LOL.
I figured some humour was called for. :)
>>> Still, the problem escalates to a whole new level if you try to
>>> install something /not/ available from your distro's package manager.
>>> Everybody raves about how great it is that you can install everything
>>> from a big old list. But you can't, of course. There will be packages
>>> that aren't in the list.
>>
>> Actually, with openSUSE's Open Build Service, you can.
>
> That's a nice idea. I can't comment on whether it works or not (given
> tha I've never heard of it before). I guess it doesn't help if you have
> time pressure - but hey, it's free...
It's free, and you can be damned sure it works. It's been out there for
a few years.
>>> Under Windows, if you want to install something, you just download it
>>> and install it. Under Linux, you probably have to download a tarball,
>>> work out how to unzip and untar it, figure out where the "install me
>>> now" script is, and then watch as it directs you to install a
>>> different version of gcc, asks where the kernel header files are,
>>> tries to auto-detect the stuff it needs... It almost never works.
>>
>> Certainly if you don't know what you're doing, it almost never works.
>> If you know what you're doing, then it almost never fails (and when it
>> does, it's usually a dependency version issue or a bug in the code that
>> prevents the compile from happening).
>
> Last time I tried this with VMware tools, it went something like this: -
> Where are the kernel headers?
> - No, the headers for the *running* kernel? - OK, now install gcc
> please.
> - No, the version of gcc that the kernel was compiled with. At that
> point, I discovered that the version of gcc in question isn't available
> for this release of Ubuntu. WTF?
I can't speak to Ubuntu. openSUSE has a pretty strict "no kernel
upgrades" policy within a particular version. (That doesn't mean "no
updates" - security updates are backported by the openSUSE kernel team,
and important enhancements frequently are as well AFAIK). That means
it's incredibly rare to have to deal with something like that with VMware
once it's working.
>>> To the point
>>> where which Linux I use on my VM depends mostly on which one has
>>> VMware driver packages provided.
>>
>> VMware provides their own tools, but there are free (as in OSS) tools
>> as well. ISTR they're included with openSUSE, in fact.
>
> Yeah, I tried several distros, and some of them just had no VMware
> support at all, some of them you could install packages for VMware as an
> option [not that it explains WTF each package does], and some of them
> automatically installed a bunch of VMware stuff without me even asking.
> It's as if the software somehow "knows" it's running in a VM...
>
> VMware Tools comes with a script that's supposed to compile and install
> the necessary kernel modules, but I have never, ever seen it work. It
> always fails. Not that I blame them; there are such radical differences
> between distros that targetting all of them looks like a hopelessly
> difficult task.
I've seen it fail, but I've seen it succeed more often than not.
It's a shame you don't ask questions in the Linux forums related to the
distribution you use. Those issues are often easily resolved, and
novices can get help instead of just bitching "this damned stuff never
works right!"
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Under Unix, the primary way to control most software is through
>> configuration files. These days Linux has added pretty front-ends to
>> some of these systems, but they tend to be designed only for the people
>> who aren't smart enough to use the "real" interface - i.e., edit the
>> text fails manually.
>
> Well, yes and no. Users of SUSE products (openSUSE and SLE*) often do
> know how to do the manual edits, but prefer using YaST anyways.
If you pull up the documentation for (say) Apache, it won't tell you how
to use the Apache YaST module. It will tell you how to edit the
underlying text file. And if something doesn't work right, and you can't
figure it out from YaST, you'll have to look under the covers to see
what it's written in the configuration file, to see why Apache isn't
doing what you want.
>> Under Windows, the GUI is the "real" interface. The configuration data
>> is stored in the registry, but you're not supposed to edit it directly.
>
> Except for when there's no other way.
Except that this almost never happens. That's the entire point. Most
Linux front-ends seem to be tacked on afterwards, whereas on Windows,
the GUI is the primary focus.
> In openSUSE and SLE, there are in fact several files that are explicitly
> commented with "DO NOT EDIT THIS FILE DIRECTLY".
I thought that's just code for "this file is autogenerated from some
other configuration file - you should go edit that instead".
>> It's just about where the developers focus their attention. Under Unix,
>> the configuration file is the definite interface.
>
> Well, again, on Linux it depends.
OK. But certainly most Linux uses seem to have the opinion of "GUI? Pah!
We don't need that. That's just for n00bs who don't know what they're
doing..." (Whether this attitude applies to most /developers/ is more
debatable.)
>> Oh yeah, but /all/ platforms have crappy software.
>
> Well, look at OpenOffice or LibreOffice. Those are not programs designed
> for the geek, they're designed for the casual user. You can't lump all
> programs on Linux in one category and all programs on Windows in the
> other - there's crossover.
Sure. But most programs seem to be primarily Unix or primarily Windows.
POV-Ray: The Windows version has a full IDE. All the other versions are
just the rendering engine.
Apache: It runs everywhere, but it's clearly designed in the mould of a
Unix daemon process.
CUPS: It's available for Windows. But it has "Unix" right there in the name.
>> No more nightmarish than navigating to a particular file. You just click
>> on a tree view. Just like a file browser.
>
> No need for a file browser with CLI in Linux (though if you want, you can
> use something like mc). I've navigated the /etc directory on Linux, and
> I've navigated the registry on several versions of Windows (including the
> most recent non-beta releases). I'll take the /etc directory any day.
Well, each to their own...
>> You've misparsed what I wrote.
>
> OK, I guess I did. Hey, it was 7:15 AM here and I've been up all
> night. ;)
This is not a good thing.
>> Interesting. I'm pretty sure I had to send SIG_HUP (or whatever it is)
>> to sshd to get it to notice that I just turned off password
>> authentication...
>
> Just like in Windows, it depends on the program, and how long ago. You
> may have noticed that Linux development isn't exactly stagnant.
I notice that there's always a lot of stuff "happening" with Linux. I'm
never sure what the hell any of it actually /does/. As far as I can
tell, the difference between each release of any given Linux distro is
that the colour scheme is different, and some of the default options
have changed. I'm sure there must be more to it than that, but...
(A simliar thing could be said about MS Office, of course.)
>> [Let's not even get into the fact that the registry is transactional,
>> while text files aren't. Or that it supports storing binary blobs
>> relatively efficiently...]
>
> Transactionality is a function of the filesystem, and I use a journaled
> filesystem.
Doesn't stop two scripts both trying to update the same config file at
the same time. If you do that with the registry, it works. Because it's
a proper database engine, not just a flat file.
>> That's just ironic. Doing something defective because that's how Windows
>> does it. Ha!
>
> Sometimes distros choose that route because it's just easier than
> educating the user. I would prefer if they educated the user instead.
I guess it isn't just MS that makes poor choices in the name of keeping
users...
>> AFAIK, you boot the CD, do the text-mode bit, reboot into GUI mode,
>> reboot one final time, and you're done. That's, like, 2 reboots. Hardly
>> excessive...
>
> But then start applying patches on Windows. To get 2008R2 current,
> that's probably 2-3 more reboots.
OK, fair enough.
Personally, I'm not very impressed by the Windows Update system. Like,
it'll install a bazillion updates for IE6 in the same session as it also
installs IE8. And then you go back and it wants to install a bunch of
IE8 updates. Um, why couldn't you do that the first time around??
>> That I will grant you. Originally Windows was literally just an OS with
>> a text editor. If you wanted to get /anything/ done, you had to pay
>> money to install more software. (That's slowly changing of course. Now
>> you have a web browser and a movie player and even video editing built
>> in, and everybody screaming "monopoly!"...)
>
> Slightly different situation when the manufacturer is extorting OEMs to
> pre-install Windows on every machine they ship (and charge for a license
> regardless of whether they ship Windows or not). That actually is an
> abuse of monopoly power; the US Antitrust trial found that, and so did
> the EC's investigation.
I love how multiple courts have proved that what MS is doing is illegal,
and as a result they have received NO PUNISHMENT OF ANY KIND. That's
such a big motivation for them to stop casually disregarding the law...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> I still don't see why it's necessary to install a network protocl just
>> to run a text editor.
>
> That's because you're not grokking the similarities between Windows and
> Linux.
>
> Seriously.
>
> Try installing Notepad on Windows without installing Windows Networking.
>
> Oh, you can't do that. Why? Because Windows Networking is an integrated
> component of the operating system.
>
> Guess what - it's also an integrated component of GNOME, because
> interoperability matters.
The irony is, you actually /can/ uninstall Windows networking (and even
the TCP/IP protocol). And Notepad still works. :-P
Plus, installing Windows isn't a 4GB download. Honestly, I can remember
a time when all the Linux fanboys used to shout about how much leaner
Linux is than Windows. Today a default install of most distros either
involves DVDs or multi-GB downloads. It installs everything *and* the
kitchen sink, and when I want to use a different text editor it *still*
wants to download another couple of GB of data. ENOUGH ALREADY! >_<
>> Me and my dad tried updating OpenSUSE one time. After several days of
>> hell, we decided never to attempt this ever again.
>
> It's a shame you didn't come over to the forums and ask for some help.
Wouldn't that require me to figure out how to display IPv6 so that
Firefox works again?
>> Uh, yeah. Updating Windows in-place isn't something I'd recommend
>> *either*...
>
> I generally wouldn't recommend it for any OS, but it can be a bit easier
> with Linux if your /home partition is separate from the rest of the
> system. Worst case, you do a fresh install of the root partition and
> leave the /home data alone.
Same works for any OS.
(The only real difference is that since Unix has mount points rather
than drive letters, you don't have this stupidity of applications which
/assume/ your home folder is on partition #1...)
>>> RPM does a pretty good job of dependency management
>>
>> Well, some distros use RPM, some use .deb, some use something else
>> entirely. I've yet to see a package manager where it's entirely clear
>> what the heck is going on, or why selecting one small application
>> requires a 2GB download.
>
> Well, again, it comes down to understanding the interdependencies, rather
> than throwing your hands up in the air and saying "it's too damned
> complex for anyone to understand."
How about spending several years working with Linux and still not being
able to get it to work right. Does that count? :-P
>>> but you have to take care not to add too many repositories
>>
>> I don't even know how to do that.
>
> In openSUSE: sudo yast2 repositories
OK. But the fact that I don't know how to do it demonstrates fairly
conclusively that that isn't the problem I had.
>> Last time I tried this with VMware tools, it went something like this: -
>> Where are the kernel headers?
>> - No, the headers for the *running* kernel? - OK, now install gcc
>> please.
>> - No, the version of gcc that the kernel was compiled with. At that
>> point, I discovered that the version of gcc in question isn't available
>> for this release of Ubuntu. WTF?
>
> I can't speak to Ubuntu. openSUSE has a pretty strict "no kernel
> upgrades" policy within a particular version. (That doesn't mean "no
> updates" - security updates are backported by the openSUSE kernel team,
> and important enhancements frequently are as well AFAIK). That means
> it's incredibly rare to have to deal with something like that with VMware
> once it's working.
I think I tried it with Debian and Fedora as well. Can't remember if I
tried OpenSUSE.
This sort of thing tends to be typical of /any/ attempt to install
something that isn't packaged. And even if the website has an RPM or a
.deb, usually that just flips the package manager out because all the
dependencies are wrong...
> It's a shame you don't ask questions in the Linux forums related to the
> distribution you use. Those issues are often easily resolved, and
> novices can get help instead of just bitching "this damned stuff never
> works right!"
Yes, because I want to sign up to /yet another/ online forum just to
make one piece of software install cleanly...
As I say, I generally just stick to Windows. When you install stuff, it
just works.
(Not that I'm completely unsympathetic, you understand. "Linux" is one
hell of a big moving target to try to hit...)
I love how I'm the biggest Microsoft-hater ever, and I've ended up
defending Windows. When Linux came out, I really thought it was going to
be the answer. Turns out it just brought a different set of problems...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 2:27, Orchid XP v8 wrote:
> On 07/10/2011 11:45 PM, Darren New wrote:
>> On 10/7/2011 7:36, Invisible wrote:
>>> I'm fairly sure Office v2 had that. I may be wrong. Certainly Office 97
>>> definitely had that. And that was, what, 14 years ago?
>>
>> Pretty sure they didn't have .NET integration,
>
> No. But how is that useful?
It's useful for people trying to script Office apps from (say) PowerShell.
Or from any other .NET-enabled language. It's useful in the same way that
.NET stored procedures are useful in SQL.
>> integration with SQL server,
>
> I'm fairly sure Office 97 quite happily let you connect to any database with
> an ODBC driver. (That's kind of the whole point of ODBC.)
I wasn't aware they had actually let macros get to that.
>> or cooperative shared editting.
>
> It's news to me that /any/ version of Office has that.
That's kind of my point.
>>> In fairness, I'm not aware of anything else that does what Outlook and
>>> Exchange do.
>>
>> And that is why the world still runs Microsoft. :-)
>
> Well, no, that's /one of/ the reasons...
Fair enough. But I think that's one of the *main* reasons small businesses
without a bunch of money still use it on the desktop.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 2:29, Orchid XP v8 wrote:
> On 08/10/2011 05:34 AM, Darren New wrote:
>> On 10/7/2011 20:54, Jim Henderson wrote:
>>> Architecturally they're fairly different, though.
>>
>> Yeah. And architecturally, C++ and Java are different, but if you're
>> bored of learning new programming languages, looking at Smalltalk or APL
>> might be exciting again. :-)
>
> *cough* Haskell
Another excellent example. Or Hermes.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>>> Yeah. And architecturally, C++ and Java are different, but if you're
>>> bored of learning new programming languages, looking at Smalltalk or APL
>>> might be exciting again. :-)
>>
>> *cough* Haskell
>
> Another excellent example. Or Hermes.
People hate on Haskell for being so different - but that's kind of THE
WHOLE POINT... ;-)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 3:52, Jim Henderson wrote:
> In Windows, you have the entire ecosystem to support it. It's called
> "Windows".
Plus, the tendency is to bundle all that stuff together with the program,
because you can't rely on the people having access to a "repository". So
every install disk has IE6, Adobe Acrobat, mvcrt.dll, and DX9 on it, along
with the program.
> That's because in Windows you have one desktop environment, and one set
> of dependencies. Choice comes with a cost. If you don't want the
> choices, use Windows. Or Mac.
Oh, and because people programming Windows know you don't have a repository,
so they either bundle specifically what they need, or they don't reuse code
they could because of dependencies, or they buy a version to include with
their code that doesn't have the dependencies they want to avoid, or etc.
Why do you think the initial install of Windows takes so long and reboots so
often? It's installing a bunch of stuff that you'd otherwise have to grab
from a repository during installs of other stuff. You get .NET even if
you're not going to use it, because you might in the future.
>> or had my entire Windows installation completely cease
>> functioning to the point where I have to reinstall.
>
> "Orchid XP v8" - you once said that the "v8" indicated how many times you
> had reinstalled Windows XP. So I call BS. ;)
Bazinga.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 5:40, Jim Henderson wrote:
> It's hard to understand why people have trouble affording a single hard
> drive when you buy in such bulk quantities.
And remember that you're not really their big customer. When 85% of your
sales go to the OEMs, worrying about whether this one guy can afford to
upgrade his disk doesn't really make sense. Especially since if you can't
afford a $50 disk, you can't afford a $200 OS. :-)
> After all, on Windows, you have CIFS/SMB available on all systems by
> default. You take it for granted on Windows, but for the rest of the
> world, there is a choice.
Actually, it's there by default, but it doesn't have to be. You don't need
to have any networking installed at all if you don't want. Not even TCP/IP.
> upgraded to each incremental pre-release alpha, beta, and release
> candidate on several of their internal servers.
I can imagine that would screw stuff up. Most people don't design upgrades
to deal with every intermediate release of the software.
> RPM does a pretty good job of dependency management,
I think it's more that the programmers don't. They assume you have enough
disk space, a fast connection, and etc. I bet the people writing the
editors would avoid the need to include SAMBA if you said "we'll give you
$1000 for every package you don't depend on."
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>>> or cooperative shared editting.
>>
>> It's news to me that /any/ version of Office has that.
>
> That's kind of my point.
So... how do you do that?
>>>> In fairness, I'm not aware of anything else that does what Outlook and
>>>> Exchange do.
>>>
>>> And that is why the world still runs Microsoft. :-)
>>
>> Well, no, that's /one of/ the reasons...
>
> Fair enough. But I think that's one of the *main* reasons small
> businesses without a bunch of money still use it on the desktop.
Major reasons include:
- They've heard of it.
- Everybody else is using it. (Easier to interact with clients, easier
to find people who know how to use it, etc.)
- Because everybody else uses it, it gives some people the impression
that it's the "correct" choice because that's what all the "big boys" use.
- Because it's so popular, there's a lot of software for it.
These arguments would all apply to /any/ product which has captured the
majority of the market. And then, yes, there are a few things that MS
product do that I haven't seen a comparable competetor for.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/7/2011 21:47, Jim Henderson wrote:
> Well, no, it's more about advanced usage. And CLI in Windows these days
> is also for advanced users.
And for anything above the level of really simple BAT files, you're better
off using wsh, which is much closer to bash than cmd.exe.
> Like you said, it's an extra install. sed/grep/awk/perl/vim are standard
> tools in most Linux installs.
I'd argue the entire Linux install is a free, extra install. ;-)
> I can edit text files without installing tools that are non standard.
You can edit the registry without installing non-standard tools too. If
you're going to argue that a developer having to download the free developer
toolkit is a significant difference, then you really shouldn't be a
developer on Windows. ;-)
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 08/10/2011 05:42 PM, Darren New wrote:
> On 10/8/2011 5:40, Jim Henderson wrote:
>> It's hard to understand why people have trouble affording a single hard
>> drive when you buy in such bulk quantities.
>
> And remember that you're not really their big customer. When 85% of your
> sales go to the OEMs, worrying about whether this one guy can afford to
> upgrade his disk doesn't really make sense. Especially since if you
> can't afford a $50 disk, you can't afford a $200 OS. :-)
That's a point. As far as OEMs are concerned, the more hardware it takes
to run Windows, the more likely and users are to buy more hardware.
This, I suspect, is one of the main reasons OEMs love MS...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 08/10/2011 05:34 PM, Darren New wrote:
> Why do you think the initial install of Windows takes so long and
> reboots so often? It's installing a bunch of stuff that you'd otherwise
> have to grab from a repository during installs of other stuff. You get
> .NET even if you're not going to use it, because you might in the future.
On which version of Windows?
(I ask because of the amount of time I've spent installing .NET because
it wasn't already there...)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 4:08, Jim Henderson wrote:
> I have yet to see a text file change on a Linux system that can hork the
> system up as badly as Microsoft wants you to believe Windows can be
> messed up with a single registry change.
echo > /etc/fstab
> Because with Linux it's pretty rare to have to reboot to affect the
> change. It's sometimes easier, but to this day, I continue to be amazed
> at how frequently a Windows system has to be restarted. Twice during
> installation, and if you're applying system updates, sometimes multiple
> times to get everything current (certainly with XP, later versions are
> somewhat better).
Because nobody but Linux weenies care whether they have to reboot their
system to upgrade their software?
> Trivial. No scripting required.
These are relatively recent tools in Linux, you must admit. UNIX went 40
years before getting such support, and only because it started to get
targeted at less tech-savvy people.
>> If you wanted to do any of this with Linux, you would have a whole bunch
>> of scripting ahead of you. Under Windows, it just takes a few button
>> presses to set up. You just can't do it from the end-user versions of
>> Windows; it requires a server OS. (Three guesses why those cost so much
>> more.)
>
> Wrong, again on the Linux front. I personally know people who administer
> *thousands* of Linux servers. I worked for a company that has a product
> to apply updates on a schedule to remote Linux systems.
Is it included standard in Linux? ;-)
But yeah, this stuff happens fine in Linux. Probably easier in Linux than
Windows, actually. I can't imagine the kind of operations Google does in
their data centers working on something proprietary like Windows.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Darren New
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 13:01:53
Message: <4e908201@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On 10/8/2011 5:40, Orchid XP v8 wrote:
> Well, in the days before computer networks, security was pretty much a moot
> point.
Except Windows always had security for network connections. Heck, MS network
connections had security before Windows was even around. It's just the local
machine that didn't have security, because it was a *personal* computer.
> What's UAC? Is that new in Windows 7 or something? (I've only used Vista.)
It's the box that pops up and says "you're trying to run this as an
administrator. Are you sure?"
> It's all too easy to break them though, or to end up with cryptic
> error messages and need to look under the hood to find the "real" error and
> how to fix it.
I never had YaST break something, or mess up manual configurations when I
invoke the GUI.
> whereas the registry typically doesn't.
*Because* you're supposed to be using the GUI. :-)
> Ubuntu seems to contantly want me to reboot when I install updates too. I
> think the problem is more that Windows requires updating more often.
There's more stuff that's "always running" and can't easily be shut down
programmatically under Windows. If you have some COM server dealing with
some background job that needs to be updated, there's no clean interface to
ask it to exit and restart itself with a new version. UNIX, always having
had background services, tends to make it easier to figure out what needs to
get restarted and what doesn't.
> That's just it. Windows is one product, with one set of management tools.
Well, XP, Vista, and Win7 are all quite different management-wise, methinks. :-)
> The original Unix, as best as I can tell, has almost no management features
> at all. You're supposed to roll your own. So every major distro builder has
> built their own independent system of management tools.
Yes.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> What's UAC? Is that new in Windows 7 or something? (I've only used
>> Vista.)
>
> It's the box that pops up and says "you're trying to run this as an
> administrator. Are you sure?"
Oh. What, you mean EXACTLY LIKE LINUX? Yeah, I can see how that's such
an annoying Windows feature. :-P
Far more amusing is the fact that if you take, say, Notepad.exe and
rename it to Setup.exe, suddenly Vista thinks it needs elevated
privilages to run...
>> It's all too easy to break them though, or to end up with cryptic
>> error messages and need to look under the hood to find the "real"
>> error and
>> how to fix it.
>
> I never had YaST break something, or mess up manual configurations when
> I invoke the GUI.
Really? That's impressive. I've lost count of how many times the nice
shine GUI for something or other has got confused or crashed or whatever
and I had to spend an hour or two reading manpages to figure out where
the *real* configuration files are and how to edit them to achieve what
I actually wanted...
>> whereas the registry typically doesn't.
>
> *Because* you're supposed to be using the GUI. :-)
That was my point, yes.
>> Ubuntu seems to contantly want me to reboot when I install updates too. I
>> think the problem is more that Windows requires updating more often.
>
> There's more stuff that's "always running" and can't easily be shut down
> programmatically under Windows.
RPC.
I have no idea what this service does, but if you ever try to restart
it, Windows crashes. No idea why. (One wonders why they even gave you
the option to restart it in the first place...)
>> That's just it. Windows is one product, with one set of management tools.
>
> Well, XP, Vista, and Win7 are all quite different management-wise,
> methinks. :-)
Really? I haven't used Vista or 7 extensively, but I wasn't aware that
anything had changed...
Regardless, *every* copy of (say) Vista has the same management
capabilities. It's a "standard" part of a Windows system. Which I guess
is just another way of saying "there's more than one Linux distro"...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 9:47, Orchid XP v8 wrote:
>>>> or cooperative shared editting.
>>>
>>> It's news to me that /any/ version of Office has that.
>>
>> That's kind of my point.
>
> So... how do you do that?
You stick it on a share and you go to the menu that says something like
"cooperative editing" or some such. You're sitting in front of a
google-enabled computer just like I am. :-)
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 7:32, Jim Henderson wrote:
> Just like on Windows it used to depend on whether the developer wrote an
> INI file or used the registry.
More precisely, it's a question of whether the developer wrote his own code
to frob INI files, or whether he used the Windows API to do so. Because when
the registry came out, the Windows API was later changed to stor INI files
in the registry.
>> [Let's not even get into the fact that the registry is transactional,
>> while text files aren't. Or that it supports storing binary blobs
>> relatively efficiently...]
>
> Transactionality is a function of the filesystem, and I use a journaled
> filesystem.
The Linux file system isn't transactional. It's just journaled. There's no
way to update three files at once and ensure nobody sees only one of them
updated. There's no way to save six files full of Apache config and ensure
the backup program running in the background hasn't backed up three of the
new ones and three of the old ones.
> And I've yet to see anything more effective than a binary blob as a
> file.
I'm curious what this sentence is supposed to mean. Binary blobs are the
lowest common denominator, but almost no files actually store a binary blob.
> Sometimes distros choose that route because it's just easier than
> educating the user. I would prefer if they educated the user instead.
Or because it's more reliable. If you update half an installation without
actually restarting the programs using the DLLs and config files you just
updated, you could be pretty screwed down the line. Happened all the time
to me when (for example) the sys admin would update a running server but not
save the configuration to outlast a reboot, and then the machine would get
rebooted and all the software depending on that new configuration would fail.
> Doing the same on my openSUSE boxes, it's one reboot. Period. *If*
> there's a kernel update.
Out of curiosity, why would you care how many boots it takes to install the
OS? It's not like there's other things running while you're trying to
install, right?
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 10:09, Orchid XP v8 wrote:
> Regardless, *every* copy of (say) Vista has the same management
> capabilities.
Nonsense. The home versions can't even log into a domain.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Darren New
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 15:38:51
Message: <4e90a6cb@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On 10/8/2011 2:41, Orchid XP v8 wrote:
> I bought some hardware that lets me remotely connect to my grandparent's PC.
Why do you need that? All that sort of thing is built into Windows.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 17:17:44
Message: <4e90bdf8$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 16:10:16 +0100, Orchid XP v8 wrote:
>> Try installing Notepad on Windows without installing Windows
>> Networking.
>>
>> Oh, you can't do that. Why? Because Windows Networking is an
>> integrated component of the operating system.
>>
>> Guess what - it's also an integrated component of GNOME, because
>> interoperability matters.
>
> The irony is, you actually /can/ uninstall Windows networking (and even
> the TCP/IP protocol). And Notepad still works. :-P
Not if you try to save to a networked drive.
> Plus, installing Windows isn't a 4GB download. Honestly, I can remember
> a time when all the Linux fanboys used to shout about how much leaner
> Linux is than Windows. Today a default install of most distros either
> involves DVDs or multi-GB downloads. It installs everything *and* the
> kitchen sink, and when I want to use a different text editor it *still*
> wants to download another couple of GB of data. ENOUGH ALREADY! >_<
Installing Windows + applications is a lot more than 4 GB. With the
caching done on my Win7 VM, it sure seems to have downloaded 4+ GB of
updates since installed, too.
>>> Me and my dad tried updating OpenSUSE one time. After several days of
>>> hell, we decided never to attempt this ever again.
>>
>> It's a shame you didn't come over to the forums and ask for some help.
>
> Wouldn't that require me to figure out how to display IPv6 so that
> Firefox works again?
No.
You have a Windows machine, do you not? It's not uncommon for people to
use one OS to ask questions about another, especially when they're having
networking issues.
>>> Uh, yeah. Updating Windows in-place isn't something I'd recommend
>>> *either*...
>>
>> I generally wouldn't recommend it for any OS, but it can be a bit
>> easier with Linux if your /home partition is separate from the rest of
>> the system. Worst case, you do a fresh install of the root partition
>> and leave the /home data alone.
>
> Same works for any OS.
True enough.
>>>> RPM does a pretty good job of dependency management
>>>
>>> Well, some distros use RPM, some use .deb, some use something else
>>> entirely. I've yet to see a package manager where it's entirely clear
>>> what the heck is going on, or why selecting one small application
>>> requires a 2GB download.
>>
>> Well, again, it comes down to understanding the interdependencies,
>> rather than throwing your hands up in the air and saying "it's too
>> damned complex for anyone to understand."
>
> How about spending several years working with Linux and still not being
> able to get it to work right. Does that count? :-P
>
>>>> but you have to take care not to add too many repositories
>>>
>>> I don't even know how to do that.
>>
>> In openSUSE: sudo yast2 repositories
>
> OK. But the fact that I don't know how to do it demonstrates fairly
> conclusively that that isn't the problem I had.
Your problem is a lack of knowledge. That can be corrected. If you go
into using Linux thinking it's going to be exactly like Windows, you're
doomed to fail before you even boot the machine.
Newsflash: Linux is NOT Windows. It doesn't work like Windows. It
doesn't feel like Windows. Why? BECAUSE IT ISN'T FREAKING WINDOWS!!!
>>> Last time I tried this with VMware tools, it went something like this:
>>> - Where are the kernel headers?
>>> - No, the headers for the *running* kernel? - OK, now install gcc
>>> please.
>>> - No, the version of gcc that the kernel was compiled with. At that
>>> point, I discovered that the version of gcc in question isn't
>>> available for this release of Ubuntu. WTF?
>>
>> I can't speak to Ubuntu. openSUSE has a pretty strict "no kernel
>> upgrades" policy within a particular version. (That doesn't mean "no
>> updates" - security updates are backported by the openSUSE kernel team,
>> and important enhancements frequently are as well AFAIK). That means
>> it's incredibly rare to have to deal with something like that with
>> VMware once it's working.
>
> I think I tried it with Debian and Fedora as well. Can't remember if I
> tried OpenSUSE.
>
> This sort of thing tends to be typical of /any/ attempt to install
> something that isn't packaged. And even if the website has an RPM or a
> .deb, usually that just flips the package manager out because all the
> dependencies are wrong...
Which is why having a community to ask questions of (including 'is there
a pre-built package for 'x'', surprisingly enough) is a good thing.
>> It's a shame you don't ask questions in the Linux forums related to the
>> distribution you use. Those issues are often easily resolved, and
>> novices can get help instead of just bitching "this damned stuff never
>> works right!"
>
> Yes, because I want to sign up to /yet another/ online forum just to
> make one piece of software install cleanly...
If you're using Fedora, go to fedoraforums. If you're using Ubuntu, go
to ubuntuforums. If you use openSUSE, go to the openSUSE forums.
Chances are you're not going to get sent to a forum for Photivo (for
example), unless you're having a problem specific to Photivo. Just like
with Windows apps, you're not going to go to the Microsoft forums to ask
a question about issues installing Peachtree Accounting.
> As I say, I generally just stick to Windows. When you install stuff, it
> just works.
>
> (Not that I'm completely unsympathetic, you understand. "Linux" is one
> hell of a big moving target to try to hit...)
>
> I love how I'm the biggest Microsoft-hater ever, and I've ended up
> defending Windows. When Linux came out, I really thought it was going to
> be the answer. Turns out it just brought a different set of problems...
Software isn't perfect. No matter which platform it is, it isn't going
to be perfect. You have to be willing to take some time to learn how the
system works, rather than just try it and lament "it's hard".
Linux is not hard. It requires some dedication to learn in order to use
it effectively, just as Windows does. If you doubt that, look at any
user on your network who hasn't taken the time to figure out how to use
Windows effectively.
Everyone's a new user at least once.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 17:21:24
Message: <4e90bed4$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 09:42:26 -0700, Darren New wrote:
> On 10/8/2011 5:40, Jim Henderson wrote:
>> It's hard to understand why people have trouble affording a single hard
>> drive when you buy in such bulk quantities.
>
> And remember that you're not really their big customer. When 85% of your
> sales go to the OEMs, worrying about whether this one guy can afford to
> upgrade his disk doesn't really make sense. Especially since if you
> can't afford a $50 disk, you can't afford a $200 OS. :-)
That's certainly true. But chances are if you bought the machine,
Windows was included.
>> After all, on Windows, you have CIFS/SMB available on all systems by
>> default. You take it for granted on Windows, but for the rest of the
>> world, there is a choice.
>
> Actually, it's there by default, but it doesn't have to be. You don't
> need to have any networking installed at all if you don't want. Not even
> TCP/IP.
I guess that's true, but kinda beside the point. The point is there's an
entire ecosystem of DLLs and system drivers/files that are necessary for
Windows to run if you want to run Notepad or Word. Just because on
Windows there's exactly one option means that all that stuff is installed
by default.
Linux brings a number of choices - for better or for worse - and bitching
about having to install the entirety of the KDE libraries to run k3b (for
example) because it's a better disc burning tool than brasero (which is
the GNOME utility) is kinda disingenuous.
>> upgraded to each incremental pre-release alpha, beta, and release
>> candidate on several of their internal servers.
>
> I can imagine that would screw stuff up. Most people don't design
> upgrades to deal with every intermediate release of the software.
The guys at Microsoft I talked to (this was back in 2002/2003) said it
was a complete nightmare.
>> RPM does a pretty good job of dependency management,
>
> I think it's more that the programmers don't. They assume you have
> enough disk space, a fast connection, and etc. I bet the people writing
> the editors would avoid the need to include SAMBA if you said "we'll
> give you $1000 for every package you don't depend on."
True, and it does come down to developers identifying the prerequisites
appropriately. There are sloppy coders in both OSS and closed source
development, so that's not really a problem unique to Linux.
It is perhaps more common in Linux than it should be, though.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 17:23:15
Message: <4e90bf43$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 09:34:06 -0700, Darren New wrote:
> On 10/8/2011 3:52, Jim Henderson wrote:
>> In Windows, you have the entire ecosystem to support it. It's called
>> "Windows".
>
> Plus, the tendency is to bundle all that stuff together with the
> program, because you can't rely on the people having access to a
> "repository". So every install disk has IE6, Adobe Acrobat, mvcrt.dll,
> and DX9 on it, along with the program.
Windows could benefit from implementing something akin to a Linux
software repository for stuff like this. Getting the software makers to
agree might take some work, but then again, Adobe has Acrobat Reader in
most distributions' official repositories.
>> That's because in Windows you have one desktop environment, and one set
>> of dependencies. Choice comes with a cost. If you don't want the
>> choices, use Windows. Or Mac.
>
> Oh, and because people programming Windows know you don't have a
> repository, so they either bundle specifically what they need, or they
> don't reuse code they could because of dependencies, or they buy a
> version to include with their code that doesn't have the dependencies
> they want to avoid, or etc.
>
> Why do you think the initial install of Windows takes so long and
> reboots so often? It's installing a bunch of stuff that you'd otherwise
> have to grab from a repository during installs of other stuff. You get
> .NET even if you're not going to use it, because you might in the
> future.
Yep, same reason some libraries are installed on a default Linux
installation unless you're using Gentoo or LFS.
>>> or had my entire Windows installation completely cease functioning to
>>> the point where I have to reinstall.
>>
>> "Orchid XP v8" - you once said that the "v8" indicated how many times
>> you had reinstalled Windows XP. So I call BS. ;)
>
> Bazinga.
LOL
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 17:28:18
Message: <4e90c072@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 12:34:21 -0700, Darren New wrote:
> On 10/8/2011 7:32, Jim Henderson wrote:
>> Just like on Windows it used to depend on whether the developer wrote
>> an INI file or used the registry.
>
> More precisely, it's a question of whether the developer wrote his own
> code to frob INI files, or whether he used the Windows API to do so.
> Because when the registry came out, the Windows API was later changed to
> stor INI files in the registry.
Yes, that's more or less what I meant.
>>> [Let's not even get into the fact that the registry is transactional,
>>> while text files aren't. Or that it supports storing binary blobs
>>> relatively efficiently...]
>>
>> Transactionality is a function of the filesystem, and I use a journaled
>> filesystem.
>
> The Linux file system isn't transactional. It's just journaled. There's
> no way to update three files at once and ensure nobody sees only one of
> them updated. There's no way to save six files full of Apache config and
> ensure the backup program running in the background hasn't backed up
> three of the new ones and three of the old ones.
Depends on the filesystem in question. I think the new upcomer 'btrfs'
is supposed to be transactional.
>> And I've yet to see anything more effective than a binary blob as a
>> file.
>
> I'm curious what this sentence is supposed to mean. Binary blobs are the
> lowest common denominator, but almost no files actually store a binary
> blob.
All files are binary blobs. Some have restricted character sets, but
when it comes down to it, a file is nothing more than a collection of
bytes.
>> Sometimes distros choose that route because it's just easier than
>> educating the user. I would prefer if they educated the user instead.
>
> Or because it's more reliable. If you update half an installation
> without actually restarting the programs using the DLLs and config files
> you just updated, you could be pretty screwed down the line. Happened
> all the time to me when (for example) the sys admin would update a
> running server but not save the configuration to outlast a reboot, and
> then the machine would get rebooted and all the software depending on
> that new configuration would fail.
Well, it's more reliable with users who don't have the education on how
to restart the service rather than rebooting the system.
>> Doing the same on my openSUSE boxes, it's one reboot. Period. *If*
>> there's a kernel update.
>
> Out of curiosity, why would you care how many boots it takes to install
> the OS? It's not like there's other things running while you're trying
> to install, right?
It's a matter of design elegance in my book. Yes, it doesn't really
matter if the system reboots a hundred times during the installation.
Well, except that I'm used to dealing with a single reboot on OS
installs, so each time the system reboots, I stop what I'm working on
because I think it's done, and it turns out it's not.
If I spent more time installing Windows, I'm sure I'd become more used to
it. In this case, it's a question of being used to going "Oh, it's not
done yet". But Windows has never been good at telling the user how long
something's going to take (to the point that I guess in Win 8, they're
going to stop trying to predict things like how long a multiple file copy
is going to take to complete).
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 17:38:01
Message: <4e90c2b9@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 15:59:14 +0100, Orchid XP v8 wrote:
>>> Under Unix, the primary way to control most software is through
>>> configuration files. These days Linux has added pretty front-ends to
>>> some of these systems, but they tend to be designed only for the
>>> people who aren't smart enough to use the "real" interface - i.e.,
>>> edit the text fails manually.
>>
>> Well, yes and no. Users of SUSE products (openSUSE and SLE*) often do
>> know how to do the manual edits, but prefer using YaST anyways.
>
> If you pull up the documentation for (say) Apache, it won't tell you how
> to use the Apache YaST module. It will tell you how to edit the
> underlying text file. And if something doesn't work right, and you can't
> figure it out from YaST, you'll have to look under the covers to see
> what it's written in the configuration file, to see why Apache isn't
> doing what you want.
If you use openSUSE for configuration, you use the openSUSE documentation
to see how to use YaST to make those configuration changes. And if that
doesn't get you where you need to be, you ask a question in the community.
OSS is big about community.
>>> Under Windows, the GUI is the "real" interface. The configuration data
>>> is stored in the registry, but you're not supposed to edit it
>>> directly.
>>
>> Except for when there's no other way.
>
> Except that this almost never happens. That's the entire point. Most
> Linux front-ends seem to be tacked on afterwards, whereas on Windows,
> the GUI is the primary focus.
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.
>> In openSUSE and SLE, there are in fact several files that are
>> explicitly commented with "DO NOT EDIT THIS FILE DIRECTLY".
>
> I thought that's just code for "this file is autogenerated from some
> other configuration file - you should go edit that instead".
Configuration files don't autogenerate other configuration programs.
Configuration programs do, and in those instances, the warning is there
to tell you to use the proper configuration program.
>>> It's just about where the developers focus their attention. Under
>>> Unix, the configuration file is the definite interface.
>>
>> Well, again, on Linux it depends.
>
> OK. But certainly most Linux uses seem to have the opinion of "GUI? Pah!
> We don't need that. That's just for n00bs who don't know what they're
> doing..." (Whether this attitude applies to most /developers/ is more
> debatable.)
Obviously you don't know many Linux users. I know at least 5,000, and
many of them not only love and use the GUI, but tend to have religious
wars over which GUI is better.
Of course, that's most certainly an attitude taken by people who think
GUIs suck, right?
>>> Oh yeah, but /all/ platforms have crappy software.
>>
>> Well, look at OpenOffice or LibreOffice. Those are not programs
>> designed for the geek, they're designed for the casual user. You can't
>> lump all programs on Linux in one category and all programs on Windows
>> in the other - there's crossover.
>
> Sure. But most programs seem to be primarily Unix or primarily Windows.
Which doesn't actually address the underlying point.
>>> You've misparsed what I wrote.
>>
>> OK, I guess I did. Hey, it was 7:15 AM here and I've been up all
>> night. ;)
>
> This is not a good thing.
Not generally, no. I've had some sleep now, but next week is going to
see me needing to be up early every morning for the first time in months.
(this is a good thing) :)
>>> Interesting. I'm pretty sure I had to send SIG_HUP (or whatever it is)
>>> to sshd to get it to notice that I just turned off password
>>> authentication...
>>
>> Just like in Windows, it depends on the program, and how long ago. You
>> may have noticed that Linux development isn't exactly stagnant.
>
> I notice that there's always a lot of stuff "happening" with Linux. I'm
> never sure what the hell any of it actually /does/. As far as I can
> tell, the difference between each release of any given Linux distro is
> that the colour scheme is different, and some of the default options
> have changed. I'm sure there must be more to it than that, but...
Linux (and most OSS software) evolves rather than going through discrete
cycles. The downside is that it can be difficult to peg a specific
'stable' release unless that's built into the release schedule (of a
distro or a particular piece of software). The upside is that bug fixes
and enhancements (particularly the latter) tend to find their way into
incremental releases a bit quicker.
Commercial software tends to hold back on incremental improvements (new
features) for a major release so they can get customers to buy it.
No market pressure for cashflow means a more flexible release schedule
for incremental enhancements.
>> Transactionality is a function of the filesystem, and I use a journaled
>> filesystem.
>
> Doesn't stop two scripts both trying to update the same config file at
> the same time. If you do that with the registry, it works. Because it's
> a proper database engine, not just a flat file.
I'm not sure how "proper" that database engine is - IIRC, it's JET, and
most DBAs that I know would say that's certainly not a proper database
engine.
>>> That's just ironic. Doing something defective because that's how
>>> Windows does it. Ha!
>>
>> Sometimes distros choose that route because it's just easier than
>> educating the user. I would prefer if they educated the user instead.
>
> I guess it isn't just MS that makes poor choices in the name of keeping
> users...
Indeed.
>>> AFAIK, you boot the CD, do the text-mode bit, reboot into GUI mode,
>>> reboot one final time, and you're done. That's, like, 2 reboots.
>>> Hardly excessive...
>>
>> But then start applying patches on Windows. To get 2008R2 current,
>> that's probably 2-3 more reboots.
>
> OK, fair enough.
>
> Personally, I'm not very impressed by the Windows Update system. Like,
> it'll install a bazillion updates for IE6 in the same session as it also
> installs IE8. And then you go back and it wants to install a bunch of
> IE8 updates. Um, why couldn't you do that the first time around??
Yep, I've been frustrated by that as well.
>> Slightly different situation when the manufacturer is extorting OEMs to
>> pre-install Windows on every machine they ship (and charge for a
>> license regardless of whether they ship Windows or not). That actually
>> is an abuse of monopoly power; the US Antitrust trial found that, and
>> so did the EC's investigation.
>
> I love how multiple courts have proved that what MS is doing is illegal,
> and as a result they have received NO PUNISHMENT OF ANY KIND. That's
> such a big motivation for them to stop casually disregarding the law...
Oh, I don't know, having to admit that Firefox is a reasonable browser to
use and they should change Windows architecturally to decouple IE from it
(or at least loosen the coupling) is a pretty significant sanction.
Microsoft wanted to prove that IE was a core part of Windows that
couldn't be removed (because it removed part of their competitive
advantage - or at least they thought it did), and the EC told them "do it
anyway", so they had to create a special version of Windows for Europe
that had that change in place.
Maintaining multiple versions of an entire operating system can be time
and resource intensive.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 17:44:25
Message: <4e90c439$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 09:55:14 -0700, Darren New wrote:
> On 10/8/2011 4:08, Jim Henderson wrote:
>> I have yet to see a text file change on a Linux system that can hork
>> the system up as badly as Microsoft wants you to believe Windows can be
>> messed up with a single registry change.
>
> echo > /etc/fstab
While it will create a problem with getting the system running, it's far
from unrecoverable.
Windows Server 2000 as a domain controller. If you lose your
administrator password, you're hosed. You're reinstalling. (I understand
they fixed that oversight in Server 2003, but that's beside the point).
Had a lab full of machines that the power went out in once (electricians
doing a power upgrade). We shut everything down properly, they did some
work, we powered everything up, and then they started their actual work
and threw the main breaker.
Half the Windows machines wouldn't boot. All the *nix and NetWare
machines (and AS/400s et al) booted more or less without any issue at all.
>> Because with Linux it's pretty rare to have to reboot to affect the
>> change. It's sometimes easier, but to this day, I continue to be
>> amazed at how frequently a Windows system has to be restarted. Twice
>> during installation, and if you're applying system updates, sometimes
>> multiple times to get everything current (certainly with XP, later
>> versions are somewhat better).
>
> Because nobody but Linux weenies care whether they have to reboot their
> system to upgrade their software?
It's an inconvenience. An annoyance. Something that's far too often
required on Windows. Yes, Windows weenies don't particularly care,
because they've been taught not to care. They've been taught that
"troubleshooting" involves "did you turn it off and back on again, and
when it came back up, did the problem recur?".
Sorry, *that's* not troubleshooting. That's problem avoidance.
>> Trivial. No scripting required.
>
> These are relatively recent tools in Linux, you must admit. UNIX went 40
> years before getting such support, and only because it started to get
> targeted at less tech-savvy people.
Relatively recent being "in the last 10 years or so". That's about 2-3
technological generations.
I might as well name Windows faults based on experiences exclusively with
Windows 3.1.
>>> If you wanted to do any of this with Linux, you would have a whole
>>> bunch of scripting ahead of you. Under Windows, it just takes a few
>>> button presses to set up. You just can't do it from the end-user
>>> versions of Windows; it requires a server OS. (Three guesses why those
>>> cost so much more.)
>>
>> Wrong, again on the Linux front. I personally know people who
>> administer *thousands* of Linux servers. I worked for a company that
>> has a product to apply updates on a schedule to remote Linux systems.
>
> Is it included standard in Linux? ;-)
No, but at least one of the tools is a free tool to download and use.
> But yeah, this stuff happens fine in Linux. Probably easier in Linux
> than Windows, actually. I can't imagine the kind of operations Google
> does in their data centers working on something proprietary like
> Windows.
Indeed. :)
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 17:45:52
Message: <4e90c490$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 09:48:10 -0700, Darren New wrote:
> On 10/7/2011 21:47, Jim Henderson wrote:
>> Well, no, it's more about advanced usage. And CLI in Windows these
>> days is also for advanced users.
>
> And for anything above the level of really simple BAT files, you're
> better off using wsh, which is much closer to bash than cmd.exe.
And a relatively recent development, no?
>> Like you said, it's an extra install. sed/grep/awk/perl/vim are
>> standard tools in most Linux installs.
>
> I'd argue the entire Linux install is a free, extra install. ;-)
Of course you would, coming from a Windows background. You'd probably
also call it 'unnecessary'. ;)
>> I can edit text files without installing tools that are non standard.
>
> You can edit the registry without installing non-standard tools too. If
> you're going to argue that a developer having to download the free
> developer toolkit is a significant difference, then you really shouldn't
> be a developer on Windows. ;-)
Good thing I'm not a Windows developer. ;)
Point is, on most *nix systems, those are standard tools, not an
additional download.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Patrick Elliott
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 19:05:20
Message: <4e90d730$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On 10/8/2011 2:41 AM, Orchid XP v8 wrote:
> On 08/10/2011 05:39 AM, Darren New wrote:
>> On 10/7/2011 20:43, Jim Henderson wrote:
>>> Sounds *so* familiar. Another reason to use Linux. ;)
>>
>> How the hell would that help?
>
> Seconded.
>
>> What helped was getting him off dial-up so I could talk to him at the
>> same time he's on the net, *and* connect into his computer remotely.
>
> I bought some hardware that lets me remotely connect to my grandparent's
> PC. (Unless, you know, the problem I'm trying to troubleshoot IS the
> Internet connection...)
>
Sounds like the nForce chipset bug, where the "internet security"
feature built in seemed to have the basic function, when turned on (and
you can't turn it off short of uninstalling the whole security manager),
seemed to be to slow the connection, cause packet errors, and prevent
you successfully downloading anything over a few megs in size. Took me
months to figure out that the problem wasn't the damn patch panels I put
in the wall, to connect the two rooms, for my network, but the damn
"internet security" on the motherboard of the computer that had the problem.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 08/10/2011 08:38 PM, Darren New wrote:
> On 10/8/2011 2:41, Orchid XP v8 wrote:
>> I bought some hardware that lets me remotely connect to my
>> grandparent's PC.
>
> Why do you need that? All that sort of thing is built into Windows.
Really? So how do I create an encrypted video connection to the target
machine, while at the same time preventing anybody else from doing the same?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 08/10/2011 10:44 PM, Jim Henderson wrote:
> Had a lab full of machines that the power went out in once (electricians
> doing a power upgrade). We shut everything down properly, they did some
> work, we powered everything up, and then they started their actual work
> and threw the main breaker.
>
> Half the Windows machines wouldn't boot. All the *nix and NetWare
> machines (and AS/400s et al) booted more or less without any issue at all.
Now I'm puzzled. Why the heck would that happen? Last time we had a
power cut at work, all 50 desktop PCs booted back up just fine afterwards...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 20:33:56
Message: <4e90ebf4$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sun, 09 Oct 2011 01:32:08 +0100, Orchid XP v8 wrote:
> On 08/10/2011 08:38 PM, Darren New wrote:
>> On 10/8/2011 2:41, Orchid XP v8 wrote:
>>> I bought some hardware that lets me remotely connect to my
>>> grandparent's PC.
>>
>> Why do you need that? All that sort of thing is built into Windows.
>
> Really? So how do I create an encrypted video connection to the target
> machine, while at the same time preventing anybody else from doing the
> same?
Remote Desktop + password.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 20:35:50
Message: <4e90ec66$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sun, 09 Oct 2011 01:33:11 +0100, Orchid XP v8 wrote:
> On 08/10/2011 10:44 PM, Jim Henderson wrote:
>
>> Had a lab full of machines that the power went out in once
>> (electricians doing a power upgrade). We shut everything down
>> properly, they did some work, we powered everything up, and then they
>> started their actual work and threw the main breaker.
>>
>> Half the Windows machines wouldn't boot. All the *nix and NetWare
>> machines (and AS/400s et al) booted more or less without any issue at
>> all.
>
> Now I'm puzzled. Why the heck would that happen? Last time we had a
> power cut at work, all 50 desktop PCs booted back up just fine
> afterwards...
We never actually figured out why so many of the Windows machines in the
lab failed to boot. They were older HP servers (this was circa
2001/2002). In the end, the Windows engineers ended up rebuilding the
systems; they were lab systems after all.
All I remember is those of us who handled systems other than the Windows
systems found it amusing that the Windows stuff was so fragile and the
other stuff just rolled with it.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 08/10/2011 10:17 PM, Jim Henderson wrote:
> On Sat, 08 Oct 2011 16:10:16 +0100, Orchid XP v8 wrote:
>
>>> Try installing Notepad on Windows without installing Windows
>>> Networking.
>>>
>>> Oh, you can't do that. Why? Because Windows Networking is an
>>> integrated component of the operating system.
>>>
>>> Guess what - it's also an integrated component of GNOME, because
>>> interoperability matters.
>>
>> The irony is, you actually /can/ uninstall Windows networking (and even
>> the TCP/IP protocol). And Notepad still works. :-P
>
> Not if you try to save to a networked drive.
OK. But I don't actually want to do that, so I don't care.
Likewise, if I install GTK+ but not Samba, I can't save to a networked
drive. But since I'm not trying to do that, it's irrelevant.
>> Plus, installing Windows isn't a 4GB download.
>
> Installing Windows + applications is a lot more than 4 GB. With the
> caching done on my Win7 VM, it sure seems to have downloaded 4+ GB of
> updates since installed, too.
Seriously?
The Windows XP CD holds less than 650 MB of data. (It's a CD.) Service
Pack 3 is only a few hundred MB, last I checked. Most individual updates
are a few KB to maybe a dozen MB. I would be /greatly/ surprised if you
need to download more than 1 GB.
Applications? Well, yeah, that could be arbitrarily large, depending on
what applications you want...
>>>> Me and my dad tried updating OpenSUSE one time. After several days of
>>>> hell, we decided never to attempt this ever again.
>>>
>>> It's a shame you didn't come over to the forums and ask for some help.
>>
>> Wouldn't that require me to figure out how to display IPv6 so that
>> Firefox works again?
>
> No.
>
> You have a Windows machine, do you not?
Not in the same building, no.
I mean, I guess I could have set something up. It's just frustrating
when all you're trying to do is a default install or whatever, and that
isn't working.
> Your problem is a lack of knowledge. That can be corrected. If you go
> into using Linux thinking it's going to be exactly like Windows, you're
> doomed to fail before you even boot the machine.
>
> Newsflash: Linux is NOT Windows. It doesn't work like Windows. It
> doesn't feel like Windows. Why? BECAUSE IT ISN'T FREAKING WINDOWS!!!
And, uh, what do you base this assertion on?
You make it sound like I used Linux for five minutes, couldn't work it,
and gave up. That's not what happened at all!
> Software isn't perfect. No matter which platform it is, it isn't going
> to be perfect.
Funny, I could have sworn Mac OS was perfect...
> You have to be willing to take some time to learn how the
> system works, rather than just try it and lament "it's hard".
You make it sound like I've made no attempt to do so.
I can work Linux. I can usually make it do what I want it to do. I
pointed out one specific issue: installing stuff tends to be a
dependency nightmare. Which is true. I don't see how that makes me an idiot.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Orchid XP v8
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 20:45:32
Message: <4e90eeac@news.povray.org>
|
|
 |
|  |
|  |
|
 |
>>> Why do you need that? All that sort of thing is built into Windows.
>>
>> Really? So how do I create an encrypted video connection to the target
>> machine, while at the same time preventing anybody else from doing the
>> same?
>
> Remote Desktop + password.
Now how do you /encrypt/ that?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 14:17, Jim Henderson wrote:
> On Sat, 08 Oct 2011 16:10:16 +0100, Orchid XP v8 wrote:
>
>>> Try installing Notepad on Windows without installing Windows
>>> Networking.
>>>
>>> Oh, you can't do that. Why? Because Windows Networking is an
>>> integrated component of the operating system.
>>>
>>> Guess what - it's also an integrated component of GNOME, because
>>> interoperability matters.
>>
>> The irony is, you actually /can/ uninstall Windows networking (and even
>> the TCP/IP protocol). And Notepad still works. :-P
>
> Not if you try to save to a networked drive.
But that's a stupid argument. Notepad still works even without networking if
you don't try to use networking. Linux doesn't, because everything assumes
it's there.
On the other hand, Linux still works if you uninstall graphics drivers, and
Windows (and Notepad) fall over.
> Installing Windows + applications is a lot more than 4 GB.
Windows hasn't fit on less than a DVD in quite some time. I think the base
install is a 3.5G DVD image or so. Not counting Office and such.
> Which is why having a community to ask questions of (including 'is there
> a pre-built package for 'x'', surprisingly enough) is a good thing.
Does anyone else miss the good old days when it was possible to use a
computer based on the instructions it came with, without having to have a
live connection open to the people who wrote the software you're using?
Where you could buy a book, and read the book, and then use in all its
details the software the book described?
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Which is why having a community to ask questions of (including 'is there
>> a pre-built package for 'x'', surprisingly enough) is a good thing.
>
> Does anyone else miss the good old days when it was possible to use a
> computer based on the instructions it came with, without having to have
> a live connection open to the people who wrote the software you're
> using? Where you could buy a book, and read the book, and then use in
> all its details the software the book described?
<raise hand>
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 20:50:46
Message: <4e90efe6@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sun, 09 Oct 2011 01:45:29 +0100, Orchid XP v8 wrote:
>>>> Why do you need that? All that sort of thing is built into Windows.
>>>
>>> Really? So how do I create an encrypted video connection to the target
>>> machine, while at the same time preventing anybody else from doing the
>>> same?
>>
>> Remote Desktop + password.
>
> Now how do you /encrypt/ that?
It's RDP. It's already *encrypted*.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 14:21, Jim Henderson wrote:
> On Sat, 08 Oct 2011 09:42:26 -0700, Darren New wrote:
>
>> On 10/8/2011 5:40, Jim Henderson wrote:
>>> It's hard to understand why people have trouble affording a single hard
>>> drive when you buy in such bulk quantities.
>>
>> And remember that you're not really their big customer. When 85% of your
>> sales go to the OEMs, worrying about whether this one guy can afford to
>> upgrade his disk doesn't really make sense. Especially since if you
>> can't afford a $50 disk, you can't afford a $200 OS. :-)
>
> That's certainly true. But chances are if you bought the machine,
> Windows was included.
That's kind of my point exactly. :-)
> is kinda disingenuous.
I don't know "disingenuous" is the word I'd use, but sure. There are
benefits to having one entity saying "here, it's solved, do it this way."
There are problems with that too, when you want to do it a different way.
>>> upgraded to each incremental pre-release alpha, beta, and release
>>> candidate on several of their internal servers.
>>
>> I can imagine that would screw stuff up. Most people don't design
>> upgrades to deal with every intermediate release of the software.
>
> The guys at Microsoft I talked to (this was back in 2002/2003) said it
> was a complete nightmare.
Sure. But "the guy who installs every pre-release version over top of the
previous pre-release version" isn't the target audience. It's much more
efficient to design an upgrade to replace the previous production system
than to design an upgrade to replace every previous version of every
unreleased upgrade.
> It is perhaps more common in Linux than it should be, though.
I'm saying it's because it hurts Linux less. You don't actually lose sales
due to having your software pull in too many prerequisites. As opposed to
(for example) having to distribute on a DVD rather than a CD if you are
close to the edge. (Of course, much more worrisome with downloads or with
floppies or other low-capacity media.)
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 09/10/2011 01:50 AM, Jim Henderson wrote:
> On Sun, 09 Oct 2011 01:45:29 +0100, Orchid XP v8 wrote:
>
>>>>> Why do you need that? All that sort of thing is built into Windows.
>>>>
>>>> Really? So how do I create an encrypted video connection to the target
>>>> machine, while at the same time preventing anybody else from doing the
>>>> same?
>>>
>>> Remote Desktop + password.
>>
>> Now how do you /encrypt/ that?
>
> It's RDP. It's already *encrypted*.
Yeah, right. I'll believe it when I see it.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 14:23, Jim Henderson wrote:
> Windows could benefit from implementing something akin to a Linux
> software repository for stuff like this.
They have it. Windows Update. Where your device drivers come from. :-)
> Getting the software makers to agree might take some work,
And that is the problem. That, and commercial entities don't really want
their software in Windows Update where people could install it without
paying for it. The model really only works for free software.
> but then again, Adobe has Acrobat Reader in
> most distributions' official repositories.
Probably because Adobe doesn't have to deal with it. They just have to give
permission.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 20:57:22
Message: <4e90f172@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sun, 09 Oct 2011 01:44:45 +0100, Orchid XP v8 wrote:
>>> Plus, installing Windows isn't a 4GB download.
>>
>> Installing Windows + applications is a lot more than 4 GB. With the
>> caching done on my Win7 VM, it sure seems to have downloaded 4+ GB of
>> updates since installed, too.
>
> Seriously?
>
> The Windows XP CD holds less than 650 MB of data. (It's a CD.) Service
> Pack 3 is only a few hundred MB, last I checked. Most individual updates
> are a few KB to maybe a dozen MB. I would be /greatly/ surprised if you
> need to download more than 1 GB.
Oh, so you want to compare a modern Linux distribution against Windows
from 10-ish years ago? *Really*? How about I say Linux is so much
better than Windows 3.1?
> Applications? Well, yeah, that could be arbitrarily large, depending on
> what applications you want...
Precisely. That 4 GB DVD has loads of applications on it.
>>> Wouldn't that require me to figure out how to display IPv6 so that
>>> Firefox works again?
>>
>> No.
>>
>> You have a Windows machine, do you not?
>
> Not in the same building, no.
Huh, so the guy I was helping over in the openSUSE forums who has one
computer and it isn't connected to the Internet at all is SOL for asking
questions because he doesn't have a network connection.
Oh, wait, he went to the library and used a public computer to ask his
questions. Is there some reason that wouldn't work for you?
Those who want to will find a way. Those who want to just complain will
give up without even trying.
> I mean, I guess I could have set something up. It's just frustrating
> when all you're trying to do is a default install or whatever, and that
> isn't working.
Yeah, and it sucks when the power goes out and you have to wait for
something to be fixed. If you don't call it in to the power company, it
may never get fixed. One wouldn't be justified to just sit there and
bitch that they haven't fixed it when you didn't report a problem.
>> Your problem is a lack of knowledge. That can be corrected. If you go
>> into using Linux thinking it's going to be exactly like Windows, you're
>> doomed to fail before you even boot the machine.
>>
>> Newsflash: Linux is NOT Windows. It doesn't work like Windows. It
>> doesn't feel like Windows. Why? BECAUSE IT ISN'T FREAKING WINDOWS!!!
>
> And, uh, what do you base this assertion on?
I base it on the fact that LINUX != WINDOWS.
> You make it sound like I used Linux for five minutes, couldn't work it,
> and gave up. That's not what happened at all!
Did you ask any questions? Or did you never, ever get to a Windows
machine where you could ask questions?
If you want to *learn*, you ask questions. You know this, because you're
moderately inquisitive about lots of different topics. But somehow it's
absolutely impossible for you to ask for a little help sorting out a
Linux issue. Far easier to just say "Linux suxxors the biggest donkey
balls" than to go to a Linux forum and ask for a little assistance!
>> Software isn't perfect. No matter which platform it is, it isn't going
>> to be perfect.
>
> Funny, I could have sworn Mac OS was perfect...
Only those who haven't used it say that. Oh, wait, you haven't used it
(by your own admission).
>> You have to be willing to take some time to learn how the system works,
>> rather than just try it and lament "it's hard".
>
> You make it sound like I've made no attempt to do so.
You say "I couldn't get it working" and didn't ask anyone with expertise
for help. That sure sounds to me like "little attempt to get some
assistance".
> I can work Linux. I can usually make it do what I want it to do. I
> pointed out one specific issue: installing stuff tends to be a
> dependency nightmare. Which is true. I don't see how that makes me an
> idiot.
It doesn't. Not asking for help when you need it? Yeah, *that's* not
too bright. Then using that experience to say "this sucks" - really not
that useful.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 21:00:12
Message: <4e90f21c$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 17:47:22 -0700, Darren New wrote:
>>> The irony is, you actually /can/ uninstall Windows networking (and
>>> even the TCP/IP protocol). And Notepad still works. :-P
>>
>> Not if you try to save to a networked drive.
>
> But that's a stupid argument. Notepad still works even without
> networking if you don't try to use networking. Linux doesn't, because
> everything assumes it's there.
Conceded.
> On the other hand, Linux still works if you uninstall graphics drivers,
> and Windows (and Notepad) fall over.
Indeed that is true. :)
>> Installing Windows + applications is a lot more than 4 GB.
>
> Windows hasn't fit on less than a DVD in quite some time. I think the
> base install is a 3.5G DVD image or so. Not counting Office and such.
Well, Andy wants to compare modern Linux distributions with a 10-year old
version of Windows. <shrug>
>> Which is why having a community to ask questions of (including 'is
>> there a pre-built package for 'x'', surprisingly enough) is a good
>> thing.
>
> Does anyone else miss the good old days when it was possible to use a
> computer based on the instructions it came with, without having to have
> a live connection open to the people who wrote the software you're
> using? Where you could buy a book, and read the book, and then use in
> all its details the software the book described?
Yes, I certainly do. Software documentation of most kinds absolutely
sucks rocks these days. It tends to focus on what the software does
rather than how to do it or why you'd want to use it the way they
designed it.
NetWare - one of my favourite OSes of all time - the last version that
had decent documentation was 2.15. *Maybe* 3.11 (it's been a while) did
as well. The last version was 6.5, and in spite of knowing and
respecting members of the team that wrote the docs, it was pretty ugly in
terms of actually being documentation.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10/8/2011 14:38, Jim Henderson wrote:
> Configuration files don't autogenerate other configuration programs.
Autoconf? :-)
> Obviously you don't know many Linux users. I know at least 5,000, and
> many of them not only love and use the GUI, but tend to have religious
> wars over which GUI is better.
I still giggle when I see someone using a gui in Linux to do things like
find files. Just because I'm so used to the command line (and GUIs for Linux
tend to suck horribly compared to something where it's the expected
interface) that it looks silly to me.
--
Darren New, San Diego CA, USA (PST)
How come I never get only one kudo?
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 21:02:24
Message: <4e90f2a0$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sun, 09 Oct 2011 01:55:00 +0100, Orchid XP v8 wrote:
> On 09/10/2011 01:50 AM, Jim Henderson wrote:
>> On Sun, 09 Oct 2011 01:45:29 +0100, Orchid XP v8 wrote:
>>
>>>>>> Why do you need that? All that sort of thing is built into Windows.
>>>>>
>>>>> Really? So how do I create an encrypted video connection to the
>>>>> target machine, while at the same time preventing anybody else from
>>>>> doing the same?
>>>>
>>>> Remote Desktop + password.
>>>
>>> Now how do you /encrypt/ that?
>>
>> It's RDP. It's already *encrypted*.
>
> Yeah, right. I'll believe it when I see it.
I use it for what I work on. The connection is encrypted. RDP ain't VNC
(which actually *isn't* encrypted).
When I connect to the Windows Server 2008 box for the classes I'm working
on, I get a certificate validation request.
That sure as hell seems to be an encrypted connection.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 21:03:52
Message: <4e90f2f8$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 18:00:56 -0700, Darren New wrote:
> On 10/8/2011 14:38, Jim Henderson wrote:
>> Configuration files don't autogenerate other configuration programs.
>
> Autoconf? :-)
Autoconf isn't really a configuration file. It's a configuration file
parser. ;)
>> Obviously you don't know many Linux users. I know at least 5,000, and
>> many of them not only love and use the GUI, but tend to have religious
>> wars over which GUI is better.
>
> I still giggle when I see someone using a gui in Linux to do things like
> find files. Just because I'm so used to the command line (and GUIs for
> Linux tend to suck horribly compared to something where it's the
> expected interface) that it looks silly to me.
Yeah, I do as well. find or locate does the job just fine, and beagle
and its successors are just resource pigs.
Though I find that the state of Linux GUIs is improving. Certainly has
since I started using it.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 21:05:08
Message: <4e90f344$1@news.povray.org>
|
|
 |
|  |
|  |
|
 |
On Sat, 08 Oct 2011 17:56:20 -0700, Darren New wrote:
> On 10/8/2011 14:23, Jim Henderson wrote:
>> Windows could benefit from implementing something akin to a Linux
>> software repository for stuff like this.
>
> They have it. Windows Update. Where your device drivers come from. :-)
I didn't know I could install Adobe Acrobat, Flash, or other third party
software from Windows Update. ;)
(That's actually what I was talking about - not about driver installs)
>> Getting the software makers to agree might take some work,
>
> And that is the problem. That, and commercial entities don't really want
> their software in Windows Update where people could install it without
> paying for it. The model really only works for free software.
The software in question I'm talking about is available gratis as it is.
Like Flash, Acrobat Reader, Java, etc.
>> but then again, Adobe has Acrobat Reader in most distributions'
>> official repositories.
>
> Probably because Adobe doesn't have to deal with it. They just have to
> give permission.
So why not something like that for Windows, too?
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Orchid XP v8
Subject: Re: Is this the end of the world as we know it?
Date: 8 Oct 2011 21:07:02
Message: <4e90f3b6@news.povray.org>
|
|
 |
|  |
|  |
|
 |
>>>> Now how do you /encrypt/ that?
>>>
>>> It's RDP. It's already *encrypted*.
>>
>> Yeah, right. I'll believe it when I see it.
>
> I use it for what I work on. The connection is encrypted. RDP ain't VNC
> (which actually *isn't* encrypted).
>
> When I connect to the Windows Server 2008 box for the classes I'm working
> on, I get a certificate validation request.
>
> That sure as hell seems to be an encrypted connection.
So, just because it does strong authentication, you think that means the
actual data is encrypted?
Given how weak the password challenge/response protocol in Windows is,
I'd be happier tunnelling via SSH or something. You know, if I could
actually find an SSH *server* for Windows... (Then I wouldn't need any
extra hardware at all.)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|
 |