Re: [expert] Any problems with NEC LCD 1550V monitor?

2002-05-11 Thread Alastair Scott

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Friday 10 May 2002 11:46 am, Phil wrote:
> Hello,
>
> I'm about to replace my CRT monitor with an LCD monitor mainly
> because of RF interference to my radio equipment.
>
> The monitor that I'm considering is an NEC LCD 1550V Multisync.
> Online reviews show this to be an economical and all-round useful
> monitor. However I'm concerned by reports that text is hard to read
> especially for old eyes.
>
> Apparently this is due to very thin characters. I would expect that
> if this a problem then a larger font could be selected. Is this true?
> Any comments on this monitor or LCD monitors in general would be
> appreciated.

'Very thin characters' ... ? Not sure what this means ... I presume it 
refers to the Linux console, or similar, on bootup, and is a result of 
the graphics card used (different cards produce different 'system 
text'). Certainly in Gnome, KDE or whatever you can use as large a font 
as you like, although 9pt Tahoma is perfectly good for me as the screen 
is so phenomenally sharp.

I bought an iiyama 4636D (18.1" TFT) a few months ago. Although it cost 
the princely sum of £936 it was worth it; I haven't regretted it for a 
minute. Compared with a CRT there is:

- - less power used (40W max; my old iiyama 19" CRT used 300W max);

- - little heat;

- - very little space taken up (there's no "depth" to it);

- - a wonderfully clear and sharp screen (especially with DVI output);

- - no more tired eyes or headaches (in my case);

- - no more degaussing or playing with geometry controls to try to get an 
(almost) rectangular picture ;)

Alastair
- -- 
Alastair Scott (London, United Kingdom)
http://www.unmetered.org.uk/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE83N6jCv59vFiSU4YRAq4lAKCXArecRvZZ0I/ObDNaTdBE+5u2awCgvuor
qrBbiXLxMQH8QXOuSyHNKKA=
=0cTh
-END PGP SIGNATURE-




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] Apache "SERVER_NAME" quick Q

2002-05-11 Thread Bo O. Erichsen

It depends on the order you have in the nsswitch.conf file.

i have in a default mdk setup:

hosts:  files nisplus nis dns

This means that gethostname will check your hostsfiles first.. Then it'll 
check nis services and lastly it'll check via bind in the order you have 
listed your dns-hosts in resolv.conf

/bo

On Saturday 11 May 2002 05:14, James wrote:
> That one I don't have and will have to rely on someones else to be able
> to duplicate.
>
> James
>
>
> On Fri, 10 May 2002 16:32:55 -0500
>
> David Rankin <[EMAIL PROTECTED]> wrote:
> > Hmm.., but what if I have BIND running and host.resolve set to BIND,
> > hosts?
> >
> > James wrote:
> > > Ok did a test. and got the following.
> > >
> > > If you have something like this in /etc/hosts.
> > >
> > > 10.0.0.1  my.box.com my
> > >
> > > where 10.0.0.1 is your IP number, my.box.com is the full name of the
> > > box, and my is the nickname.  hostname and hostname --fqdn work.  If
> > > you remove the nickname and just have
> > >
> > >  10.0.0.1 my.box.com
> > >
> > > hostname returns my.box.com and hostname --fqdn returns host unknow.
> > >  or if you have the default that Mandrake sets up,
> > >
> > >  10.0.0.1 my
> > >
> > > then hostname works and again hostname --fqdn returns host unkown.
> > >
> > > James
> > >
> > > On Thu, 09 May 2002 15:18:23 -0500
> > >
> > > David Rankin <[EMAIL PROTECTED]> wrote:
> > > > Well, I should have been more clear, and maybe the problem
> > > > isn't as simple as I thought. On my 7.2 box, #ServerName
> > > > your.server.name is still commented out, but apache is able to
> > > > use gethostbyname() and correctly fill in the welcome screen
> > > > in apache.
> > > >
> > > > In 8.2, something is fishy.
> > > >
> > > > [Skyline] # hostname
> > > > Skyline.3111Skyline.com
> > > >
> > > > That looks OK
> > > >
> > > > [Skyline] # hostname --fqdn
> > > > Unknown host
> > > >
> > > > That looks bad
> > > >
> > > > So it seems the problem with apache isn't with apache or
> > > > httpd.conf, but rather with my hostname setup. I have set
> > > > hostname and domainname, and I can't figure out why hostname
> > > > --fqdn would return unknown host?
> > > >
> > > > What config file am I failing to check? /etc/sysconfig/network
> > > > has the right hostname.
> > > >
> > > > Gary Dunn wrote:
> > > > > On Thu, 2002-05-09 at 06:29, David Rankin wrote:
> > > > > > Just a quick Q, because I'm suffering from a mental lapse.
> > > > > >
> > > > > > I'm getting Apache configured on 8.2. The "SERVER_NAME"
> > > > > > variable in the default Welcome screen is pulling
> > > > > > 127.0.0.1 instead of the actual host name. Hostname is
> > > > > > working fine. Where do I look to get this fixed.
> > > > >
> > > > > You definitely need to edit httpd.conf, which may be located in
> > > > > /usr/local/apache/conf depending on how your system is set up.
> > > > > (My apache is on a FreeBSD box, which puts it in
> > > > > /usr/local/etc/apache.)
> > > > >
> > > > > Look for this:
> > > > >
> > > > > # ServerName allows you to set a host name which is sent back to
> > > > > clients for
> > > > > # your server if it's different than the one the program would
> > > > > get(i.e., use
> > > > > # "www" instead of the host's real name).
> > > > > #
> > > > > # Note: You cannot just invent host names and hope they work.
> > > > > The name you
> > > > > # define here must be a valid DNS name for your host. If you
> > > > > don't understand
> > > > > # this, ask your network administrator.
> > > > > # If your host doesn't have a registered DNS name, enter its IP
> > > > > address here.
> > > > > # You will have to access it by its address (e.g.,
> > > > > http://123.45.67.89/)
> > > > > # anyway, and this will make redirections work in a sensible
> > > > > way.#
> > > > > # 127.0.0.1 is the TCP/IP local loop-back address, often named
> > > > > localhost. Your
> > > > > # machine always knows itself by this address. If you use Apache
> > > > > strictly for
> > > > > # local testing and development, you may use 127.0.0.1 as the
> > > > > server name.
> > > > > #
> > > > > ServerName your.server.name
> > > > >
> > > > > Gary Dunn
> > > > > Open Slate Project
> > > > >
> > > > >   -
> > > > >   --- Want to buy your Pack or Services from
> > > > >   MandrakeSoft? Go to http://www.mandrakestore.com
> > > >
> > > > --
> > > > David C. Rankin, J.D., P.E.
> > > > RANKIN * BERTIN, PLLC
> > > > 1329 N. University, Suite D4
> > > > Nacogdoches, Texas 75961
> > > > (936) 715-9333
> > > > (936) 715-9339 fax
> > >
> > >   -
> > >   --- Want to buy your Pack or Services from MandrakeSoft?
> > > Go to http://www.mandrakestore.com
> >
> > --
> > David C. Rankin, J.D., P.E.
> > RANKIN * BERTIN, PLLC
> > 1329 N. University, Suite D4
> > Nacogdoches, Texas 75

Re: [expert] Compiling the Mandrake kernel

2002-05-11 Thread Bjarne Thomsen

Thank you Tom,

That was the kind of answer that I hoped for.
I just took a quick look at the README file,
and cut out all the many words. I then made
a file from where I copied the lines by using
my mouse. I did not dare to include the "make install".
Yes, you are right. The number of lines can be cut
down to about half.

I have installed the new gcc-3.1 compiler as the default
gcc without too many difficulties. I have now compiled
the 2.4.18-16 enterprise kernel minus SMP, and for
Pentium4. I used "make menuconfig" as "make xconfig"
seems to be broken (see below). Maybe I should have
updated some other package. Anyway, the compile proceeded
without any problems.

I am not sure, however, that any specific P4 code was
generated. Here is my shorter recipe:

Procedure for compiling the kernel:

(1) cd /usr/src/linux
(2) "make mrproper" in case we start from scratch.
(3) cp /boot/config-2.4.18-16mdkenterprise /usr/src/linux/.config
(4) edit .config followed by "make oldconfig" or "make menuconfig"
(5) "EXTRAVERSION = -16P4" in /usr/src/linux/Makefile
(6) "export INSTALL_PATH=/boot" in /usr/src/linux/Makefile
(7) "make dep && make bzImage && make modules"
(8) "make modules_install && make install"
(9) inspect /boot and /etc/lilo.conf, and run lilo (to be sure).

"make xconfig":
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
3rdparty/dxr3/Config.in: 8: can't handle dep_bool/dep_mbool/dep_tristate
condition
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.18-16mdk/scripts'
make: *** [xconfig] Error 2



On Thu, 2002-05-09 at 21:32, Tom Brinkman wrote:
> On Thursday 09 May 2002 12:04 pm, Bjarne Thomsen wrote:
> 
> > But I have not tried to compile 2.4.18-6mdk using the
> > default gcc-2.96.
> 
>I have, and also including -12 and -13mdk using gcc-2.96
> -13 was to have some big improvement, but i forget what it was ;>
> 
> > I edited the EXTRAVERSION  [Makefile]  variable,
> > so my own kernel can live without interfering with
> > the standard kernels.
> 
> You didn't go far enough, and then again too far.  Best kernel 
> install/upgrade guidelines are at mandrakeuser, IMO.  
> 
> > Here are my 19 points:
> 
>Way too many partner ;)
> >
> > Procedure for compiling the kernel.
> >
> > ( 1) cd /usr/src/linux
> > ( 2) "make mrproper"
> > ( 3) cp /boot/config /usr/src/linux/.config
> 
>   in my last compile, I used   cp /boot/config-2.4.18-13mdk .config   
> 'Course as you properly point out, this needs to be after mrproper.  
> I'd like if y'all would check the cooker ML archive for the reasons/ 
> discussion on why mrproper is still 'the way to go'/necessary with 
> ML kernels.  To satisfy yourself, or explain it better to me ;)
> 
> > ( 4) edit .config   if necessary.
> 
>I do, but only to set K7 as the arch. I have an oc'd 1.4 Tbird 
> with VIA chipset, compiling for K7 seems to provide slight benefits, 
> including stability.  Strictly anecdotal, maybe just psychological ;)
>   
> > ( 5) Alternate configuration commands:
> >  (a) "make config"  to configure the basic kernel.
> >  (b) "make menuconfig"  Text based color menus, radiolists &
> > dialogs.
> >  (c) "make xconfig" X windows based configuration tool.
> >  (d) "make oldconfig"   Default all questions based on the
> > contents of
> 
>I use oldconfig, to make a default 'Mandrake' kernel, with just my 
> edit to k7 arch.  I know it says not to, ie, " # Automatically 
> generated make config: don't edit", but I've never had a problem doin 
> so ;)
> 
> > your existing ./.config file.
> > ( 6) edit "EXTRAVERSION = -14mdkbt" in /usr/src/linux/Makefile
> 
> I would just edit this to -14k7 in my situation.  Here's where I 
> believe you don't go far enough.  Also enable (uncomment the line) 
> further down,  export  INSTALL_PATH=/boot 
> 
> > ( 7) "make dep" to set up all the dependencies
> > correctly. ( 8) "make bzImage" to create a compressed
> > kernel image. ( 9) "make modules" to compile the modules.
> 
> Now here's (IMO) where you get out of order/include unnecessary 
> steps.  As MU advises,
>make dep && make clean && make bzImage && make modules
>followed with,
>make modules_install && make install
> 
> The 'make install' will take care of all the cp'ing, linking, and 
> mkinitrd'ing, etc. (you get into), edit lilo.conf, and run it for 
> you.  Less chance for user error, IME  ;)  Still, bein an untrusting 
> soul, I usually cd to /boot and run 'll' to make sure the pointers 
> were created to the new kernel. Then cd to /etc, do a 'less' on 
> lilo.conf to make sure the new kernel is an option, then run 'lilo', 
> just to make sure there's no error msg's. Rarely has been, good job 
> Mandrake!  ;)
> 
> > (10) "make modules_install" to install the modules in /lib/modules/
> > (11) cp /usr/src/linux/arch/i386/boot/bzImage
> > /boot/vmlinuz-2.4.18-14m

