Hi
> Thank You. Just to be sure you underntand what I want: I want to login as root
> at the diskless machine, not at the server. I don't know what login manager am
> I using. I did the default LTSP install. You mean at the server? I think it is
> Kdm as I use KDE. When I try to su at the diskless
--- Kenneth Godee <[EMAIL PROTECTED]> escreveu:
> First you should know what login manager your using, try
> this from any console window...
> "ps -A" and check out what services you are running
> look for "gdm" or "kdm" or do a
> "ps -A | grep gdm" or "ps -A | grep kdm" and see what's
> running
First you should know what login manager your using, try
this from any console window...
"ps -A" and check out what services you are running
look for "gdm" or "kdm" or do a
"ps -A | grep gdm" or "ps -A | grep kdm" and see what's
running.
Can you "su" at the server? Do you know the root password
f
--- Ken Godee <[EMAIL PROTECTED]> escreveu:
> What login manager are you using?
> Kdm, Gdm..
> If using Gdm (I'm not sure about others) I believe it
> defaults to not allow remote login by "root"
> for security reasons. This can be changed in gdm.conf.
> If not using Gdm, the others may have
and you can set that with gdmsetup as root, not on
ltsp.conf 8)
--- Ken Godee <[EMAIL PROTECTED]> wrote:
> What login manager are you using?
> Kdm, Gdm..
> If using Gdm (I'm not sure about others) I believe
> it
> defaults to not allow remote login by "root"
> for security reasons. This can b
What login manager are you using?
Kdm, Gdm..
If using Gdm (I'm not sure about others) I believe it
defaults to not allow remote login by "root"
for security reasons. This can be changed in gdm.conf.
If not using Gdm, the others may have the same type of
security setting. Many remote programs do
Hi,
This is just to say you I managed to login. Added one line to
/opt/ltsp/i386/etc/lts.conf:
[Default]
SERVER = 192.168.0.2
XSERVER= auto
X_MOUSE_PROTOCOL = "PS/2"
X_MOUSE_DEVICE = "/dev/psaux"
X_MOUSE_RESOLUTION = 400
Hallo Clodoaldo,
am 09.03.2003, 22:39 schriebst Du:
> Hi Anselm,
> Detail: It only works when the user is set to root in /etc/xinetd.d/tftp
Explained by G. Baum probably.
> Here are the good news: I changed the permissions on the kernel file to
> owner-execute and now it works !!! I can ping a
> If this is tftpd-hpa, then change the user to root. This version of tftpd
> will change the effective user id / group id to nobody/nogroup internally
> (unless you specify something else with the -u commandline option).
> If tftpd is started as nobody, then it has no rights to change its group
Hi Anselm,
> You wrote that you could tftp-get the kernel from the server. You used
> "tftp localhost", not "tftp 192.168.0.2", did you? What happens on the
> .0.2 address (or whatever the local ip of the linux server is) when
> downloading back on the linux-server itself?
[EMAIL PROTECTED] cpn]#
Am Sonntag, 9. März 2003 19:30 schrieb Clodoaldo Pinto Neto:
> After the group change I have the same message about user nobody:
> Mar 9 15:18:21 k7s5a in.tftpd[18887]: cannot set groups for user nobody
If this is tftpd-hpa, then change the user to root. This version of tftpd
will change the eff
Hallo Clodoaldo,
am 09.03.2003, 19:30 schriebst Du:
> After the group change I have the same message about user nobody:
> Mar 9 15:18:21 k7s5a in.tftpd[18887]: cannot set groups for user nobody
OK, I do not like it. It most probably is the cause for why tftp does
not (fully?) work.
You wrote th
Anseml,
If it weren't your help I would have already gave up. At least for this
weekend. Thanks again.
> Try additionally specifying something like "group=nogroup" (of course
> that group must exist) in combination with "user=nobody".
I did it:
{
disable = no
socket_type
Hallo Clodoaldo,
am 09.03.2003, 13:46 schriebst Du:
> It happens the same message about the user nobody.
Try additionally specifying something like "group=nogroup" (of course
that group must exist) in combination with "user=nobody". You can find
out if they exist with
grep nogroup /etc/group
gr
Anselm,
Your support is appreciated.
> You could make "user=nobody" instead of "user=tftp". What happens then?
It happens the same message about the user nobody.
> Please post your dhcpd.conf.
ddns-update-style none;
allow booting;
allow bootp;
default-lease-time21600;
Hallo Clodoaldo,
am 09.03.2003, 10:45 schriebst Du:
> Yes they are in a single hub. The adresses are
> 198.162.0.1-2-3 and the mask is 255.255.255.0
Fine.
>> Can you tftp-get the file from the win machine?
> No, I can't tftp-get the file from the win machine.
> The server gives me the same mes
Dragos,
Thank you for your response.
> Yeah, LTS is plain stupid, it won't work (even if I
>spend weeks configuring it).
> You may try to spend a few days reading some
>documentation and then it will be easy to configure
>your server.
> Try not to be upset on Linux systems, they are
smart, >ofte
Anselm,
Thank you again for your reply
> The diskless client and the linux machine are
> connected to the same
> ethernet segment, aren't they (that means, only
> hubs/switches, no
> routers/other computers in between)?
Yes they are in a single hub. The adresses are
198.162.0.1-2-3 and the mask
Hallo Clodoaldo,
am 08.03.2003, 23:18 schriebst Du:
> service tftp
> {
> disable = no
> socket_type = dgram
> protocol= udp
> wait= yes
> user= tftp
> server = /usr
Hello Anselm,
Thank you,
> > What should I do abou the user nobody? This is my
> > \etc\xinetd.d\tftp:
>
> didn't transfer up to me. Check that a user "nobody"
> exists in
> /etc/passwd and that his group exists too.
Sorry, this is my /etc/xinetd.d/tftp:
service tftp
{
disable = no
On Sat, 2003-03-08 at 23:24, Clodoaldo Pinto Neto wrote:
> Hi,
>
> TFTPD is working since I can connect to it using the
> tftp client and get the files in /tftpboot/lts.
> Mar 8 17:09:35 k7s5a in.tftpd[23761]: cannot set
> groups for user nobody
>
> What should I do abou the user nobody? This is
Hallo Clodoaldo,
am 08.03.2003, 22:24 schriebst Du:
> Hi,
> TFTPD is working since I can connect to it using the
> tftp client and get the files in /tftpboot/lts.
> What should I do abou the user nobody? This is my
> \etc\xinetd.d\tftp:
didn't transfer up to me. Check that a user "nobody" exis
Hi,
TFTPD is working since I can connect to it using the
tftp client and get the files in /tftpboot/lts.
The problem is this:
Mar 8 17:09:35 k7s5a dhcpd: DHCPDISCOVER from
00:07:95:fd:44:24 via eth0
Mar 8 17:09:35 k7s5a dhcpd: DHCPOFFER on 192.168.0.3
to 00:07:95:fd:44:24 via eth0
Mar 8 17:09:
23 matches
Mail list logo
