Date: Thu, 08 Apr 2010 12:19:24 +0200 From: "Svein Skogen (Listmail Account)" <svein-listmail@stillbilde.net> To: freebsd-current@freebsd.org Subject: Re: [RFC] Rewriting sade(8) Message-ID: <4BBDADAC.7080803@stillbilde.net> In-Reply-To: <867hoi8gbl.fsf@ds4.des.no> References: <55861270658151@web135.yandex.ru> <l2we277d6c81004071049h21670783ic4a9f419aedca272@mail.gmail.com> <4BBD68DB.7050600@yandex.ru> <201004080727.21020.bruce@cran.org.uk> <4BBD7CDC.2070505@yandex.ru> <20100408103809.13496s9i6ny03ocg@webmail.leidinger.net> <867hoi8gbl.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig78661AF243B84F14DC2E64AD
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 08.04.2010 11:05, Dag-Erling Sm=C3=B8rgrav wrote:
> Alexander Leidinger <Alexander@Leidinger.net> writes:
>> Please consider using SVN instead. A lot more users will be able to
>> check out from there.
>=20
> We don't grant non-committers access to the Subversion repo.
>=20
>> It looks like other people had a look at sysinstall, not at sade. As
>> sysinstall is supposed to be used at installation time, and the intent=
>> for sade was to offer the functionality (or more) of the part of
>> sysinstall which is useful after installation (and to prevent admins
>> from using sysinstall after the installation to prevent some unwanted
>> foot-shooting), I do not think that we need to think about a strong
>> lock between sysinstall and sade.
>=20
> Yes we do. Otherwise we'll just end up back where we are today, where
> if you want anything more complicated than a single-disk install you
> have to drop into the fixit shell and do it manually before running the=
> installation procedure. Anythig that sade can do, we want sysinstall t=
o
> do as well, and we don't want to implement everything twice.
>=20
> My suggestion is to add a "sysinstall mode" to sade where it operates
> under certain (minor) constraints and reports what it did in a format
> that sysinstall can parse, so sysinstall can just fork-exec sade instea=
d
> of duplicating the code.
Wouldn't a setup similar to fetch/libfetch do the trick here? Move most
of the actual "working payload" of sade into a library, and make sade
just a frontend for this? That way poking the sysinstall code to use
sade should be easier, and updates will automagically fix both things?
//Svein
--=20
--------+-------------------+-------------------------------
/"\ |Svein Skogen | svein@d80.iso100.no
\ / |Solberg =C3=98stli 9 | PGP Key: 0xE5E76831
X |2020 Skedsmokorset | svein@jernhuset.no
/ \ |Norway | PGP Key: 0xCE96CE13
| | svein@stillbilde.net
ascii | | PGP Key: 0x58CD33B6
ribbon |System Admin | svein-listmail@stillbilde.net
Campaign|stillbilde.net | PGP Key: 0x22D494A4
+-------------------+-------------------------------
|msn messenger: | Mobile Phone: +47 907 03 575
|svein@jernhuset.no | RIPE handle: SS16503-RIPE
--------+-------------------+-------------------------------
If you really are in a hurry, mail me at
svein-mobile@stillbilde.net
This mailbox goes directly to my cellphone and is checked
even when I'm not in front of my computer.
------------------------------------------------------------
Picture Gallery:
https://gallery.stillbilde.net/v/svein/
------------------------------------------------------------
--------------enig78661AF243B84F14DC2E64AD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
iEYEARECAAYFAku9ra8ACgkQODUnwSLUlKQaVgCgpLIvqQWK/NsUv4e6i7IUZl6U
3JQAnjz0dNoBMFTsYOBzplrfaYiMA6mO
=FkCG
-----END PGP SIGNATURE-----
--------------enig78661AF243B84F14DC2E64AD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BBDADAC.7080803>