Re: [expert] Compiling the Mandrake kernel

2002-05-11 Thread Tom Brinkman

On Saturday 11 May 2002 04:55 am, Bjarne Thomsen wrote:
> Thank you Tom,
>
> That was the kind of answer that I hoped for.
> I just took a quick look at the README file,
> and cut out all the many words. I then made
> a file from where I copied the lines by using
> my mouse. I did not dare to include the "make install".
> Yes, you are right. The number of lines can be cut
> down to about half.
>
> I have installed the new gcc-3.1 compiler as the default
> gcc without too many difficulties. I have now compiled
> the 2.4.18-16 enterprise kernel minus SMP, and for
> Pentium4. I used "make menuconfig" as "make xconfig"
> seems to be broken (see below).
 see way down below ;)
> I am not sure, however, that any specific P4 code was
> generated. Here is my shorter recipe:
   It should have been if you edited this line in .config
# CONFIG_MPENTIUM4 is not set   
to  CONFIG_MPENTIUM4=y and then commented out whatever the 
default arch was (eg,   # CONFIG_M586 is not set)
Also during the compile you should'a seen a lot of lines here'n 
there with  -march=P4  in 'em. (not sure it'd be P4, I don't have 
one, but you get the idea. Mine read  -march=athlon   ;)
>
> Procedure for compiling the kernel:
>
> (1) cd /usr/src/linux
> (2) "make mrproper" in case we start from scratch.  
  Not 'in case we start from scratch', _always_

