From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Thorsten Leemhuis <Thorsten_Leemhuis@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: User-Experiences 2.6.0-test5[-mm2]: General, Power-Management and tmscsim
Date: Thu, 18 Sep 2003 22:05:42 -0700 [thread overview]
Message-ID: <20030918220542.08e47374.rddunlap@osdl.org> (raw)
In-Reply-To: <20030919.4461700@thl.ct.heise.de>
On Fri, 19 Sep 2003 04:46:17 GMT Thorsten Leemhuis <Thorsten_Leemhuis@gmx.de> wrote:
| [third attempt to send mail, seems the first two (send more then 18 and
| 36 hours ago) didn't arrive at the list]
|
| Hi *,
|
| now that we're some time in the 2.6.0-test stage I thought to disturb
| development a bit by testing the new kernel ;-) . I'm mostly a normal
| linux "desktop" user with only minor programming experiences in C.
|
| Base Distro was a Red Hat 9 System updated with some security updates. I
| also installed the initscripts and modutils rpm packages from
| http://people.redhat.com/arjanv/2.5/RPMS.kernel/
|
| Hardware is an Athlon XP 2400+ on an Asus A7V266-E (Via KT266-A).
[snip]
|
| -----------------
| - gconfig currently doesn't work so nice:
|
| -- Double-mouse-clicks in the checkboxes sometimes aren't noticed.
| Clicking in the _N M Y_ Fields in the full view works correct it seems.
|
| -- In the _Split-View_ it will throw this segfault when trying to turn
| of/on something:
| ----start
[snip]
| ----end
I think that 'vi .config' and menuconfig get the most use.
I use xconfig occasionally, and have never used gconfig.
| -----------------
| - Using xconfig worked without problems. But IMHO some things are a bit
| disturbing:
|
| -- Split-View: When do options appear in the left panel ("Support for
| USB Gadgets" and "Remove kernel Features")? It seems to me that these
| two are not a the right place there.
| Another thing: Sometimes Sub-Menus appear in a sub-field in the left
| tree-view (like Power Management -> CPU Frequency Scaling) and sometimes
| they only have an own sub-menu in the top-right panel (like Networking
| -> Ethernet (10 or 100 MBit)?
Yes, we could use more consistency there.
I find that sometimes it's easier to click on a different mehu item
completely than to up-level (backtrack) on a menu.
| -- Selecting "Code maturity level options -> Select only drivers
| expected to compile cleanly" is helpful but it would be nice if the
| config-system would show these drivers in a light grey (or something
| like that) and make them not-selectable.
I certainly like that suggestion.
[snip]
Thanks.
--
~Randy
next prev parent reply other threads:[~2003-09-19 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 4:46 Thorsten Leemhuis
2003-09-19 5:05 ` Randy.Dunlap [this message]
2003-09-19 7:54 ` Alex Riesen
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=20030918220542.08e47374.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=Thorsten_Leemhuis@gmx.de \
--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
all inboxes | Powered by JetHome®