[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Various strange problems - lilo, wdm, vi - you name it, i've got it.



Ok. Many strange problems are assailing me. any help is appriciated. all
systems are running slink with the latest packages.

LILO:
I have a system that is _suppossed_ to dualboot dos & Linux. Linux is on
the first drive on the first controller. DOS is on the second drive on
the first controller. LILO is setup to boot the DOS drive like so:

other=/dev/hdb1
label=dos
table=/dev/hdb

-but it dosen't work. I get a 'non-system disk or disk error' when I try
to boot it. The drive is bootable and working, because dosemu will work
fine using it with partition access, and when I set it as the master it
booted fine. I've tried many things, to no avail. I have set up several
dualboots almost exactly this, and never run into any problems. Please
someone tell me what is wrong.


wdm:
on one system I have wdm (NeXTStep-alike xdm replacement) on, it does
not work using XDMCP. I start an X server on my workstation like this:
``X :1 -query pyros'' and the X server starts, gets a black background,
and dies. wdm works fine on a different system I put it on. The
irritating thing is that pyros is a fresh install.

vi:
Is there any way to make nvi use the home/end keys properly? They don't
seem to have any effect. Also, whenever I move to the very first
character in a line with the arrow keys, I get dropped out of insert
mode and into command mode. Very irritating when you are commenting out
a bunch of lines in /etc/inetd.conf, for example.

A cc to my reply address would be good, since I'm not subscribed.

Thanks in advance.


-- 
 ______________________________________________________________
| ian eure, network admin, freelance security consultant, and  |
| manically depressed paranoid schizophrenic, at your service. |
;           <ieure@minion.org> - http://minion.org             ;
:           raw speed = 105.6 wpm with 4.5% errors             :
.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .


Reply to: