Re: [Ltsp-discuss] How to eliminate "mouse droppings"?

2005-12-09 Thread Cristi Mitrana
On 12/8/05, Tom Griffing <[EMAIL PROTECTED]> wrote: > Hello; > > I am using a new thin client with the following specs: > > *Processor and System Chipset:* > > · AMD GX2-466 333Mhz processor > > · Front side bus 33/66 Mhz > > · AMD CS5535 chipset [..] try the SWCursor and HWCursor

Re: [Ltsp-discuss] Problems with PXE-kernel without initrd

2005-12-09 Thread Cristi Mitrana
On 12/5/05, qeldroma <[EMAIL PROTECTED]> wrote: > Hello, > > i have a kernel-image, that works perfectly with NBI-tag as bootrom-enabled > kernel via tftp. > > Now i need to implement some PXE-clients. So i changed dhcp slightly to fit > this need and it works, the kernel boots. > > Unfortunately,

[Ltsp-discuss] Can someone please send me a PXE-kernel+initrd?

2005-12-09 Thread qeldroma
Hi all, i need to setup a pxe-bootable client on my ltsp with bootroms. I am so far that the kernel is booting, but i always get a kernel panic because he can't find the root. I have not much time in the moment, so i would be very glad, if someone could send me this two files and the "append"-l

Re: [Ltsp-discuss] DHCP don't start on 172.16.XX.YY network

2005-12-09 Thread Jim McQuillan
Denis, Look and see if you have a /etc/ltsp/dhcpd.conf file. That is used by Ubuntu's implementation of LTSP. Jim McQuillan [EMAIL PROTECTED] DenisG wrote: Hi all I'm trying to configure a LTSP server (Ubuntu 5.10) on a 172.16.XX.YY network, but dhcpd refuses to start. Here's my config, I

[Ltsp-discuss] DHCP don't start on 172.16.XX.YY network

2005-12-09 Thread DenisG
Hi all I'm trying to configure a LTSP server (Ubuntu 5.10) on a 172.16.XX.YY network, but dhcpd refuses to start. Here's my config, I don't understand what's wrong. #cat /var/log/syslog ... Dec 9 13:35:54 ltsp dhcpd: No subnet declaration for eth0 (172.16.122.10). Dec 9 13:35:54 ltsp dhcpd:

RE: [Ltsp-discuss] automount cleanup?

2005-12-09 Thread David Heinzerling
We won’t be implementing the system until January, and I think that the new version of LSTP should be out by then, which sounds like it will solve most problems associated with local drive access.  Thus, you can ignore this post…   -David   From: [EMAIL PROTECTED] [mailto:[EMAIL

Re: [Ltsp-discuss] pipe skips lines longer than 80 characters

2005-12-09 Thread Klaus-Peter Niedermann
[EMAIL PROTECTED] schrieb: I dont know if this will help but with ldapsearch i only get 76 characters..apparently in a n attempt to support earlier monitors..with ldasearch i pipe the output through this perl command..chuck `slapcat|perl -p0e 's.\n ..g'|grep "dn: cn=$group"` Thanks, but no. No

Re: [Ltsp-discuss] pipe skips lines longer than 80 characters

2005-12-09 Thread Klaus-Peter Niedermann
Jim McQuillan schrieb: When you run the output of ps to the screen, ps can figure out how wide your screen is, and use all of the available width. When you send the output through a pipe, ps doesn't even bother checking, and assumes a width of 80 characters. So, if you want to see more, you

Re: [Ltsp-discuss] local scanner

2005-12-09 Thread Peter Ehrenberg
brouwers roland lx <[EMAIL PROTECTED]> writes: > I need to install a scanner on a pxe-workstation xsane works on the > server, but how do I install this as a local application. [...] There is no mandatory need to run xsane as a local application. The xsane on your server is able to access your s