From: Adrien Farkas <freddy@redneck.sk.oracle.com>
To: Fernando Dammous <ferdam@internetcom.com.br>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM, raw-io, devfs
Date: Fri, 1 Oct 1999 14:40:03 +0200 [thread overview]
Message-ID: <19991001144003.B29576@redneck.sk.oracle.com> (raw)
In-Reply-To: <006201bf0bb7$6eae4a60$030116ac@fd1>
Fernando Dammous (ferdam@internetcom.com.br) wrote :
> 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.
well, I'm still not sure whether Oracle software is compatible with raw-io patch in linux kernel, please let me know how are you doing with that.
> The devfs isn't so important for me (should it be ?).
devfs is a very usable patch compatible with most of devices (including LVM) and software (I can only think of vmware that doesn't run with vmware). it saves a lot of inodes in /dev and contains only devices really present in the system and uses intelligent backward-compatible naming scheme (so you can still use inodes like /dev/sda etc) present in many modern UN*X flavors (like Solaris, e.g.). You should give it at lease a chance before saying you use it only because of raw-devices ;)
> If anyone knows about restrictions or some clues I would thank a lot.
Regards,
--
freddy
----==-- _ Adrien "freddy" Farkas
---==---(_)__ __ ____ __ freddy@sk.oracle.com
--==---/ / _ \/ // /\ \/ / We all know Linux is great... It
-=====/_/_//_/\___/ /_/\_\ does infinite loops in 5 seconds
next prev parent reply other threads:[~1999-10-01 12:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-01 2:48 [linux-lvm] LVM, raw-io, devfs Fernando Dammous
1999-10-01 12:40 ` Adrien Farkas [this message]
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=19991001144003.B29576@redneck.sk.oracle.com \
--to=freddy@redneck.sk.oracle.com \
--cc=ferdam@internetcom.com.br \
--cc=freddy@sk.oracle.com \
--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.