> (3) cp /boot/config-2.4.18-16mdkenterprise /usr/src/linux/.config
 Could shorten to 'cp /boot/config-2.4.18-16mdkenterprise .config' 
since you're already in /usr/src/linux/

> (4) edit .config followed by "make oldconfig" or "make menuconfig"
> (5) "EXTRAVERSION = -16P4" in /usr/src/linux/Makefile
> (6) "export INSTALL_PATH=/boot" in /usr/src/linux/Makefile
> (7) "make dep && make bzImage && make modules"
> (8) "make modules_install && make install"
> (9) inspect /boot and /etc/lilo.conf, and run lilo (to be sure).

5&6 are one step, 7&8 could be all one step, 9 is optional but 
recommended, So we're really down to just 6 steps + check needed to 
compile a cooker kernel ;)

   As to make xconfig, remember I said,
> > As a footnote, I don't recommend usin newer kernels unless
> > you also either monitor the cooker ML, or at least check it's
> > recent archive. 

   Check the cooker ML archive, I believe you'll find notice that 
lately 'make xconfig' is broken, make menuconfig works
-- 
Tom BrinkmanCorpus Christi, Texas



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] Making load file for repeated 8.1 CD installs ?

2002-05-11 Thread gianpaolo racca

On Saturday 11 May 2002 02:09, db wrote:
> I am going to reinstall again and was wondering if anyone knows how I can
> create this ability for either of these distributions so that if I need to
> format and reinstall again, it won't be so time consuming?

http://members.shaw.ca/mandrake/
probably here you find want you need

