Hi,
On Saturday 06 March 2010 00:35:06 Thomas Bächler wrote:
> > Ok, didn't know that. works with ext[23]-images though. They're rw and
> > stay mounted after boot, if you do a pivot_root in initrd.
>
> You can always write a hook that creates a ramdisk, create a filesystem
> on it, mount it and
Am 06.03.2010 00:27, schrieb Ihad:
>>> How early? Maybe keeping the ramdisk mounted helps. This way udevadm
>>> monitor could write its results do /somewhere. I did that with images
>>> having a defined size, creating a container with an ext2 fs and then
>>> mount it rw. If it's big enough we can
Hi,
On Saturday 06 March 2010 00:21:24 Thomas Bächler wrote:
> Am 06.03.2010 00:15, schrieb Ihad:
> >> There is udevadm monitor - we could start that very early and redirect
> >> the output into a file inside rootfs. Then, we kill it and look at the
> >> file. Not sure if that will work well, have
Am 06.03.2010 00:15, schrieb Ihad:
>> There is udevadm monitor - we could start that very early and redirect
>> the output into a file inside rootfs. Then, we kill it and look at the
>> file. Not sure if that will work well, haven't tried it.
>
> How early? Maybe keeping the ramdisk mounted helps.
Hi,
On Friday 05 March 2010 23:56:05 Thomas Bächler wrote:
> Am 05.03.2010 23:45, schrieb Ihad:
> > The custom kernel has RAID autodetect compiled in, so I get my root fs,
> > and I also have md0 and md1 but nothing more. No hd[a-f][0-2]. On top of
> > the RAID is LVM, so after:
> > # lvm
> >
> >
Am 05.03.2010 23:45, schrieb Ihad:
>> Some rules with respect to IDE devices were in fact removed in a
>> previous udev version. In fact, almost nobody still uses the IDE
>> subsystem, most(!) drivers work better with the ATA subsystem these days.
>>
>> However, these "standard" nodes should still
Hi,
On Friday 05 March 2010 23:31:25 Thomas Bächler wrote:
> Am 05.03.2010 23:12, schrieb Ihad:
> > Maybe this is more suitable for arch-dev, but I hope that the devs also
> > read here. Let me know if I should redirect this to arch-dev-public.
>
> arch-dev-public is read-only for non-developers.
Am 05.03.2010 23:12, schrieb Ihad:
> Hi,
>
> Maybe this is more suitable for arch-dev, but I hope that the devs also read
> here. Let me know if I should redirect this to arch-dev-public.
arch-dev-public is read-only for non-developers.
> The rebuilding device has devices connected to the PCI c
On 03/05/2010 07:12 PM, Ihad wrote:
The autodetect hook from mkinitcpio thinks that pata_hpt366 is the module of
choice. But it doesn't work. It crashes the kernel after some time,
unfortunately not reproducible and without a log message. The box just stops
responding to anything, including a p
9 matches
Mail list logo
