On Thu, 23 Jul 2020 at 12:09, Riccardo Paolo Bestetti via arch-general
wrote:
>
> I have root encryption set up on my system and I currently boot with the
> sd-encrypt and sd-lvm hooks.
>
> I would like to change my current crypto setup in a way that would require
> more step to unlock the root
This is a good example how to uncrypt via tpm
https://aur.archlinux.org/packages/mkinitcpio-tpm2-encrypt/
On Thu, 23 Jul 2020, 16:03 Giancarlo Razzolini via arch-general, <
arch-general@archlinux.org> wrote:
> Em julho 23, 2020 7:09 Riccardo Paolo Bestetti via arch-general escreveu:
> >
> > I wo
Em julho 23, 2020 7:09 Riccardo Paolo Bestetti via arch-general escreveu:
I would like to change my current crypto setup in a way that would require more
step to unlock the root than just typing in a passphares. For this reason,
sd-encrypt clearly cannot serve my use case.
What step would t
I have root encryption set up on my system and I currently boot with the
sd-encrypt and sd-lvm hooks.
I would like to change my current crypto setup in a way that would require more
step to unlock the root than just typing in a passphares. For this reason,
sd-encrypt clearly cannot serve my use
On 09-11-2015 20:42, Eli Schwartz wrote:
> Well, you could install a custom mkinitcpio.conf and use it in the preset.
> The custom mkinitcpio.conf can source the system one.
This will work. It will be a custom mkinitcpio.conf calling another
custom mkinitcpio.conf but it works like I want it to :)
On 11/09/2015 02:20 PM, Mauro Santos wrote:
> I'm working on install and hook files for mkinitcpio and I'm adding some
> modules to the initramfs image with the install file.
>
> My problem is that the modules I add with the install file get removed
> when the autodetect hook runs.
>
> Is there a
I'm working on install and hook files for mkinitcpio and I'm adding some
modules to the initramfs image with the install file.
My problem is that the modules I add with the install file get removed
when the autodetect hook runs.
Is there any way to keep some modules when the autodetect hook runs
I was being silly. Found the answer myself:
if [ -n "$earlymodules$MODULES" ]; then
modprobe -qab ${earlymodules//,/ } $MODULES
fi
in base hook init.
On 10 June 2015 at 10:30, Tom Yan wrote:
> For my current system, I need the following modules (and their
> dependencies) to boot (mount the
For my current system, I need the following modules (and their
dependencies) to boot (mount the real root):
ahci, sd_mod, btrfs
(which are drivers for the sata controller, disk, and the root
filesystem respectively.)
If I specify these three in the MODULES array of mkinitcpio.conf, the
only hook
Pacman SyncFirst I miss you :_(
https://projects.archlinux.org/pacman.git/tree/NEWS#n122
https://bbs.archlinux.org/viewtopic.php?id=160697
2014-12-29 23:28 GMT+01:00 Ido Rosen :
> On Mon, Dec 29, 2014 at 5:23 PM, Martti Kühne wrote:
> > On Mon, Dec 29, 2014 at 12:27 AM, Ido Rosen wrote:
>
On Mon, Dec 29, 2014 at 5:23 PM, Martti Kühne wrote:
> On Mon, Dec 29, 2014 at 12:27 AM, Ido Rosen wrote:
>>
>> Not sure what the best way to accomplish this would be?
>>
>
>
> Sounds like the case for pacman hooks. Those were still in the works
> though, last time checked.
This is a pain point
On Mon, Dec 29, 2014 at 12:27 AM, Ido Rosen wrote:
>
> Not sure what the best way to accomplish this would be?
>
Sounds like the case for pacman hooks. Those were still in the works
though, last time checked.
cheers!
mar77i
Hi,
Currently, mkinitcpio runs before the correct version of
linux-headers is installed, since linux gets upgraded before
linux-headers gets upgraded.
The reason this is a problem for me is that it interferes with dkms,
nvidia, vboxguest, and other mkinitcpio install/hook scripts that need
the l
Jonathan Hudson on Fri, 2014/10/31 17:30:
> On Fri, 31 Oct 2014 16:34:18 +0100, Christian Hesse wrote:
>
> >Hello everybdoy,
> >
> >just installed systemd 217-2, building a systemd-enabled initramfs I get:
> >
> > -> Running build hook: [systemd]
> >==> ERROR: file not found: `/init'
> >
> >Let'
On Fri, Oct 31, 2014 at 6:30 PM, Jonathan Hudson wrote:
> On Fri, 31 Oct 2014 16:34:18 +0100, Christian Hesse wrote:
>
>>Hello everybdoy,
>>
>>just installed systemd 217-2, building a systemd-enabled initramfs I get:
>>
>> -> Running build hook: [systemd]
>>==> ERROR: file not found: `/init'
>>
>
On Fri, 31 Oct 2014 16:34:18 +0100, Christian Hesse wrote:
>Hello everybdoy,
>
>just installed systemd 217-2, building a systemd-enabled initramfs I get:
>
> -> Running build hook: [systemd]
>==> ERROR: file not found: `/init'
>
>Let's see whether or not this breaks boot. :D
>--
>main(a){char*c=
Hello everybdoy,
just installed systemd 217-2, building a systemd-enabled initramfs I get:
-> Running build hook: [systemd]
==> ERROR: file not found: `/init'
Let's see whether or not this breaks boot. :D
--
main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;f
On Thu, Sep 25, 2014 at 7:21 PM, Tobias Hunger wrote:
> Hi Martti,
>
> I did mention that I have been playing with the hooks and systemd in my
> initial mail. At least I thought that would be clear. Sorry if it was not.
> I will try to make that more clear next time. Was my first post here, I
> on
Hi Martti,
I did mention that I have been playing with the hooks and systemd in my
initial mail. At least I thought that would be clear. Sorry if it was not.
I will try to make that more clear next time. Was my first post here, I
only joined this list recently.
My question about how to open a deb
hi tobias,
I wasn't taking you rude. But implying you were using custom packages
while we're trying to debug an issue is generally seen as a serious
undermining of any help... Such things are to be mentioned beforehand,
since the basic assumption is a repo install.
cheers!
mar77i
Hi Martti,
It was definitely not my intention to be rude. I am sorry if I gave
that impression.
Thanks again for taking the time to help me!
Best Regards,
Tobias
On Thu, Sep 25, 2014 at 9:32 AM, Martti Kühne wrote:
> On Wed, Sep 24, 2014 at 1:47 PM, Tobias Hunger
> wrote:
>>
>> My C-foo is a
On Wed, Sep 24, 2014 at 1:47 PM, Tobias Hunger wrote:
>
> My C-foo is a bit rusty, so who knows what I actually put into my
> patched version of systemd-fstab-generator that I have on that
> initrd;-)
>
I was planning to complain already.
Try not to insult people trying to help you like that...
Ha, found it!
I gave the wrong subvol to mount:-/ Stupid mistake, pretty much as expected.
Martti: Thanks for your help!
Best Regards,
Tobias
On Wed, Sep 24, 2014 at 1:02 PM, Martti Kühne wrote:
> On Wed, Sep 24, 2014 at 9:51 AM, Tobias Hunger
> wrote:
>> Then it fails with "/bin/sh not found".
>>
>
> As new_root is mounted (/bin/sh is there in the initrd), where /bin is
> a symlink to /usr/bin, this should be obvious...
Yeap. I just
On Wed, Sep 24, 2014 at 9:51 AM, Tobias Hunger wrote:
> Then it fails with "/bin/sh not found".
>
As new_root is mounted (/bin/sh is there in the initrd), where /bin is
a symlink to /usr/bin, this should be obvious...
>> You also did not provide any error message or other
>> pointer which would
Hi Matti,
On Wed, Sep 24, 2014 at 9:20 AM, Martti Kühne wrote:
> Thanks for the pointer. I just removed the init= setting from
> /etc/default/grub and added the systemd hook to mkinitcpio.conf.
> I generated both the bootloader config and the initcpio.
Yeap, that part works fine for me, too. Mak
On Wed, Sep 24, 2014 at 12:38 AM, Tobias Hunger wrote:
> Hello!
>
> I am running a initrd make with mkinitcpio using the "systemd" hook.
>
> This works great in general, but after a bit of playing with the hooks
> and systemd code the generated initrd will no longer start. That is no
> big deal an
Hello!
I am running a initrd make with mkinitcpio using the "systemd" hook.
This works great in general, but after a bit of playing with the hooks
and systemd code the generated initrd will no longer start. That is no
big deal and entirely my fault and I should be able to fix it. My
problem is no
Yamakaky on Wed, 2014/06/04 09:29:
> Hi
>
> For the 207 systemd release, the mkinitcpio's hook for systemd is broken
> when used with the lvm2 one. It was nearly a year ago, any improvement ?
Package lvm2 provides hook sd-lvm2. You should use that when using systemd
enabled initramfs.
--
main(
Hi
For the 207 systemd release, the mkinitcpio's hook for systemd is broken
when used with the lvm2 one. It was nearly a year ago, any improvement ?
Yamakaky
Am 09.04.2013 23:41, schrieb Tom Gundersen:
> On Mon, Apr 8, 2013 at 10:45 PM, Karol Babioch wrote:
>> I'm wondering whether it makes actually sense to include the fsck hook
>> into the initial ramdisk.syt
>
> In case your filesystem needs fsck before being mounted (i.e., it is
> not btrfs), then
On Mon, Apr 8, 2013 at 10:45 PM, Karol Babioch wrote:
> I'm wondering whether it makes actually sense to include the fsck hook
> into the initial ramdisk.syt
In case your filesystem needs fsck before being mounted (i.e., it is
not btrfs), then the sane thing to do is to first fsck it, and then
mo
On Mon, Apr 8, 2013 at 10:45 PM, Karol Babioch wrote:
> Hi,
>
> I'm wondering whether it makes actually sense to include the fsck hook
> into the initial ramdisk. With the "current" switch to systemd
> filesystems get fsck'ed by default anyway, so it seems to be sort of
> redundant.
>
> Is there s
Hi,
I'm wondering whether it makes actually sense to include the fsck hook
into the initial ramdisk. With the "current" switch to systemd
filesystems get fsck'ed by default anyway, so it seems to be sort of
redundant.
Is there something I'm missing here, or how do you handle this?
Best regards,
Hi
I'm using btrfs on two LUKS encrypted partitions as root. This is
working perfectly with the mkinitcpio hook "encrypt-multi" from the aur
package "mkinitcpio-encrypt-multi".
Does anybody know if there is a plan to include this functionality in
the "encrypt" hook from core/cryptsetup ?
regard
2013/1/18 Dave Reisner
> On Jan 18, 2013 4:52 PM, "Jameson" wrote:
> >
> > On Thu, Jan 17, 2013 at 1:37 PM, Leonardo Dagnino
> wrote:
> > > 2013/1/16 Arno Gaboury
> > >
> > >> On 16/01/13||11:22, Tom Gundersen wrote:
> > >> > Hi Arno,
> > >> >
> > >> > On Tue, Jan 15, 2013 at 12:34 PM, Arno Ga
On Jan 18, 2013 4:52 PM, "Jameson" wrote:
>
> On Thu, Jan 17, 2013 at 1:37 PM, Leonardo Dagnino
wrote:
> > 2013/1/16 Arno Gaboury
> >
> >> On 16/01/13||11:22, Tom Gundersen wrote:
> >> > Hi Arno,
> >> >
> >> > On Tue, Jan 15, 2013 at 12:34 PM, Arno Gaboury <
arnaud.gabo...@gmail.com>
> >> wrote:
On Thu, Jan 17, 2013 at 1:37 PM, Leonardo Dagnino wrote:
> 2013/1/16 Arno Gaboury
>
>> On 16/01/13||11:22, Tom Gundersen wrote:
>> > Hi Arno,
>> >
>> > On Tue, Jan 15, 2013 at 12:34 PM, Arno Gaboury
>> wrote:
>> > > HOOKS="base udev autodetect block lvm2 filesystems fsck usr usbinput
>> > > shut
2013/1/16 Arno Gaboury
> On 16/01/13||11:22, Tom Gundersen wrote:
> > Hi Arno,
> >
> > On Tue, Jan 15, 2013 at 12:34 PM, Arno Gaboury
> wrote:
> > > HOOKS="base udev autodetect block lvm2 filesystems fsck usr usbinput
> > > shutdown modconf"
> > >
> > > When # mkinitcpio, I get this error:
> > >
On 16/01/13||11:22, Tom Gundersen wrote:
> Hi Arno,
>
> On Tue, Jan 15, 2013 at 12:34 PM, Arno Gaboury
> wrote:
> > HOOKS="base udev autodetect block lvm2 filesystems fsck usr usbinput
> > shutdown modconf"
> >
> > When # mkinitcpio, I get this error:
> > -> Running build hook: [fsck]
> > ==>
Hi Arno,
On Tue, Jan 15, 2013 at 12:34 PM, Arno Gaboury wrote:
> HOOKS="base udev autodetect block lvm2 filesystems fsck usr usbinput
> shutdown modconf"
>
> When # mkinitcpio, I get this error:
> -> Running build hook: [fsck]
> ==> ERROR: file not found: `fsck.btrfs'
> ==> WARNING: No fsck hel
Dear list,
here is my mkinitcpio hook list.
HOOKS="base udev autodetect block lvm2 filesystems fsck usr usbinput
shutdown modconf"
When # mkinitcpio, I get this error:
-> Running build hook: [fsck]
==> ERROR: file not found: `fsck.btrfs'
==> WARNING: No fsck helpers found. fsck will not be run
On Thu, Dec 20, 2012 at 12:55 AM, Karol Babioch wrote:
> Now my idea so far was the following: Start a screen session early
> (using "run_earlyhook"). Start dropbear whenever SSH access is needed,
> e.g. right before the "encrypt" hook itself using a separate "dropbear"
> hook ("run_hook" should b
Hi,
so far I was using "dropbear_initrd_encrypt" (see [1]) to unlock a
cryptdevice remotely via SSH, which worked reasonably well. However
since the latest release of mkinitcpio it doesn't work anymore. I could
fix the issues in the meantime, however it got me into thinking that
this could be done
On 03/10/12, Thomas Bächler wrote:
| First of all, once you add the mdadm.conf file, the mdX names will
| follow the naming usual scheme - the md126+ names will only be used when
| the array is not mentioned in mdadm.conf.
|
| Second, you can always use /dev/disk/by-uuid/.
Cool, makes sense, and
> On 03/10/12, Thomas B?chler wrote:
>
>> You need to create a file /etc/mdadm.conf. mdadm --examine --scan will
>> generate the right lines for you. This file will be added to the
>> initramfs and your names will be fine again.
>
> Yep, that's what I've done, and I've used the mdadm hook as I ha
Am 03.10.2012 22:07, schrieb Simon Perry:
> Based on the mkinitcpio wiki page, and the forum post, I'm under the
> impression that using mdadm_udev to auto-assemble the arrays is what I
> should be using (and is what will be supported in the future).
>
> The mdadm_udev hook does work as advertised
On 03/10/12, Thomas Bächler wrote:
| You need to create a file /etc/mdadm.conf. mdadm --examine --scan will
| generate the right lines for you. This file will be added to the
| initramfs and your names will be fine again.
Yep, that's what I've done, and I've used the mdadm hook as I have in the
p
Am 03.10.2012 14:41, schrieb Simon Perry:
> Hi,
>
> I've just been re-installing a box, and saw that the wiki says regarding
> using the mdadm_udev hook:
>
>> "This is the preferred method of mdadm assembly (rather than using the
>> above mdadm hook). "
>
> I've tried to use the mdadm_udev hook,
Hi,
I've just been re-installing a box, and saw that the wiki says regarding
using the mdadm_udev hook:
> "This is the preferred method of mdadm assembly (rather than using the
> above mdadm hook). "
I've tried to use the mdadm_udev hook, but the devices get named:
> normal md0 (/boot)
On Fri, Mar 2, 2012 at 11:32, Thomas Bächler wrote:
> Am 02.03.2012 18:22, schrieb Tom Gundersen:
>> Assuming you have ext[234] in your MODULES array in mkinitcpio.conf,
>> then yes, that's the reason :-) (you pasted your MODULES array from
>> rc.conf above, which is not involved in mkinitcpio). I
Am 02.03.2012 18:22, schrieb Tom Gundersen:
> Assuming you have ext[234] in your MODULES array in mkinitcpio.conf,
> then yes, that's the reason :-) (you pasted your MODULES array from
> rc.conf above, which is not involved in mkinitcpio). If, on the other
> hand, you don't have any fs modules in m
Am 02.03.2012 18:12, schrieb Myra Nelson:
> Back to my original question.
>
> my box -> HOOKS="base udev autodetect pata scsi sata filesystems usb
> usbinput fsck numlock"
>
> new box ->HOOKS="base udev autodetect pata scsi sata filesystems usb
> usbinput fsck"
>
> Modules in my rc.conf -> MODUL
On Fri, Mar 2, 2012 at 6:15 PM, Myra Nelson wrote:
> On Fri, Mar 2, 2012 at 11:12, Myra Nelson wrote:
>> First off, sorry for causing so much noise. That was not my intent.
Don't think you caused any :-)
>> my box -> HOOKS="base udev autodetect pata scsi sata filesystems usb
>> usbinput fsck nu
On Fri, Mar 2, 2012 at 11:12 AM, Myra Nelson wrote:
>
> cp: warning: source file
> `/lib/modules/3.2.9-1-ARCH/kernel/fs/ext4/ext4.ko.gz' specified more
> than once
>
> What causes this warning? Does it need to be fixed? Is the error
> something I've done or is it in the hooks from mkinitcpio?
>
>
On Fri, Mar 2, 2012 at 11:12, Myra Nelson wrote:
> On Fri, Mar 2, 2012 at 08:19, Tom Gundersen wrote:
>> On Mar 2, 2012 3:09 PM, "Thomas Bächler" wrote:
>>>
>>> Am 02.03.2012 14:58, schrieb Simon Perry:
>>> > I have removed ext4 from my MODULES line, and removed the filesystems
>>> > hook in ord
On Fri, Mar 2, 2012 at 08:19, Tom Gundersen wrote:
> On Mar 2, 2012 3:09 PM, "Thomas Bächler" wrote:
>>
>> Am 02.03.2012 14:58, schrieb Simon Perry:
>> > I have removed ext4 from my MODULES line, and removed the filesystems
>> > hook in order to get rid of the dupe message.
>>
>> If you don't hav
On Fri, Mar 2, 2012 at 5:37 PM, Simon Perry wrote:
> Something clearly changed in order to make this warning appear. I used
> to have ext2 and ext4 in my MODULES line, and autodetect and filesystems
> in my HOOKS. Never used to get a warning about ext4 being included
> twice, regardless of my lack
On 02/03/12, C Anthony Risinger wrote:
| ... respectively. i make backups so often that i should really have a
| little alias or something ... then again, `cp` does backups itself,
| maybe should leverage that, meh.
I normally stick to the "if I have the last working one there, and I can
load it
On Fri, Mar 2, 2012 at 10:07 AM, Simon Perry wrote:
> On 02/03/12, C Anthony Risinger wrote:
>
> | i guess you missed the "make a backup copy of your old
> | initramfs-linux.img" part? you should have been able to simply edit
> | you bootloader on the fly, and use the old copy.
>
> Yep, dumb mist
On 02/03/12, C Anthony Risinger wrote:
| i guess you missed the "make a backup copy of your old
| initramfs-linux.img" part? you should have been able to simply edit
| you bootloader on the fly, and use the old copy.
Yep, dumb mistake. :(
Forgot to put it in /boot ...
--
Simon Perry (aka Pezz
On 02/03/12, Thomas Bächler wrote:
| Which I told you in my first reply.
Apologies for missing this after reading:
"Actually, except for 'atl1', all those module specs are unnecessary."
In the subsequent message...
Not blaming you at all, but jesus - Captain Smug alert.
--
Simon Perry (aka P
On Fri, Mar 2, 2012 at 9:45 AM, Simon Perry wrote:
> On 02/03/12, Thomas Bächler wrote:
>
> | Actually no. But you can make a backup copy of your old
> | initramfs-linux.img and compare lsinitcpio -a output for the old and new
> | one.
>
> It's a lot of output to parse and diff accurately.
comm -
Am 02.03.2012 16:45, schrieb Simon Perry:
> Filesystems hook is necessary if you want to leave MODULES bare.
Which I told you in my first reply.
signature.asc
Description: OpenPGP digital signature
On 02/03/12, Thomas Bächler wrote:
| Actually no. But you can make a backup copy of your old
| initramfs-linux.img and compare lsinitcpio -a output for the old and new
| one.
It's a lot of output to parse and diff accurately.
Nevertheless, be glad you didn't bet (even though I provided no counte
Am 02.03.2012 15:35, schrieb Simon Perry:
> On 02/03/12, Thomas Bächler wrote:
>
> | Actually, except for 'atl1', all those module specs are unnecessary.
>
> Booting is scary.
>
> If I take out all the modules except atl1, leave my hooks as is, and my
> machine doesn't boot after a mkinitcpio +
On 02/03/12, Thomas Bächler wrote:
| Actually, except for 'atl1', all those module specs are unnecessary.
Booting is scary.
If I take out all the modules except atl1, leave my hooks as is, and my
machine doesn't boot after a mkinitcpio + reboot - will you buy me a
slab of beer?
("Slab" is the A
Am 02.03.2012 15:24, schrieb Simon Perry:
> On 02/03/12, Tom Gundersen wrote:
>
> | Unless you have ext2/3, as those are now aliases for ext4.
>
> Cheers, that explains it.
>
> Example: http://pastebin.com/f760JeFA
>
> So, in order to make things "nice", I should just use the filesystems
> hook
On 02/03/12, Tom Gundersen wrote:
| Unless you have ext2/3, as those are now aliases for ext4.
Cheers, that explains it.
Example: http://pastebin.com/f760JeFA
So, in order to make things "nice", I should just use the filesystems
hook, and not specify ext2 or ext4 in the modules line?
--
Simon
On Mar 2, 2012 3:09 PM, "Thomas Bächler" wrote:
>
> Am 02.03.2012 14:58, schrieb Simon Perry:
> > I have removed ext4 from my MODULES line, and removed the filesystems
> > hook in order to get rid of the dupe message.
>
> If you don't have the filesystem hook, and you don't have ext4 it in
> MODUL
Am 02.03.2012 14:58, schrieb Simon Perry:
> I have removed ext4 from my MODULES line, and removed the filesystems
> hook in order to get rid of the dupe message.
If you don't have the filesystem hook, and you don't have ext4 it in
MODULES, ext4 will be missing from the initramfs and you won't be a
On 02/03/12, Myra Nelson wrote:
| I don't think this is significant enough to warrant a bug. Since the
| linux-3.2.6-1 kernel updates ( I don't remeber which version of
| mkinitcpio, sorry), I've been getting the following warning when
| mkinitcpio runs during the kernel install:
|
| cp: warning:
I don't think this is significant enough to warrant a bug. Since the
linux-3.2.6-1 kernel updates ( I don't remeber which version of
mkinitcpio, sorry), I've been getting the following warning when
mkinitcpio runs during the kernel install:
cp: warning: source file
`/lib/modules/3.2.9-1-ARCH/kerne
On Fri 13 January 2012 at 21:48 -0500, Dave Reisner wrote:
> Hi all,
>
> With the release of mkinitcpio 0.8.2, we've added support for mounting
> /usr from early userspace when it exists as a separate partition. This
> has been something people have been asking about for a little while, so
> I fig
On Fri, Jan 13, 2012 at 20:48, Dave Reisner wrote:
> Hi all,
>
> With the release of mkinitcpio 0.8.2, we've added support for mounting
> /usr from early userspace when it exists as a separate partition. This
> has been something people have been asking about for a little while, so
> I figured I'
On 01/13/2012 07:30 PM, Isaac Dupree wrote:
On 01/13/2012 09:48 PM, Dave Reisner wrote:
The fsck hook is highly recommended for everyone, not just those with a
separate /usr. Running fsck in early userspace means the device can be
Should it be moved to hooks now?
checked before it's even moun
On 01/13/2012 09:48 PM, Dave Reisner wrote:
The fsck hook is highly recommended for everyone, not just those with a
separate /usr. Running fsck in early userspace means the device can be
checked before it's even mounting -- any and all repairs can be
performed without the need for a reboot.
Cur
Hi all,
With the release of mkinitcpio 0.8.2, we've added support for mounting
/usr from early userspace when it exists as a separate partition. This
has been something people have been asking about for a little while, so
I figured I'd make a call out for the feature.
There's two requirements to
Hi all,
I've tagged mkinitcpio 0.8.0, which came a little earlier than I would
have liked, but there's still fun things to talk about.
The major point of interest is the addition of fsck functionality. The
logic in init is triggered by the addition of the 'fsck' install hook.
If added after the a
On Sunday 21 of August 2011 15:06:25 Tom Gundersen wrote:
> On Sun, Aug 21, 2011 at 1:42 PM, Marek Otahal wrote:
> > Hi,
> >
> > I have a custom hook [1] (opencrypt to setup encrypted partitions for me)
> > and last days (well, a couple of months maybe:P) I'm getting this on
> > every mkinitcpio
>
On Sun, Aug 21, 2011 at 1:42 PM, Marek Otahal wrote:
> Hi,
>
> I have a custom hook [1] (opencrypt to setup encrypted partitions for me)
> and last days (well, a couple of months maybe:P) I'm getting this on
> every mkinitcpio
> generation:
>
> -> Parsing hook: [opencrypt]
> ==> WARNING: Hook 'ope
Hi,
I have a custom hook [1] (opencrypt to setup encrypted partitions for me)
and last days (well, a couple of months maybe:P) I'm getting this on
every mkinitcpio
generation:
-> Parsing hook: [opencrypt]
==> WARNING: Hook 'opencrypt' uses a deprecated 'install' function.
This should be renamed '
On Sun, 27 Feb 2011, Thomas Bächler wrote:
Am 27.02.2011 03:12, schrieb Dimitrios Apostolou:
Hello list,
I'm using arch on an old laptop with only 128MB RAM. I had problems
compressing the initcpio image with lzma, it always failed allocating
memory. The following one-line patch allowed me to s
Am 27.02.2011 03:12, schrieb Dimitrios Apostolou:
> Hello list,
>
> I'm using arch on an old laptop with only 128MB RAM. I had problems
> compressing the initcpio image with lzma, it always failed allocating
> memory. The following one-line patch allowed me to set my own
> compression level in mki
On Sun, Feb 27, 2011 at 10:12 AM, Dimitrios Apostolou wrote:
> Hello list,
>
> I'm using arch on an old laptop with only 128MB RAM. I had problems
> compressing the initcpio image with lzma, it always failed allocating
> memory. The following one-line patch allowed me to set my own compression
> l
On Sun, Feb 27, 2011 at 10:12 AM, Dimitrios Apostolou wrote:
> --- /sbin/mkinitcpio.orig 2010-10-06 03:23:00.966415649 +0300
> +++ /sbin/mkinitcpio 2011-02-26 19:11:36.309682053 +0200
> @@ -277,7 +277,7 @@
> status=0
> if [ -n "${GENIMG}" ]; then
> echo -n ":: Generating image '${GE
Hello list,
I'm using arch on an old laptop with only 128MB RAM. I had problems
compressing the initcpio image with lzma, it always failed allocating
memory. The following one-line patch allowed me to set my own compression
level in mkinitcpio.conf, with COMPRESSION="lzma -4"
--- /sbin/mkin
It looks like mkinitcpio.conf till mention the "raid" hook whereas it looks
like it has been superseded by "mdadm" hook
Indeed :
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcp
Quoted from http://bugs.archlinux.org/task/17298 (which is also to be
used for feedback, besides the threads on these mailing lists):
So, now something can be tested. I recommend using it in conjunction
with testing/udev only:
[kill-klibc]
Server = http://dev.archlinux.org/~thomas/kill-klibc/i686
Am 12.01.2010 22:24, schrieb Evangelos Foutras:
>> I tried in VirtualBox on Arch i686 and it worked fine here (meaning I
>> didn't have that particular problem).
>>
>> It then paniced due to problems in /init. Rev
>> 93a8be170ff841dd345084b5f5eda66c76e6534f boots fine here on VirtualBox.
>>
>> I do
On Tue, Jan 12, 2010 at 10:43 PM, Thomas Bächler wrote:
> Am 12.01.2010 15:07, schrieb Evangelos Foutras:
>> I gave it a try in a VM but it still fails with "Failed to execute
>> /init" like last time (http://i.imgur.com/h6xDu.png).
>>
>> The mkinicpio revision I tried was 54fd032, along with late
Am 12.01.2010 15:07, schrieb Evangelos Foutras:
> On 12/01/2010 11:03 πμ, Thomas Bächler wrote:
>> I think what we have now in the kill-klibc branch might actually boot in
>> a standard setup (no raid, nfs, lvm, encryption), but I didn't try. I'll
>> keep you posted.
>
> I gave it a try in a VM bu
On Wed, 2009-12-09 at 11:02 +0800, Ng Oon-Ee wrote:
> On Wed, 2009-12-09 at 03:36 +0100, Damjan Georgievski wrote:
> > > It looks vanilla to me, and doesn't work here =(. Says 'waiting 10
> > > seconds for swap:/dev/sda8' and then continues normal boot after 10
> > > seconds.
> >
> >
> > I only u
On Wed, 2009-12-09 at 03:36 +0100, Damjan Georgievski wrote:
> > It looks vanilla to me, and doesn't work here =(. Says 'waiting 10
> > seconds for swap:/dev/sda8' and then continues normal boot after 10
> > seconds.
>
>
> I only use resume=/dev/sda2, but I also have
> CONFIG_TOI_REPLACE_SWSUSP=y
> It looks vanilla to me, and doesn't work here =(. Says 'waiting 10
> seconds for swap:/dev/sda8' and then continues normal boot after 10
> seconds.
I only use resume=/dev/sda2, but I also have
CONFIG_TOI_REPLACE_SWSUSP=y
--
damjan
On Wed, 2009-12-09 at 02:13 +0100, Damjan Georgievski wrote:
> > A quick look into testing shows that I won't be able to update the
> > 2.6.32 kernel due to dependencies on klib invalidating my 'old'
> > mkinitcpio package. Unfortunately I'm stuck here, since without this
> > 'old' package for mkin
> A quick look into testing shows that I won't be able to update the
> 2.6.32 kernel due to dependencies on klib invalidating my 'old'
> mkinitcpio package. Unfortunately I'm stuck here, since without this
> 'old' package for mkinitcpio (0.5.24-1) I'm unable to resume from
> hibernate in tuxonice.
On Tue, 2009-12-08 at 14:40 +0500, Vasiliy Kurdin wrote:
> 2009/12/8 Ng Oon-Ee
>
> > On Tue, 2009-12-08 at 09:02 +0100, Thomas Bächler wrote:
> > > Ng Oon-Ee schrieb:
> > > > On Tue, 2009-12-08 at 07:13 +0100, Thomas Bächler wrote:
> > > >> Ng Oon-Ee schrieb:
> > > >>> Hi all, I've been holding t
I have tried that 'patch' from wiki, but it didn't help me.
2009/12/8 Ng Oon-Ee
> On Tue, 2009-12-08 at 09:02 +0100, Thomas Bächler wrote:
> > Ng Oon-Ee schrieb:
> > > On Tue, 2009-12-08 at 07:13 +0100, Thomas Bächler wrote:
> > >> Ng Oon-Ee schrieb:
> > >>> Hi all, I've been holding the mkinitc
On Tue, 2009-12-08 at 09:02 +0100, Thomas Bächler wrote:
> Ng Oon-Ee schrieb:
> > On Tue, 2009-12-08 at 07:13 +0100, Thomas Bächler wrote:
> >> Ng Oon-Ee schrieb:
> >>> Hi all, I've been holding the mkinitcpio package due to
> >>> http://bugs.archlinux.org/task/15240
> >>>
> >>> A quick look into t
1 - 100 of 107 matches
Mail list logo
