<br><br><div class="gmail_quote">On Mon, Oct 10, 2011 at 10:54 AM, Andrew Bradford <span dir="ltr"><<a href="mailto:bradfa@gmail.com">bradfa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Mon, Oct 10, 2011 at 10:40 AM, Lance Jump <<a href="mailto:lancej29@gmail.com">lancej29@gmail.com</a>> wrote:<br>
> /dev/ttyS0 is the USB/serial console. It is my only console connection to<br>
> either u-boot or Linux and all of the output appears to go there. It is<br>
> also the "console=" in the Linux command line. When I execute something<br>
> (inittab) other than getty (e.g. ls) the output goes there. When I do getty<br>
> in inittab, it does put out a message saying that root logged in on<br>
> /dev/ttyS0. Is it still possible that this connection is actually not<br>
> /dev/ttyS0? How would I check and/or correct? If it is not /dev/ttyS0,<br>
> what might it be?<br>
<br>
</div><div class="im">>> Can you provide the entire boot output including uboot output data?<br>
>> <a href="http://pastebin.cross-lfs.org/" target="_blank">http://pastebin.cross-lfs.org/</a><br>
> Done.<br>
<br>
</div>For those not searching, direct link here:<br>
<a href="http://pastebin.cross-lfs.org/230524" target="_blank">http://pastebin.cross-lfs.org/230524</a><br>
<div class="im"><br>
> I wanted to "lock down" a repeatable configuration with a specific<br>
> distribution. As I recall, LFS-Live was actually recommended in one of the<br>
> CLFS books (maybe this one). The chroot also allows me ensure that nothing<br>
> "gets outside" the environment and to very easily "snapshot" places in the<br>
> development or start over completely without having to worry about any<br>
> lasting side effects on my main system.<br>
<br>
</div>Understandable. The LFS live CD should work well for building but<br>
I've not personally tried it.<br>
If you follow the embedded book exactly for creating the user account<br>
to build an embedded system, nothing will leak into your build from<br>
the host.<br></blockquote><div><br>Yes, it is well thought out in that respect. The problem is the "follow it exactly" part. Experience has shown me that I make enough mistakes to want a safety net.<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
How do you snapshot builds? I'm curious as I've not found an easy way<br>
that works well.<br></blockquote><div><br>The "snaphot" to which I refer is basically being able to build up to a certain point and start over from there if I make a mistake later in the process. I have everything from the book scripted so I can exactly reproduce my steps. At the end of a script (typically a chapter) I will archive the result as a "snapshot" of the build to that point. I used to do this with a virtual machine (I bought VMware workstation for the multiple snapshot capability). But what I do now is simply tar my chroot environment. To go back, I delete the current chroot tree and untar an old one.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> The bootscripts appear to be in /etc/rc.d/init.d and related. This agrees<br>
> with inittab. The startup script does have code in it to perform the mounts,<br>
> but it is looking like it never executes. I have echo messages in it both<br>
> to the console and to a file in /var/log and I never see anything.<br>
<br>
</div>Based on your pastebin, your bootscirpts aren't executing. There<br>
should be some nice "OK" messages printed out for things like doing<br>
the mounts, bringing up networking, and starting services. Your<br>
output doesn't appear to have any of that.<br>
<br>
Example:<br>
init started: BusyBox v1.17.3 (2011-02-27 14:07:01 EST)<br>
Starting mdev: OK<br>
Mounting devpts: OK<br>
Starting fsck for local filesystems.<br>
Checking local filesystems: OK<br>
Enabling swap space: OK<br>
Remounting root rw: OK<br>
Setting hostname: OK<br>
Cleaning up system: OK<br>
Setting up interface lo: OK<br>
Running start scripts.<br>
Starting syslogd: OK<br>
Starting klogd: OK<br>
<br>
I think that's part of your problem but possibly not the entire problem.<br></blockquote><div><br>I agree that scripts are not running. My earlier experiments of putting messages (including echoing to files) appears to confirm this. I seem to be able to run various things by replacing sysinit and TTY entries in inittab. So inittab is being read and busybox runs as do various applets. But it seems that sh (or ash or whatever) itself will not actually run so no shell scripts (e.g. startup) can run.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5">-Andrew<br>
_______________________________________________<br>
Clfs-support mailing list<br>
<a href="mailto:Clfs-support@lists.cross-lfs.org">Clfs-support@lists.cross-lfs.org</a><br>
<a href="http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org" target="_blank">http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org</a><br>
</div></div></blockquote></div><br>