From: ralph stickley <ralph@datalux.com>
To: "Tkatchouk, Pavel" <PTkatchouk@squirrelsystems.com>
Cc: "'linux-embedded@waste.org'" <linux-embedded@waste.org>,
MTD <mtd@imladris.mvhi.com>, Oron Ogdan <Orono@m-sys.com>
Subject: Re: Anyone embedding RH 6.1 / 2.2.12 ?
Date: Wed, 08 Dec 1999 17:08:40 -0500 [thread overview]
Message-ID: <384ED6E8.59F54440@datalux.com> (raw)
In-Reply-To: 9182AA6C8DACD311A8D70006294EF76808D3C1@exchange-yvr.squirrelsystems.com
Yeah! M-Systems updated their linux drivers - seems like they
only changed their patch file for V2.2.0...
Boo ! - they still don't have a file listing for V2.2.0 :-(
>I was wondering if anyone has sucessfully "embedded" the 2.2.12 kernel
>from the RedHat 6.1 distro...
>2.0.36 worked fine but I am required to do an upgrade and there seems to
>be quite a few differences.
>I am looking for a list of files that will allow the system to boot
>(from M-Systems DOC) and run Fvwm2 (or similiar). Also, a minimum
>kernel .config file would be useful :-)
>Currently, I can boot to the M-Systems chip as single user . With a
>normal boot, the login prompt shows but does not allow anyone, even
>root, to login (I've copied the passwd, shadow, tons of library files
>and pam.d stuff, but still no luck).
>Our system is as follows:
>Media GX 233
>Touchscreen
>32MB ram
>AMI BIOS
>LCD panel
>M-Systems DOC 2000 - 16MB
>Any pointers or suggestions would be appreciated !
>Thanks,
>Ralph Stickley
>Datalux, Corp.
"Tkatchouk, Pavel" wrote:
> Unlikely your case, but here it goes...
> When I moved my diskless from libc to glibc login all of a sudden
> stopped to let anyone in. The problem appeared to be missing
> /lib/libnss_files.so.1,libnss_files.so.2,libnss_dns.so.2,
> libnss_nis.so.2,libresolv.so.2,libnsl.so.1 (not reported by ldd)
> and /etc/nsswitch.conf.
>
Seems like these libraries are required for passwd, maybe some of
the pam stuff...I copied these too..still no luck
I'd like to turn the pam stuff off anyhow...not sure how yet...
Is nsswitch.conf used during the login ?? Hmmmmm....
>
> Also, perhaps the following extract from my "Diskless-from-NT-mini-howto"
> (can be found in www.slug.org.au/etherboot distribution
> under name NT-Diskless-Terminal.txt) may be helpful in determining files
> required:
>
> "Pruning standard distribution (RedHat, Debian, etc.) to your needs might be
> very time
> consuming. To ease that painful process I have used remotely booted diskless
> client with
> NFS-Root (see Etherboot's Readme, NFS-Root and NFS-Root-Client mini-HOWTO's,
> Diskless-
> HOWTO):
>
If you have done this, do you have a directory listing available ? :-)
I have not used NFS stuff yet...not sure if I'll be able to figure this one
out.
> <snip>
> Regards,
>
> Pavel Tkatchouk
>
Thanks,
Ralph
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next parent reply other threads:[~1999-12-08 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9182AA6C8DACD311A8D70006294EF76808D3C1@exchange-yvr.squirrelsystems.com>
1999-12-08 22:08 ` ralph stickley [this message]
1999-12-13 15:01 ` Anyone embedding RH 6.1 / 2.2.12 ? Adi Linden
1999-12-14 20:14 ` ralph stickley
1999-12-15 0:07 ` Adi Linden
1999-12-15 14:54 ` ralph stickley
1999-12-15 16:27 ` Adi Linden
1999-12-15 21:16 ` ralph stickley
1999-12-20 15:14 ` Adi Linden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=384ED6E8.59F54440@datalux.com \
--to=ralph@datalux.com \
--cc=Orono@m-sys.com \
--cc=PTkatchouk@squirrelsystems.com \
--cc=linux-embedded@waste.org \
--cc=mtd@imladris.mvhi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox