Hi!
I also faced this issue a few months ago, with no 'smart' solution
involving NFS. However, CODA might do the trick, if you can afford the
quite large disk and cpu requirements it requires on the server. Oh, and
last time I tried I have had a tough time configuring it properly, so you
Hi!
I also faced this issue a few months ago, with no 'smart' solution
involving NFS. However, CODA might do the trick, if you can afford the
quite large disk and cpu requirements it requires on the server. Oh, and
last time I tried I have had a tough time configuring it properly, so you
Hi,
> You might want to experiment with running things that are usually cron jobs
> as at jobs then, e.g. logrotate etc. Alternatively running them out of startup
> if you for some reason reboot occasionally.
This is an interesting idea, I'll have a look at it...
> There's a flavor of cron called
> Mobile-update won't work on kernels 2.2.11 and above, as the
> sys_bdflush call will make it do_exit(0) on first call. And
> noflushd _requires_ 2.2.11 or above, so noflushd and mobile-update
> will be mutually exclusive.
>
> Also, I didn't set the noatime option for mount and this all still
Hi,
I own a TP310 with Slink and some updates installed on it. It only
has 16Mb RAM, so disk buffers aren't large and I cannot disable swap
space. However, I (eventually) got it to let its hard disk alone,
thus allowing it to spin it down.
Here is what I did:
> * set noatime on fi
Since the debian bootdisks are SYSLINUX disks, just mount them (MSDOS
FAT12 filesystem), take the kernel out of the tecra bootdisk and copy it
over the kernel in the lowmem bootdisk.
This is how a friend of mine which installed 2.0 did on his tp700.
Regards
raph
> On Fri, 19 May 2000, A.C. Alme
> hi
>
> I've installed xfree ver 3.3.6-6, still having problems though. Have
> included the output from running 'startx' (thorough "startx &> startxout").
>
> Would be grateful for any assistance ...
>
> XFree86 Version 3.3.6 / X Window System
> (protocol Version 11, revision 0, vendor release
found, but display modes could not be resolved. ***
>
> Fatal server error:
> no screens found
>
> any ideas? tks
>
> Andrew
>
>
> -Original Message-
> From: Elrond [mailto:[EMAIL PROTECTED]
> Sent: Sunday, May 07, 2000 2:45 AM
> To: Andrew McRobert
&g
Hi,
Have a look at the attached XF86Config. Read the comments, and try
it once you got XF86 3.3.6 (no proper Savage support before). Be very
careful with HorizSync and VertRefresh in your Monitor section.
If the first try gives you a garbled screen (or blinking, or
such), first of
Hi,
I(m using a T2000Sx Toshiba notebook with a 386SX-25 and
a monochrome VGA board inside. There is no hard disk, but I have an
expansion memory card (8Mb) plugged in and a parallel ZIP drive with
Debian 1.2 installed on a disk (I boot the kernel from a floppy, and
then the kernel mounts
Hi,
It is a well-known fact that with 2.0.x kernels and more than
64Mb of RAM you have to add the "mem=XXX" parameter to the kernel when
booting (check lilo.conf). If you are using bare slink, you should do it.
If you are using a 2.2 kernel, then it's strange. "mem=XXX" never hurts,
though
Hi,
For the extra keys on a keyboard, if they are reported as exotic
keycodes, you can make them recognized by the kernel with the
"setkeycodes" command and then assign them new tasks with "loadkeys". See
the man pages for further info (I have a Multimedia Trust keyboard with my
desktop, th
12 matches
Mail list logo