From: Daze N. Knights on 28 Aug 2006 13:18 raincoater wrote: > Hello, Mark Warner ! > You wrote: > > >> No. KDE is the window manager; e.g. the GUI interface and all the basic >> programs and utilities that come with it. Gnome is the other big name. >> >> Knoppix is a live CD packge based on Debian that uses Gnome. > > Not so. Knoppix defaults to KDE. You're late to the party. Someone else already nailed Mark on that one. ;-) -- Daze
From: Mark Warner on 28 Aug 2006 13:46 Daze N. Knights wrote: > raincoater wrote: >> >> Not so. Knoppix defaults to KDE. > > You're late to the party. Someone else already nailed Mark on that one. ;-) You're enjoying this, aren't you? -- Mark Warner lose .inhibitions when replying
From: raincoater on 29 Aug 2006 12:27 Hello, Daze N. Knights! You wrote: > You're late to the party. Someone else already nailed Mark on that one ;-) Sorry bout that. I read my usenet groups on my Palm device at work and reply at that time, but the replies don't get posted until my next HotSync session, which is sometimes a number of hours later. I guess timeshifting isn't such a good idea with usenet. -raincoater PS-I'm usually not even invited to the party, so 'better late than never'. :0)
From: Al Klein on 29 Aug 2006 15:16 On 29 Aug 2006 18:27:27 +0200, raincoater(a)x-privat.org (raincoater) wrote: >Sorry bout that. I read my usenet groups on my Palm device at work and >reply at that time, but the replies don't get posted until my next HotSync >session, which is sometimes a number of hours later. I guess timeshifting >isn't such a good idea with usenet. >-raincoater It's inherent in Usenet. For instance, you wrote your post at 18:27 your time (or posted it then, I don't know which), while I read it at 21:18 your time (if my calculations are correct - 15:18 New York time) - a shift of almost 3 hours. While it's possible to have an almost realtime conversation on Usenet (I used to do it with someone about 20 years ago), most posts are responding to posts that were posted hours (if not days, weeks or months) ago.
From: Richard Steven Hack on 1 Sep 2006 20:50
On Sun, 27 Aug 2006 20:44:24 -0700, Daze N. Knights wrote: > Mark Warner wrote: >> mike wrote: >> >> Yes, getting the lingo can be difficult. One reason is that using Linux >> gives you so many choices, and all those choices have different names. >> >> In very non-technical terms: >> >> "Linux" is the kernel -- the base layer that interacts with the >> hardware. It is strictly command line. Everything is built on top of it. >> This alone can be considered an operating system, though only a few >> uber-geeks would find it useful. Well, true enough for end users, but UNIX has been run like that for thirty years. And it's damn nice to have a command line system underlying the GUI when the GUI for some odd reason dies. I had a client running a Linux file server for a law office. The /tmp directory filled up due to the idiots who installed in dumping everything including games on a file server. The X server dies when /tmp fills up. But their file serving just kept on keeping on. The only issue was the office manager couldn't run the backup system since it depended on a GUI frontend. Redirecting /tmp to some open file space on another partition brought the X server right back up. Not the best solution - the best solution would be redesigning their partitions to free up adequate space on root for /tmp - but it worked. In Windows, when the GUI dies, you have to resort to the lame Recovery Console - which has barely enough tools to resuscitate a system. >> "KDE", "Gnome", "xFce", "Fluxbox", etc. are window managers -- they are >> essentially the GUI interface and a set of included applications. >> Windows-think prevents us from thinking of the kernel and the window >> manager as being separate, but they are -- W2K, XP, and 2K3 are all >> built on the Microsoft NT kernel. Just a pedantic nitpick - XFce, Fluxbox and the like are "window managers" - KDE and GNOME are desktops/application layers. There IS a difference. A window manager just does that and little else. A desktop/application layer provides window management and a lot more - such as APIs for applications to communicate with each other and the like. It's more like the Windows shell. >> Then there are the applications. Some are essentially stand-alone, >> others "depend" on other components found in KDE or Gnome or elsewhere. That's the difference between a window manager and an application layer. >> Fortunately, the 'apt' and/or 'rpm' systems that are used to download >> and install most applications are able to seamlessly find these >> 'dependencies' and include them in the download and installation. MOST of the time...:-) >> Other bases are Red Hat, which has spawned Mandriva Used to be - Mandriva has been entirely separate from Red Hat for some years. But yeah, they started out as a derivative of Red Hat and they're both rpm-based (i.e., they use the same underlying package management tools, although the GUI front-ends to those tools are entirely different.) All in all, a nice recap, though. |