--
"Errare e' umano. Vagabondare e' reato"
gianpaolo racca
[EMAIL PROTECTED]
http://www.preciso.net




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] OT: HD upgrade

2002-05-11 Thread Praedor Tempus

On Saturday 11 May 2002 08:54 am, David wrote:
> I have bought a new harddrive and would like to _move_ my current Mandrake
> installation over to the new drive without having to re-install.  Is this
> possible?  How would I go about doing so?  My guess is that it is _not_
> possible to do so while booted into Linux.

It IS possible, with relative ease, while booted to linux.  You install the 
new harddrive (obviously not YET as a replacement for the original), for 
instance, connect it up to the slave position to your current master on IDE 1 
if it is available - though this position is likely taken by your CDROM in 
which case attach it to the master position on IDE 2.  It will likely take on 
the position of /dev/hde on the assumption that you currently have one 
harddrive and one cdrom on IDE 1.

Run "fdisk /dev/hde" (or whatever it turns out to be) and set up partitions 
and filesystems - don't forget a swap partition (this is the way I always do 
it - I imagine there are nifty graphical tools for this...diskdrake?).  You 
will now have devices like /dev/hde1, /dev/hde5, ../hde6, ../hde7, etc, 
depending on how you setup.  Depending on how you want to layout the new 
drive, you will need to create mountpoints to accompany the layout.  For me, 
I always have /, /var, /usr, /usr/local, and /home on separate partitions.  
You do as you like.  In my case, I need separate, but nested, mountpoints for 
each partition, so I might create mountpoint "/mnt/disk", cd into /mnt/disk 
and then create "var", "usr", "usr/local", and "home" under /mnt/disk.  I 
then would first mount say "/dev/hde5" (assuming linux is going on an 
extended partition) on /mnt/disk, cd to /mnt/disk and subsequently mount the 
other partitions (/dev/hde6, hde7, etc) to their appropriate /var, /usr, etc 
mountpoints.  You COULD then begin copying all my current linux system files 
over to /mnt/disk from the root directory (recursive copy).  I do not know 
offhand the copy command arguments needed - you want to make sure you copy 
files AND symlinks but NOT the /proc directory (I think that's the one - if 
you try to copy that one you will get into recursion hell). The better way 
would be to tar and gzip your system into tarballs.
  
Copying would take a lng time.  If you tar it all up, it will take a long 
time but be potentially easier.  Depending on your partitioning scheme and 
drivespace, you could tar up the entire system (quite large) or tar up 
portions, like create a "root.tar.gz", a "usr.tar.gz" (which in my case could 
include /usr/local even though it is on a separate partition), etc.  Move the 
tarballs to their appropriate location on /mnt/disk, ie, root.tar.gz, which 
would likely have /, /boot, /root, /sbin, /bin, etc in it, to /mnt/disk.  
usr.tar.gz would also go to your /mnt/disk partition (when it untars/ungzips 
it will automatically go into /usr and /usr/local - you need space for this 
in /mnt/disk).  I haven't done this for a while but I recall making the 
mistake of putting usr.tar.gz into my /mnt/disk/usr directory/mountpoint and 
untarring it there - it will create what works out to be a /mnt/disk/usr/usr 
directory instead of doing as you might hope - this is a bit of a pain to fix.

My memory is faded on this so another will need to flesh out better details.  
I just want to provide a reasonable outline of how to do it.  It is tedious 
but not impossible by any means.

Once you have untarred or copied your system to the new drive, you power 
down, unplug and remove the old drive and replace it with the new drive (have 
a bootdisk because you will need to run lilo to get it finished up).  Bootup 
with a bootdisk and go to failsafe.  Run lilo.  You should then be good to 
go.  

To end - look into it a bit and I am sure others with more recent experience 
will provide information or corrections to my general outline.

praedor



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



[expert] Paranoid Security level question

2002-05-11 Thread Jay

I have two question about paranoid (and higher) security levels. First
what do I modify to allow login by root, I cuurently log in as a normal
user and then su into root, and secondly, I cannot ssh into my server when
in these two security levels, is this normal or is something screwed up on
my server?
-Jay


-- 
Never do anything against conscience even if the state demands it. -
Albert Einstein (1879-1955)




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] Compiling the Mandrake kernel

2002-05-11 Thread Bjarne Thomsen

Hi Tom,

As a matter of fact the -march=i686 option is given
to gcc even when CONFIG_MPENTIUM4=y.
I traced that to /usr/src/linux/arch/i386/Makefile.
Either -march=pentium4 is not yet considered safe,
or it has been forgotten. I edited that Makefile.
The Makefile editing should really not be considered
a part of the compilation procedure.
I prefer to separate the compilation from the intallation
so I have kept them as two points.
Now I have compiled the kernal source with -march=pentium4,
and so far it seems to be running without problems.

I am really only interested in using -march=pentium4
and/or -msse2 for heavy floating point calculations,
but that is another matter.

 -- Bjarne

Procedure for compiling the kernel:

After installing a new 2.4.xx kernel edit the following two lines
"EXTRAVERSION = -16P4"
"export INSTALL_PATH=/boot"
in /usr/src/linux/Makefile
In case you wish to compile for Pentium4 using gcc-3.1 edit
ifdef CONFIG_MPENTIUM4
CFLAGS += -march=i686  -->  CFLAGS += -march=pentium4
endif
in /usr/src/linux/arch/i386/Makefile


