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

Re: [K12OSN] Trouble with PXE Boot; Fedora 17



Burke,

Right now I'm outside the LTSP realm; my attempt with the latter failed, so I tried what Gianluca suggested and just tried the basic steps of setting up a pxe boot (I don't think I've done any client building, per se).  I would have really preferred to use something like LTSP but unfortunately it doesn't support fedora 17 (the client side stops at fedora 14, which is an unacceptable option for me).

So, right now I have a 32-bit thin/zero client and a x86-64 F17 OS installation on my workstation. The 32-bit version of F17 is unfortunately not acceptable for what I do (and use), so I can't change the ecosystem of my workstation. The only real solution for me is something that would allow me to connect my 32-bit zero client to my 64-bit OS, but I don't know if/how it's possible (perhaps some sort of a compatibility software or something).

Any hope of getting LTSP for F17?

Thanks

adrin

On Jan 29, 2013, at 5:27 PM, Burke Almquist wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> On Jan 29, 2013, at 6:57 PM, Adrin Gharakhani wrote:
> 
>> Thank you Gianluca,
>> 
>> I followed your instructions (similar to the instructions on the fedora site), and I was initially unable to read the initrd.img file. After a long set of experiments I finally found out that the read permissions were not set properly for the default initrd.img. So, heads up to others who might encounter a similar problem: change the read permission to allow all to read.
>> 
>> So, finally, I passed the "golden gate", but now I have a hardware incompatibility problem. I don't know if I should continue this thread or create a new one. I'll continue, for now:
>> 
>> I'm getting a message that my zero client is unable to boot because "This kernel requires an x86-64 CPU, but only detected an i686 CPU"
>> 
>> My workstation is x86-64 and apparently the new zero client that I bought is i686. Any suggestions how to go about correcting this problem? (does fedora 17 provide i686 compatibility?)
>> 
>> I have to add that my sole interest is to move my workstation to another building (on the same LAN), but I want my zero client set up such that I'm "in front of the workstation", with _full_ access to all capabilities of the x86-64 kernel (there is only myself; this is not a multi-client environment)
>> 
>> Thanks all for your help and suggestions
> 
> You built a 64 bit environment for the clients too, which is almost never what you want to do. Make sure you set the chroot to 32 bit when you start building your clients.
> https://fedorahosted.org/k12linux/wiki/Tips
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> 
> iEYEARECAAYFAlEIduQACgkQxWV7OPa/g5F5QQCfbg1ag2/xpIwmke8zVUggEO3g
> SaUAoISyrbRp274vwb+y1nUK6BYmAuGo
> =Wqhf
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 



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