Ragnar,
I've purposely kept the lts.conf file small, because it has to be read
serveral times by the client, and that read is taking place across
NFS. So, although a complete lts.conf file might me really nice
for an example, I'd rather that not be read by the client. Also,
there is already a lt
Russ,
This is the 'alpha' version of the source code.
It's no where near ready to consider rpms and other packaging
formats.
Lets at least get it to the point where it is ready for
beta releases, when we have the features and methods all
worked out. Then, we'll think about rpms.
Jim.
On Sat,
John,
With XFree86 4.2.99, they've moved a few libraries around, from
where we expect to find them. So, you need to rebuild
the ld.so.cache file. Luckily, it's easy.
on the server, just do this:
ldconfig -r /opt/ltsp/i386
Then, reboot the client and enjoy.
Jim McQuillan
[EMAIL PROTECTED]
Hi guys. LTSP, Etherboot and Rom-o-Matic mentioned in an article in the Nov
2002 issue of Linux Journal
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.n
I installed the new ltsp_x_core-3.0.3 rpm in order to obtain the Jammin
125 driver, but my workstations stopped producing UK keyboard inputs
(Pound sign is now #, double-quote is @, etc.)
Any ideas what changed?
My ltsp.conf entries haven't changed, and the UK keyboard works properly
on the serve
I use openoffice but it should be the same. I install to /opt as root
with -net switch and then my students enter the following:
cd /opt/OpenOffice.org1.0
./setup
and the local setup program runs. Any help?
garry saddington
---
This sf.net
> Does anyone know what "magic file" StarOffice is looking for in the user
> home directory that indicates it's been successfully installed?
*** I think you are looking for the file .sversionrc
Take a look at the contents of that file. It's easy to reconstruct.
On 2 Nov 2002, Tom Lisjac wrot
A reply to a question on Star Office I gave last month regarding th escript
files we wrote to initialise open office for each of our users when it is
run, might have useful clues for you. The message is in the list archive at:
http://sourceforge.net/mailarchive/forum.php?thread_id=1158453&forum
Russ,
you are right about the theoretical impossibility of fully
securing the ltsp installations. That said, encrypting the X traffic, in
particular the login process, is of great value, because it hinders the
casual and/or unsophisticated attacker.
I am beginning to see that there
We're having a strange problem trying to get StarOffice 6.0 and
LTSP working with NT authentication. We install (with the -net
option) and setup SO6 as root. We can also login with gdm and
a local account and run SO6 without any problems. When we log
in with gdm via the domain, however, we have th
> I want to allow workstations (clients) to use Star
> Office suite but are unsure on the installation type
>(single, network or user) and where to install to
?/root/staroffice folder (default) or /home/staroffice
> folder or /homes/user folder.
StarOffice 6.0 installs in /opt/staroffice6.0 by d
Title: :::¶óº§ Àü¹® ȸ»ç ¿ÀÇǽºÇÁ¶óÀÚ:::
I am using redhat 8.0 with 2.4.18-17.8.0 kernel and 2.4.19 ltsp-kernel.
I have insert into /opt/ltsp/i386/bin the file /bin/loadkeys of kernel
2.4.18-17.8.0.
Remapping the keyboard in the rc.local file with the command 'loadkeys
it' appear this error:
"/bin/loadkeys:/lib/libc.so.6 version 'GLIBC_2.
13 matches
Mail list logo