(1) cd /usr/src/linux
(2) "make mrproper"
(3) cp /boot/config-2.4.18-16mdkenterprise .config
(4) edit .config followed by "make oldconfig" or "make menuconfig"
(5) "make dep && make bzImage && make modules"
(6) "make modules_install && make install"
(7) inspect /boot and /etc/lilo.conf, and run lilo (to be sure).



On Sat, 2002-05-11 at 15:37, Tom Brinkman wrote:
> On Saturday 11 May 2002 04:55 am, Bjarne Thomsen wrote:
> > Thank you Tom,
> >
> > That was the kind of answer that I hoped for.
> > I just took a quick look at the README file,
> > and cut out all the many words. I then made
> > a file from where I copied the lines by using
> > my mouse. I did not dare to include the "make install".
> > Yes, you are right. The number of lines can be cut
> > down to about half.
> >
> > I have installed the new gcc-3.1 compiler as the default
> > gcc without too many difficulties. I have now compiled
> > the 2.4.18-16 enterprise kernel minus SMP, and for
> > Pentium4. I used "make menuconfig" as "make xconfig"
> > seems to be broken (see below).
>  see way down below ;)
> > I am not sure, however, that any specific P4 code was
> > generated. Here is my shorter recipe:
>It should have been if you edited this line in .config
> # CONFIG_MPENTIUM4 is not set   
> to  CONFIG_MPENTIUM4=y and then commented out whatever the 
> default arch was (eg,   # CONFIG_M586 is not set)
> Also during the compile you should'a seen a lot of lines here'n 
> there with  -march=P4  in 'em. (not sure it'd be P4, I don't have 
> one, but you get the idea. Mine read  -march=athlon   ;)
> >
> > Procedure for compiling the kernel:
> >
> > (1) cd /usr/src/linux
> > (2) "make mrproper" in case we start from scratch.  
>   Not 'in case we start from scratch', _always_
> 
> > (3) cp /boot/config-2.4.18-16mdkenterprise /usr/src/linux/.config
>  Could shorten to 'cp /boot/config-2.4.18-16mdkenterprise .config' 
> since you're already in /usr/src/linux/
> 
> > (4) edit .config followed by "make oldconfig" or "make menuconfig"
> > (5) "EXTRAVERSION = -16P4" in /usr/src/linux/Makefile
> > (6) "export INSTALL_PATH=/boot" in /usr/src/linux/Makefile
> > (7) "make dep && make bzImage && make modules"
> > (8) "make modules_install && make install"
> > (9) inspect /boot and /etc/lilo.conf, and run lilo (to be sure).
> 
> 5&6 are one step, 7&8 could be all one step, 9 is optional but 
> recommended, So we're really down to just 6 steps + check needed to 
> compile a cooker kernel ;)
> 
>As to make xconfig, remember I said,
> > > As a footnote, I don't recommend usin newer kernels unless
> > > you also either monitor the cooker ML, or at least check it's
> > > recent archive. 
> 
>Check the cooker ML archive, I believe you'll find notice that 
> lately 'make xconfig' is broken, make menuconfig works
> -- 
> Tom BrinkmanCorpus Christi, Texas
> 
> 
> 

> Want to buy your Pack or Services from MandrakeSoft? 
> Go to http://www.mandrakestore.com





Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] Compiling the Mandrake kernel

2002-05-11 Thread Tom Brinkman

On Saturday 11 May 2002 12:49 pm, Bjarne Thomsen wrote:

> I am really only interested in using -march=pentium4
> and/or -msse2 for heavy floating point calculations,
> but that is another matter.

Actually, it doesn't surprise me that editing for P4, still 
produces an i686 kernel.  I believe the K7 compile enabling adds some 
benefits, mostly since the athlon out performs the P4, and clock for 
clock the P3 out performs the P4.  You might consider testing your P4 
with kernels compiled for both 586 and 686.  586 might just be better 
for a P4. 

 Also, specially on Intel systems, how you have your ram 
configured (Cas latency, banking, etc) will probly affect system 
performance more than tryin to optimize the kernel for a P4.  For 
real performance, you might be able to up the Vcore, and IO voltages 
a touch, along with a few mhz added to the FSB speed if your 
motherboard supports doin so. I wouldn't buy one that didn't. A lot 
of good high performance motherboards provide increased Vcore and IO 
by default, some increased FSB mhz by default.

 A good app for checking ram performace is memtest86.  You don't 
need to run all the tests, other than to see if you've pushed ram 
timings too far. When you boot memtest86, you'll see right away the 
ram performance in mb/sec in the upper left corner.  BIOS settings 
for the ram will have an immediate affect.  Increased IO voltage will 
probly be required to get to optimum. FPU is very affected by ram 
performance, so this might be where you should concentrate your 
optimization efforts.  I don't believe optimizing the kernel will 
have as much affect as optimizing your hardware/configuration will.

 I know this sort'a smacks of overclocking, and many are 
