[juneau-lug] Re: Linux Installed

  • From: "Zachary Family" <dzachary@xxxxxxxxx>
  • To: <juneau-lug@xxxxxxxxxxxxx>
  • Date: Mon, 23 Jul 2001 10:14:20 -0800

----- Original Message -----
From: Tony <tony.taylor@xxxxxxxxxx>
To: <juneau-lug@xxxxxxxxxxxxx>
Sent: Monday, July 23, 2001 8:25 AM
Subject: [juneau-lug] Re: Linux Installed


| > Not sure what order would make sense to tackle some of these....
| >
| > 1. sharing the hard drive space with Win 98 machines on local network
| > 2. sharing the hard drive space with DOS 6.22 machines on local network
| > 3. establishing a local e-mail server for in-house e-mail with a port to
the
| > real world
| > 4. learn perl scripting language
| > 5. ???
|
|
| If you have experience networking MS-Windows machines, then 1&2 make
| sense.

    I've done a little of 1, but not to a point that it is really
satisfactory.
    Don't have #2 going yet.



If you can re-compile your kernel, I'd also suggest setting up
| your Linux machine to be a masqing proxy for your other machines (also
| called PAT (port address translation)).

    I've never messed with compiling or re-compiling the Kernel.  Is that a
big deal or pretty straightforward?  once I have linux running, I don't
really care to mess it up and have to start all over again if a destroy the
kerner with a small typo or something. At this point, Linux still feels very
fragile to me.  It works, but I can easily mess it up and get stuck.  (I
love to tinker with things, but that sometimes gets me in trouble on
computers. Can't afford to have a production machine at work down for
several days because I tinkered with something and have to reinstall the
system.).



| 4 will be an ongoing experience.  If you are serious about learning
| Perl, pick up the O'Reilly books "Learning Perl," and "Programming
| Perl."  They are invaluable.

    I think that I have the Programming Perl book -- latest edition.  Feels
like learning to swim in the ocean with 20 foot seas. So I've been
supplimenting with some perl tutorials that I find online to cover some of
the basics that the book appears to assume that you already know. Still lots
of questions.


|
| I've been programming Perl for about 4 years now, and I'm a long way
| from being an expert, so don't get too frustrated when you realize
| you've been programming Perl for 4 years and there are wizards who write
| code you can't read.
|
| 5 should be (IMNSHO), "Learn to compile and install from source."  Start
| simply (say, with some Gnome or KDE package that doesn't come
| pre-packaged (say, Downloader for X at
http://www.krasu.ru/soft/chuchelo/ )

    THIS SOUNDS LIKE A GOOD IDEA.

    I suppose that there are so many variables in Linux that it is hard to
write a single How To that really covers a project.  Many that I have read
seem to have some rather specific assumptions about the system that you are
running.

    I tried doing a Mozilla install, for example, over the weekend.  The
docs were pretty clear, although concise.  I think that I followed them step
by step.  Then it says that "this step will create a directory ./package".
Well, that did not happen.  Did not see an error message. There was supposed
to be a program installed in the ./package directory, but since the
directory did not exist, neither did the program.  The KDE version of the
install program asked for a directory to install the program.  created the
directory and then entered that choice into the 'box'.  installed responds
that it cannot find the directory, although I was able to navigate to it.
Yes, the capitalization was correct.  The installed still could not find it
and thus exited with an error message to start all over.  Ah, well.



|
| Then move up to compiling your kernel (if you didn't do that for 1&2
| already).
|


    No, have not compiled kernels yet.

Dan



------------------------------------
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the 
word unsubscribe in the subject header.

Other related posts: