All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelsha@ez-darmstadt.telekom.de>
To: chris@alwan.com
Cc: mge@u9ete.ez-darmstadt.telekom.de, linux-lvm@msede.com
Subject: Re: [linux-lvm] Raw/Cahr devices
Date: Tue, 27 Apr 1999 18:00:36 METDST	[thread overview]
Message-ID: <199904271600.AA07879@mailgate1b.telekom.de> (raw)
In-Reply-To: <99Apr27.101317cdt.28406@firewall.sigg.com>; from "Chris Anderson" at Apr 27, 99 10:22 am

> 
> Can lvm create a Raw/Char devices?
> 
> Not a blocked device.  Much like a tape device. See below the
> two(listing A).  The first position shows what type of device it is.
> 
> Informix and other database like to have char devices for database
> space.
> 
> 
> Listing A:
> 
> crw-r-----   1 root     disk       9,   1 Jul 18  1994 /dev/st1
> 
> brw-r-----   1 root     disk      34,  73 Aug 18  1995 /dev/hdh9
> 
> 
> Thanks,
>     Chris Anderson
> 
> 


--

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Systemmanagement C/S                             Deutsche Telekom AG
                                                 Entwicklungszentrum Darmstadt
Heinz Mauelshagen                                Otto-Roehm-Strasse 71c
Senior Systems Engineer                          Postfach 10 05 41
                                                 64205 Darmstadt
mge@ez-darmstadt.telekom.de                      Germany
                                                 +49 6151 886-425
                                                          FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~1999-04-27 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-27 15:22 [linux-lvm] Raw/Cahr devices Chris Anderson
1999-04-27 16:00 ` Heinz Mauelshagen [this message]
1999-04-30  0:29 ` Stephen C. Tweedie

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=199904271600.AA07879@mailgate1b.telekom.de \
    --to=mauelsha@ez-darmstadt.telekom.de \
    --cc=chris@alwan.com \
    --cc=linux-lvm@msede.com \
    --cc=mge@u9ete.ez-darmstadt.telekom.de \
    /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.