predjudiced that oc'ing is dangerous.  IMO, quite the contrary. 
Reasonable, prudent oc'ing will actually improve stability, 
reliability, and specially FPU ;)  Just make sure you don't up the 
FSB too much (< 138mhz), and that the PCI bus stays under 35mhz. 
Call it tweaking ;)
-- 
Tom BrinkmanCorpus Christi, Texas



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



[expert] access to CD-RW

2002-05-11 Thread David

Last night I upgraded my HD.  After doing so, everything worked fine except the fact 
that I can no longer access my CD-RW drive.  My fstab is below.  I have tried all 
combinations of options that I could think of, nothing has worked so far.  The error I 
get is:  You do not have enough permissions to read file:/mnt/cdrom.  Even root gets 
this same error.  Any ideas?


$ cat /etc/fstab
/dev/hda5 / ext2 defaults 1 1
none /dev/pts devpts mode=0620 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda8 /home ext2 defaults 1 2
/mnt/cdrom /mnt/cdrom supermount dev=/dev/hdd,fs=auto,--,user 0 0
/mnt/floppy /mnt/floppy supermount 
dev=/dev/fd0,fs=vfat,--,iocharset=iso8859-1,umask=0,sync,codepage=850 0 0
none /proc proc defaults 0 0
/dev/hda7 /usr ext2 defaults 1 2
/dev/hda6 swap swap defaults 0 0



-- 
°°°
David L. Steiner   Registered Linux User   #262493
Mandrake  8.2  Enlightenment  0.16.5   Sylpheed  0.7.4claws
Email: [EMAIL PROTECTED]   Homepage: www.davidlsteiner.com
°°°








Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] access to CD-RW

2002-05-11 Thread David



nDiScReEt said onto me:  
--

 |> /mnt/cdrom /mnt/cdrom supermount dev=/dev/hdd,fs=auto,--,user 0 0
 |
 |If this is a cd-rw, you have to point it to /dev/scd0 not /dev/hdd. 
 |

I also tried it as 

/mnt/cdrom /mnt/cdrom supermount 
dev=/dev/scd0,fs=iso9660,ro,--,user,iocharset=iso8859-1 0 0

(and any other combination w/scd0 that I could think off)

No dice.  DrakConf sees the drive as /dev/hdd.  I don't know why.  It used to be seen 
correctly.  Any other ideas?



 |-- 
 |
 |Altoine B
 |Maximum Time Unlimited
 |Chicago Based and Operated
 |
 |"Oh, he [a big dog] hunts with papa," she said. "He says Don Carlos [the
 |dog] is good for almost every kind of game.  He went duck hunting one time
 |and did real well at it.  Then Papa bought some ducks, not wild ducks but,
 |you know, farm ducks.  And it got Don Carlos all mixed up.  Since the
 |ducks were always around the yard with nobody shooting at them he knew he
 |wasn't supposed to kill them, but he had to do something.  So one morning
 |last spring, when the ground was still soft, he took all the ducks and
 |buried them."  "What do you mean, buried them?"  "Oh, he didn't hurt them.
 |He dug little holes all over the yard and picked up the ducks in his mouth
 |and put them in the holes.  Then he covered them up with mud except for
 |their heads.  He did thirteen ducks that way and was digging a hole for
 |another one when Tony found him.  We talked about it for a long time.  Papa
 |said Don Carlos was afraid the ducks might run away, and since he didn't
 |know how to build a cage he put them in holes.  He's a smart dog."
 |  -- R. Bradford, "Red Sky At Morning"
 |---
 |2.4.18-13mdk
 |Mandrake Linux release 8.3 (Cooker) for i586
 |
 |

--

-- 
°°°
David L. Steiner   Registered Linux User   #262493
Mandrake  8.2  Enlightenment  0.16.5   Sylpheed  0.7.4claws
Email: [EMAIL PROTECTED]   Homepage: www.davidlsteiner.com
°°°








Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] access to CD-RW

2002-05-11 Thread Steve Browne

On Sun, 12 May 2002 06:42:23 -0400, you wrote:

>
>
>nDiScReEt said onto me:  
>--
>
> |> /mnt/cdrom /mnt/cdrom supermount dev=/dev/hdd,fs=auto,--,user 0 0
> |
> |If this is a cd-rw, you have to point it to /dev/scd0 not /dev/hdd. 
> |
>
>I also tried it as 
>
>/mnt/cdrom /mnt/cdrom supermount 
>dev=/dev/scd0,fs=iso9660,ro,--,user,iocharset=iso8859-1 0 0
>
>(and any other combination w/scd0 that I could think off)
>
>No dice.  DrakConf sees the drive as /dev/hdd.  I don't know why.  It used to be seen 
>correctly.  Any other ideas?

I'm having the same problem, so I hope you get an answer. It has
something to do with missing symbolic links. You could try asking this
in the newsgroup alt.os.linux.mandrake; I often get quick answers
there.

Good luck,
Steve
Stephen B. Browne
[EMAIL PROTECTED]
"Veritas odit moras"



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] access to CD-RW

2002-05-11 Thread bascule

have you tried mounting by hand to see if you can, what does work?
comment out or delete the line in fstab that you have there for the time 
being, make sure /mnt/cdrom exists and check its permissions, even root can't 
read or write a file it doesn't have permissions for if they are not set - 
the point of root is that it can always set them - which is why sometmes it 
seems that root is locked out of something, then as root try 
#mount -t iso9660 /dev/hdd /mnt/cdrom
or
#mount -t iso9660 /dev/scd0 /mnt/cdrom

