uilt for the xp workstations, or it defaults to just chain booting
to the hard disk, in which case xp loads.
Chain booting has been available in grub for a long time. Rolling it
into syslinux is relatively new, and that's a pretty powerful feature.
On 3/9/07, Asmo Koskinen <[EMAIL PROTECTED]&
I'm not sure I see what use it would really be. It seems to just be a
real mode dos implementation of the grub configuration and loader. I
can see a use for it if you're running in a multiboot environment
(linux, windows, dos) but I don't see it having much to do with ltsp.
If someone's a teache
There's no alternative? Perhaps dropping the resolution in order to
get to 16-bit or deeper color depth?
I think if I were doing it, I'd want depth over resolution, but that's
just me. I'm just remembering all of the nightmares of the early
1990s when we had to install colormaps for those applic
Add:
next-server 192.168.1.9
to the global section of your dhcpd.conf file. This is assuming
you're using version 3.0.3 or later of the isc dhcp server. They made
some changes to the server a while back that doesn't automatically set
the tftp server to be the same as the dhcp server. Etherboot
Sounds like the video card on the 616 isn't fully compatible with
whatever X driver you've got installed. Is it using the SVGA driver?
It might help to know what video card is actually embedded in those
systems. I've also seen graphic cards with low memory available do
things like this. Do you k
I just read some specs for that class of thin clients from NeoWare
(the Capio 600 series). You're going to be very lucky to do anything
with LTSP on those boxes. It doesn't look like they'll PXE boot, they
have very little memory, and they use a compact flash for the little
storage they have (32M
when it can't determine the geometry for the drive. That's why you
continue to get that clicking noise (the attempted head probe) even when
the drive is dead.
Dave Fenwick
On Fri, 19 Jan 2007 17:21:22 +0900, "Tomoki Taniguchi"
<[EMAIL PROTECTED]> said:
> I have a 2 y
GDM already handles this on my Fedora Core 3 implementation. If I'm
logged in and try to log in from another workstation it tells me I'm
logged in and puts up a confirmation dialog box. You might want to look
and see how GDM provides this service.
Karl Huysmans said:
> Hi all,
>
> I am new to LT
lient should be stored anywhere but in a ramdisk.
> -Original Message-
> From: Mohsen Pahlevanzadeh [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 05, 2005 7:34 AM
> To: Dave Fenwick
> Cc: [EMAIL PROTECTED]; ltsp-discuss@lists.sourceforge.net
> Subject: Re: [Ltsp-discuss] How
LTSP, DietPC, ThinStation, Damned Small Linux (DSL), and a variety of
other distributions are all similar implementations of the thin client
concept. I've tried the majority of them with my thin clients. While
none of them (including LTSP) is exactly what I need in my environment,
LTSP comes clos
Log out using the standard X logout from whatever X environment you're
running (Gnome, KDE, whatever). Then press the power button on your
client. Your client's being on has absolutely nothing to do with your
server being on.
Mohsen Pahlevanzadeh said:
> Dears,
> How can turn off my client that
s GDM running on the server?
2) Do you a firewall enabled on the server?
3) If a firewall is enabled, are you allowing inbound port 177 requests and
outbound port 6000 activity from the server?
---
Dave Fenwick
> > Op dinsdag 15 maart 2005 18:52, schreef Søren Haagerup:
&g
The problem is kernel header files are intentionally tainted for userspace
builds now. The interim fix (while someone figures out a better process) is
to get:
http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
Get the one closest to your 2.6.x kernel. Untar it to
/lib/modules/`uname -r`/buil
13 matches
Mail list logo
