freebsd-advocacy Digest, Vol 305, Issue 1
freebsd-advo...@freebsd.org
freebsd-...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-advocacy
or, via email, send a message with subject or body 'help' to
freebsd-advo...@freebsd.org
You can reach the person managing the list at
freebsd-adv...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-advocacy digest..."
Today's Topics:
1. Re: why BSDs got no love (Petrus)
2. Re: why BSDs got no love (Dag-Erling Sm?rgrav)
3. Re: why BSDs got no love (Sd?vtaker)
----------------------------------------------------------------------
Message: 1
Date: Tue, 29 Dec 2009 03:59:00 +1000
From: "Petrus" <pet...@tpg.com.au>
Subject: Re: why BSDs got no love
To: <freebsd-...@freebsd.org>
Message-ID: <001001ca87e7$70b00760$0301a8c0@jim4fb89194d83>
Content-Type: text/plain; format=flowed; charset="UTF-8";
reply-type=original
> There is absolutely no reason to change the default FreeBSD installer in
> my
> opinion, when the PC-BSD one will suffice for the 'snazzy' desktop
> installs.
I won't say that sysinstall couldn't benefit from at least *some*
renovation. ;)
The interface is fine, sure, but what I'm primarily talking about is the
download mechanism. Apparently when certain files get downloaded with it,
they actually get copied in-place during the transfer process, which means
that if you abort it, you can end up with partially digested conf files (my
/etc/passwd got hosed once) all over the place.
What I'd propose would be caching whatever files the system needs to
download until everything is cached locally, and then installing the lot
after that, rather than doing both downloading and installing/copying in the
same step. That way you can safely abort during the process if you need to.
A scenario where individual files that are to be rewritten, get temporarily
backed up until the setup is complete would probably also really help.
So as said, the interface is fine, but I think the internal mechanism could
definitely benefit from being made a bit more robust.
------------------------------
Message: 2
Date: Mon, 28 Dec 2009 19:20:30 +0100
From: Dag-Erling Sm?rgrav <d...@des.no>
Subject: Re: why BSDs got no love
To: Astrodog <astr...@gmail.com>
Cc: freebsd-...@freebsd.org
Message-ID: <86r5qf0...@ds4.des.no>
Content-Type: text/plain; charset=utf-8
Astrodog <astr...@gmail.com> writes:
> Basically... if you really want to see this change, I think you're
> gonna have to do it yourself.
What do you think this is, a collaborative open source project? Furrfu!
DES
--
Dag-Erling Smørgrav - d...@des.no
------------------------------
Message: 3
Date: Mon, 28 Dec 2009 15:26:38 -0300
From: Sd?vtaker <sdav...@gmail.com>
Subject: Re: why BSDs got no love
To: Petrus <pet...@tpg.com.au>
Cc: freebsd-...@freebsd.org
Message-ID:
<c37d69f60912281026k6c6...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
it will be nice make sysinstall use the port tree, since a lot of
applications in the dvd use to fail the install because dependencies that
can be resolved in the ports (as portinstall/portmaster does whena package
dependency is not fulfilled).
On Mon, Dec 28, 2009 at 14:59, Petrus <pet...@tpg.com.au> wrote:
> There is absolutely no reason to change the default FreeBSD installer in my
>> opinion, when the PC-BSD one will suffice for the 'snazzy' desktop
>> installs.
>>
>
> I won't say that sysinstall couldn't benefit from at least *some*
> renovation. ;)
>
> The interface is fine, sure, but what I'm primarily talking about is the
> download mechanism. Apparently when certain files get downloaded with it,
> they actually get copied in-place during the transfer process, which means
> that if you abort it, you can end up with partially digested conf files (my
> /etc/passwd got hosed once) all over the place.
>
> What I'd propose would be caching whatever files the system needs to
> download until everything is cached locally, and then installing the lot
> after that, rather than doing both downloading and installing/copying in the
> same step. That way you can safely abort during the process if you need to.
> A scenario where individual files that are to be rewritten, get temporarily
> backed up until the setup is complete would probably also really help.
>
> So as said, the interface is fine, but I think the internal mechanism could
> definitely benefit from being made a bit more robust.
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-advocacy
> To unsubscribe, send any mail to "freebsd-advoca...@freebsd.org
> "
>
--
http://dfbsd.trackbsd.org.ar
------------------------------
End of freebsd-advocacy Digest, Vol 305, Issue 1
************************************************