On Sun, May 15, 2016 at 3:44 PM, Super Twang <[email protected]> wrote:

> @Robert
>>
> Thanks for the tip.  Are the '*fs' filesystem packages actually
> functionally complete OS's?   Does your barefs boot the BBB into a state
> into which I can ssh?  In my local network setup, I believe I'd need a dhcp
> client on the ethernet port (I don't control the router).  Oh wait, I could
> probably start with a usb connection and apt-get that, couldn't I?
>

The *fs's listed on eewiki.net are just a generic fs no kernel stuff
installed by default.. It's up to you do that stuff..


>
> I've seen mentions of your various '*fs' (filesystems?), but, although I'm
> a seasoned software developer, I'm new enough at linux system
> administration that I don't fully grasp the various terminology differences
> between the ways that parts/wholes of linux come packaged: Like: 'file
> systems', 'kernels', (the various kernel flavors) and 'images'... I don't
> fully grasp where one starts and the other leaves off.  In other words, I
> wasn't sure if the '*fs' filesystems were overlays of some sort, rather
> than the functionally complete foundations.  I had been working under the
> assumption that the 'images' were the smallest starting point, short of
> getting into my own kernel compilation (by which I'm a little daunted).
>

file system = generic file system  (aka you set eveything up)
images = generic file system with a custom/specific kernel pre-installed
(along with bootloader) (aka i have it setup for you out of the box)



>
> So, if indeed something like the barefs is functionally complete, is the
> following correct?  A Linux installation is: a specific version of the
> compiled Linux kernel, paired with a set of installed packages (including
> hardware specific drivers, and general utilities) delivered as files and
> folders in a 'filesystem' (ie your barefs). An 'image' that is just a
> filesystem stored in a way that can be easily read/written to/from media in
> whole.
>

barefs is as bare as we could get it and still use dpkg/apt... ;)  any bit
smaller or one less package would break dpkg/apt...

it's up to you to install ssh..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgVciZi0h7SNxdAg-2UKu4E8VhjFqHfoLML9mGehNUs_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to