On Thu, 8 Jan 2004, Norman Gaywood wrote:
> On Wed, Jan 07, 2004 at 11:00:07PM -0500, [EMAIL PROTECTED] wrote:
> > You'd need to modify the /linuxrc script in the initrd image to pass
> > the runlevel from the commandline on to the /sbin/init program.
>
> This would be the most elegant way IMHO.
On Wed, Jan 07, 2004 at 11:00:07PM -0500, [EMAIL PROTECTED] wrote:
> You'd need to modify the /linuxrc script in the initrd image to pass
> the runlevel from the commandline on to the /sbin/init program.
This would be the most elegant way IMHO. It would be a small change yet
add considerable flexi
Norman,
You'd need to modify the /linuxrc script in the initrd image to pass
the runlevel from the commandline on to the /sbin/init program.
Or, another method would be to pass an argument on the kernel command
line, maybe something descriptive like 'FIXWIN=Y'.
This would get passed as an envi
I'm using ltsp4.
How do you pass a run level to init when booting a ltsp kernel?
Here is my setup:
1. Workstation uses dhcp and tftp to boot nbgrub.
2. nbgrub provides a menu with choices:
Linux Terminal (ltsp)
windows on local disk
The nbgrub entry for the
I've tried a number of times to get various Windows programs running
under wine, but to be honest I've never got any of them running 100%
successfully and reliably.
On the other hand I can recommend unreservedly the commercial Win4Lin
software from Netraverse, which I use to run Win98 under Linux.
Hi,
IÂd like to use a Barebone with an integrated graphic card from SHUTTLE (SK41G). They
are using an VIA KM266/VT8375 chipset an an "full featured" S3 ProSavge8 AGP
controller. How do I get to use this under LTSP 3 How can I change the default
color depth to 8bpp?
Greetings
Nicolai
--
Matt,
There really isn't an 'upgrade' from ltsp-3 to ltsp-4. You can run
both if you'd like, just install ltsp-4 into a different directory.
THen, point the root-path to that new directory for those clients that
you'd like to have using the ltsp-4 directory.
For simplicity, I'd look at renaming
Jim,
Thanks for your reply.
First of all you won the bet. I have been following a 'howto' for the ICA
client integration and in there it suggests to copy /usr/X11R6/bin/xinit
from the Linux server to /opt/ltsp/i386/usr/X11R6/bin/xinit. So, what you
said makes complete sense. From what I have rea
Matt,
You've got 2 problems.
1) cannot write to remote file handle. This indicates that syslogd
on your server hasn't been configured to accept remote connections.
You just need to configure it for that. Look at
/etc/rc.d/init.d/syslogd and see how to add a '-r' to the syslogd
I'm using RH 9, LTSP 3.0 and integrating the ICA client for Linux. When
booting the workstation it gets as far as starting syslogd then gives:
Cannot write to remote file handle on 10.0.10.56:514. Also, right after
this is it gives: /usr/X11R6/bin/xinit: /lib/libc.so.6: version 'GLIBC_2.3'
not fo
Am Mittwoch, 7. Januar 2004 07:40 schrieb Novita:
> Does anybody ever experienced implementing wine on ltsp ?
> BTW, I try to run Tally, an Indian accounting program in wine and
> it has dongle protection
> to make it run
Wine is in my opinion only good for small windows applications like
"ms-pa
> >
> > I did try to run ltsp a thin client from compaq last
> summer. Succeded
> > to get it to boot up the ltsp-kernel, but didn't get any
> GUI. I didn't
> > knew what kind of gra
>
> Kim,
> Do you recall what model the compaq was?
>
> Scott
Sure, I tried out a Compaq T20.
//kim
--
Hello All,
I've been using LTSP for couple months, with some users running Openoffice.
Now, I'm ready to migrate all my Windows NT clients to ltsp.
But I have some problems because the clients still needs to run some Windows
applications.
Then I try to use wine as the solution. But after building f
13 matches
Mail list logo
