[UCLA-LUG] Dan Helfman

Thu, 13 Apr 2000 08:31:59 -0700

Thanks Dam it work ,

Luis

ps i'm still having trouble with the themes. you would also know how to 
make the icons smaller.

At 07:22 AM 4/13/00 -0700, you wrote:

>Send Linux mailing list submissions to
>         linux@linux.ucla.edu
>
>To subscribe or unsubscribe via the web, visit
>         http://linux.ucla.edu/mailman/listinfo/linux
>or, via email, send a message with subject or body 'help' to
>         linux-request@linux.ucla.edu
>You can reach the person managing the list at
>         linux-admin@linux.ucla.edu
>
>When replying, please edit your Subject line so it is more specific than
>"Re: Contents of Linux digest..."
>
>
>Today's Topics:
>
>   1. Re: RAM prob and security questions--new to list (Frederick Lee)
>   2. Re: RAM prob and security questions--new to list (Joshua Uziel)
>   3. Re: help with xscreen saver (Dan Helfman)
>
>--__--__--
>
>Message: 1
>Date: Wed, 12 Apr 2000 19:39:02 -0700
>From: Frederick Lee <phaethon@fire.csua.ucla.edu>
>To: linux@linux.ucla.edu
>Subject: Re: [UCLA-LUG] RAM prob and security questions--new to list
>Reply-To: linux@linux.ucla.edu
>
>On Wed, 12 Apr 2000 15:04:37 -0700, said Joshua Uziel <uzi@linuxcare.com>:
> >* ryanV <ryan42@ucla.edu> [000412 14:31]:
> >> my problem is a comman one but i cant seem to fix it with common
> >> methods, linux does not recognize all of my 128 MB of RAM... i have one
> >> PC100 dimm of 128 MB and it only catches 64 MB.  ive looked far and wide
> >
> >If you use lilo, you can add this line to it's boot parameters:
> >
> >append="mem=128M"
> >
> >or you can boot with "image mem=128M", where "image" is the image's
> >name.  Your booting off a floppy is totally unnecesary.  What you
> >should do is install Linux with a /boot partition within the first
> >8.4GB ... then you won't want to do that nasty step.
>
>The other thing to note is that RH 6.1 used kernel 2.2.12.  The "Can't See
>Above 64MB" bug is fixed as of 2.2.14 (RH 6.2).  IOW, Linux 2.2.14 will be
>able to see all 128MB without special parameters.
>
>-Fred
>
>--__--__--
>
>Message: 2
>Date: Wed, 12 Apr 2000 23:40:13 -0700
>From: Joshua Uziel <uzi@linuxcare.com>
>To: linux@linux.ucla.edu
>Subject: Re: [UCLA-LUG] RAM prob and security questions--new to list
>Reply-To: linux@linux.ucla.edu
>
>* Frederick Lee <phaethon@fire.csua.ucla.edu> [000412 23:21]:
> > The other thing to note is that RH 6.1 used kernel 2.2.12.  The "Can't See
> > Above 64MB" bug is fixed as of 2.2.14 (RH 6.2).  IOW, Linux 2.2.14 will be
> > able to see all 128MB without special parameters.
>
>Not necesarily... I have some machines that 2.2.12 detects all
>memory on... and I'm sure 2.2.14 will still get it wrong on
>some of them...
>
>... but then again, I don't pay as much attention to what gets
>fixed in the x86 land...
>
>--
>Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
>415.354.4878 tel, 415.701.7457 fax
>uzi@linuxcare.com, http://www.linuxcare.com/
>Linuxcare. Support for the revolution.
>
>--__--__--
>
>Message: 3
>Date: Thu, 13 Apr 2000 01:12:26 -0700
>From: Dan Helfman <witten@linux.ucla.edu>
>To: linux@linux.ucla.edu
>Subject: Re: [UCLA-LUG] help with xscreen saver
>Reply-To: linux@linux.ucla.edu
>
>On Wed, Apr 12, 2000 at 06:22:49PM -0700, Luis wrote:
> > I loaded red hat 6.2 on my box . When i was ready to go home, i tried to
> > set up my screen saver but i keep on getting a error message . when i 
> tried
> > to go into the xscreensaver it told me
> >
> > Xlib: connection to ":0.0" refused by server
> > Xlib: Client is not authorized to connect to Server
> > xscreensaver: Can't open display: :0
> > xscreensaver: initial effective uid/gid was root/root (0/0)
> > xscreensaver: running as nobody/nobody (99/99)
> >
> > xscreensaver: Errors at starup are usually authorization problems
> >
> >                       Did you read the manual on the faz? Specifically 
> the parts of the manual
> > that talk about XAUTH, XDMA and root logins?
> >
> > Well thats the whole message that i get when i try to run the xscreensaver
> > . so would anyone out there be able to help me out with this problem
>
>Try typing:
>xhost +localhost
>
>If that dosen't work, let us know.
>
> >
> >
> > Luis
>
>--
>Dan Helfman
>UCLA Linux Users Group: http://www.linux.ucla.edu
>My GnuPG key: http://torsion.org/witten/public-key.txt
>
>
>
>--__--__--
>
>_______________________________________________
>UCLALUG Linux mailing list - Linux@linux.ucla.edu
>http://linux.ucla.edu/mailman/listinfo/linux
>
>
>End of Linux Digest