All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Ju. Tokarev" <mjt@tls.msk.ru>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] Revised petition WAS: LVM in stock kernel!?
Date: Fri, 27 Aug 1999 15:22:03 +0400	[thread overview]
Message-ID: <37C674DB.2EB5B424@tls.msk.ru> (raw)
In-Reply-To: Pine.LNX.3.96.990826175120.22041A-100000@zeke.sympatico.ca

Shane Shrybman wrote:
> PROS
[a lot of pros's skipped]
> 
> CONS
[]
What about adding new complecity to kernel code? Is this a cons?
Kernel already (maybe gone?) have some instabilities with fs,
saying some "Ooops" that are very hard to debug. Sorry if all
this Ooops are iliminated already, but info about them can be
found in many mailinglist archives (1997, 1998 yy at least).

And another two questions (maybe "politic"):

 - yes, Linux lacks now a great ability that exisit in other Unices.
   yes, Linux should have this ability.
   But why this should be linux-lvm? I do not know if other projects exists,
   and think that no, but is linux-lvm have exactly that things that really
   should have Linux? I like linux-lvm, but I like also Veritas, and like
   BSD's implementation... And all of them have different approaches!
   Sorry for this. One old good Russian proverb says that each orn compliments
   it's own morass.

 - look to solaris, for example -- it have lvm in a separate package (DiskSuite),
   that don't included kernel :!). This is an addon to os, and it doesn't do
   anything with kernel itself. Yes, I know about differences in kernel's architectures,
   and know little about Linux kernel internals, but linux have kernel modules!
   Is it possible to make lvm a separate package, like on Solaris? And not only
   lvm, but other things like drivers (!), fs's etc? Kernel should have base set
   of modules, and some sort of config files where others are listed, and as result
   there should be no need to recompile kernel at all! Yes, this is not an lvm
   question, but lvm-related. There are many kernel patches for different packages
   not included into stock kernel (like lvm ;), and each need this recompilation.
   Yes, some of them really _need_ recompilation, such as acl project, but some
   at least logically doesn't. So maybe ask Linus to work around pluggable modules
   instead of including lvm into kernel? This also seriously simplifies other parts
   of kernel. But I doesn't know if it is possible at all with current architecture.
   Microkernel? Hurd? ;)

> 
> Please feel free to edit and add your own points!
> 
> Shane

Regards,
  Michael.

  parent reply	other threads:[~1999-08-27 11:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-26 22:28 [linux-lvm] Revised petition WAS: LVM in stock kernel!? Shane Shrybman
1999-08-27  9:18 ` Luca Berra
1999-08-31 17:47   ` Shane Shrybman
1999-08-27 11:22 ` Michael Ju. Tokarev [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-08-27  3:38 Andreas Dilger
1999-08-27  9:13 ` Luca Berra
1999-08-27 10:20   ` Heinz Mauelshagen
1999-08-27 13:06 ` Steve Brueggeman
1999-08-27 15:37 ` S. Ryan Quick
     [not found] ` <Pine.LNX.3.96.990827113200.23961B-100000@aristotle.phaedo. com>
1999-08-27 17:12   ` Mats Wichmann
1999-08-27 19:18     ` S. Ryan Quick
1999-08-27  7:37 rolf.aebi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37C674DB.2EB5B424@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-lvm@msede.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.