All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: CONFIG_SYSFS_DEPRECATED and similar issues
Date: Tue, 06 Mar 2007 12:36:35 -0500	[thread overview]
Message-ID: <45EDA6A3.7010109@tmr.com> (raw)

Just a few comments on changes like this in general. Prompted by, but 
not otherwise related to the subject.

When any new feature in the kernel requires significant changes in 
userspace, attention should be given to documenting the user items which 
must change. Now "attention" doesn't mean handwaving b.s. like "user 
programs which depend on sysfs will need to be modified." It means a 
list of which common user features need to be updated and where to find 
new ones. That's what the whole Documentation directory is for, but it's 
rarely used for such a purpose.

In the most recent case, a user tool is needed which doesn't even exist 
as a release.

The other issue is to avoid "trap door" changes, which occur when a 
kernel change requires new user tools, and the user tools will not run 
with older kernels. That includes missing major features like having a 
display and being able to mount filesystems, even if the kernel is 
technically running. When there were stable and development kernel 
series that was not so much of an issue, now that every kernel is an 
adventure it would be nice to ensure that testing a new kernel is not an 
irrevocable step.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

             reply	other threads:[~2007-03-06 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 17:36 Bill Davidsen [this message]
2007-03-06 18:08 ` CONFIG_SYSFS_DEPRECATED and similar issues Lee Revell

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=45EDA6A3.7010109@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.