From: Shawn Starr <shawn.starr@rogers.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modern 2.6 kernels - Notification for changing hostname from proc/sys/kernel/hostname ?
Date: Mon, 19 May 2008 16:05:31 -0400 [thread overview]
Message-ID: <200805191605.32484.shawn.starr@rogers.com> (raw)
In-Reply-To: <20080519204535.GA23629@martell.zuzino.mipt.ru>
On Monday 19 May 2008 04:45:35 pm Alexey Dobriyan wrote:
> On Mon, May 19, 2008 at 01:16:12PM -0400, Shawn Starr wrote:
> > I was looking at utsname_sysctl.c (if this is the right place) and
> > noticed there doesn't seem to be any notification via the connector bus
> > to tell userspace the hostname has changed? Is this correct?
>
> Yes. No notifications.
>
> > if so, would not not make sense to add such event triggers so that things
> > like KDE would not have to poll to determine if the hostname changes and
> > instead had D-BUS tell userspace the hostname changed?
>
> Why does it want to know if and when hostname changes?
>
Well, It's for keeping track of the X session, if the hostname changes things
go bad.
> > Perhaps this could be applied to other values (where applicable)
> > in /proc/sys/kernel?
>
> Probably, what other stuff desktop crowd wants?
No idea on the other values, but maybe others can jump in on this discussion?
>
> > Or is this all going to go into sysfs eventually (where some of this
> > really might belong)
>
> Hopefully, not. There is already uname(2), sysctls -- proc and binary,
Hopefully this can all be cleaned up, we really should have one unified place
for kernel tweaking/settings either /proc or /sys.
next prev parent reply other threads:[~2008-05-19 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 17:16 Modern 2.6 kernels - Notification for changing hostname from proc/sys/kernel/hostname ? Shawn Starr
2008-05-19 20:45 ` Alexey Dobriyan
2008-05-19 20:05 ` Shawn Starr [this message]
2008-05-21 9:38 ` Jan Engelhardt
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=200805191605.32484.shawn.starr@rogers.com \
--to=shawn.starr@rogers.com \
--cc=adobriyan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).