You don't need to learn c/c++ if you just want to be a Linux sysadmin, you
only really need to know them if you want to develop applications. But at
the very least you need to know how to compile applications (which varies
on a per application bases)
I highly recommend learning python, it is easy to learn, available out of
the box on just about every Linux distro which makes it the ideal language
to write scripts in as it is highly likely that they will work on most
Linux systems without needing to install many extra packages.
I also recommend learning how to use the vi editor as it is often the only
editor on some systems and you will likely need to at least know how to use
it.
Apart from that the best way to learn is to get stuck in and try installing
the services you want, configuring them to do what you want and playing
around with them. If you get stuck or need help there is plenty of support
out, just don't be afraid to ask for it ;)
On 20 August 2013 11:31, Gordon Scott <gordon@???> wrote:
> On 20/08/2013 07:27, Bob Dunlop wrote:
>
>> or ./configure && make && make install
>>
>
> You could consider variant like this, too:
>
> ( ./configure ; make ; make install ) 2>&1 | tee Errors.txt
>
> FWIW, I personally always do the three stages of installing separately.
> The "make install" often needs a sudo, unless you're already root.
You should always use && instead of ; for that sequence of commands, as &&
will stop when one of the commands fails, where ; will just continue with
the next command and you really don't want to make if configure fails, or
make install if make fails (the point Bob Dunlop was trying to make). You
might also be interested in "command1 || command2" where command2 will only
run if command 1 fails, very useful for exiting a script on failure:
command1 || exit 1 # Will exit if command 1 fails for any reason
command2
Also, there is no reason you cannot add sudo to the make install command,
and you should NEVER* run "make" as root.
( ./configure && make && sudo make install ) &> | tee errors.log
Though I dislike "sudo make install", and prefer to package things properly.
There is also no reason to use the .txt extension, most file on linux are
text files of some sort, best to give them extensions that tell you what is
in side them so you can easily tell the difference between errors.log and
errors.sh.
* unless you really really know what you are doing and know the potential
problems and there is no possible way around it.
On 19 August 2013 23:53, Ally Biggs <bluechrome@???> wrote:
> Thanks for the replies, I use Red Hat primarily because I have been
> looking at the RHCSA / RHCE materials and that is what I am comfortable
> using. I have used Debian and Ubuntu Server alot aswell but for the time
> being Red Hat is what I have stuck with.
>
> I'm not a programmer I don't have the mentality and currently I would say
> the Linux side of things is more of a hobby / passion I work primarily
> supporting and maintaining Windoze boxes. Although I am teaching myself
> BASH scripting nothing to serious at the moment just building the
> foundation dabbling customising the shell, writing rsync scripts Nothing
> to fancy just basic level stuff. My lack of programming experience is
> holding me back in terms of understanding stuff like variables, functions,
> loops so it was suggested that I learnt Python to get a foundation?
> Is this a good choice or should I stick with BASH scripting.
>
> The small business / charity side appeals to me, I work for Jamie's
> computers I like the whole ethos of reuse and putting older hardware to
> good use. I would love to one day run my own enterprise that specialises in
> providing Open Source solutions to this sector.
>
> As for areas of Internet myself I guess I enjoy the networking /
> Administration side of things. I have a few goals which I want to delve
> into further.
>
> Apache web server
> Samba file server (setup D/C)
> Rsync and scheduling backups cron.
> Proxy server
> FTP server
> Administration / user management
> Firewall setting up IP tables
> SElinux configuration
> Media Server setup
> KVM virtualisation
> Unattended installations via kickstart
>
> Those are the areas of interest for myself and areas I intend to work on.
> Would be kool to meet some of you guys and learn from the masters :)
>
> On 19 Aug 2013, at 23:12, "Keith Edmunds" <kae@???> wrote:
>
> > On Mon, 19 Aug 2013 20:35:22 +0100, bluechrome@??? said:
> >
> >> My interest is more in the way of providing Open Source solutions to
> >> small business / Charity completely bypassing the Windows side from a
> >> server perspective altogether.
> >
> > Why specifically small businesses and charities?
> >
> >> My distro of choice is Red Hat have been looking at the RHCSA materials
> >> and I feel this is the path I wish to go down.
> >
> > Look at where you want to end up. Do you need RH qualifications to get
> > there? Why is your choice of distro important? To whom is it important?
> >
> >> Sent from my iPhone
> >
> > Are you sure you want to be Linux through and through?
> >
> > Start with the end point. You originally asked, "How do you start a
> career
> > in Linux?", but you haven't said what you want to do. Program? Support?
> > Consult? Sell? Evangelise? Describe (at least to yourself) in as much
> > detail as you can how you want it to be. Then you can work out how to get
> > there.
> > --
> > "You can't live a perfect day without doing something for someone
> > who will never be able to repay you."
> >
> > --
> > Please post to: Hampshire@???
> > Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
> > LUG URL: http://www.hantslug.org.uk
> > --------------------------------------------------------------
>
> --
> Please post to: Hampshire@???
> Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
> LUG URL: http://www.hantslug.org.uk
> --------------------------------------------------------------
>
--
Michael Daffin <james1479@???>
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
