On Fri, Aug 1, 2014 at 11:29 AM, Canek Peláez Valdés wrote:
> On Fri, Aug 1, 2014 at 10:21 AM, Peter Humphrey wrote:
>
>> I wouldn't like to be the one who has to write a new installation handbook
>> for
>> systemd-only systems! :)
>
> We'll need to rewrote the whole thing when we switch to sy
On Friday 01 August 2014 20:32:54 Neil Bothwick wrote:
> On Fri, 01 Aug 2014 14:07:08 +0100, Peter Humphrey wrote:
> > I run a couple of chroots on this box to build packages for other boxes
> > on the LAN. So far, I haven't worked out what I should
> > populate /etc/mtab with in each chroot. Is it
On Friday 01 August 2014 16:44:11 Canek Peláez Valdés wrote:
> I was only offering options. The OP will use whatever he decides to use.
All interesting stuff. Personally, I'm not ready to go for systemd, as the
openrc system I have works well for me and I understand it (mostly).
I settled on an
On 1 August 2014 23:46:00 CEST, "Canek Peláez Valdés" wrote:
>
>Sorry; I almost missed this. Actually systemd-nspawn does much more
>than chroot'ing and bind-mounting some dirs; it also runs the
>container in its own namespace. And it can add virtual networking a
>lot more stuff. See [1] for detai
On 1 August 2014 23:44:11 CEST, "Canek Peláez Valdés" wrote:
>On Fri, Aug 1, 2014 at 4:39 PM, J. Roeleveld
>wrote:
>> On 1 August 2014 23:33:05 CEST, "Canek Peláez Valdés"
> wrote:
>>>On Fri, Aug 1, 2014 at 4:31 PM, Canek Peláez Valdés
>
>>>wrote:
On Aug 1, 2014 3:46 PM, "J. Roeleveld" wrot
J. Roeleveld wrote:
> On 1 August 2014 15:28:01 CEST, Dale wrote:
>
>> It has been a good while since I used this. So, make sure it makes
>> sense to you before trying this. This may not work if something has
>> changed in the past several years. Use with caution if at all.
>>
>> This is a lit
On Fri, Aug 1, 2014 at 4:44 PM, Canek Peláez Valdés wrote:
> On Fri, Aug 1, 2014 at 4:39 PM, J. Roeleveld wrote:
>> On 1 August 2014 23:33:05 CEST, "Canek Peláez Valdés"
>> wrote:
>>>On Fri, Aug 1, 2014 at 4:31 PM, Canek Peláez Valdés
>>>wrote:
On Aug 1, 2014 3:46 PM, "J. Roeleveld" wrot
On Fri, Aug 1, 2014 at 4:39 PM, J. Roeleveld wrote:
> On 1 August 2014 23:33:05 CEST, "Canek Peláez Valdés"
> wrote:
>>On Fri, Aug 1, 2014 at 4:31 PM, Canek Peláez Valdés
>>wrote:
>>> On Aug 1, 2014 3:46 PM, "J. Roeleveld" wrote:
On 1 August 2014 15:28:01 CEST, Dale wrote:
>Pet
On 1 August 2014 23:33:05 CEST, "Canek Peláez Valdés" wrote:
>On Fri, Aug 1, 2014 at 4:31 PM, Canek Peláez Valdés
>wrote:
>> On Aug 1, 2014 3:46 PM, "J. Roeleveld" wrote:
>>>
>>> On 1 August 2014 15:28:01 CEST, Dale wrote:
>>> >Peter Humphrey wrote:
>>> >> On Friday 01 August 2014 14:07:08 I wr
On Fri, Aug 1, 2014 at 4:31 PM, Canek Peláez Valdés wrote:
> On Aug 1, 2014 3:46 PM, "J. Roeleveld" wrote:
>>
>> On 1 August 2014 15:28:01 CEST, Dale wrote:
>> >Peter Humphrey wrote:
>> >> On Friday 01 August 2014 14:07:08 I wrote:
>> >>
>> >>> I run a couple of chroots on this box to build pack
On Aug 1, 2014 3:46 PM, "J. Roeleveld" wrote:
>
> On 1 August 2014 15:28:01 CEST, Dale wrote:
> >Peter Humphrey wrote:
> >> On Friday 01 August 2014 14:07:08 I wrote:
> >>
> >>> I run a couple of chroots on this box to build packages for other
> >boxes on
> >>> the LAN. So far, I haven't worked o
On 1 August 2014 15:28:01 CEST, Dale wrote:
>Peter Humphrey wrote:
>> On Friday 01 August 2014 14:07:08 I wrote:
>>
>>> I run a couple of chroots on this box to build packages for other
>boxes on
>>> the LAN. So far, I haven't worked out what I should populate
>/etc/mtab with
>>> in each chroot. I
On 1 August 2014 21:32:54 CEST, Neil Bothwick wrote:
>On Fri, 01 Aug 2014 14:07:08 +0100, Peter Humphrey wrote:
>
>> I run a couple of chroots on this box to build packages for other
>boxes
>> on the LAN. So far, I haven't worked out what I should
>> populate /etc/mtab with in each chroot. Is it e
On Fri, 01 Aug 2014 14:07:08 +0100, Peter Humphrey wrote:
> I run a couple of chroots on this box to build packages for other boxes
> on the LAN. So far, I haven't worked out what I should
> populate /etc/mtab with in each chroot. Is it enough to "grep
> ext4 /etc/mtab > /mnt/chroot/etc/mtab"? Tha
On Friday 01 August 2014 10:29:17 Canek Peláez Valdés wrote:
> On Fri, Aug 1, 2014 at 10:21 AM, Peter Humphrey
wrote:
> > On Friday 01 August 2014 10:00:40 Canek Peláez Valdés wrote:
> >> ... just for completeness, systemd actually requires /etc/mtab as a
> >> link to /proc/self/mounts, so don't
On Fri, Aug 1, 2014 at 10:21 AM, Peter Humphrey wrote:
> On Friday 01 August 2014 10:00:40 Canek Peláez Valdés wrote:
>
>> ... just for completeness, systemd actually requires /etc/mtab as a
>> link to /proc/self/mounts, so don't be surprised if software in the
>> future in Linux just assumes that
On Friday 01 August 2014 11:07:26 Rich Freeman wrote:
> On Fri, Aug 1, 2014 at 11:00 AM, Canek Peláez Valdés
wrote:
> > And just for completeness, systemd actually requires /etc/mtab as a
> > link to /proc/self/mounts, so don't be surprised if software in the
> > future in Linux just assumes that
On Friday 01 August 2014 10:00:40 Canek Peláez Valdés wrote:
> ... just for completeness, systemd actually requires /etc/mtab as a
> link to /proc/self/mounts, so don't be surprised if software in the
> future in Linux just assumes that.
Well, that seems to imply that you can't run a systemd chro
On Fri, Aug 1, 2014 at 11:00 AM, Canek Peláez Valdés wrote:
> And just for completeness, systemd actually requires /etc/mtab as a
> link to /proc/self/mounts, so don't be surprised if software in the
> future in Linux just assumes that.
Part of the reason for this is namespace support. As namesp
On Fri, Aug 1, 2014 at 8:12 AM, Peter Humphrey wrote:
> On Friday 01 August 2014 14:07:08 I wrote:
>
>> I run a couple of chroots on this box to build packages for other boxes on
>> the LAN. So far, I haven't worked out what I should populate /etc/mtab with
>> in each chroot. Is it enough to "grep
On Friday 01 August 2014 14:12:46 Peter Humphrey wrote:
> On Friday 01 August 2014 14:07:08 I wrote:
> > I run a couple of chroots on this box to build packages for other boxes on
> > the LAN. So far, I haven't worked out what I should populate /etc/mtab
> > with
> > in each chroot. Is it enough to
On Fri, Aug 1, 2014 at 9:07 AM, Peter Humphrey wrote:
> Hello list,
>
> I run a couple of chroots on this box to build packages for other boxes on the
> LAN. So far, I haven't worked out what I should populate /etc/mtab with in
> each chroot. Is it enough to "grep ext4 /etc/mtab > /mnt/chroot/etc/
Peter Humphrey wrote:
> On Friday 01 August 2014 14:07:08 I wrote:
>
>> I run a couple of chroots on this box to build packages for other boxes on
>> the LAN. So far, I haven't worked out what I should populate /etc/mtab with
>> in each chroot. Is it enough to "grep ext4 /etc/mtab >
>> /mnt/chroot/
On Friday 01 August 2014 14:07:08 I wrote:
> I run a couple of chroots on this box to build packages for other boxes on
> the LAN. So far, I haven't worked out what I should populate /etc/mtab with
> in each chroot. Is it enough to "grep ext4 /etc/mtab >
> /mnt/chroot/etc/mtab"? That catches all t
Hello list,
I run a couple of chroots on this box to build packages for other boxes on the
LAN. So far, I haven't worked out what I should populate /etc/mtab with in
each chroot. Is it enough to "grep ext4 /etc/mtab > /mnt/chroot/etc/mtab"?
That catches all the physical partitions, but I imagin
25 matches
Mail list logo
