Linux Introduction

Linux Introduction

[JP Jamous]

Thank you all for your feedback. I have to say that this is a new area for
me that I am exploring. I don't mind the command prompts, but I prefer the
GUI, due to speed and ease of use.
 
I am just wondering how much RAM and CPU power does Linux use? The servers
that I would eventually like to install Linux on are P3 Xeon processors with
anywhere from 128MB of RAM up to 1GB.
 
I am familiar with the history of Linux, but not the way it functions. I am
going to follow your feedback and give it a test drive. I just asked the
above questions to be ahead of the game when I implement it. Thank you.

Re: Linux Introduction

[Tyler Littlefield]

My old debian system used to run off a p3 with 128 ram. The ram depends on what you use; I had a LAMP system going for being able to play with php/mysql stuff locally, but the more users you get on your site and the more daemons/processes running, the more ram you'll want. Php instances are rather big, etc. You can use swap too, but when the system starts thrashing you'll have issues in terms of speed. Reading and writing from the hd is considerably slower than ram, and the applications that are forced to use swap are going to be considerably slower than they would be if you had the right amount of ram for them to run.

		Thanks,
Tyler Littlefield
	http://tds-solutions.net
	Twitter: sorressean

On Mar 14, 2010, at 4:10 PM, JP Jamous wrote:

> Thank you all for your feedback. I have to say that this is a new area for
> me that I am exploring. I don't mind the command prompts, but I prefer the
> GUI, due to speed and ease of use.
> 
> I am just wondering how much RAM and CPU power does Linux use? The servers
> that I would eventually like to install Linux on are P3 Xeon processors with
> anywhere from 128MB of RAM up to 1GB.
> 
> I am familiar with the history of Linux, but not the way it functions. I am
> going to follow your feedback and give it a test drive. I just asked the
> above questions to be ahead of the game when I implement it. Thank you.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Linux Introduction

[Alex H.]

Hello,

Basically the "bigger the better" applies here. If you're going to run
a server with 128 MB of RAM, putting a GUI on it isn't a good idea.
Use Speakup and a minimal console system. It also depends on how much
traffic you're planning to have on the servers. Linux does run much
lighter than other legacy OS's propperly configured. HTH

Alex

On 3/14/10, Tyler Littlefield <tyler@tysdomain.com> wrote:
> My old debian system used to run off a p3 with 128 ram. The ram depends on
> what you use; I had a LAMP system going for being able to play with
> php/mysql stuff locally, but the more users you get on your site and the
> more daemons/processes running, the more ram you'll want. Php instances are
> rather big, etc. You can use swap too, but when the system starts thrashing
> you'll have issues in terms of speed. Reading and writing from the hd is
> considerably slower than ram, and the applications that are forced to use
> swap are going to be considerably slower than they would be if you had the
> right amount of ram for them to run.
>
> 		Thanks,
> Tyler Littlefield
> 	http://tds-solutions.net
> 	Twitter: sorressean
>
> On Mar 14, 2010, at 4:10 PM, JP Jamous wrote:
>
>> Thank you all for your feedback. I have to say that this is a new area for
>> me that I am exploring. I don't mind the command prompts, but I prefer the
>> GUI, due to speed and ease of use.
>>
>> I am just wondering how much RAM and CPU power does Linux use? The servers
>> that I would eventually like to install Linux on are P3 Xeon processors
>> with
>> anywhere from 128MB of RAM up to 1GB.
>>
>> I am familiar with the history of Linux, but not the way it functions. I
>> am
>> going to follow your feedback and give it a test drive. I just asked the
>> above questions to be ahead of the game when I implement it. Thank you.
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: Linux Introduction

[John G. Heim]

I think you've gotten a lot of good advice in this thread. The only thing 
I'd add is that if you are getting into linux with the goal of ultimately 
finding a job as a linux systems administrator, you should eventually work 
toward learning the command line and you should ultimately end up using 
either fedora or debian (or both). Getting started with ubuntu or one of the 
other easier to use distros is probably the best plan because there is 
nothing worse than trying to learn both a new operating system and a new 
screen reader at the same time. That is a very difficult task.  So starting 
off with whatever is easiest is probably your best bet. I'm guessing that 
would be ubuntu but opinions may vary.

