Linux-Setup Digest #655, Volume #19 Wed, 20 Sep 00 02:13:08 EDT
Contents:
Re: StarOffice and fax configuration (E J)
Re: NT and Linux outside 1024 Cylinders (Simon Reye)
Intel Binary Compatability Standard - iBCS ("Stephen Scattergood")
Re: Increase memory to 128M ("David ..")
Re: Increase memory to 128M ("David ..")
HP 693 Problems ("Timothy J. Miller")
Re: New Linux Install ("Blake Leverett")
Re: New Linux Install (Dean Plude)
Linux Mandrake 7.0 & 7.1 Install Failure - Is There a Fix? (Felix Miata)
Re: New Linux Install ("kosh")
Re: NEW NVIDIA DRIVERS (Warning) (moonie;))
Re: NEW NVIDIA DRIVERS (Warning) (moonie;))
Re: Cambio di risoluzione (Valentin Guillen)
failed redhat 6.2 installl now can't fdisk ("Deb")
Re: Making LILO wait? (Valentin Guillen)
----------------------------------------------------------------------------
From: E J <[EMAIL PROTECTED]>
Subject: Re: StarOffice and fax configuration
Date: Tue, 19 Sep 2000 19:22:06 -0700
from man pages from efax:
SENDING FAXES USING THE PRINT SPOOLER
You can configure a "fax" printer into the lpr print spooler that
will fax a
document out using efax instead of printing it. This allows
a network
server running efax to send faxes on behalf of other machines,
including
non-Unix clients. In the following steps use the directories
specified in
the fax script if they are different than /usr/bin and
/var/spool/fax
(FAXDIR). To set up a fax printer do the following as root:
(1) Create a link to the fax script called ``faxlpr'' so the fax
script can
determine when it is being invoked from the print spooler:
ln /usr/bin/fax /usr/bin/faxlpr
(2) Edit /etc/printcap and add an entry such as:
fax:lp=/dev/null:sd=/var/spool/fax:if=/usr/bin/faxlpr:
to define a printer called "fax". Print files will be
spooled to the
/var/spool/fax (sd=) directory and then piped to the
/usr/bin/faxlpr filter
(if=).
(3) Create and/or set the permissions to allow anyone to read
and write in
the fax spool directory. For example:
mkdir /var/spool/fax
chmod 777 /var/spool/fax
(4) Create a printer daemon lock file that is readable by anyone:
touch /var/spool/fax/lock
chmod 644 /var/spool/fax/lock
You should now be able to send a fax using the lpr interface by
using a com�
mand such as:
lpr -P fax -J "555 1212" file.ps
where the -J option is used to specify the phone number or
alias to be
dialed.
Now for Star Office
Create a generic printer driver in Printer Setup
Rename it to a fax printer
Configure your fax queue to the following:
fax_queue=/home/user_id/office52/program/sfax.bin
Configure "Configure Fax Output" to
lpr -P fax -J(PHONE)
and click on "PIPE"
When you choose the Fax Printer to print, a dialogue box pops with the
phone number to fax to.
Aleksander Starczewski wrote:
> Hi
> I want to send faxes from SO, but I don't know how. Could you help me?
> Olek
------------------------------
From: Simon Reye <[EMAIL PROTECTED]>
Subject: Re: NT and Linux outside 1024 Cylinders
Date: Wed, 20 Sep 2000 13:50:51 +1000
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] says...
> Hi,
>
> I have NT as primary OS and have installed Linux on the 3rd-5th
> partition starting with a boot-disc. Now, there is a description to
> export the LiLo-Bootsector as bootsek.lin from /boot to NT-root (C:\)
> and put it into boot.ini of NT to let the Boot-manager start Linux. Is
> this a possible solutions for those who can't install /boot under the
> 1024 cylinder limitation. So, can I alter my boot system from floppy
> boot to NT-loader this way or do I need to have /boot under 1024
> cylinders???
>
> Thanks fpr your help.
>
> Michael.
>
>
Works for me - Check out the mini-HOWTOs.
Simon
------------------------------
Reply-To: "Stephen Scattergood" <[EMAIL PROTECTED]>
From: "Stephen Scattergood" <[EMAIL PROTECTED]>
Subject: Intel Binary Compatability Standard - iBCS
Date: Wed, 20 Sep 2000 03:19:21 GMT
I have an app which insists that iBCS be installed so that it can run under
Linux.
Does anyone know how to tell if this "package" is installed, especially in
Mandrake 7.1?
Also, where can I find out more info on just what this standard is?
Thanks in advance
------------------------------
From: "David .." <[EMAIL PROTECTED]>
Subject: Re: Increase memory to 128M
Date: Tue, 19 Sep 2000 22:14:23 -0500
"Teck Meng, Liaw" wrote:
>
> Hi!
>
> I have install RedHat 6.2 with 64M ram, now I have upgrade the server
> to128M, how do I change the system configuration to utilize all there 128M?
> Any help is appreciate.
>
> Teck Meng, Liaw
It should find it automatically. If it doesn't then you need to add this
line to /etc/lilo.conf
apend="mem=128M"
--
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
ID # 123538
------------------------------
From: "David .." <[EMAIL PROTECTED]>
Subject: Re: Increase memory to 128M
Date: Tue, 19 Sep 2000 22:28:04 -0500
"David .." wrote:
>
> It should find it automatically. If it doesn't then you need to add this
> line to /etc/lilo.conf
>
> apend="mem=128M"
Also run /sbin/lilo to update the MBR.
--
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
ID # 123538
------------------------------
From: "Timothy J. Miller" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.install,linux.redhat,linux.redhat.misc,comp.os.linux.misc
Subject: HP 693 Problems
Date: Tue, 19 Sep 2000 23:16:18 -0500
Wondering if anyone out there has "successfully" configured the HP 693c
Color InkJet
printer under Linux. If so, how.
I have it working, sporadically. It will print some pages and then all
of a sudden just start spitting out
garabage. Any ideas?
I am running Redhat 6.2 and have it setup under printtool as an HP
Deskjet 550C (UP) on /dev/lp0
- Thanks
- Tim
------------------------------
From: "Blake Leverett" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.advocacy,alt.os.linux.mandrake
Subject: Re: New Linux Install
Date: Wed, 20 Sep 2000 04:13:33 GMT
A little advice:
1. Make a detailed list of all hardware you have, including
settings. Also include BIOS settings.
2. Read a little about stuff you don't understand, then proceed.
3. Have a pencil and paper handy to record what happens, plus all
the information that springs forth during the install that will
be useful later.
OR
Just stick the CD in and go for it. In case of troubles, goto
step #1 above.
Blake Leverett
ps Draper? Are you a fellow MIT grad?
James M. Luongo <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I plan on installing Linux Mandrake 7.1 for the first time. I need some
> help. How big should the partitions be? And, I heard something about
> LiLo not recognizing a Linux partition after a certain disk cylinder (or
> sector, whatever). I think it was 1023, but I'm not sure. Is this
> true? Help!
> --
> ------------------------
> James M. Luongo x1427
> Draper Laboratory Room 4207
> ------------------------
------------------------------
From: Dean Plude <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.advocacy,alt.os.linux.mandrake
Subject: Re: New Linux Install
Date: Wed, 20 Sep 2000 04:44:31 GMT
Blake Leverett wrote:
> A little advice:
>
> 1. Make a detailed list of all hardware you have, including
> settings. Also include BIOS settings.
> 2. Read a little about stuff you don't understand, then proceed.
> 3. Have a pencil and paper handy to record what happens, plus all
> the information that springs forth during the install that will
> be useful later.
>
> OR
>
> Just stick the CD in and go for it. In case of troubles, goto
> step #1 above.
>
> Blake Leverett
>
> ps Draper? Are you a fellow MIT grad?
>
> James M. Luongo <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > I plan on installing Linux Mandrake 7.1 for the first time. I need some
> > help. How big should the partitions be? And, I heard something about
> > LiLo not recognizing a Linux partition after a certain disk cylinder (or
> > sector, whatever). I think it was 1023, but I'm not sure. Is this
> > true? Help!
> > --
> > ------------------------
> > James M. Luongo x1427
> > Draper Laboratory Room 4207
> > ------------------------
Mandrake 7.1 no longer has that problem use GRUB when prompted for a boot
loader
------------------------------
From: Felix Miata <[EMAIL PROTECTED]>
Subject: Linux Mandrake 7.0 & 7.1 Install Failure - Is There a Fix?
Reply-To: Felix Miata <[EMAIL PROTECTED]>
Date: Wed, 20 Sep 2000 01:07:00 -0400
Current error message on screen:
unable to open for writing /mnt/etc/ld.so.conf.
Another observed:
illegal division by zero
These happen after closing format partitions, leaving the last green
star on "Format Partitions". It is the attempt to get through the
"choose packages to install" that the errors occur. Whether I choose
"Miscellaneous" or "Individual Package Selection" or both or neither
doesn't matter.
Here are some messages in /tmp/ddebug.log:
starting step choose packages
available size 1023745914 (corrected 855350733.502697)
unknown package 'numlock'
unknown install class normal in compssList
warning: setstep formatPartitions
starting step 'formatPartitions'
warning: can't open /etc/raidtab for reading: No such file or directory
step 'formatPartitions' finished
starting step 'choosePackages'
available size 1027345914 (corrected 855350733.502697)
unknown parkage 'numlock'
unknown install class normal in compssList
unknown install class normal in compssList
warning: Illegal division by zero at
/usr/bin/perl-install/install_steps_gtk.pm line 303
On starting all over again, another set of messages in /tmp/ddebug.log:
starting step choose packages
psUsingHdlists read 0 headers on 0 hdlists
unknown package 'basesystem'
warning: missing basesystem package at
/usr/bin/perl-install/install_any.pm line 278
At this point, the installer circles back to "Format Partitions".
Choose packages to install simply will not work. This is with v7.1. I
tried two different v7.0 CD's several months ago. Both returned similar
results, various error messages, and missing packages.
This system currently has functioning windoze 98SE in /dev/sda1, IBM
Boot Manager in /dev/sda3, OS/2 in /dev/sda4, OS/2 in /dev/sda6, CLOS
1.1 in 1.0 Gb /dev/sdc9 and RedHat 6.1 in 1.0 Gb /dev/sdc8. I'm
attempting to install to 1.0 Gb /dev/sdc10, created by Partition Magic
v5, on a 4 Gb disk. Swap is 125 Mb in /dev/sdc6.
Hardware info:
AcerOpen AX5T3 TX chipset mobo
P55C 233 CPU
96 Mb EDO SIMMs
SYM8751SP Symbios 53c875 SCSI
8 Gb /dev/sda Quantum Fireball SE
4 Gb /dev/sdb Quantum Fireball SE
4 Gb /dev/sdc Quantum Fireball ST
Sony 2.4X SCSI CD
1.44 Mb floppy
2.88 Mb floppy
no sound
no IDE
external modem
Is there a way to make this install?
--
A man of knowledge uses words with restraint . . . . Proverbs 17:27
NKJV
Felix Miata *** http://mrmazda.members.atlantic.net
------------------------------
From: "kosh" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.advocacy,alt.os.linux.mandrake
Subject: Re: New Linux Install
Date: Tue, 19 Sep 2000 23:10:24 -0600
In article <[EMAIL PROTECTED]>, "James M. Luongo"
<[EMAIL PROTECTED]> wrote:
> I plan on installing Linux Mandrake 7.1 for the first time. I need some
> help. How big should the partitions be? And, I heard something about
> LiLo not recognizing a Linux partition after a certain disk cylinder (or
> sector, whatever). I think it was 1023, but I'm not sure. Is this
> true? Help!
If you are installing Mandrake 7.1 just read the docs it has with it. I
have installed Mandrake 7.1 on many boxes and never had a problem on
anything more modern then a P90. It does a very good job at detection. If
you put the kernel where lilo can't reach grub is used automatically. The
mandrake 7.1 install is about the easiest linux install I have ever used.
That is why whenever I help a customer who wants to get rid of windows I
help them dual boot Mandrake and let them install it with me watching.
Usually they never ask me a single question during the install. Usually I
get comments about how easy it is to set up.
------------------------------
From: moonie;) <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux.mandrake,comp.os.linux.x
Subject: Re: NEW NVIDIA DRIVERS (Warning)
Date: Wed, 20 Sep 2000 01:09:11 -0400
On Tue, 19 Sep 2000, Stuart Levy wrote:
>In article <[EMAIL PROTECTED]>,
>moonie;) <[EMAIL PROTECTED]> wrote:
>
>>Hate to burst your bubble but its not the drivers themselves, I have VIA
>>chipset with K6-III/450 running ATA/66 with DMA and all the optimizations
>>running with XFree86 4.0, Nvidia .94's on a TNT2U. Same with my friends C300
>>with TNT. My sons system doesn't like (locks up on boot up) the optimizations
>>(pcchips mobo, going to replace it soon with the 503a like mine) with or
>>without XFree86 4.0/.94 nvidia.
>>--
>>moonie ;)
>
>It's hard to see how you can claim that there must be no problem with the
>drivers themselves, just because they work for you!
>
>Of course I wouldn't want to be in NVidia's position trying to support
>all combinations of motherboard and NVidia-based cards.
>
>I was interested to see, in a tomshardware.com review of 3D cards
>with NV Linux drivers, that he encountered one of the same symptoms I had:
>a scrolling text window could freeze, apparently in mid-bitblt
>(or perhaps after one of several bitblt's needed for scrolling?),
>only to resume when he touched the mouse! This often happened to me,
>and when lockups occurred it was usually the immediate precedent.
>
> Stuart Levy, [EMAIL PROTECTED]
What can I say, I had no trouble from 3 different chipset mobo's (Intel LX, VIA
MVP3, TXPro), 3 different manufacurers of processors (Intel C300, AMD
K6-III/450, Cyrix PR233), 3 different chipset cards (TNT, TNT2U, TNT2 M64),
and 2 different kernels (2.2.14, 2.4.0-test5). Now I understand that this
isn't a comprehensive list of all combinations available, but I do believe it
is a pretty good cross section of them.
--
moonie ;)
Registered Linux User #175104
http://counter.li.org
KDE2
Kernel 2.4.0-test5
XFree86 4.0 Nvidia .94 drivers
RAID 0 Striped
Test-Pilots-R-Us ;)
------------------------------
From: moonie;) <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux.mandrake,comp.os.linux.x
Subject: Re: NEW NVIDIA DRIVERS (Warning)
Date: Wed, 20 Sep 2000 01:22:24 -0400
On Tue, 19 Sep 2000, [EMAIL PROTECTED] wrote:
>In comp.os.linux.x moonie;) <[EMAIL PROTECTED]> wrote:
>> On Fri, 08 Sep 2000, Bernhard Mogens Ege wrote:
>>>>>>>> "Stuart" == Stuart Levy <[EMAIL PROTECTED]> writes:
>>>
>>>> In article <[EMAIL PROTECTED]>,
>>>> Bernhard Mogens Ege <[EMAIL PROTECTED]> wrote:
>>>>> I would be very carefull with these new nvidia drivers (version 0.9-5)
>>>>> as I have just lost my ext2 partition due to a crash caused by these
>>>>> drivers. I am reinstalling redhat as I type this.
>>>> [...]
>>>
>>>> Do you enable DMA on your hard disk? If so, don't!
>>>
>>>No DMA enabled. AMD chipset not recognized in RedHat kernels.
>>>
>>>> With earlier NVidia drivers (0.92), I did experience lockups,
>>>> and if I had DMA enabled on my IDE system drive, my filesystem
>>>> would be corrupted (chunks of i-node control information replaced
>>>> by junk) at essentially every lockup. With DMA off -- using slower
>>>> PIO for disk I/O -- I still got lockups, but never any filesystem
>>>> corruption.
>>>
>>>Good for you (not loosing data). I did get filesystem corruption with
>>>DMA off. It is less likely to appear with DMA off, I believe, but not
>>>impossible.
>>>
>>>> I haven't tried any of the more recent NVidia drivers (0.93-0.95)
>>>> though maybe I'll try again now -- but with DMA disabled, for sure.
>>>
>>>I did not have problems with DMA enabled and XFree86-4.0 and the 0.92
>>>drivers. Only the later ones posed problems.
>>>
>>>> I did report the above to NVidia and to this newsgroup. I never heard
>>>> back from NVidia, but did see a reference from there to a web page
>>>> I'd mentioned with a screen snapshot of an opengl rendering defect,
>>>> so somebody *was* paying attention to bug reports.
>>>
>>>I also reported some of my experiences and files bugreports to nvidia
>>>without ever hearing from them.
>>>
>>>> For free software, I don't expect help-line support. Sounds good to me.
>>>
>>>I don't expect help-line support, just a feedback on bugreports. I can
>>>live without that feedback if only I knew they were working that much
>>>harder on removing the cause for the crashes instead of fixing minor
>>>problems.
>>>
>>>> Stuart Levy, [EMAIL PROTECTED]
>>>
>>>Bernhard Ege
>
>> Hate to burst your bubble but its not the drivers themselves, I have VIA
>> chipset with K6-III/450 running ATA/66 with DMA and all the optimizations
>> running with XFree86 4.0, Nvidia .94's on a TNT2U. Same with my friends C300
>> with TNT. My sons system doesn't like (locks up on boot up) the optimizations
>> (pcchips mobo, going to replace it soon with the 503a like mine) with or
>> without XFree86 4.0/.94 nvidia.
>> --
>> moonie ;)
>
>If we can show that it locks up on some machines with the drivers, but doesn't
>lock up on the same machine *without* the drivers, then it's probably something
>to do with the drivers.
>
>Adam
Not necessarily, could be something to do with the kernel (they don't like the
2.2.17 kernel, but work fine with others) or something to do with the way the
XFree86 4.0/4.01 was installed (RPM instead of source, I installed from source
not from RPM, because I read that the RPM were having trouble). There are many
other variables that could be causing the problem. I have done the install of
94 with XFree86 4.0 on an Intel LX system with C300 processor and a TNT, my
own system with VIA MVP3, K6-III/450 with a TNT2U, and my sons TXPro mobo with
Cyrix PR233 with TNT2 M64, using both the 2.2.14 and 2.4.0-test5 kernels with
NO PROBLEMS AT ALL! While I do understand that this isn't a complete list of
all possible combinations, it is however a good cross section of them.
--
moonie ;)
Registered Linux User #175104
http://counter.li.org
KDE2
Kernel 2.4.0-test5
XFree86 4.0 Nvidia .94 drivers
RAID 0 Striped
Test-Pilots-R-Us ;)
------------------------------
From: Valentin Guillen <[EMAIL PROTECTED]>
Subject: Re: Cambio di risoluzione
Date: Wed, 20 Sep 2000 05:29:27 GMT
Marco,
When you ran the video configuration utility, you must or should have
specified the resolutions which you desire to use. If you did, and if
the configuration utility wrote a correct XF86Config file, then you can
switch (toggle) between all of the active resolutions with the
keystrokes
Ctrl-Alt-NumKyPad+ or with
Ctrl-Alt-NumKyPad-
If you did not specify other resolutions when you originally configured
the X system, then those other resolutions you desire are not configured
yet. In that case, you must rename or remove or move the current
XF86Config file, and rerun the video configuration utility once again.
If you think that those resolutions should be available to you now, you
can use a text editor like vi, or a graphical text editor, to open and
edit the XF86Config file. In each of the sections of this file which
reference the resolutions, be sure to put the resolution which you
desire to be DEFAULT as the first resolution mentioned in that section
of the file.
Ciao!
Valentin Guillen
If this doesn't help you, repost again with a bit more detail...:-)
ssibilmente risposte in e-mail)
> [EMAIL PROTECTED]
------------------------------
From: "Deb" <[EMAIL PROTECTED]>
Subject: failed redhat 6.2 installl now can't fdisk
Date: Wed, 20 Sep 2000 16:49:38 +1000
Greetings
Toshiba laptop
1 primary dos partition with Win98 (C - 2 gig)
1 extended dos with two logical (D & E - 1 gig each)
attempted to install redhat 6.2 to E - not enough space - tried to increase
space - got back to install window - clicked install -failed - rebooted to
Win98
E drive now gone, D drive still 1 gig - nothing else changed
Booted to floppy to run fdisk but it fails after asking about large drive
support, so can't fdisk, so can't go on with Linux installation until I get
the other half of my drive back
What have I done wrong?
deb
------------------------------
From: Valentin Guillen <[EMAIL PROTECTED]>
Subject: Re: Making LILO wait?
Date: Wed, 20 Sep 2000 05:52:20 GMT
Here's my /etc/lilo.conf file
I don't remember off hand how to tell not to boot until you give a
command. This file tells lilo to wait at least 40 seconds for input
from user before it does anything. This gives the user time to select
their boot options. =
What can greatly assist you is to have an instructional message file
which tell the user what the boot options are. That way you know what
to do.
===============================================================
# LILO Konfigurations-Datei
# Start LILO global Section
boot=3D/dev/hda3
#compact # faster, but won't work on all systems.
message=3D/boot/message
read-only
prompt
timeout=3D400
vga =3D normal # force sane state
# End LILO global Section
#
image =3D /boot/vmlinuz
root =3D /dev/hda3
label =3D linux
=============================================
in this example, the delay is 400 which equals about 40 seconds.
timeout=3D400
The line which says message (message=3D/boot/message) is the location and=
name of the file which contains the message to be displayed at boot
time. Here's an example from one of my machines. Everyting between the
dotted lines is in the file called message This contains characters
which only display correctly at the console, like at boot time. =
=========================================
=C9=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=
=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=
=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=BB
=BA =BA=
=BA Welcome to LiLo on Valentin's laptop computer... =BA=
=BA LiLo allows us to offer multiple operating systems =BA=
=BA (GNU/Linux, DOS, and OS/2) on this single computer. =BA=
=BA =BA=
=CC=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=
=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=
=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=B9
=BA =BA=
=BA Press the TAB key for a list of boot options =BA=
=BA Pressing ENTER without entering any options will =BA=
=BA invoke a default boot into SuSE 6.3 =BA=
=BA =BA=
=C7=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=
=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=
=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=B6
=BA=B2=B2=B1=B1=B0=B0~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~~=B0=B0=B1=B1=B2=B2=BA
=BA=B2=B2=B1=B1=B0=B0 ENJOY YOUR FLIGHT! =
=B0=B0=B1=B1=B2=B2=BA
=BA=B2=B2=B1=B1=B0=B0..........................................=
=2E..=B0=B0=B1=B1=B2=B2=BA
=C8=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=
=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=
=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=BC
========================================================================
The lilo man pages can tell you how to set lilo.conf file to where it
will never boot anything until you input a valid selection. Also, the
SuSE sites and mandrake user's site have very informative and
EASY-TO-UNDERSTAND lilo configuration sections. =
http://www.suse.com
http://www.suse.de
http://mandrakeuser.org
Hope it helps
Valentin Guillen
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.setup) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
