Re: [RFC] what do we do with picobsd ?

Dario Freni <[email protected]>
Newsgroups gmane.os.freebsd.devel.small
Message-ID <43DFFF1A.4050406__27106.1543179259$1138753434$gmane$org@freesbie.org>
Julian Elischer wrote:
> Poul-Henning Kamp wrote:
> 
>> In message <[email protected]>, "M. Warner
>> Losh" writes:
>>  
>>
>>> In message: <[email protected]>
>>>           Sam Leffler <[email protected]> writes:
>>>   
>>
>>  
>>
>>> Since I've started working on the bring up on an ARM based board, I've
>>> been wanting something that is easy to work with and that worked.  I
>>> think it would help us a lot in the embedded space if we had something
>>> integrated into the base OS to do this stuff.
>>>   
>>
>> I agree.  I think we need to be much more inclusive in our concept of
>> a 'release' than we are now.
>>
>> As I see it, PicoBSD with its "additive" approach would cover the
>> low-capacity (<32 MB ?) range, NanoBSD with its "subtractive" approach
>> takes over from there, FreeSBIE covers the "don't touch my disk"
>> range and finally the full blown release as we know it.
>>  
>>
> 
> I'd like to see us take the freesbie release into the tree somewhere
> (since it uses so many
> ports, maybe in ports, or maybe in tools)
> _______________________________________________
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[email protected]"

Do you mean the livecd or the build toolkit? The toolkit only needs
mkisofs as port (like release/ scripts do, afaik).

Bye,
Dario

-- 
Dario Freni ([email protected])
FreeSBIE developer (http://www.freesbie.org)
GPG Public key at http://www.saturnero.net/saturnero.asc
signature.asc (application/pgp-signature, 186 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFD3/8aymi72IiShysRAnCYAKDuLhArEQ2taebuatmLm8/U2vrLggCg2Sjx
r5zkVygNMShiZHezUqzgJqk=
=6Vus
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.