[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Test NBD Root?



On Aug 13, 2011, at 5:29 PM, David Hopkins wrote:

> On Sat, Aug 13, 2011 at 11:58 AM, Burke Almquist <burke thealmquists net> wrote:
>> 
>> On Aug 12, 2011, at 3:24 PM, Dean Jones wrote:
>> 
>>> On 8/12/11 12:36 PM, Dean Jones wrote:
>>>> On 8/12/11 11:15 AM, Burke Almquist wrote:
>>>>> 
>>>>> On Aug 12, 2011, at 2:53 AM, Warren Togami Jr. wrote:
>>>>> 
>>>>>> https://fedorahosted.org/k12linux/wiki/NBDRootConfiguration
>>>>>> 
>>>>>> Could someone please test if the NBD Root boot documentation still
>>>>>> works?
>>>>>> 
>>>>>> Warren
>>>>>> 
>>>>> 
>>>>> My Optiplex GX1 (PIII 450 192MB) works out of the box as a client on
>>>>> a fresh install of SL6.1. Even the network setup seemed to work fine
>>>>> for me. When I enable NBD root instead of NFS, it gets to the login
>>>>> screen fine. But when I try to log in, it keeps going back to the
>>>>> login screen again. Does NBD require more memory to work?
>>>> 
>>>> It is working fine for me with a box with 2gigs ram.  I just followed
>>>> the steps I posted yesterday for a base thin client on NFS, then
>>>> followed the NBD page and it is working.
>>>> 
>>>> Maybe it is a mem issue?  But that sounds like it can't mount the user
>>>> home dir or something to me.
>>>> 
>>> 
>>> I retract my statement.
>>> 
>>> I did a clean install (to clear out all the random things i did but didn't take notes about), basic thin client NFS is working fine.
>>> 
>>> Add in the NBD via the instructions on the official page and the results are just as you describe.  Can't login with any valid user,  right back to the login screen.
>>> 
>>> ldminfod is the only log output i can see from an attempted login:
>>> 
>>> Aug 12 13:07:51 hostname123 xinetd[5388]: START: ldminfod pid=5569 from=::ffff:172.31.100.74
>>> Aug 12 13:07:51 hostname123 xinetd[5388]: EXIT: ldminfod status=0 pid=5569 duration=0(sec)
>>> Aug 12 13:07:51 hostname123 xinetd[5388]: START: ldminfod pid=5572 from=::ffff:172.31.100.74
>>> Aug 12 13:07:51 hostname123 xinetd[5388]: EXIT: ldminfod status=0 pid=5572 duration=0(sec)
>>> 
>>> It tries twice?
>>> 
>>> It also doesn't boot right to the GUI login, but instead to the message console, and ALT-F7 jumps to the GUI.
>>> 
>>> The rootfs looks to be mounted:
>>> Aug 12 13:16:33 hostname123 xinetd[5801]: START: nbdrootd pid=5822 from=::ffff:172.31.100.74
>>> Aug 12 13:16:33 hostname123 nbd-server: connect from 172.31.100.74, assigned file is /opt/ltsp/images/i386.img
>>> Aug 12 13:16:33 hostname123 nbd-server: Size of exported file/device is 232845312
>> 
>> 
>> If your client with 2GB RAM isn't working, then it's probably not because it needs more memory.
>> 
> Does the client boot if you set metacity as the default/mandatory
> window manager instead of compiz?
> 
> I think the command is: gconftool-2 --direct --configure-source
> xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set
> /desktop/gnome/session/required_components/windowmanager metacity
> 
> Sincerely,
> Dave Hopkins


If that's the case though, why does it log in ok using NFS?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]