Anyway, probably the best linux related item you can put on a resume is 
knowledge of Red Hat and/or fedora. Second would be debian. Being able to 
use Thunderbird and Firefox in ubuntu might help a little but that's not 
really what employers are looking for.

I was actually a web programmer before I got my current job. I felt that web 
programming was a dying profession so I bought a used computer, put linux on 
it, and taught myself network, database, and web server administration. I'd 
have included email administration if i'd had any sense. I was able to go 
into job interviews and let them connect to this server and I even gave some 
of the people who interviewed me accounts on my machine.

----- Original Message ----- 
From: "JP Jamous" <JP@Jepelsy.com>
To: <speakup@braille.uwo.ca>
Sent: Sunday, March 14, 2010 5:10 PM
Subject: Linux Introduction


> Thank you all for your feedback. I have to say that this is a new area for
> me that I am exploring. I don't mind the command prompts, but I prefer the
> GUI, due to speed and ease of use.
>
> I am just wondering how much RAM and CPU power does Linux use? The servers
> that I would eventually like to install Linux on are P3 Xeon processors 
> with
> anywhere from 128MB of RAM up to 1GB.
>
> I am familiar with the history of Linux, but not the way it functions. I 
> am
> going to follow your feedback and give it a test drive. I just asked the
> above questions to be ahead of the game when I implement it. Thank you.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> 

Re: Linux Introduction

[Jason White]

John G. Heim <speakup@braille.uwo.ca> wrote:
>I think you've gotten a lot of good advice in this thread. The only thing 
>I'd add is that if you are getting into linux with the goal of ultimately 
>finding a job as a linux systems administrator, you should eventually work 
>toward learning the command line and you should ultimately end up using 
>either fedora or debian (or both). 

Knowing the shell very well is a prerequisite to being a competent and
effective Linux user, and even more so for anyone who wants to administer
systems for other people, professionally or otherwise.

Speakup would be a good starting point, since it has very few dependencies and
can run even when large parts of the system are unavailable - precisely the
situations in which an administrator's skills are put to the test.

I would suggest learning to use the shell and Linux tools as a user first,
proceeding thereafter to acquire administrative skills.

RE: Linux Introduction

[JP Jamous]

Thank you so much for your responses. I have been a Windows platform
administrator for the last 12 years.

Is there a certain book or site recommended to learn the shell commands?

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Jason White
Sent: Monday, March 15, 2010 9:11 PM
To: speakup@braille.uwo.ca
Subject: Re: Linux Introduction

John G. Heim <speakup@braille.uwo.ca> wrote:
>I think you've gotten a lot of good advice in this thread. The only 
>thing I'd add is that if you are getting into linux with the goal of 
>ultimately finding a job as a linux systems administrator, you should 
>eventually work toward learning the command line and you should 
>ultimately end up using either fedora or debian (or both).

Knowing the shell very well is a prerequisite to being a competent and
effective Linux user, and even more so for anyone who wants to administer
systems for other people, professionally or otherwise.

Speakup would be a good starting point, since it has very few dependencies
and can run even when large parts of the system are unavailable - precisely
the situations in which an administrator's skills are put to the test.

I would suggest learning to use the shell and Linux tools as a user first,
proceeding thereafter to acquire administrative skills.


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

RE: Linux Introduction

[Øyvind Lode]

The Linux Documentation Project is a good starting point.
Start off with the Introduction To Linux book.
Then Bash Guide for Beginners and then Advanced Bash Scripting.
There is also System Admin manuals and Networking books available.

http://www.tldp.org/

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of JP Jamous
Sent: 16. mars 2010 07:19
To: 'Speakup is a screen review system for Linux.'
Subject: RE: Linux Introduction

Thank you so much for your responses. I have been a Windows platform
administrator for the last 12 years.

Is there a certain book or site recommended to learn the shell commands?

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Jason White
Sent: Monday, March 15, 2010 9:11 PM
To: speakup@braille.uwo.ca
Subject: Re: Linux Introduction

John G. Heim <speakup@braille.uwo.ca> wrote:
>I think you've gotten a lot of good advice in this thread. The only 
>thing I'd add is that if you are getting into linux with the goal of 
>ultimately finding a job as a linux systems administrator, you should 
>eventually work toward learning the command line and you should 
>ultimately end up using either fedora or debian (or both).

Knowing the shell very well is a prerequisite to being a competent and
effective Linux user, and even more so for anyone who wants to administer
systems for other people, professionally or otherwise.