that is about as basic a mount command as you can get for a cdrom, the latter 
would be if you are using ide-scsi for the writer, if neither of these work 
then perhaps you have incorrectly configured ide-scsi (i'm guessing wildly 
here) 

bascule

On Sunday 12 May 2002 11:42 am, you wrote:
> nDiScReEt said onto me:
> --
>
>  |> /mnt/cdrom /mnt/cdrom supermount dev=/dev/hdd,fs=auto,--,user 0 0
>  |
>  |If this is a cd-rw, you have to point it to /dev/scd0 not /dev/hdd.
>
> I also tried it as
>
> /mnt/cdrom /mnt/cdrom supermount
> dev=/dev/scd0,fs=iso9660,ro,--,user,iocharset=iso8859-1 0 0
>
>
-- 
Stupid men are often capable of things the clever would not dare to 
contemplate...
(Feet of Clay)



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] Paranoid install unable to ping.

2002-05-11 Thread tbeason

/usr/share/doc/msec-0.19/security.txt

and

man mseclib

Len Pikulski [[EMAIL PROTECTED]] wrote:
> Thanks much!!!
> As you probably know it worked great.
> 
> Have you seen any docs on the different levels of "security" during
> the latest Mandrake 8.2 install??
> 
> It would be nice to know the other differences.
> 
> Thanks again
> ***
> 
> > On Fri, 10 May 2002, JOHAM,DAVID (HP-Boise,ex1) wrote:
> > I've got this at the end of my firewall script to allow me to do pings. 
> > 
> > echo "0" > /proc/sys/net/ipv4/icmp_echo_ignore_all
> > echo "0" > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
> > 
> > HTH
> > 
> > David
> > 
> > -Original Message-
> > From: Len Pikulski [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 09, 2002 4:19 PM
> > To: [EMAIL PROTECTED]
> > Subject: [expert] Paranoid install unable to ping. 
> > 
> > 
> > Is there a way to allow ping returns when doing a "Paranoid" security
> > level install.
> > I couldn't find any documented differences between the different levels,
> > (that would also be helpful)
> > 
> > Thanks in advance for your reply
> > 
> > <*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*>
> >  Len Pikulski[EMAIL PROTECTED]   (856) 222-1514
> >   http://www.nothinbut.net
> > 
> > 
> > 
> > 
> 
> <*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*>
>  Len Pikulski[EMAIL PROTECTED]   (856) 222-1514
>   http://www.nothinbut.net
> 
> 

> Want to buy your Pack or Services from MandrakeSoft? 
> Go to http://www.mandrakestore.com




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] access to CD-RW

2002-05-11 Thread nDiScReEt

On Saturday 11 May 2002 06:08 pm, you wrote:
> have you tried mounting by hand to see if you can, what does work?
> comment out or delete the line in fstab that you have there for the time
> being, make sure /mnt/cdrom exists and check its permissions, even root
> can't read or write a file it doesn't have permissions for if they are not
> set - the point of root is that it can always set them - which is why
> sometmes it seems that root is locked out of something, then as root try
> #mount -t iso9660 /dev/hdd /mnt/cdrom
> or
> #mount -t iso9660 /dev/scd0 /mnt/cdrom
>
> that is about as basic a mount command as you can get for a cdrom, the
> latter would be if you are using ide-scsi for the writer, if neither of
> these work then perhaps you have incorrectly configured ide-scsi (i'm
> guessing wildly here)
>
> bascule
>
Good plus he needs to have his cdrom writer drivers running first.
YOu are right about getting the drive to at least behave like a cdrom drive 
first. Because once he has it doing that, he can then install the appropriate 
drivers for cdwriting depending on his hardware. I use ide-scsi as that is 
what supports my hardware. When you make the cdrom dev (ie /dev/hdd) from 
scratch for the first time, use MAKEDEV not mkdir. But that shouldn't be 
necessary if you have devfs installed and running or if diskdrake already has 
it as /dev/hdd. You might have to recompile your kernel for that support if 
it isn't present. After getting the drive to at least behave like a cdrom 
drive, load the appropriate cd writing modules, after doing "modprobe 
ide-scsi" (in my case), run the command "cdrecord -scanbus". That should 
detect your cd writer and with that information, you should then be able to 
do as you were once able to do. Write cdr discs once again.


-- 

Altoine B
Maximum Time Unlimited
Chicago Based and Operated

Do you like "TENDER VITTLES"?
---
2.4.18-13mdk
Mandrake Linux release 8.3 (Cooker) for i586




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] access to CD-RW

2002-05-11 Thread pross

i used to have a 'disapearing CDROM' problem with redhat...i'd boot up and 
sometimes i couldnt mount the cdrom.i finally discovered that if i did a 
'modprobe cdrom' at boot it'd come back...
maybe the same problemmaybe











