[Discuss] getting seriously into Linux
George Farris
farrisga at gmail.com
Tue Jan 21 08:41:00 PST 2014
Greetings,
Also take a look at Arch is a very nice system now. Basically you end
up with a minimal install and do everything by hand but it does have a
great package system.
You can also go with Manjaro to get a fully working Arch system in a
complete desktop and Manjaro is arch but with a delay of about 30 days
on the packages to help make it smoother. I have moved away from Debian
and buntu's because Arch keeps me completely up to date, it's a full
rolling distro and much much smoother than it was a few years ago.
For an interesting take on it watch this:
http://www.jupiterbroadcasting.com/38086/the-arch-way-aas-s27e03/
George
On Tue, 2014-01-21 at 00:51 -0800, Noel Burton-Krahn wrote:
> Hi Bernie,
>
>
> You're nuts. But, if you really like to know that all your code is
> compiled from scratch, check out Gentoo or
> other http://en.wikipedia.org/wiki/Category:Source-based_Linux_distributions
>
>
> --
> Noel
>
>
>
>
> On Mon, Jan 20, 2014 at 8:13 PM, Bernie C. Till <bctill at ece.uvic.ca>
> wrote:
> Hello --
>
> My name is Bernie Till, and I'm interested in getting
> seriously into Linux,
> so I wanted to get to know some local people who have
> knowledge of, and
> experience with, various Linux distros, in addition to the art
> of compiling
> and installing Linux from scratch, as well as the practical
> aspects of
> co-located internetworking. Yes, I have a lot to learn, which
> is why I am
> here.
>
> My plan is to buy a machine, without operating system, and
> install a
> standard Linux distro, like Debian or Ubuntu on it. I will
> then assemble a
> second machine from components. Using the first machine as a
> platform to
> work from, I will download and compile everything that I load
> onto the
> second machine.
>
> The goal is that the second machine should be running nothing
> that wasn't
> compiled by me, and should be configured with an absolutely
> minimal "attack
> surface" so it can be connected to the internet 24/7 with some
> hope of being
> secure.
>
> The combination of strengths and weaknesses I bring to this
> endeavour is a
> bit unusual. I have a degree in computer science, I am
> comfortable in C,
> C++, and assembler, I have taught operating systems internals,
> and I have
> designed and implemented real-time systems including real-time
> kernels. I
> actually extended the Linux hotplug system for a client once
> upon a time,
> but the development environment (GCC, Eclypse, Ubuntu) was set
> up for me by
> the client's sysadmin. I am a complete novice when it comes
> to networking.
>
> What I'm looking for initially is some advice on how to get
> started. What
> distros do you recommend for each of the two machines, what
> hardware and
> software components are necessary, what ones are desirable,
> what should be
> avoided, and how would you proceed with the plan I've
> outlined? Any advice
> about how to run a co-located server (not restricted only to
> the www) would
> be invaluable, as would recommendations for co-location
> companies in
> Victoria.
>
> Also, I'm hoping to draw on the community's base of practice
> and experience
> when I run into weird error messages that have no right to
> exist, and when I
> try to make sense of documentation that assumes familiarity
> with a culture
> that I haven't yet had time to assimilate.
>
> So... if you're willing to help me out with any of this, I
> would love to
> hear from you.
>
> Regards,
> -- Bernie.
>
> _______________________________________________
> Discuss mailing list
> Discuss at vlug.org
> http://lists.vlug.org/mailman/listinfo/discuss
>
>
> _______________________________________________
> Discuss mailing list
> Discuss at vlug.org
> http://lists.vlug.org/mailman/listinfo/discuss
More information about the Discuss
mailing list