From: Bart Verwilst <verwilst@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Fwd: kppp on Gentoo Linux
Date: Wed, 8 Jan 2003 14:20:07 +0100 [thread overview]
Message-ID: <200301081420.07499.verwilst@gentoo.org> (raw)
Hi! Could somebody please take a look at the problem listed below?
I don't know wether it's a core system issue, or a kppp one, since i never
used kppp in my life :o)
Thanks!
---------- Forwarded Message ----------
Subject: kppp on Gentoo Linux
Date: Saturday 04 January 2003 04:38
From: Harri Porten <porten@trolltech.com>
To: verwilst@gentoo.org
Hi Bart,
I'm the maintainer of kppp and I'm writing to you since I saw that you
were involved in creating KDE packages for Gentoo Linux at some point in
time. If your are not the right person to talk to please forward my mail
to the appropriate developer. Thanks.
In the 2nd comment of
http://bugs.kde.org/show_bug.cgi?id=30805
you'll find a Gentoo user observing permission problems with
/etc/resolv.conf while using kppp. As kppp doesn't create that file (it
just reads&writes) I see no way how it can be responsible for changing
both owner and permissions of that file.
As stated in my last comment I think that the if-up/if-down scripts I
found to be potentially problematic. Depending on what they are supposed
to do a chown and chmod call migh be in order to ensure the proper setup.
Please tell me about your opinion on where the problem really lies. If
it's in kppp I'll try to fix it. If you can give a statement on possible
improvements on your side I'll also be greatful to know. I'd like to close
this report and probably update the kppp FAQ.
Thanks,
Harri.
-------------------------------------------------------
--
Bart Verwilst
Gentoo Linux Developer, Desktop Team
Gent, Belgium
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2003-01-08 13:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200301081420.07499.verwilst@gentoo.org \
--to=verwilst@gentoo.org \
--cc=gentoo-dev@gentoo.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