ls no display directory
Howdy all:-) I inadvertently typed " cd\ " (without the quotes) while at the root prompt. I got a what looked like a DOS prompt " > " (again without the quotes) so I am assuming that somehow I switched over to DOS mode somehow. I haven't even looked at running stuff from the DOS side yet as I have been concentrating on learning linux syntax, installing etc. Anyways to make a long story short, now whenever I try to do a directory listing of root with " ls " (yes indeed, without the quotes) no directory names/files are displayed. If I switch to a subdirectory or do a "ls" (yep, you guessed it!) with full directory path, then ls seems to work just fine.it's only in the root directory that names aren't displayed. Any clues on this strange behaviour anyone? Thanks.:-) Opps, almost forgot! How does one go about displaying which directory they are in as part of the prompt? eg: etc/foo/bar# rather than just having the "#" displayed (Need I mention about the quotes? ) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mono monitor with x (fwd)
Addressed to: Lazar Fleysher <[EMAIL PROTECTED]> debian-user@lists.debian.org ** Reply to note from Lazar Fleysher <[EMAIL PROTECTED]> Tue, 30 Sep 1997 13:16:14 -0600 (MDT) > > I have an old Hercules card and monitor. (I do not know whether being old > matters). In /etc/X11/XF86Config file I use > > HorizSync 18.43 > VertRefresh 50 > > Mode: 720x350 > > Modeline "720x350" 18.43 720 760 800 820 350 360 475 400 > > Note: All numbers in Modeline I took from "sky" except 720 and 350 of > course. Nevertheless, it works o.k. > > If the above is to the point I can send you full XF86Config file. If you (or anyone else who knows about doing this) could send me the config files, it would be very much appreciated. I just starting to setup Debian on an old system that uses a Herc monitor so being able to run XWindows on it sounds really interesting. Thanks for any info you can provide.:-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dpkg and dselect
Addressed to: Dale Scheetz <[EMAIL PROTECTED]> Debian ** Reply to note from Dale Scheetz <[EMAIL PROTECTED]> Fri, 26 Sep 1997 13:19:49 -0400 (EDT) > > On Fri, 26 Sep 1997, Lawrence Lucier wrote: > > > The Rescue/Base installation refuses to install LILO on my system. > > What steps did you take to get here? The installation should be nearly > complete at this point. You made partitions, installed and configured the > kernel and drivers, installed and configured the base system? I can totally complete the floppy base installation except for the part where the installation procedure is supposed to install LILO but refuses to do so. > So, what were the steps you followed to install LILO, Just worked my way through the floppy based installation procedure > and what error > messages, if any, did you recieve? sbin/dinstall: /target/sbin/lilo not found! > > The boot disk refuses to > > boot up because, AFAIK, LILO isn't installed on the harddrive. > > The boot disk does not depend on LILO or the hard drive to boot up the > kernel. You will need a "valid" root file system for the kernel to mount > before the boot up can complete. > > Changed > > the reference in > > SYSLINUX.CFG on the floppy boot disk to: > > > > APPEND root=/dev/fd0 ro > > > No root file system here ;-) No that's true but if the floppy drive is given as root, the boot floppy installation procedure will pause and ask you to insert a root floopy disk. >From the docs, I gathered the impression that the root disk generated from the root.bin file qualified as a valid root file system. Unfortunatly, a kernal warning is generated when using this method and so I can't even boot this way either. > > > from > > > > APPEND root=/dev/hda6 ro > > > If this is actually where you installed the base system, what are the > other partitions like? OS/2 Boot Manager, (primary)DOS, (extended)OS/2 HPFS, Linux and Linux swap. >(BTW, LILO will not install on an extended > partition AFAIK) HI looked through the docs for this kind of limitation but didn't see anything that pointed to this fact. Will be checking this out again though. > > > When prompted for the root floppy I used the file image floppy > generated by ROOT.BIN..still > > the system won't boot. > > > This is a compressed image and is typically uncompressed on a RAM disk, so > the arguments passed to the kernel are more complex than what you have > used. When using loadlin for this task the command line looks like: > > loadlin linux root=/dev/ram initrd=root.bin > > If you use APPEND and have used rawrite2.exe to put the root.bin image > onto a floppy, you probably want to change the initrd to =/dev/fd0. Ahhh...OK, thanks for the tip! :-) > > > OK, I thought did I, no problem, I will just do a LILO manual install > with the LILO_19-2.deb > > file I grabbed off the Debian site and tweak it from there. Read the > information on dpkg and > > dselect in the debian and install docs.booted the Rescue floppy > and went into the shell. > > So, you can boot the rescue floppy! The rescue disk is part of the floppy based install, along with the driver disk and the 4 1.44 base image disks. Booting with the rescue disk is no problemit's the boot disk that won't proceed past a certain point. It goes fine until just after the partition checkheres' the screen output from there on: Partition check: hda: hda1 hda2 hda3 VFS: Mounted root (ext2 filesystem) readonly. After these lines are displayed, the boot will proceed no further. > and look at and modify files on that > partition, but you don't have access > to any tools not available at > installation time. This means you can't run > dpkg/dselect from the rescue > disk. > Ahhh..OK thanks for clearing that up. :-) > Before we can do much more for you, we will need some details of the > installation as well as the failures you experienced. Basically it's just a matter of the installation procedure not installing LILO which then necessitates the utilization of the boot floppy (made by the installation procedure) as an alternative means of booting the system. Alas, even the boot floppy refuses to cooperate! Thanks for your reply and will ttyl...:-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dpkg and dselect
Addressed to: Dale Scheetz <[EMAIL PROTECTED]> Debian ** Reply to note from Dale Scheetz <[EMAIL PROTECTED]> Fri, 26 Sep 1997 13:19:49 -0400 (EDT) > > On Fri, 26 Sep 1997, Lawrence Lucier wrote: > > > The Rescue/Base installation refuses to install LILO on my system. > > What steps did you take to get here? The installation should be nearly > complete at this point. You made partitions, installed and configured the > kernel and drivers, installed and configured the base system? I can totally complete the floppy base installation except for the part where the installation procedure is supposed to install LILO but refuses to do so. > So, what were the steps you followed to install LILO, Just worked my way through the floppy based installation procedure > and what error > messages, if any, did you recieve? sbin/dinstall: /target/sbin/lilo not found! > > The boot disk refuses to > > boot up because, AFAIK, LILO isn't installed on the harddrive. > > The boot disk does not depend on LILO or the hard drive to boot up the > kernel. You will need a "valid" root file system for the kernel to mount > before the boot up can complete. > > Changed > > the reference in > > SYSLINUX.CFG on the floppy boot disk to: > > > > APPEND root=/dev/fd0 ro > > > No root file system here ;-) No that's true but if the floppy drive is given as root, the boot floppy installation procedure will pause and ask you to insert a root floopy disk. >From the docs, I gathered the impression that the root disk generated from the root.bin file qualified as a valid root file system. Unfortunatly, a kernal warning is generated when using this method and so I can't even boot this way either. > > > from > > > > APPEND root=/dev/hda6 ro > > > If this is actually where you installed the base system, what are the > other partitions like? OS/2 Boot Manager, (primary)DOS, (extended)OS/2 HPFS, Linux and Linux swap. >(BTW, LILO will not install on an extended > partition AFAIK) HI looked through the docs for this kind of limitation but didn't see anything that pointed to this fact. Will be checking this out again though. > > > When prompted for the root floppy I used the file image floppy > generated by ROOT.BIN..still > > the system won't boot. > > > This is a compressed image and is typically uncompressed on a RAM disk, so > the arguments passed to the kernel are more complex than what you have > used. When using loadlin for this task the command line looks like: > > loadlin linux root=/dev/ram initrd=root.bin > > If you use APPEND and have used rawrite2.exe to put the root.bin image > onto a floppy, you probably want to change the initrd to =/dev/fd0. Ahhh...OK, thanks for the tip! :-) > > > OK, I thought did I, no problem, I will just do a LILO manual install > with the LILO_19-2.deb > > file I grabbed off the Debian site and tweak it from there. Read the > information on dpkg and > > dselect in the debian and install docs.booted the Rescue floppy > and went into the shell. > > So, you can boot the rescue floppy! The rescue disk is part of the floppy based install, along with the driver disk and the 4 1.44 base image disks. Booting with the rescue disk is no problemit's the boot disk that won't proceed past a certain point. It goes fine until just after the partition checkheres' the screen output from there on: Partition check: hda: hda1 hda2 hda3 VFS: Mounted root (ext2 filesystem) readonly. After these lines are displayed, the boot will proceed no further. > and look at and modify files on that > partition, but you don't have access > to any tools not available at > installation time. This means you can't run > dpkg/dselect from the rescue > disk. > Ahhh..OK thanks for clearing that up. :-) > Before we can do much more for you, we will need some details of the > installation as well as the failures you experienced. Basically it's just a matter of the installation procedure not installing LILO which then necessitates the utilization of the boot floppy (made by the installation procedure) as an alternative means of booting the system. Alas, even the boot floppy refuses to cooperate! Thanks for your reply and will ttyl...:-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
dpkg and dselect
Howdy all:-) First off, many thanks to the people who responded to my DOSKey and file format queries. Lots of great information sent my way and much appreciated at this end! :-) Quick recap of my problem here: The Rescue/Base installation refuses to install LILO on my system. The boot disk refuses to boot up because, AFAIK, LILO isn't installed on the harddrive. Changed the reference in SYSLINUX.CFG on the floppy boot disk to: APPEND root=/dev/fd0 ro from APPEND root=/dev/hda6 ro When prompted for the root floppy I used the file image floppy generated by ROOT.BIN..still the system won't boot. OK, I thought did I, no problem, I will just do a LILO manual install with the LILO_19-2.deb file I grabbed off the Debian site and tweak it from there. Read the information on dpkg and dselect in the debian and install docs.booted the Rescue floppy and went into the shell. >From what I can see, neither dpkg or dselect is included (or can be run from >the shell) in the base installation setup. (ARRRH..did I mention yet that I'm having fun? ). I seemed to have reached a Catch-22 stage here and am no longer sure how to proceed on rectifying this problem...any words of wisdom for this confused but enthusiastic newbie would be greatly appreciated. :-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
DOSKey equivalent
Howdy all:-) Just wondering if there is a proggie analogous to MSDOS's DOSKey (which saves typed in keystrokes and then allows the user to recall them by using the arrow keys)? Thanks...:-) PS.I am having trouble getting past the installation floppy boot stage so even though a program like this might be included in a future package install I haven't reached that stage yet. "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: formatted floppy type??
Addressed to: Will Lowe <[EMAIL PROTECTED]> debian-user@lists.debian.org ** Reply to note from Will Lowe <[EMAIL PROTECTED]> Thu, 25 Sep 1997 15:14:08 -0400 (EDT) > > reason I'm asking is because my boot floppy and install disks don't seem to > > respond to either > > ext2 or dos when I try to mount them. > > Or maybe because I'm a newbie at linux I am issuing the wrong command??? > > :-) > > It's entirely possible -- you should be doing someting like > > mount -t msdos /dev/fd0 /mnt Howdy Will...thanks for the reply. :-) Seems it's just the four 1.44 base install disks that don't respond to either: mount -t msdos /dev/fd0 /mnt or mount -t ext2 /dev/fd0 /mnt VFS gives an error message stating "Can't find MSDOS/ext2 filesystem on dev 02:00". BTW, would you happen to know what the 02:00 describes? Thanks again...:-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
formatted floppy type??
Hi all. Is there any way of determining which kind of filesystem a floppy has been formatted with? The reason I'm asking is because my boot floppy and install disks don't seem to respond to either ext2 or dos when I try to mount them. Or maybe because I'm a newbie at linux I am issuing the wrong command??? :-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
newsgroup
** Reply to note from George Bonser <[EMAIL PROTECTED]> Wed, 24 Sep 1997 19:37:43 -0700 (PDT) Howdy all.:-) See from the docs (and various net searchs) there is a newsgroup called linux.debian.users available but I haven't been able to track down a news server which carries it. Anyone have an address (preferably one that allows postings as well as reading)thanks! :-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
lilo
** Reply to note from George Bonser <[EMAIL PROTECTED]> Wed, 24 Sep 1997 19:37:43 -0700 (PDT) Howdy all.:-) Using Rescue disk install program, I have set up Boot Manager, DOS, OS/2 HPFS, Linux ext2, and linux swap partitions on my harddrive. Seems that the floppy install didn't (won't or can't find relevent file(s)) install liloI grabbed lilo_19-2.deb off a debian ftp site. Can I just install this file or do I also need some other files? Thanks:-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: [RANT] The Future of Debian (and Linux)
** Reply to note from George Bonser <[EMAIL PROTECTED]> Wed, 24 Sep 1997 19:37:43 -0700 (PDT) Howdy all.:-) Using Rescue disk install program, I have set up Boot Manager, DOS, OS/2 HPFS, Linux ext2, and linux swap partitions on my harddrive. Seems that the floppy install didn't (won't or can't find relevent file(s)) install liloI grabbed lilo_19-2.deb off a debian ftp site. Can I just install this file or do I also need some other files? Thanks:-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: [RANT] The Future of Debian (and Linux)
** Reply to note from George Bonser <[EMAIL PROTECTED]> Wed, 24 Sep 1997 19:37:43 -0700 (PDT) Howdy all.:-) See from the docs (and various net searchs) there is a newsgroup called linux.debian.users available but I haven't been able to track down a news server which carries it. Anyone have an address (preferably one that allows postings as well as reading)thanks! :-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Newbie going crazy........part 2
** Reply to note from Lawrence Lucier <[EMAIL PROTECTED] Sun, 21 Sep 1997 01:28:15 PST Howdy all...:-) Still having problems with trying to install DebianI have included my original message below but am also providing some new information on this: The boot floppy will proceed loading various drivers until this one is displayed: "VFS: Mounted root (ext2 filesystem) readonly." Anyone have any idea what driver Debian loads next? Also I have a old Herc amber monitor hooked up to this computercould this be a source of potential problems (eg: not the right video driver being loaded?) Can't see how it would be considering everything has been texted based during the install but thought I might as well ask anyways. Can anyone suggest a URL for a good FAQ or primer which covers installing Debian...the one I have is kinda scant on information regarding install problems. <<< Original message starts >>> Picked up the following files: 9-18-97 2:24p 1474560 42 base14-1.bin 9-18-97 2:28p 1474560 42 base14-2.bin 9-18-97 2:27p 1474560 42 base14-3.bin 9-18-97 2:23p 1299456 42 base14-4.bin 9-18-97 12:05p 1474560 42 drv1440.bin 9-18-97 11:14a 50556 0 install.txt 9-18-97 1:08p 17863 42 rawrite2.exe 9-18-97 12:10p 1474560 42 resc1440.bin Followed the directions layed out in install.txt to make the boot, rescue, base, and driver floppies using rawrite2.exe. Didn't appear to be any problems involved with generating the floppies. Have run through the install proceedure three times now, ending up with the same problem(s) each time: The following error message is generated when the installation program is setting up Debian so that it can be booted from the harddrive: sbin/dinstall: /target/sbin/lilo: not found When exiting the installation program upon completing the setup, the setup program asks if the user wants the system rebooted.when I answer yes, all that happens is a couple of lines of text stating "Closing x files" etc. The reboot does not take place..the computer is just left hanging there displaying those lines of text. When I try using the boot floppy disk (NOT the rescue disk), the boot appears to proceed correctly but again I am left with a hung screen.the driver text info is displayed as it's being loaded but then I can proceed no further. (Keyboard is functional as I can still type but commands are not being processed.) Any thoughts on why these things are occuring would be greatly appreciated..thanks! :-) <<< Original Message Ends >>> "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Newbie going crazy........
Addressed to: Jose Oncina Carratala <[EMAIL PROTECTED]> debian-user@lists.debian.org ** Reply to note from Jose Oncina Carratala <[EMAIL PROTECTED]> Sat, 20 Sep 1997 13:25:01 +0200 > > Lawrence Lucier wrote: > > > Howdy all...:-) > > > > Picked up the following files: > > > > 9-18-97 2:24p 1474560 42 base14-1.bin > > 9-18-97 2:28p 1474560 42 base14-2.bin > > 9-18-97 2:27p 1474560 42 base14-3.bin > > 9-18-97 2:23p 1299456 42 base14-4.bin > > 9-18-97 12:05p 1474560 42 drv1440.bin > > 9-18-97 11:14a 50556 0 install.txt > > 9-18-97 1:08p 17863 42 rawrite2.exe > > 9-18-97 12:10p 1474560 42 resc1440.bin > > > > Followed the directions layed out in install.txt to make the boot, rescue, > > base, and driver > > floppies using rawrite2.exe. Didn't appear to be any problems involved > > with generating the > > floppies. > > > > Have run through the install proceedure three times now, ending up with the > > same problem(s) each > > time: > > > > The following error message is generated when the installation program is > > setting up Debian so > > that it can be booted from the harddrive: > > > > sbin/dinstall: /target/sbin/lilo: not found > > > > When exiting the installation program upon completing the setup, the setup > > program asks if the > > user wants the system rebooted.when I answer yes, all that happens > > is a couple of lines > > of text stating "Closing x files" etc. The reboot does not take > > place..the computer is > > just left hanging there displaying those lines of text. > > > > When I try using the boot floppy disk (NOT the rescue disk), the boot > > appears to proceed > > correctly but again I am left with a hung screen.the driver text > > info is displayed as > > it's being loaded but then I can proceed no further. (Keyboard is > > functional as I can still type > > but commands are not being processed.) > > > > Any thoughts on why these things are occuring would be greatly > > appreciated..thanks! :-) > > I had a similar problem, some times it said: > > sbin/dinstall: /target/sbin/lilo: not found > > other times it said: > > open /boot/boot.b : No such file or directory > > and other times: > > Error in archive format. > > I tried a lot of things but I soved the problem changing the hard disk. > In order to be sure of that I used the "badblocks" command with the options > "-sw" > over the partition where I was instaling the Linux and it found a lot of > badblocks. Howdy.thanks for the comeback on this! :-) My harddrives fine (touch wood! ).seems I can't even boot from the floppy that the rescue disk makes during the install. :( Oh well, will keep plugging away at it.I also tried installing FreeBDS's install disk but it would also hang until I found out I had to disable npx0now if I could only get the ruddy term program to work (seems a major point of contention with newbies). Thanks again for your response and will ttyl.:-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Newbie going crazy........
Howdy all...:-) Picked up the following files: 9-18-97 2:24p 1474560 42 base14-1.bin 9-18-97 2:28p 1474560 42 base14-2.bin 9-18-97 2:27p 1474560 42 base14-3.bin 9-18-97 2:23p 1299456 42 base14-4.bin 9-18-97 12:05p 1474560 42 drv1440.bin 9-18-97 11:14a 50556 0 install.txt 9-18-97 1:08p 17863 42 rawrite2.exe 9-18-97 12:10p 1474560 42 resc1440.bin Followed the directions layed out in install.txt to make the boot, rescue, base, and driver floppies using rawrite2.exe. Didn't appear to be any problems involved with generating the floppies. Have run through the install proceedure three times now, ending up with the same problem(s) each time: The following error message is generated when the installation program is setting up Debian so that it can be booted from the harddrive: sbin/dinstall: /target/sbin/lilo: not found When exiting the installation program upon completing the setup, the setup program asks if the user wants the system rebooted.when I answer yes, all that happens is a couple of lines of text stating "Closing x files" etc. The reboot does not take place..the computer is just left hanging there displaying those lines of text. When I try using the boot floppy disk (NOT the rescue disk), the boot appears to proceed correctly but again I am left with a hung screen.the driver text info is displayed as it's being loaded but then I can proceed no further. (Keyboard is functional as I can still type but commands are not being processed.) Any thoughts on why these things are occuring would be greatly appreciated..thanks! :-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Newbie going crazy........
Howdy all...:-) Picked up the following files: 9-18-97 2:24p 1474560 42 base14-1.bin 9-18-97 2:28p 1474560 42 base14-2.bin 9-18-97 2:27p 1474560 42 base14-3.bin 9-18-97 2:23p 1299456 42 base14-4.bin 9-18-97 12:05p 1474560 42 drv1440.bin 9-18-97 11:14a 50556 0 install.txt 9-18-97 1:08p 17863 42 rawrite2.exe 9-18-97 12:10p 1474560 42 resc1440.bin Followed the directions layed out in install.txt to make the boot, rescue, base, and driver floppies using rawrite2.exe. Didn't appear to be any problems involved with generating the floppies. Have run through the install proceedure three times now, ending up with the same problem(s) each time: The following error message is generated when the installation program is setting up Debian so that it can be booted from the harddrive: sbin/dinstall: /target/sbin/lilo: not found When exiting the installation program upon completing the setup, the setup program asks if the user wants the system rebooted.when I answer yes, all that happens is a couple of lines of text stating "Closing x files" etc. The reboot does not take place..the computer is just left hanging there displaying those lines of text. When I try using the boot floppy disk (NOT the rescue disk), the boot appears to proceed correctly but again I am left with a hung screen.the driver text info is displayed as it's being loaded but then I can proceed no further. (Keyboard is functional as I can still type but commands are not being processed.) Any thoughts on why these things are occuring would be greatly appreciated..thanks! :-) "It's A Magical World, Hobbes, Ol' Buddy... ...Let's Go Exploring !" -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
