FreeBSD installers and future direction

[Teske, Devin]

On May 26, 2013, at 9:58 AM, Super Bisquit wrote:

May I- and others- see the hyperlink to the project,
please?


Absolutely…

http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/harshbhatt/1
--
Devin



On Sat, May 25, 2013 at 11:45 PM, Teske, Devin <Devin.Teske at fisglobal.com<mailto:Devin.Teske at fisglobal.com>> wrote:

On May 25, 2013, at 7:51 PM, Super Bisquit wrote:

> Please don't turn this into an architecture dependent mess. PCBSD is i386 &
> AMD64 only.
>

There's a GSoC project (of which I'm potential mentor) to fix that.

However, you are entirely right… we can't in all seriousness even think about using pc-sysinstall until it is solid on all architectures as bsdinstall already is.

GSoC project is: "Making pc-sysinstall FreeBSD ready by porting it to multiple architectures"
--
Devin



>
> On Sat, May 25, 2013 at 9:01 PM, Dirk Engling <erdgeist at erdgeist.org<mailto:erdgeist at erdgeist.org>> wrote:
>
>> On 26.05.13 01:07, Nathan Whitehorn wrote:
>>
>>> I'm not aware of any movement there (on either side of the table). I'd
>>> personally be very suspicious of an all-sh(1) future -- by far the
>>> cleanest parts of bsdinstall are in C -- and this is especially true for
>>> interacting with geom. That said, since I've lost nearly all of my free
>>> time and ability to work on bsdinstall, I won't get in the way of anyone
>>> else working on things
>>
>> As discussed at BSDCan, I'd be willing to participate in the development
>> and at least implement setting up zpools/zfs and geli/gbde providers. I
>> have done similar things in sh in my ezjail tools and think I can glue
>> the rest together.
>>
>> Scanning through the pc-sysinstall code, I find nothing too fancy there
>> regarding either interaction with zfs nor geom tools. I do not think it
>> is necessary as a back end just for these features.
>>
>> Nathan, is there any design rationale available for the scripts, e.g. on
>> why you chose sh versus C and were you provided with some kind of wish
>> list/requirements in the first place? Any particular mail thread to scan
>> through beforehand?
>>
>> Regards,
>>
>>  erdgeist
>> _______________________________________________
>> freebsd-hackers at freebsd.org<mailto:freebsd-hackers at freebsd.org> mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers<https://urldefense.proofpoint.com/v1/url?u=http://lists.freebsd.org/mailman/listinfo/freebsd-hackers&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=Mrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=PXUSUwGuSJd2O0fuIoJYV9V4EhVmQB9ADx3bEtQaxj4%3D%0A&s=a99d68ce305ffbaf9eb7021bfc9affbf5420722ada8561c144b10f9de922ff5d>
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org<mailto:freebsd-hackers-unsubscribe at freebsd.org>"
>>
> _______________________________________________
> freebsd-hackers at freebsd.org<mailto:freebsd-hackers at freebsd.org> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers<https://urldefense.proofpoint.com/v1/url?u=http://lists.freebsd.org/mailman/listinfo/freebsd-hackers&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=Mrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=PXUSUwGuSJd2O0fuIoJYV9V4EhVmQB9ADx3bEtQaxj4%3D%0A&s=a99d68ce305ffbaf9eb7021bfc9affbf5420722ada8561c144b10f9de922ff5d>
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org<mailto:freebsd-hackers-unsubscribe at freebsd.org>"

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.


_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.