On Wed, Apr 27, 2016 at 06:05:56PM +0200, Didier Kryn wrote:
> Le 27/04/2016 17:47, Haines Brown a écrit :
> >
> >I'm doing a cross install of devuan Alpha 4 onto a newly partitioned
> >hard disk (/dev/sda1) in same box as my running Debian Wheezy system
> >(/dev/sdb1). I partitioned, formatted and mounted the needed new disk's
> >partitions; I downloaded debootstrap_1.0.75-1*.deb to a working
> >directory in my current sytem; I unpacked the data tarball, Finally I
> >ran the devuan debootstrap to install a base system on the target
> >drive.
> >

> >   # debootstrap --no-check-gpg jessie /mnt/debinst   \
> >             http://packages.devuan.org/merged

> >
>

>     I think you should use the --foreign option of debootstrap.

>
> first 'debootstrap --no-check-gpg jessie /mnt/debinst'
>
> then 'chroot /mnt/debinst debootstrap --second-stage'

Didier, thanks! That was the answer. I was confused by the debootstrap
man page because it sounded like the --foreign option was for
non-matching architectures. But adding that option to debootstrap allowe
me to go through the entire devuan installation.

There were a couple hiccups, but I await the devuan installation guide
before bringing them up.

I found I had to bind mount /sys before I could install grub2. My /dev
directly already well populated; I had no /proc directory, but mount
tells me: none on /proc type proc (rw,relatime). The /sys directory
exists, but is empty, so I do

    # mount -o bind  /sys/ /mnt/debinst/sys

and grub installation then went smoothly.

Finally I decided to beef things up with tasksel. I wanted at this point
to install print server and SSH server. I select and try to install
them. But I get: "tasksel: apt-get failed (100)". This error often
because of error in sources.list. All I have in it is one line:

      deb http://packages.devuan.org/merged jessie main

However, I have no problem installing cups-client (the equivalent of
printer-server?), xorg and fluxbox individually. Whenever I install
packages I'm warned that that the packages are untrusted and I have to
tell aptitude to proceed anyway. I wonder if tasksel fails because it
cannot convey a willingness to risk installing untrustworthy package?

I should now have a bootable system thanks to your help.

Haines