All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fernando Dammous" <ferdam@internetcom.com.br>
To: Linux LVM msede <linux-lvm@msede.com>
Subject: [linux-lvm] LVM, raw-io, devfs
Date: Thu, 30 Sep 1999 23:48:23 -0300	[thread overview]
Message-ID: <006201bf0bb7$6eae4a60$030116ac@fd1> (raw)

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

Hi all,

 I would like help from the more experts in this matter, because I fear that I can in some way to lose or to corrupt my FS under LVM.  
  
LVM 0.7 is installed (built into the kernel, which is still in the version 2.0.36) and working perfectly, with the root filesystem and swap in a LV (boot with initrd).  
  
Now, I would like to install the devfs and mainly the raw-io.   
  
Can I install them in a kernel 2.0.36, which is already patched with LVM?  
  
Should I apply the patches in which order (first devfs, later the raw-io, or vice versa)?  
  
I intend to install Oracle8 using raw-io.   
The devfs isn't so important for me (should it be ?).  

If anyone knows about restrictions or some clues I would thank a lot.  

Thanks in advance

Fernando


[-- Attachment #2: Type: text/html, Size: 1411 bytes --]

             reply	other threads:[~1999-10-01  2:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-01  2:48 Fernando Dammous [this message]
1999-10-01 12:40 ` [linux-lvm] LVM, raw-io, devfs Adrien Farkas
1999-10-01 16:38 ` Stephen C. Tweedie
1999-10-01 18:39   ` Drew Smith
1999-10-01 19:15     ` Luca Berra
1999-10-02 15:01     ` Stephen C. Tweedie
1999-10-02 15:53       ` Eric Smith
1999-10-03  7:43     ` Harald Milz
1999-10-02 17:08   ` Fernando Dammous
1999-10-03  5:56     ` pamvdam
1999-10-04 10:43       ` Stephen C. Tweedie
1999-10-04 11:03         ` pamvdam
1999-10-03 10:14     ` Adrien Farkas
1999-10-03 17:23       ` Fernando Dammous
1999-10-04  9:28         ` Adrien Farkas
1999-10-04 10:44       ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
1999-10-03 13:06 Daniel Whicker

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='006201bf0bb7$6eae4a60$030116ac@fd1' \
    --to=ferdam@internetcom.com.br \
    --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.