[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [linux-lvm] Re: Bug#150005: LVM does not fscking work at all
- From: Patrick Caulfield <caulfield sistina com>
- To: linux-lvm sistina com
- Cc: Juhapekka Tolvanen <juhtolv st jyu fi>
- Subject: Re: [linux-lvm] Re: Bug#150005: LVM does not fscking work at all
- Date: Mon Jun 17 01:58:01 2002
On Mon, Jun 17, 2002 at 01:48:18AM +0300, Juhapekka Tolvanen wrote:
>
> On Sat, 15 Jun 2002, +15:20:46 EEST (UTC +0300),
> Patrick Caulfield <patrick debian org> pressed some keys:
>
> > On Sat, Jun 15, 2002 at 03:00:26PM +0300, Juhapekka Tolvanen wrote:
>
> > > Maybe I should create a brand new .config with a little help from those
> > > aforementioned screenshots. And after that I should always use that
> > > "make oldconfig".
>
> > That might be a good thing to do. Make sure you do a "make mrproper"
> > first to really clean out the source tree.
>
> > copying a .config and doing "make oldconfig" is what I do most of the
> > time but sometimes you do need to do mrproper.
>
> It still does not fscking work! I did this:
>
> I took fresh sources of kernel 2.4.18 and unpacked them. Then I
> installed these patches:
>
> patch-2.4.19-pre10
> patch-2.4.19-pre10-ac2
> preempt-kernel-rml-2.4.19-pre10-ac2-1.patch
That /proc/devices is *still* wrong - until there's a resonable set of devices
in there LVM hasn't ahope of working. Take out all the patches and try a
"normal" kernel.
...oh, and please stop spamming everyone with your problem. It's neither an LVM
kernel nor a LVM userspace issue - simply that your kernel builds are broken.
patrick
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]