The Wanderer wrote:
> Henrique de Moraes Holschuh wrote:
>> songbird wrote:
>>
>>> # cpio -i -v < /boot/initrd.img-3.18.0-trunk-686-pae
>>> kernel
>>> kernel/x86
>>> kernel/x86/microcode
>>> kernel/x86/microcode/GenuineIntel.bin
>>> 22 blocks
>>=20
>> Yeah, well, you have a multi-segment initramfs.
On 04/25/2015 at 11:01 PM, Henrique de Moraes Holschuh wrote:
> On Sat, Apr 25, 2015, at 17:16, songbird wrote:
>
>> # cpio -i -v < /boot/initrd.img-3.18.0-trunk-686-pae
>> kernel
>> kernel/x86
>> kernel/x86/microcode
>> kernel/x86/microcode/GenuineIntel.bin
>> 22 blocks
>
> Yeah, well, you have
On Sat, Apr 25, 2015, at 17:16, songbird wrote:
> # cpio -i -v < /boot/initrd.img-3.18.0-trunk-686-pae
> kernel
> kernel/x86
> kernel/x86/microcode
> kernel/x86/microcode/GenuineIntel.bin
> 22 blocks
Yeah, well, you have a multi-segment initramfs. There's an uncompressed cpio
archive first with t
The Wanderer wrote:
>Ric Moore wrote:
...
>> Sorry I missed it, but what version of Debian does this occur on??
>
> My system, which does not have the problem, is on current testing -
> dist-upgraded just this afternoon.
>
> songbird is at least running initramfs-tools from testing (it's the same
>
On 04/25/2015 at 05:36 PM, Ric Moore wrote:
> On 04/25/2015 05:29 PM, songbird wrote:
>
>> The Wanderer wrote:
>>> That's _very_ weird. If my experience is any guide, there should
>>> be an entire root-like hierarchy in there; mine contains
>>>
>>> bin/ conf/ etc/ init lib/ lib64/ run/ sbin/ sc
On 04/25/2015 05:29 PM, songbird wrote:
The Wanderer wrote:
songbird wrote:
The Wanderer wrote:
songbird wrote:
/boot/initrd.img-3.18.0-trunk-686-pae: ASCII cpio archive (SVR4 with
no CRC)
So it's not compressed at all.
Try
cpio -i < /boot/initrd.img-3.18.0-trunk-686-pae
to expand it (
The Wanderer wrote:
>songbird wrote:
>> The Wanderer wrote:
>>> songbird wrote:
>
/boot/initrd.img-3.18.0-trunk-686-pae: ASCII cpio archive (SVR4 with
no CRC)
>>>
>>> So it's not compressed at all.
>>>
>>> Try
>>>
>>> cpio -i < /boot/initrd.img-3.18.0-trunk-686-pae
>>>
>>> to expand it (a
On 04/25/2015 at 04:16 PM, songbird wrote:
> The Wanderer wrote:
>
>> songbird wrote:
>>> /boot/initrd.img-3.18.0-trunk-686-pae: ASCII cpio archive (SVR4 with
>>> no CRC)
>>
>> So it's not compressed at all.
>>
>> Try
>>
>> cpio -i < /boot/initrd.img-3.18.0-trunk-686-pae
>>
>> to expand it (again
The Wanderer wrote:
> songbird wrote:
>> The Wanderer wrote:
>>> songbird wrote:
>
doesn't work for me, hmm:
=20
# gunzip - < /boot/initrd.img-3.18.0-trunk-686-pae | cpio -i
=20
gzip: stdin: not in gzip format
>>>=20
>>> What does
>>>=20
>>> file /boot/initrd.img-3.18.0-trunk
On 04/25/2015 at 02:50 PM, songbird wrote:
> The Wanderer wrote:
>
>> songbird wrote:
>>> doesn't work for me, hmm:
>>>
>>> # gunzip - < /boot/initrd.img-3.18.0-trunk-686-pae | cpio -i
>>>
>>> gzip: stdin: not in gzip format
>>
>> What does
>>
>> file /boot/initrd.img-3.18.0-trunk-686-pae
>>
The Wanderer wrote:
> songbird wrote:
>> Mike Kupfer wrote:
>>> songbird wrote:
>>>
how did you expand the initramfs? i tried the
command given and didn't get it to work and so set
it aside until i could read further docs today.
>>>
>>> I did
>>>
>>> $ su
>>> # cd /root
>>
On 04/25/2015 at 02:08 PM, songbird wrote:
> Mike Kupfer wrote:
>
>> songbird wrote:
>>
>>> how did you expand the initramfs? i tried the
>>> command given and didn't get it to work and so set
>>> it aside until i could read further docs today.
>>
>> I did
>>
>> $ su
>> # cd /root
>>
Mike Kupfer wrote:
> songbird wrote:
>
>> how did you expand the initramfs? i tried the
>> command given and didn't get it to work and so set
>> it aside until i could read further docs today.
>
> I did
>
> $ su
> # cd /root
> # mkdir initrd
> # cd initrd
>
> and then ran the pip
Michael Biebl wrote:
> schrieb songbird:
>> Mike Kupfer wrote:
>>> The Wanderer wrote:
>>>
If that doesn't help, then I'd advise that you expand the initramfs /=
>
initrd file from under /boot into an empty directory, and see what it=
>
contains. It may very well be missing either bi
songbird wrote:
> how did you expand the initramfs? i tried the
> command given and didn't get it to work and so set
> it aside until i could read further docs today.
I did
$ su
# cd /root
# mkdir initrd
# cd initrd
and then ran the pipeline that The Wanderer gave. I think I
Am 25.04.2015 um 15:00 schrieb songbird:
> Mike Kupfer wrote:
>> The Wanderer wrote:
>>
>>> If that doesn't help, then I'd advise that you expand the initramfs /
>>> initrd file from under /boot into an empty directory, and see what it
>>> contains. It may very well be missing either bin/touch or s
Mike Kupfer wrote:
> The Wanderer wrote:
>
>> If that doesn't help, then I'd advise that you expand the initramfs /
>> initrd file from under /boot into an empty directory, and see what it
>> contains. It may very well be missing either bin/touch or some related
>> thing.
>
> Indeed, it's missing b
The Wanderer wrote:
> If that doesn't help, then I'd advise that you expand the initramfs /
> initrd file from under /boot into an empty directory, and see what it
> contains. It may very well be missing either bin/touch or some related
> thing.
Indeed, it's missing bin/touch. Thanks for the det
On 04/23/2015 at 01:32 PM, songbird wrote:
> songbird wrote:
>
>> Mike Kupfer wrote:
>>
>>> Hi, after updating a jessie VM, I noticed a message during boot,
>>> before lightdm started. The message was something like
>>>
>>> /init [stuff I didn't catch] touch: not found
>>>
>>> After logging i
songbird wrote:
> songbird wrote:
> > Mike Kupfer wrote:
> >
> >> Hi, after updating a jessie VM, I noticed a message during boot, before
> >> lightdm started. The message was something like
> >>
> >> /init [stuff I didn't catch] touch: not found
> >>
> >> After logging in, I tried using journa
songbird wrote:
> Mike Kupfer wrote:
>
>> Hi, after updating a jessie VM, I noticed a message during boot, before
>> lightdm started. The message was something like
>>
>> /init [stuff I didn't catch] touch: not found
>>
>> After logging in, I tried using journalctl to find the message, with no
>
Mike Kupfer wrote:
> Hi, after updating a jessie VM, I noticed a message during boot, before
> lightdm started. The message was something like
>
> /init [stuff I didn't catch] touch: not found
>
> After logging in, I tried using journalctl to find the message, with no
> success. Is journalctl
Hi, after updating a jessie VM, I noticed a message during boot, before
lightdm started. The message was something like
/init [stuff I didn't catch] touch: not found
After logging in, I tried using journalctl to find the message, with no
success. Is journalctl the right tool to find the messa
23 matches
Mail list logo
