Rare project developers

[mc36 <>]

hi,

> > that's why the ttyLin should be an external process to guarantee that it 
> > runs...
> > then freerouter's side, it opens the lines (interfaces, etc) right after it
> > parsed the -hw.txt and then it immediately sends out something, including
> > all the boot defailts so i'm pretty sure it's the best we can do....
> > let me show you how my freerouter only images boot....
> > the syslinux commands are here: http://sources.freertr.net/misc/image/boot.cfg
> > then i use this as init: http://sources.freertr.net/misc/image/init.sys
> > that's how i bring up udev: http://sources.freertr.net/misc/image/init.dev
> > and finally the freerouter startup: 
> > http://sources.freertr.net/misc/image/init.jvm
>
> I don't want to go that far, at least not without consensus in the
> group. This would be a fairly drastic change from the current design
> where we essentially have a standard Debian system with RARE
> implemented as a systemd service. How hard we want to try to hide the
> system from the user is an open question, I think. My personal opinion
> is that we should not try too hard, as long as the user understands
> how to move between the system and freerouter.

my opinion on the topic, that if you close the box enough that the user 
hardly can reach linux
then there is less chance to brick it... and finally if one tries hard enough 
then one can always
do add grub option init=/bin/bash and then should be smart enough to 
recover... :)
regards,
cs