[SATLUG] Question about questions

[FIRESTORM_v1]

Well....

I can tell you from experience.......

1: Trying to compile a Linux kernel while drunk *may* result in a working
kernel but the odds are against you.
2:  the command "cat /dev/urandom > /dev/dsp" is a cool thing to do when you
want to scare the bejeezus out of someone via a remote SSH session. (if you
try this, turn your speakers down.)
3: The command "eject /dev/cdrom && eject -t /dev/cdrom" repeatedly via a
remote SSH session is a good way to get your roomates/parents/kids to think
your computer is possessed.
4: anyone telling you to "cat /dev/urandom >/dev/hda" is a safe command is
not to be trusted.
5: If you do attempt to compile a kernel, make sure you know your hardware.
After all, the pegasus, usb_cdrom, usb_storage, usb_hid drivers won't work
if your USB OHCI card can't initialize because you compiled the module for
USB UHCI.
6: There's no place like /home.
7: Or 127.0.0.1

Hope that helps, or at least makes you chuckle.

On a more serious note, Jeremy's right.  The best way to try it is to jump
right in.  A seccondary machine that isn't your test box would be
recommended so if your test box blows up, you can still do research/email
for help/find the nearest liquor store.  An alternative to having two
machines would be to use VMware Server (free) to set up a linux installation
on so that way if it blows up, you won't have to reinstall two OS'es (if i's
a dualboot and something went REALY wrong.


Good Luck.


FIRESTORM_v1

On Sun, Feb 24, 2008 at 6:34 PM, Jeremy Mann <jeremymann at gmail.com> wrote:

> Herb, you can only learn by trial by fire. Get it working, break it
> and try different things to fix it. Once you do that, break it again.
> Then, break it again. There's nothing in a book that will tell you
> everything to look for, a few things, but not everything.
>
> On Sun, Feb 24, 2008 at 4:52 PM, herb cee <hc at lookcee.com> wrote:
> >
> >  I wanna take advantage of the quiet spell and ask this.
> >
> >  So I know now after 9mos that learning Linux is hard and learning Linux
> >  when you're dumb is really hard. I don't recall seeing this printed as
> >  super important but you really have to learn about the CLI and learn
> >  some basic commands as soon as you can, if you are the admin/user.
> >
> >  I think one of the most important to understand that when dudes like me
> >  is/are a sole user, I am Captain, I must know where the bridge is. To
> do
> >  that I had to understand how to make sure I knew where the bridge is
> now
> >  not last time, tricky devil can be anywhere on the ship, and how to get
> >  there when the Captain gives a command.
> >
> >  So I also have learned that you need to know some stuff just to know
> how
> >  to ask the question, I still don't know what to read on and I wonder
> >  what questions all you cool dudes on the list would recommend to get
> off
> >  the ground learning how to steer the damn ship off the rocks? I mean
> >  regardless of why I want to use the puter for but to keep it running
> and
> >  know how to get out of a fix like being in the galley thinking I was on
> >  bridge and typing the command and winding up with a black screen, yep I
> >  did that one.
> >
> >  Thanks folks, herb
> >  --
> >  _______________________________________________
> >  SATLUG mailing list
> >  SATLUG at satlug.org
> >  http://alamo.satlug.org/mailman/listinfo/satlug to unsubscribe
> >  Powered by Rackspace (www.rackspace.com)
> >
>
>
>
> --
> Jeremy Mann
> jeremy at biochem.uthscsa.edu
>
> University of Texas Health Science Center
> Bioinformatics Core Facility
> http://www.bioinformatics.uthscsa.edu
> Phone: (210) 567-2672
> --
> _______________________________________________
> SATLUG mailing list
> SATLUG at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug to unsubscribe
> Powered by Rackspace (www.rackspace.com)
>