On Wed 15 Oct 2014 at 21:47:45 -0400, Miles Fidelman wrote:
Brian wrote:
I'd suggest that the principal udeb package to consider as responsible
for installing the base system is bootstrap-base. It runs debootstrap.
Debian Policy specifies the base packages as being of Priority: required
Brian wrote:
On Wed 15 Oct 2014 at 21:47:45 -0400, Miles Fidelman wrote:
Brian wrote:
I'd suggest that the principal udeb package to consider as responsible
for installing the base system is bootstrap-base. It runs debootstrap.
Debian Policy specifies the base packages as being of Priority:
Brian wrote:
I'd suggest that the principal udeb package to consider as responsible
for installing the base system is bootstrap-base. It runs debootstrap.
Debian Policy specifies the base packages as being of Priority: required
and Priority: important.
You can get lists of these packages
On 2014-10-16 19:12 +0200, Joey Hess wrote:
Brian wrote:
The init package is Priority: required. It pre-depends on
systemd-sysv | sysvinit-core | upstart
The first alternative is systemd-sysv, which pre-depends on systemd.
There is no preseed command which can alter this.
It may
Joey Hess wrote:
Brian wrote:
I'd suggest that the principal udeb package to consider as responsible
for installing the base system is bootstrap-base. It runs debootstrap.
Debian Policy specifies the base packages as being of Priority: required
and Priority: important.
You can get lists of
On Thu 16 Oct 2014 at 13:12:12 -0400, Joey Hess wrote:
Brian wrote:
There is no preseed command which can alter this.
It may be that adding --include=sysvinit-core to debootstrap will cause
the other branch of that dependency to be taken. I have not tested it.
If that is the case, then
On 10/16/2014 02:33 PM, Brian wrote:
On Thu 16 Oct 2014 at 13:12:12 -0400, Joey Hess wrote:
/snip/
The technique given by Jonathan Dowland works and appears to me to
involve a minimal amount of work for someone wanting to end up booting a
new install with sysvinit. Depending on what is
Brian wrote:
On Thu 16 Oct 2014 at 13:12:12 -0400, Joey Hess wrote:
Brian wrote:
There is no preseed command which can alter this.
It may be that adding --include=sysvinit-core to debootstrap will cause
the other branch of that dependency to be taken. I have not tested it.
If that is the
On Thu 16 Oct 2014 at 14:59:12 -0400, Doug wrote:
On 10/16/2014 02:33 PM, Brian wrote:
On Thu 16 Oct 2014 at 13:12:12 -0400, Joey Hess wrote:
/snip/
The technique given by Jonathan Dowland works and appears to me to
involve a minimal amount of work for someone wanting to end up
Folks,
So, it's been suggested here that one might write a preseed file to
install sysvinit-core instead of systemd - but for the life of me, I
can't figure out how to do that.
What I've been able to determine so far:
1. There is now an essential metapackage called init that depends on one
On Wed, Oct 15, 2014 at 07:49:08AM -0400, Miles Fidelman wrote:
1. There is now an essential metapackage called init that depends on
one of systemd-sysv, or sysvinit-core, or upstart. (parenthetical
question: What distinguishes a metapackage from a virtual package?
Or perhaps, more
Jonathan Dowland wrote:
On Wed, Oct 15, 2014 at 07:49:08AM -0400, Miles Fidelman wrote:
1. There is now an essential metapackage called init that depends on
one of systemd-sysv, or sysvinit-core, or upstart. (parenthetical
question: What distinguishes a metapackage from a virtual package?
Or
On Wed 15 Oct 2014 at 12:29:23 -0400, Miles Fidelman wrote:
any thoughts re. conflicts between what's in, say
tasksel tasksel/first standard, web-server
and
d-i pkgsel/include string sysvinit-core systemd-shim
I don't believe there are any. I think what happens is that standard
and
Thanks Brian.
See follow-up question embedded below.
Brian wrote:
On Wed 15 Oct 2014 at 12:29:23 -0400, Miles Fidelman wrote:
any thoughts re. conflicts between what's in, say
tasksel tasksel/first standard, web-server
and
d-i pkgsel/include string sysvinit-core systemd-shim
I don't
On Wed, Oct 15, 2014 at 03:34:40PM -0400, Miles Fidelman wrote:
Thoughts?
I'm drawing blanks at the moment, but I'm glad you are looking at this.
I'll see if I can poke about a bit Tomorrow.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe.
On Mi, 15 oct 14, 12:29:23, Miles Fidelman wrote:
3. Is there a way to list all packages with priority standard -
preferably via the package repo or one of the staging servers rather
than having to first setup up a jessie installation and pulling in the
source list?
You don't need a full
On Wed 15 Oct 2014 at 15:34:40 -0400, Miles Fidelman wrote:
So where in base system is systemd installed?
This is the list of packages in base (from the source for the jessie
version of debian-installer/build/pkg-lists/base as of yesterday):
[A little snipping]
I'd suggest that the
Brian wrote:
On Wed 15 Oct 2014 at 15:34:40 -0400, Miles Fidelman wrote:
So where in base system is systemd installed?
This is the list of packages in base (from the source for the jessie
version of debian-installer/build/pkg-lists/base as of yesterday):
[A little snipping]
I'd suggest that
Brian wrote:
On Wed 15 Oct 2014 at 15:34:40 -0400, Miles Fidelman wrote:
So where in base system is systemd installed?
This is the list of packages in base (from the source for the jessie
version of debian-installer/build/pkg-lists/base as of yesterday):
[A little snipping]
I'd suggest that
19 matches
Mail list logo
