On Fri, Oct 22, 2004 at 09:22:16AM -0400, Greg Freemyer wrote:
On Fri, 22 Oct 2004 01:16:30 -0400, Doug McGarrett
wrote: At 12:59 AM 10/22/2004 +0200, you wrote:
Wed, 13 Oct 2004, by gorebofh@comcast.net: [..]
I don't know if this is a troll, but if not, then this:
Wait, you think I'm a Troll??? Heh, dude, I've made more people switch from XP, RedHat, and other OSs over too SUSE than any marketing company could dream of, and I don't get paid for it. Hell, anyone on http://www.antionline.com knows me and knows how I feel about SUSE
connected terminals. (VT100/Wyse50/etc.) They were referred to as time-sharing computers by some.
Man, you guys got too play with all kinds of cool toys :( Heh, I've never used a Terminal like that.
Typically the console is a directly connected keyboard/monitor like most PC's have, but it can also be a serially connected terminal. ie. the words are not incompatible. Heh, I'm not green, but you have too realise I've only had a computer for 5 years, so my experience is limited on older hardware. I think I got too use a 486 once. Something all of you have probably used.
The key things is that with Linux, the console is where certain system level errors go by default. (think oops, etc.)
I think that's what I see when I am on VC1 and keep on going back farther, it shows me messages, just not errors. I found that by accident one day, I held the ALT and <-- button down too long by accident.
significant output before they crash. I don't know if it is even possible to capture this output with a directly connected console. Using the laptop/terminal emulator/serial console function, you can enable logging in the terminal emulator and save the oops to a disk file on the laptop.
People doing kernel development are particularily found of serial consoles.
Can you give some detail on this? I've never talked too any Kernel developers, but why are they fond of those?