| 1 |
On Mon, 2013-12-09 at 20:33 -0500, Rich Freeman wrote: |
| 2 |
> On Mon, Dec 9, 2013 at 2:56 PM, Rick "Zero_Chaos" Farina |
| 3 |
> <zerochaos@g.o> wrote: |
| 4 |
> > I really don't like the idea of having no networking in the stage3 by |
| 5 |
> > default, however, I'm becoming more open minded on what qualifies as |
| 6 |
> > networking. What I'm wrestling with is this, what if I want to slap a |
| 7 |
> > stage3 on a device and then access it from the network? |
| 8 |
> |
| 9 |
> Hit your head on the wall because it doesn't contain a kernel? |
| 10 |
> Stage3s in general aren't functional systems. |
| 11 |
|
| 12 |
You're thinking with your x86/amd64 hat on here. An ARM device can be |
| 13 |
booted with the kernel over networking (or even via usb, as is the case |
| 14 |
with most Android devices) and rootfs on local storage. Just because |
| 15 |
x86/amd64 doesn't do it, doesn't mean others can't/don't. |
| 16 |
|
| 17 |
What exactly is missing from a stage3 aside from a kernel? At this |
| 18 |
point on most ARM devices, it goes like this: |
| 19 |
|
| 20 |
extract stage3 |
| 21 |
edit inittab (and if needed) securetty |
| 22 |
create net.eth0 & symlink it to the default runlevel, along with |
| 23 |
openssh(assuming headless system) |
| 24 |
copy your kernel & modules into their proper places (if needed) |
| 25 |
put sdcard into arm device, watch it magically boot and work |
| 26 |
|
| 27 |
What you're proposing is: |
| 28 |
extract stage3 |
| 29 |
install qemu (assuming you don't have it yet) |
| 30 |
mount dev/proc |
| 31 |
chroot |
| 32 |
emerge a-network-manager |
| 33 |
<go get coffee, have a beer, make a three course meal> |
| 34 |
set password (might as well, since you're chrooted) |
| 35 |
vim inittab <oh wait, no vim, right, gotta run nano> |
| 36 |
nano inittab (and if needed) securetty |
| 37 |
exit chroot |
| 38 |
unmount dev/proc |
| 39 |
copy kernel & momdules to their proper places |
| 40 |
put sdcard into arm device, watch it magically boot and work |
| 41 |
|
| 42 |
Why exactly is the latter one better? the emerge a-network-manager step |
| 43 |
would be far faster on the device itself, even the RPi. |
| 44 |
|
| 45 |
I plan to look into the SUSE Qemu fork, as they've supposedly sped it up |
| 46 |
immensely (iirc it takes about a week to build gcc according to armin76 |
| 47 |
for aarch64) but even then, that would be a hack as their patches may or |
| 48 |
may not have been sent upstream - and they may be aarch64 specific and |
| 49 |
arm could still be slow as balls. |
| 50 |
|
| 51 |
So remember, just because your laptop/desktop can't do awesome stuff, |
| 52 |
doesn't mean other devices can't :) |
Archives