On Tuesday 05 June 2012 12:01:28 Chris Bannister wrote:
> I personally find Mr O'Reilly's books excellent. Recommended
> reading
In particular for the OP's question, "Running Linux" and "Linux in a
Nutshell". They have become my Linux bibles.
Lisi
--
To UNSUBSCRIBE, email to debian-user-req
Am Dienstag, 5. Juni 2012 schrieb Chris Bannister:
> On Tue, Jun 05, 2012 at 01:20:58PM +1000, terryc wrote:
> > On 05/06/12 03:55, Martin Steigerwald wrote:
> > I've told O'Reilly that their books are rather useless for trouble
> > shooting or learning for the average person.
>
> Ouch!, what did
On Tue, Jun 05, 2012 at 01:20:58PM +1000, terryc wrote:
> On 05/06/12 03:55, Martin Steigerwald wrote:
> I've told O'Reilly that their books are rather useless for trouble
> shooting or learning for the average person.
Ouch!, what did he say? Also, I have trouble envisioning the average
person.
P
I am subscribed, no need to Cc.
Am Dienstag, 5. Juni 2012 schrieb terryc:
> On 05/06/12 03:55, Martin Steigerwald wrote:
> >> I know this will be a rather difficult thing to answer I think, but
> >> are there any generic steps
>
> Nope. It really depends on the error/problem.
> The beauty of *nix
On 05/06/12 03:55, Martin Steigerwald wrote:
I know this will be a rather difficult thing to answer I think, but
are there any generic steps
Nope. It really depends on the error/problem.
The beauty of *nix is that it is compartmentalised and rarely does a
problem in one "cause" a problem in a
Am Montag, 4. Juni 2012 schrieb DragonDon:
> Greetings all!
Hi!
> I know this will be a rather difficult thing to answer I think, but
> are there any generic steps listed somewhere on how to troublehshoot a
> problem on a Debian/Linux system? I understand that each problem can
> be rather unique
paiva...@gmail.com wrote:
DragonDon writes:
> 1/ Check logs. Insert ways to check various logs (both CLI and GUI)
> 2/ Type commands (for networks use command A, for video use command
> B, for)
Aren't the first steps:
1. Are the lights on in your house?
2. Is it plugged in?
3.
DragonDon writes:
> 1/ Check logs. Insert ways to check various logs (both CLI and GUI)
> 2/ Type commands (for networks use command A, for video use command
> B, for)
That is way how it is. What is wrong with that?
>
> Right now, and perhaps the only method, is to plunk in any err
On Mon, 04 Jun 2012 09:07:06 +0900, DragonDon wrote:
> Greetings all!
>
> I know this will be a rather difficult thing to answer I think, but are
> there any generic steps listed somewhere on how to troublehshoot a
> problem on a Debian/Linux system?
Uf... "experience" is our best ally here. I
On 6/3/2012 7:07 PM, DragonDon wrote:
> Greetings all!
>
> I know this will be a rather difficult thing to answer I think, but
> are there any generic steps listed somewhere on how to troublehshoot a
> problem on a Debian/Linux system? I understand that each problem can
> be rather unique on how
10 matches
Mail list logo
