From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: [john.cagle@hp.com: FW: device number request for drbd]
Date: Wed, 18 Aug 2004 20:42:47 +0200 [thread overview]
Message-ID: <20040818184247.GP9601@marowsky-bree.de> (raw)
In-Reply-To: <uaTOpLQubcD5XbUapszkYGk=lge@web.de>
On 2004-07-30T14:14:01,
Lars Ellenberg <Lars.Ellenberg@linbit.com> said:
> > You could even use the supplied init script and put
> > ADD_MOD_PARAM="major_nr=43" into /etc/default/drbd
>
> patch will follow soon which will replace that with
> "use_nbd_major"
BTW, in real life our maintenance crew has rejected this. I will have to
patch the module to default to the old major by default. Upgrading the
kernel must work w/o updating the user-space at the same time, I'm
afraid.
We are in maintenance only mode already, so it's a matter of policy; we
only do bugfixes and security changes right now.
I can probably re-align with the first service-pack in March or so,
where we can "force" the customers to swallow a bigger chunk of packages
as a single bite.
Changing such fundamental behaviour in a stable series really is not
very good. You are breaking the kernel/user-space boundary. Nobody cares
what you do _in_ the kernel, or _within_ user-space, but this really
ain't good. Common policy for stable series (also adhered to by most
other projects) is _never_ to change the default.
I'll need to check whether that works, or whether the ioctls etc also
break, which would be very bad. That's just not a thing to do within a
stable series, but maybe we have different concepts of "stable" ;)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ This space /
SUSE Labs, Research and Development | intentionally |
SUSE LINUX AG - A Novell company \ left blank /
next prev parent reply other threads:[~2004-08-18 18:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040728080645.GB7918@tmathiasen>
2004-07-28 10:10 ` [Drbd-dev] Re: [john.cagle@hp.com: FW: device number request for drbd] Philipp Reisner
2004-07-28 10:58 ` Lars Ellenberg
2004-07-28 12:08 ` Philipp Reisner
2004-07-28 12:17 ` Lars Ellenberg
2004-07-28 12:40 ` Philipp Reisner
2004-07-28 14:12 ` Lars Marowsky-Bree
2004-07-28 14:55 ` Philipp Reisner
2004-07-28 15:33 ` Lars Marowsky-Bree
2004-07-28 15:46 ` Lars Ellenberg
2004-07-28 17:56 ` Philipp Reisner
2004-07-28 18:45 ` Lars Ellenberg
2004-07-29 22:32 ` Lars Marowsky-Bree
2004-07-30 9:56 ` Philipp Reisner
2004-07-30 11:32 ` Philipp Reisner
2004-07-30 12:14 ` Lars Ellenberg
2004-07-30 12:29 ` Philipp Reisner
2004-08-18 18:42 ` Lars Marowsky-Bree [this message]
2004-08-18 19:31 ` Philipp Reisner
2004-08-18 22:57 ` Lars Marowsky-Bree
2004-08-19 9:15 ` Philipp Reisner
2004-08-19 10:32 ` Lars Marowsky-Bree
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=20040818184247.GP9601@marowsky-bree.de \
--to=lmb@suse.de \
--cc=drbd-dev@lists.linbit.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.