<div dir="ltr">Ah, you rock! I'll have to try that out. etoys on the command line already starts eToys successfully, so that part is good to go. Loving it.</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Nov 19, 2013 at 9:45 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ah. The raspi-config script is here:<br>
<br>
<a href="https://github.com/asb/raspi-config/blob/master/raspi-config" target="_blank">https://github.com/asb/raspi-config/blob/master/raspi-config</a><br>
<br>
You could edit that to add a boottoetoys.sh similarly to boottoscratch.sh.<br>
<br>
If you're not that familiar with shell scripting, try replacing "& scratch" with "& etoys" on this line:<br>
<br>
printf "openbox --config-file /home/pi/boottoscratch/openbox_rc.xml & scratch" | xinit /dev/stdin<br>
<br>
and then when you choose "boot to scratch" it should actually boot to Etoys instead.<br>
<br>
Before doing that, make sure that executing "etoys" on a command line actually starts Etoys successfully.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Bert -<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 19.11.2013, at 09:35, Charles Schultz <<a href="mailto:sacrophyte@gmail.com">sacrophyte@gmail.com</a>> wrote:<br>
<br>
> You know more than I do on this topic. :) I do not have an URL for how Scratch boots directly, but I can point you to documentation on the <a href="http://raspberrypi.org" target="_blank">raspberrypi.org</a> website that shows you how to configure it in raspi-config (basically, you select an option - all the details are abstracted away). I have already asked this question on the raspberrypi forums, and I have not yet received a reply:<br>
> <a href="http://www.raspberrypi.org/phpBB3/viewtopic.php?t=61117" target="_blank">http://www.raspberrypi.org/phpBB3/viewtopic.php?t=61117</a><br>
><br>
> I'll try to dig around with what little Linux knowledge I have and using your hints to see how Scratch is booted.<br>
><br>
><br>
> On Tue, Nov 19, 2013 at 9:28 AM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br>
> On 18.11.2013, at 18:21, Charles Schultz <<a href="mailto:sacrophyte@gmail.com">sacrophyte@gmail.com</a>> wrote:<br>
><br>
> > Just curious, how does one configure the Raspberry Pi to boot directly into eToys just like the new option to boot directly into Scratch?<br>
><br>
> I haven't looked at how Scratch does it (do you have a URL?).<br>
><br>
> But in general the simplest thing would be to just launch Squeak from the linux startup mechanism. When the Linux kernel is finished booting, it runs an executable specified in /etc/inittab. Typically that's "init" which then executes the rc script which in turn launches everything, including the graphical shell. That is where you can hook into - either with an X server (so you would have to make Etoys auto-start when X is run) or without the X server using Squeak's fbdev display driver. The latter would make startup faster, but you would have to benchmark both to know for sure which would be more efficient at runtime.<br>
><br>
> - Bert -<br>
><br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> Charles Schultz<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Charles Schultz
</div>