[Lias] Thanks for help re Proxy

[Trevor Gunter]

Craig

What you have put below is very similar to what was on the screen when it
crashed at first.

Just a comment though. I don't know how many teachers are on the Lias list
but it seems to only get rarely used. Each time I have asked for help it has
been very forthcoming and appreciated. I know that the questions I ask (and
maybe others) are at time simplistic for all the Linux gurus out there but
those of us who need the help are most often teachers first and that's what
we are skilled at (hopefully). I spend half my time teaching, half my time
managing the Novell network and another half fixing everybodies minutae
problems. Learning more Linux stuff comes in the "find out when I need to"
basket.

I know that's a poor excuse and I appreciate all of you not treating those
teachers on this list who have varying levels of Linux skills (usually low)
as newbies. However, I find that a lot of what people recommend for me to
do, I will try and often bumble through, but what some have suggested I have
little idea of what it means or even how to do it. I know this comes in the
category of RTFM and I do try, but there are just so many hours in the day
and we are teachers first trying to integrate Linux into schools in varying
ways.

I'm out at Bathurst and Peter Hughes who also subscribes to this list is at
Forbes. We're not exactly flushed with Linux experts in schools out here.
We're probably it, but I feel like a dill at times. I know that I am not
keeping up with Linux trends, ideas etc. What can we do in this regard. We
are being very reactive to Linux in schools, I'd like to be more proactive.

Please be gentle with us poor teachers and thanks again for the help.

Trevor

> Unable to handle kernel NULL pointer dereference at virtual address
> 00000002c
> c026d0c9
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<c026d0c9>]    Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010206
> eax: 00000028   ebx: dfccc3a8   ecx: 01800204   edx: 00000001
> esi: dfccc3a8   edi: dfc265a0   ebp: 00000000   esp: defe5da8
> ds: 0018   es: 0018   ss: 0018
> Process syslogd (pid: 281, stackpage=defe5000)
> Stack: c15d957c dfc265a0 c15d9560 00000000 df381018 c01da1dc dfccc3c0
> dfc26620
>         dfccc3e0 dfccc380 dfc0c1e0 00000000 c026d750 c15d9560 dfc265a0
> 00000001
>         c15d957c c15d9560 00000001 00000000 00000008 c038e600 00000000
> c026d9c2
> Call Trace:    [<c01da1dc>] [<c026d750>] [<c026d9c2>] [<c010985d>]
> [<c01099c6>]
>    [<c010bbc8>] [<c02707e9>] [<c0271792>] [<c012f3e4>] [<c012f5c3>]
> [<c012f5de>]
>    [<c01408fa>] [<c0140bf8>] [<c027188e>] [<c0271f44>] [<c010856f>]
> Code: 8b 2c 90 8b 44 24 28 c1 e9 08 83 e1 0f d3 ed 83 e5 01 c7 44
>
>
> because if so, it was probably a kernel panic that took it down. The
> reason for the file system corruption in this case is usually that the
> fs was in the middle of writing data to the disk when the machine crashed.
>
> Journalling filesystems like reiserfs and ext3 are designed to help
> prevent this problem. If you have a vaguely recent distro with a 2.4
> kernel, you should be able to convert your existing filesystems from
> ext2 to ext3 relatively easily.... after you back up, just to make sure.
> There's plenty of info on the 'net about how to do this.
>
> Craig Ringer
> IT Manager
> POST Newspapers
>
>
> _______________________________________________
> lias mailing list
> lias at lists.linux.org.au
> http://lists.linux.org.au/listinfo/lias
>
>