On Sunday 12 May 2002 2:18 am, you wrote:
> On Saturday 11 May 2002 06:08 pm, you wrote:
> > have you tried mounting by hand to see if you can, what does work?
> > comment out or delete the line in fstab that you have there for the time
> > being, make sure /mnt/cdrom exists and check its permissions, even root
> > can't read or write a file it doesn't have permissions for if they are
> > not set - the point of root is that it can always set them - which is why
> > sometmes it seems that root is locked out of something, then as root try
> > #mount -t iso9660 /dev/hdd /mnt/cdrom
> > or
> > #mount -t iso9660 /dev/scd0 /mnt/cdrom
> >
> > that is about as basic a mount command as you can get for a cdrom, the
> > latter would be if you are using ide-scsi for the writer, if neither of
> > these work then perhaps you have incorrectly configured ide-scsi (i'm
> > guessing wildly here)
> >
> > bascule
>
> Good plus he needs to have his cdrom writer drivers running first.
> YOu are right about getting the drive to at least behave like a cdrom drive
> first. Because once he has it doing that, he can then install the
> appropriate drivers for cdwriting depending on his hardware. I use ide-scsi
> as that is what supports my hardware. When you make the cdrom dev (ie
> /dev/hdd) from scratch for the first time, use MAKEDEV not mkdir. But that
> shouldn't be necessary if you have devfs installed and running or if
> diskdrake already has it as /dev/hdd. You might have to recompile your
> kernel for that support if it isn't present. After getting the drive to at
> least behave like a cdrom drive, load the appropriate cd writing modules,
> after doing "modprobe ide-scsi" (in my case), run the command "cdrecord
> -scanbus". That should detect your cd writer and with that information, you
> should then be able to do as you were once able to do. Write cdr discs once
> again.

-- 
disbar, n:
As distinguished from some other bar.



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



FIXED! [expert] access to CD-RW

2002-05-11 Thread David

Much thanks to nDiScReEt, Bascule, Steve Browne, Brian Parish, Larry Sword, and 
Pross(who got in at the last moment).  

We got it fixed.  

The problem was that I followed the howto at 
http://www.tldp.org/HOWTO/mini/Hard-Disk-Upgrade/index.html to upgrade my HD.  

Following directions, I used a _temporary_ lilo config for the initial booting of the 
new HD.  In the config, the line _append="hdb=ide-scsi"_ was omitted.  Thus, I had not 
re-corrected my lilo config.  nDiScReEt's post below opened my eyes.  The second I 
seen it, I knew what it was.  I'm now kicking myself (HARD).  


Thanks to all  
Dave  



nDiScReEt said onto me:  
--
 |In that same link I had sent earlier it made reference to making sure that 
 |you are loading that same cdwriter driver at boot up like the below line:
 |
 |
 |
 |image=/boot/zImage-2.2.14
 |  label=Linux
 |  read-only
 |  append="hdb=ide-scsi"
 |
 |Listing: Example configuration for lilo (/etc/lilo.conf)
 |
 |linux "Linux 2.1.14" {
 |image=/boot/zImage-2.0.37
 |cmdline= root=/dev/hda5 readonly hdb=ide-scsi
 |}
 |
 |Listing: Example configuration for chos (/etc/chos.conf) 
 |
 |
 |
 |-- 
 |
 |Altoine B
 |Maximum Time Unlimited
 |Chicago Based and Operated
 |
 |Nine megs for the secretaries fair,
 |Seven megs for the hackers scarce,
 |Five megs for the grads in smoky lairs,
 |Three megs for system source;
 |
 |One disk to rule them all,
 |One disk to bind them,
 |One disk to hold the files
 |And in the darkness grind 'em.
 |---
 |2.4.18-13mdk
 |Mandrake Linux release 8.3 (Cooker) for i586
 |
 |

--

-- 
°°°
David L. Steiner   Registered Linux User   #262493
Mandrake  8.2  Enlightenment  0.16.5   Sylpheed  0.7.4claws
Email: [EMAIL PROTECTED]   Homepage: www.davidlsteiner.com
°°°








Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] OT: HD upgrade

2002-05-11 Thread John Haywood

On Sunday 12 May 2002 01:58, you wrote:
> On Saturday 11 May 2002 08:54 am, David wrote:
> > I have bought a new harddrive and would like to _move_ my current
> > Mandrake installation over to the new drive without having to re-install.
> >  Is this possible?  How would I go about doing so?  My guess is that it
> > is _not_ possible to do so while booted into Linux.
>
[SNIP]
> To end - look into it a bit and I am sure others with more recent
> experience will provide information or corrections to my general outline.
>
> praedor

Could also look at the info in the Hard-Disk Upgrade Docs.

http://www.tldp.org/HOWTO/mini/Hard-Disk-Upgrade/

...wel-explained, and a good site to bookmark.
-- 
john in sydney
=
 Mandrake Linux 8.2
 Kernel version: 2.4.17-5mdk
 Uptime: 1 day 3 hours 16 minutes
=



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



[expert]

2002-05-11 Thread James



All,

   Just found this at
http://www.kde-look.org/content/show.php?content=1332&PHPSESSID=df764edd16c338af9b6960937c4bd1a7

It starts KDE in under 2 seconds on my box (1gig celeron) it has both
fast starts for kde and kde3 ... basically it changes the init order so
that it can start and you can start working while it does all the fancy
things behind your back. (real tech talk here hehe)  It's working for me
soo.


James



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com