Linux-Setup Digest #147, Volume #20 Sat, 2 Dec 00 06:13:06 EST
Contents:
LI from LILO; I'm one answer away from the Linux promised land ("Dan Jacobson")
Re: HD off after boot - possible?? (moonie;))
Re: Making your own ISO Image. and updating Gentus to RH7 (or any other rpm based
distro) (moonie;))
Bind questions ("John Hanley")
Re: Crash While Setting Up Red Hat 6.2 on 486 ("John Hanley")
Re: HD off after boot - possible?? ("Juho L�nnblad")
Re: HD off after boot - possible?? (Isaac Kar-Keung To)
Re: Intel Integrated 815 AGP (Zip)
Re: I am confident you will help me with "LI" from LILO; I'm one (fciii)
Re: Linux Installation (fciii)
Re: Use Linux to share the broadband line (fciii)
Re: Telenet would not work from Win98 ---> Linux (DualIP)
----------------------------------------------------------------------------
From: "Dan Jacobson" <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux.mandrake,comp.os.linux.hardware,comp.sys.ibm.pc.hardware.storage
Subject: LI from LILO; I'm one answer away from the Linux promised land
Date: Sat, 2 Dec 2000 16:10:15 +0800
"Bracy" <[EMAIL PROTECTED]> ...
> When you select the partition to boot from during the install, select hdb1,
not hdb.
OK, shall I do the whole install again,
or is this something I can simply adjust in lilo.conf and run lilo again?
> > # cat /etc/lilo.conf
> > boot=/dev/hdb map=/boot/map install=/boot/boot.b vga=normal
> > default=linux keytable=/boot/us.klt
> > #lba32
> > #linear
> > prompt timeout=150 message=/boot/message menu-scheme=wb:bw:wb:bw
> > # get the numbers from your drive's docs:
> > disk=/dev/hdb
> > # bios=0x81
> > sectors=63 heads=16 cylinders=16383
> >
> > image=/boot/vmlinuz
> > label=linux root=/dev/hdb6 initrd=/boot/initrd.img append="
> > hdc=ide-scsi"
> > read-only
by the way
: try at the lilo prompt:
: linux /dev/hdb=C,H,S
: (look at the documentation for the correct syntax)
but when one only gets to LI, there is no boot prompt, unless you
mean the floppy boot prompt... from which I can already sucessfully boot into
linux from..
some 1998 quotes I found,
who knows their relevence to my
mandrake 7.2+sp97v+sis5513+quantum fireball lct 30gb case,
wherein i can boot by floppy only, lilo getting to LI otherwise
=========================1998:
Reset the BIOS on your mainboard for AUTO/AUTO and do not use
the silly disk-detect which gets the RAW CHS correct, but it to stupid
to adjust for LBA. I am will ing to bet if you poke your nose into what
the BIOS declares for each disk. The RAW LBA settings are wrong by the
total missing number of cylinders that you claim are not detected by the
kernel.
Trust me I know this does/can/usually is the case........
I have a disk that is exactly 16383,16,63 and the BIOS gets it dead wrong
everytime I auto-detect........Now if I go and manually enter the
'TRUE' CHS values into the bios-disk parameters as a user defined
setting, it will work.......Second is to skip this pain in the rear,
and set the flags to AUTO/AUTO and include that PIO settings are AUTO
also.
An AWARD Bios's config options that are effected are at the top of each
column of options.
AMI Bios's require the former method be used....drat......
The key clue to you problem was detection of "1024,255,63"
this is my classic 'screaming red-flag' warning that the BIOS
can't or is not allowed to count beyond a sector limit for an
8.0 Gig device (using the REAL definition of a MEG of disk space)
1Meg != 1,000,000 bytes (sales pitch)
1Meg != 1,024,000 bytes (memory)
1Meg == 1,048,576 bytes (reality) == 2^20
Now FDISK and LILO are a whole other issue.......
> Now think about the fdisk and LILO interaction.
> What is the effect of a too small number of cylinders?
> That part of the disk is inaccessible.
Yes if you choose not to inform the kernel that your computer is an idiot
that can't count.
ide_setup: hda=1247,255,63
ide_setup: hdc=1247,255,63
ide: Intel 82371 (single FIFO) DMA Bus Mastering IDE
Controller on PCI bus 0 function 57
ide: timings == a307e377
ide0: BM-DMA at 0xf000-0xf007
ide1: BM-DMA at 0xf008-0xf00f
hda: QUANTUM FIREBALL EL10.2A, 9787MB w/418kB Cache, CHS=1247/255/63, (U)DMA
hdb: QUANTUM FIREBALL EL10.2A, 9787MB w/418kB Cache, CHS=1247/255/63, (U)DMA
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
(Note, beginning steps of hardware RAID 1)
ide: PDC20246 UDMA Bus Mastering with ROM enabled but no address
Controller on PCI bus 0 function 152
ide: timings == 000003ee
ide0: BM-DMA at 0x7c00-0x7c07
ide1: BM-DMA at 0x7c08-0x7c0f
ide: Intel 82371 (single FIFO) DMA Bus Mastering IDE
Controller on PCI bus 0 function 57
ide: ports are not enabled (BIOS)
hda: QUANTUM FIREBALL EL10.2A, 9787MB w/418kB Cache, CHS=19885/16/63, UDMA
hdc: QUANTUM FIREBALL EL10.2A, 9787MB w/418kB Cache, CHS=19885/16/63, UDMA
ide0 at 0x6c00-0x6c07,0x7002 on irq 11
ide1 at 0x7400-0x7407,0x7802 on irq 11 (shared with ide0)
ide_setup: hda=1247,255,63
ide_setup: hdc=1247,255,63
hda: QUANTUM FIREBALL EL10.2A, 9787MB w/418kB Cache, CHS=1247/255/63, UDMA
hdc: QUANTUM FIREBALL EL10.2A, 9787MB w/418kB Cache, CHS=1247/255/63, UDMA
This logs from a modified version of 2.0.35.
Note that all three cases work with on/off board chipsets
> For LILO one may live with that - there have always
> been restrictions on the place of the kernel on disk.
> But for fdisk that is inacceptable - people struggle
> with this, and - as far as I can see - there is no
> reason at all to inflict these problems unto them.
>
> The number of people with 8+ GB disks increases quickly.
> The handling of large IDE disks has always been broken,
> but in 2.0.35 and 2.1.90 this problem was partially
> corrected by inserting the test for C/H/S=16383/16/63.
> However, this only solves the problem if the BIOS is
> not using a translation (`LBA' or `Large' or so).
> People with a large IDE disk and translating BIOS
> still cannot use the entire disk (without overriding
> the kernel view by giving LILO additional hda=C,H,S
> parameters, or going into expert mode of fdisk, etc.).
>
> The sooner this is corrected, the better.
I agree, but lets not carelessly blind-side the BIOS....I have done this
many times by disregarding Mark's and Gadi's warnings.......thus trashed
my various systems at least one order of magnitude that you have. However
I did learn..........
=================end 1998
--
www.geocities.com/jidanni E-mail: restore ".com." �n����
Tel:+886-4-5854780; starting in year 2001: +886-4-25854780
------------------------------
From: moonie;) <[EMAIL PROTECTED]>
Subject: Re: HD off after boot - possible??
Date: Sat, 2 Dec 2000 03:24:35 -0500
On Fri, 01 Dec 2000, Juho L�nnblad wrote:
>> Actually putting the HD's to sleep is not a good thing. The hardest thing
>on a
>> HD is when it spins up/down. Having a drive go into "sleep" mode and then
>> "wake up" over and over will shorten the drives life.
>> --
>> moonie ;)
>>
>> Registered Linux User #175104
>> http://counter.li.org
>
>Agreed, but my point is exactly to avoid that: I don't want to completely
>shut down the machine, because otherwise I'd need another machine running
>the "router". I want to be able to put the machine in a "sleep mode" so that
>the HD spins off and STAYS THAT WAY but the routing, forwarding and
>masquerading keep working. For example, when I would normally shut down the
>machine (and the drive would spin off) I just put it to this "sleep mode"
>instead.
>
>The problem is, I don't know if it is possible to do it in style, that is,
>so that I don't need to reboot to another version of kernel. Maybe by just
>configuring one runlevel properly??
>
>And yes, I know that it would be propably best for the HD to just let it run
>all the time. I don't care - I work in that room and I hate the noise. If it
>shortens the life span of the drive a bit, then so be it, the noise shortens
>mine... :)
>
>--Juho
If you really want to spin down the drive you can (I REALLY DON'T reccomend it
though) with the hdparm -S switch, just be sure you don't have anything that
accesses the drive (cron, etc) or it will just spin back up. If all this box
is doing is routing your net connection, a 486 (with no fan) and Coyote Linux
on a floppy will make NO noise (no HD needed) and it works very well (you
might even get away with removing the PS fan, if your brave). Do "man hdparm"
and read about the -S switch. Good luck.
--
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]>
Subject: Re: Making your own ISO Image. and updating Gentus to RH7 (or any other rpm
based distro)
Date: Sat, 2 Dec 2000 03:30:59 -0500
On Fri, 01 Dec 2000, Beavis Christ wrote:
>Hi folks, hate to be a bother, but I'm not exactly sure where to look on
>this.
>
>
>Here's my problem.
>
>abit bp6, w/ ATA66.
>
>'nuff said?..hehe
>
>Anyway, what I want to do is this.
>
>I'm running dual-boot, Winblows2000, Gentus (RH 6.2). What I want to do is
>make a new ISO image with the Gentus ATA66 driver, but use the RH 7
>packages, and I'm not 100% sure how to do all the various kernel recompiles
>and the constructing of the boot images that I would need to do.
>
>I tried updating to the RPM version on the rh7 cd and updating everything
>and removing the dependancy checks, but that met with disasterous results.
>(well not really disasterous, but I got a "too many files open" error
>message, and kpackage, and few other utilities would no longer work, so I
>was stuck with an X session that would only browse the internet, get mail,
>unless I wanted to rpm -Fvh everything by hand....pain in the butt, as I had
>270 rpm's to go).
>
>Mandrake 7 would install just fine, but they required a boot disk to
>continue the install, (to access ide2 and 3 as they called it), but Mandrake
>7 doesn't support the GeForce 256DDR out of the box, and right now my Linux
>and 2000 partitions can't see eachother yet.
Actually it does, just configure it as a TNT2 (uses the same driver for all
TNT/TNT2/GF/GF2 cards), or better yet, get XFree86 4.01 running with the Nvidia
drivers.
--
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: "John Hanley" <[EMAIL PROTECTED]>
Subject: Bind questions
Date: Sat, 02 Dec 2000 09:04:02 GMT
I'm running Linux RedHat 7.0 and want to enable a DNS.
I installed the following RPM packages:
bind-8.2.2_P5-25.i386.rpm
bind-utils-8.2.2_P5-25.i386.rpm
caching-nameserver-7.0-6.noarch.rpm
Section 3 in the DNS How-To
(http://howto.tucows.com/LDP/HOWTO/DNS-HOWTO.html) talks about the folder
'pz' (/var/named/pz) and the file 'root.hints' (/var/named/root.hints),
neither of which exist on my machine. Do I create these on my own? The
How-To isn't completely clear.
Also, I don't have a real domain of my own (my cable modem provider won't
allow it.) In my resolv.conf file, should I associate my ISP's domain with
search and list my localhost as the first nameserver? For example:
search my-isp-domain.com
nameserver 127.0.0.1 (localhost)
nameserver x.x.xx.x (my ISPs nameserver)
Thanks,
John
p.s. I tried posting this question to comp.protocols.dns.bind first but no
posts are visable since Nov. 23
------------------------------
From: "John Hanley" <[EMAIL PROTECTED]>
Subject: Re: Crash While Setting Up Red Hat 6.2 on 486
Date: Sat, 02 Dec 2000 09:21:14 GMT
Mark,
It seems obvious to me you've got some sort of hardware conflict or perhaps
a defective component.
Is that older hda legacy drive terminated somehow, perhaps with a jumper?
If so, remove it.
Is this system configuration proven? In other words, do you know if
everything is functional and that the components like each other?
As a test, I would disconnect drive hdc and try to install again. If you
might also ditch the 1.2 GB drive and promote the 10 GB to hda (device 0)
and install again.
"Mark W. Stroberg" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I was trying to install Red Hat 6.2 on an old 486 33MHz I got for cheap.
> Unfortunately, after partitioning, selecting packages to install, and
> formatting the partitions, it crashed with the message: "Abnormal
> termination -- signal 11" or something like that. I have no idea what's
> wrong. The computer has 32 MB of RAM, an ancient IDE controller as the
> primary channel and a Promise EIDE Max II UDMA 33 controller as the
> secondary channel controller. hda is 1.2 GB, there is no hdb, hdc is 10
> GB, hdd is 50X CD-ROM drive. Secondary Master (hdc) is partitioned as
> follows: Extended partition spanning entire drive, hdc5, hdc6, and hdc7
> are FAT-16 of maximum size (2GB) as Windows 3.1 is also on this
> computer, hdc8 is 127M swap, hdc9 is 50M (/boot), hdc10 is 3.5G (/). Any
> help would be appreciated.
>
> TIA
>
> Mark W. Stroberg
>
------------------------------
From: "Juho L�nnblad" <[EMAIL PROTECTED]>
Subject: Re: HD off after boot - possible??
Date: Sat, 2 Dec 2000 11:32:12 +0200
"moonie;)" <[EMAIL PROTECTED]> kirjoitti viestiss�
news:[EMAIL PROTECTED]...
> On Fri, 01 Dec 2000, Juho L�nnblad wrote:
> >> Actually putting the HD's to sleep is not a good thing. The hardest
thing
> >on a
> >> HD is when it spins up/down. Having a drive go into "sleep" mode and
then
> >> "wake up" over and over will shorten the drives life.
> >> --
> >> moonie ;)
> >>
> >> Registered Linux User #175104
> >> http://counter.li.org
> >
> >Agreed, but my point is exactly to avoid that: I don't want to completely
> >shut down the machine, because otherwise I'd need another machine running
> >the "router". I want to be able to put the machine in a "sleep mode" so
that
> >the HD spins off and STAYS THAT WAY but the routing, forwarding and
> >masquerading keep working. For example, when I would normally shut down
the
> >machine (and the drive would spin off) I just put it to this "sleep mode"
> >instead.
> >
> >The problem is, I don't know if it is possible to do it in style, that
is,
> >so that I don't need to reboot to another version of kernel. Maybe by
just
> >configuring one runlevel properly??
> >
> >And yes, I know that it would be propably best for the HD to just let it
run
> >all the time. I don't care - I work in that room and I hate the noise. If
it
> >shortens the life span of the drive a bit, then so be it, the noise
shortens
> >mine... :)
> >
> >--Juho
>
> If you really want to spin down the drive you can (I REALLY DON'T
reccomend it
> though) with the hdparm -S switch, just be sure you don't have anything
that
> accesses the drive (cron, etc) or it will just spin back up. If all this
box
> is doing is routing your net connection, a 486 (with no fan) and Coyote
Linux
> on a floppy will make NO noise (no HD needed) and it works very well (you
> might even get away with removing the PS fan, if your brave). Do "man
hdparm"
> and read about the -S switch. Good luck.
> --
> moonie ;)
>
Thanks a lot, I really appeciate your feedback. I agree that using a surplus
486 (I have one) would be the smart thing to do. But removing the PS fan
would risk a fire (in theory, anyway) and I don't want to do that.
One last question: I've tried shutting down just about everything but the
drive spins up after about 5 minutes and does something which sounds a lot
like sychronizing the swap. Is there a way to temporarily shut down virtual
memory or switch it to a ram disk?
--Juho
------------------------------
From: Isaac Kar-Keung To <[EMAIL PROTECTED]>
Subject: Re: HD off after boot - possible??
Date: 02 Dec 2000 18:09:58 +0800
>>>>> "Juho" =3D=3D Juho L=F6nnblad <[EMAIL PROTECTED]> writes:
Juho> Thanks a lot, I really appeciate your feedback. I agree that using
Juho> a surplus 486 (I have one) would be the smart thing to do. But
Juho> removing the PS fan would risk a fire (in theory, anyway) and I
Juho> don't want to do that.
I had a 486 in such configuration, and I didn't noticed that its cooling fan
is malfunctioning for months. It's somewhat hot, but far from anything
close to cause fire.
Juho> One last question: I've tried shutting down just about everything
Juho> but the drive spins up after about 5 minutes and does something
Juho> which sounds a lot like sychronizing the swap. Is there a way to
Juho> temporarily shut down virtual memory or switch it to a ram disk?
Shut down virtual memory: just say swapoff -a.
On the other hand, it is very difficult to avoid all disk activity, as I
have tried (and end up having a couple of worn HDs). The problem is that
Unix pretty expect that "writing to disk" is a good thing. For example,
whenever you read anything from the disk, even if it is cached, it has to
write back the last access time (unless you switch that off in fstab). Any
logging activity will also cause the disk to wake up. Of course, "update"
will somehow write something to the disk even if there seems nothing to be
written. So good luck.
Regards,
Isaac.
------------------------------
From: Zip <[EMAIL PROTECTED]>
Subject: Re: Intel Integrated 815 AGP
Date: Sat, 02 Dec 2000 10:53:27 +0100
With Redhat 7.0 the 810+815 chipset and VGA is recognized.
Tested on a ASUS CUSL2 board
Henry W Meyerding wrote:
> Does anyone have a way to use a recent HP vectra computer that uses the
> integrated motherboard video card that uses the "Intel Integrated 815
> AGP" chipset? I also have another one that uses an 810.
>
> Any assistance cheerfully accepted.
>
> Thanks
>
> HWenry Meyerding
------------------------------
From: fciii <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux.mandrake,comp.os.linux.hardware,comp.sys.ibm.pc.hardware.storage
Subject: Re: I am confident you will help me with "LI" from LILO; I'm one
Date: Sat, 2 Dec 2000 02:32:19 -0800
You need to have the /boot partition on the first harddrive below sector
1024. It will not work from the second disk. You can use something like
fips to create a 10Mb /boot partition on hda and edit your /etc/fstab file
to reflect the change. Alternately, you can boot from floppy.
On Fri, 1 Dec 2000, Dan Jacobson wrote:
> Dear sirs, I am able to boot Mandrake 7.2 by floppy, however from hard
> disk I am stuck at lilo's "LI", which I use as it is better documented
> than grub (stuck too). I have windows on hda and boot linux on
> hdb. Apparantly hdb's geometry is not properly autodetected in BIOS. I
> suppose the strategy is to enter the manufacturer's specs into BIOS
> and lilo.conf rather than put wrong info found in BIOS into
> lilo.conf. Below are excerpts.
> # dmesg
> Linux version 2.2.17-21mdk Thu Oct 5 13:16:08 CEST 2000
> SiS5597
> ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA
> hdb: QUANTUM FIREBALLlct15 30, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hdb: QUANTUM FIREBALLlct15 30, 28629MB w/418kB Cache, CHS=3D58168/16/63, =
UDMA(33)
> ***58168/16/63 aparantly has the number of cylenders upped to
> agree with the true size instead of the artificially low 16383 specified =
by
> Quantum. I wonder how the kernal gets this number.
> Partition check:
> hdb: [PTBL] [8191/32/63] hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 >
> ***is the wrong 8191/32/63 now imprinted into my kernal from what the
> bios said that day I installed mandrake? Shall I worry
> about this even though I can boot by floppy?
> Shall I reinstall mandrake after manually editing bios cmos settings?
> If I say yes to LBA in my bios it forces heads=3D255.
> Would just using "normal" instead of "lba" be ok when configuring
> bios?
>=20
> my bios:
> BIOS Date: 01/22/98
> BIOS Type: Award Modular BIOS v4.51PG
> BIOS ID: 01/22/98-SiS-5598-<SP97_V>C-00
>=20
> # hdparm -g /dev/hdb
> geometry =3D 8191/32/63, sectors =3D 58633344, start =3D 0
> ***ok, these incorrect values are spread far and wide
> in my computer, but i thought it doesn't matter at least to linux...
> # hdparm -i /dev/hdb
> Model=3DQUANTUM FIREBALLlct15 30, FwRev=3DA01.0F00, SerialNo=3D614019446=
573
> Config=3D{ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=3D16383/16/63, TrkSize=3D32256, SectSize=3D21298, ECCbytes=3D4
> BuffType=3DDualPortCache, BuffSize=3D418kB, MaxMultSect=3D16, MultSect=
=3D16
> CurCHS=3D16383/16/63, CurSects=3D16514064, LBA=3Dyes, LBAsects=3D5863334=
4
> ***yes, 16383/16/63 is what the quantum docs say
> I assume the number of cylinders are delibrately kept below a barrier.
> IORDY=3Don/off, tPIO=3D{min:120,w/IORDY:120}, tDMA=3D{min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
> # hdparm -I /dev/hdb
> RawCHS=3D16/21298/0, TrkSize=3D63, SectSize=3D0, ECCbytes=3D12590
> (maybe): CurCHS=3D63/64528/251, CurSects=3D-1400897264, LBA=3Dyes, LBAse=
cts=3D458752
> ***could these two rawly reported lines give me a clue as to how hdb actu=
ally
> talks to my computer?
> # fdisk -l /dev/hdb
> Disk /dev/hdb: 32 heads, 63 sectors, 29084 cylinders
> Units =3D cylinders of 2016 * 512 bytes
> ****again, wrong values branded into place...
> Device Boot Start End Blocks Id System
> /dev/hdb1 * 1 507 511024+ 83 Linux
> ***well, one puts /boot on a low cylinder
> I assume lilo doesn't need to read "/" to know where /boot is.
> /dev/hdb2 508 11194 10772496 5 Extended
> /dev/hdb5 508 760 254992+ 82 Linux swap
> /dev/hdb6 761 1774 1022080+ 83 Linux
> /dev/hdb7 1775 5837 4095472+ 83 Linux
> /dev/hdb8 5838 9222 3412048+ 83 Linux
> /dev/hdb9 9223 10236 1022080+ 83 Linux
> /dev/hdb10 10237 11194 965632+ 83 Linux
>=20
> # cat /etc/lilo.conf
> boot=3D/dev/hdb
> map=3D/boot/map
> install=3D/boot/boot.b
> vga=3Dnormal
> default=3Dlinux
> keytable=3D/boot/us.klt
> #lba32
> #linear
> prompt
> timeout=3D150
> message=3D/boot/message
> menu-scheme=3Dwb:bw:wb:bw
> # get the numbers from your drive's docs:
> disk=3D/dev/hdb
> # bios=3D0x81
> sectors=3D63
> heads=3D16
> cylinders=3D16383
>=20
> image=3D/boot/vmlinuz
> label=3Dlinux
> root=3D/dev/hdb6
> initrd=3D/boot/initrd.img
> append=3D" hdc=3Dide-scsi"
> # append=3D" hdc=3Dide-scsi hd=3D16383,16,63" ***i have a lilo problem
> not a kernal problem, so no need to pass this line?
> read-only
>=20
> # lilo -v -v -v
> Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
> 63 sectors. Partition offset: 63 sectors.
> Secondary loader: 11 sectors.
> Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
> 63 sectors. Partition offset: 63 sectors.
> Mapping message file /boot/message
> Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
> 63 sectors. Partition offset: 63 sectors.
> Message: 1 sector.
> Boot image: /boot/vmlinuz
> Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
> 63 sectors. Partition offset: 63 sectors.
> Setup length is 7 sectors.
> Mapped 1301 sectors.
> Mapping RAM disk /boot/initrd.img
> Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
> 63 sectors. Partition offset: 63 sectors.
> RAM disk: 748 sectors.
> Added linux *
> <dev=3D0x81,hd=3D2,cyl=3D3,sct=3D46>
> "ro root=3D346 hdc=3Dide-scsi"
> Boot image: /boot/vmlinuz
> Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
> 63 sectors. Partition offset: 63 sectors.
> Setup length is 7 sectors.
> Mapped 1301 sectors.
>=20
> By the way, to those who plan to tinker,
> http://einstein.et.tudelft.nl/~robn/linux-docs/chs-translation-how-it-wor=
ks
> though dated, says:
> "Read this so that you understand the possible data integrity
> problem that a WD EIDE type BIOS creates. Any BIOS that has a
> "LBA mode" in the BIOS setup could be a WD EIDE BIOS. Be very
> careful and NEVER chage the "LBA mode" setting after you have
> partitioned and installed your software."
> --
> www.geocities.com/jidanni E-mail: restore ".com." =BFn=A4=A6=A5=A7
> Tel:+886-4-5854780; starting in year 2001: +886-4-25854780
>=20
>=20
>=20
>=20
------------------------------
From: fciii <[EMAIL PROTECTED]>
Subject: Re: Linux Installation
Date: Sat, 2 Dec 2000 02:56:19 -0800
vi /etc/inittab
=========================
# Default runlevel.....
# 0 - halt (Do NOT set .....
# 1 - Single user mode
# 2 - Multiuser, without NFS ....
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - roboot (Do NOT set ....
id:2:initdefault
=========================
I think mandrake uses the same inittab settings as above, you'll notice
the 2 on the line that starts with id, in this example, to change to a GUI
logon, one would change the 2 to a 5, save it and be done.
On Thu, 30 Nov 2000, Dennis wrote:
> have you tried typing startx at the $ prompt?
> NagaSri <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > I am new to Linux. I tried to install Linux Mandrake 7.2 on a partition.
> > Everything seemed OK. But when I booted up, it booted to a $ prompt while
> > I was expecting a GUI. I re-installed it a few times and each time it was
> > behaving a bit different. I tried Recommended as well as custom modes. It
> > asked for monitor and display setting sometimes and sometimes it did not.
> >
> > I am installing it on Toshiba Satellite Pro 460 CDX laptop.
> >
> > Anyone with good guess, your help is appreciated.
> >
> > Thanks
> > Sridhar
> >
> > --
> > Posted via CNET Help.com
> > http://www.help.com/
>
>
>
>
------------------------------
From: fciii <[EMAIL PROTECTED]>
Subject: Re: Use Linux to share the broadband line
Date: Sat, 2 Dec 2000 03:00:30 -0800
RTFM
On Thu, 30 Nov 2000, test wrote:
> Our company lease the ADSL line and we want to setup a Linux setup to share
> the broadband line with two network cards inserted.
>
> Do anybody tells me how to configure and use what software to do such a
> project ?
>
>
>
>
------------------------------
From: [EMAIL PROTECTED] (DualIP)
Subject: Re: Telenet would not work from Win98 ---> Linux
Date: Sat, 02 Dec 2000 11:04:25 GMT
On Sat, 02 Dec 2000 06:53:03 +0800, Ming Fai LI <[EMAIL PROTECTED]> wrote:
>I am trying to update and change the configuration files of my linux
>box via telnet from another window 98 machine inside my home LAN.
>
>For all the telnet client programs that I've downloaded, the F10 key
>just doesn't work.
>
>So:
>
>1. How can I make F10 key work in my telnet client program?
>2. Is there any recommended telnet client program for Win 98 machines?
>3. What is the other way that i can remotely change the configuration
>files and do installations form Window 98 machines to my Linux box?
>
>I am using Suse Linux 6.2 F10 is important because after choosing a
>package from the CD ROM, it need F10 to confirm the selection to
>continue the selection. The scenerio now is pressing F10 will give an
>equivalent ESC effect and installation cannot be continued.
I use CRT3.1 to telnet into my RH62 box.
F10 simply works , (at least in midnight commander) for other function
keys I must use <ALT>-1 instead of F1
DualIP
------------------------------
** 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
******************************