Speakup would be a good starting point, since it has very few dependencies
and can run even when large parts of the system are unavailable - precisely
the situations in which an administrator's skills are put to the test.

I would suggest learning to use the shell and Linux tools as a user first,
proceeding thereafter to acquire administrative skills.


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Linux Introduction

[Gaijin]

On Sun, Mar 14, 2010 at 06:10:09PM -0400, JP Jamous wrote:
> Thank you all for your feedback. I have to say that this is a new area for
> me that I am exploring. I don't mind the command prompts, but I prefer the
> GUI, due to speed and ease of use.

	I'm running Debian Linux on a P6 Celeron at 2GHz, and the Orca 
screen reader in the GUI is as slow as molasses, sometimes taking 5 full 
seconds for the next keypress to be read, if at all, and I'm running the 
fastest Seagate HDD I could find, in 1.25G of memory.  I don't know if a 
P3 could handlethe Orca screen reader, as I think it's a piece of crap 
at my end.  I stick with (gags) Windows and the NVDA 
(www.nvda-project.org) screen reader for any GUI operations here.  I 
told those Orca losers years ago they were implementing it wrong and 
they'd be spending their time from now until doomsday, cleaning up other 
programmer'sFUBARs, but hey, what can I say.  No accessibility standard, 
no accessibility following by the mainstream.  Hehe.

				Michael

Re: Linux Introduction

[John G. Heim]

With all due respect, Michael, you shouldn't refer to orca as "a piece of 
crap" or to the developers as losers. First of all, its not true. Secondly, 
it is rude and counter productive. If you think you're making people think 
less of orca, you're wrong. All it does is make people think less of you.

----- Original Message ----- 
From: "Gaijin" <gaijin@clearwire.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, March 17, 2010 1:34 PM
Subject: Re: Linux Introduction


> On Sun, Mar 14, 2010 at 06:10:09PM -0400, JP Jamous wrote:
>> Thank you all for your feedback. I have to say that this is a new area 
>> for
>> me that I am exploring. I don't mind the command prompts, but I prefer 
>> the
>> GUI, due to speed and ease of use.
>
> I'm running Debian Linux on a P6 Celeron at 2GHz, and the Orca
> screen reader in the GUI is as slow as molasses, sometimes taking 5 full
> seconds for the next keypress to be read, if at all, and I'm running the
> fastest Seagate HDD I could find, in 1.25G of memory.  I don't know if a
> P3 could handlethe Orca screen reader, as I think it's a piece of crap
> at my end.  I stick with (gags) Windows and the NVDA
> (www.nvda-project.org) screen reader for any GUI operations here.  I
> told those Orca losers years ago they were implementing it wrong and
> they'd be spending their time from now until doomsday, cleaning up other
> programmer'sFUBARs, but hey, what can I say.  No accessibility standard,
> no accessibility following by the mainstream.  Hehe.
>
> Michael
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> 

Re: Linux Introduction

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Mar 18, 2010 at 10:19:18AM -0500, John G. Heim wrote:
> With all due respect, Michael, you shouldn't refer to orca as "a piece of 
> crap" or to the developers as losers. First of all, its not true. 
> Secondly, it is rude and counter productive. If you think you're making 
> people think less of orca, you're wrong. All it does is make people think 
> less of you.

Exactly, and if you think that orca is a piece of crap, then why don't
you get involved in some way, and try to make it better however you
can. Ranting about the software, and the people working on it isn't
productive, and doesn't help anyone make the software better, or in
deciding whether someone wants to use the software, or not.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkuicMIACgkQ7s9z/XlyUyCEWACfQRphX5/iU8v1CmjQafajqRVc
EAgAn0UYGwb0taATl7dGv8M0y9zWEQbn
=w404
-----END PGP SIGNATURE-----

Re: Linux Introduction

[Jason White]

Gregory Nowak  <speakup@braille.uwo.ca> wrote:

>Exactly, and if you think that orca is a piece of crap, then why don't
>you get involved in some way, and try to make it better however you
>can. Ranting about the software, and the people working on it isn't
>productive, and doesn't help anyone make the software better, or in
>deciding whether someone wants to use the software, or not.

Another option is to start your own project and write an alternative
implementation. If it's any good, others will start using it. If not, they
won't. That's how the community works. Rants are not helpful and not
appreciated.