color in man pages and less etc
by Harry Putnam
I've run FC1 for a while but more rh9 recently. I'm used to a certain
set of colors present when viewing man pages in black xterm.
My fresh intall of FC2 shows a combination of colors in black xterm
that are not good for me. I see them elsewhere too. In less, at the
prompt in ncftp. The worst offender is a `bold' blue that nearly
disappears on a black background.
Wracking my feeble brain, I don't remember where this kind of stuff is
set or changed. Do I have to meddle with termcap? Or something else?
20 years, 3 months
Unsubscribe me from the Newsletter
by Ralf Hippen Computer Systeme
Ralf Hippen Computer Systeme
Glatzer Strasse 6
26427 Esens
Telefon: (04971) 290683, FAX: (04971) 290682
---
Gesendete Mail ist zertifiziert Virenfrei.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.593 / Virus Database: 376 - Release Date: 20.02.2004
20 years, 3 months
kudzu and gpm
by LICHTENBERGER Janos
Hello,
I use rh9 with and Logitech TrackmanVista trackball (well, actually I use it
since rh6.2), kudzu recognizes it as 'Generic PS/2' mouse and works fine in
Console and in X too.
I installed FC2 Test and kudzu recognizes my trackball as 'msintellips/2' and
'Generic PS/2 Wheel Mouse'
Here is the corresponding section of rh9 /etc/sysconfig/hwconf:
- -
class: MOUSE
bus: PSAUX
detached: 0
device: psaux
driver: genericps/2
desc: "Generic Mouse (PS/2)"
- -
and this is FC2 Test1:
- -
class: MOUSE
bus: PSAUX
detached: 0
device: psaux
driver: msintellips/2
desc: "Generic PS/2 Wheel Mouse"
- -
It is this way from installation, if I try graphical install, no mouse
(fortunately keyboard works :-)) ...
Neither GPM nor X can recognize the trackball, thus X fails to start with
'cannot open psaux' or something
Janos Lichtenberger
20 years, 3 months
Re: Testing test releases: do not update (was: yum.conf that works)
by Jason Knight
I couldn't thave said it better myself, I believe this is a simple case
of a little effort now a whole lot less effort later. This would make
much more sense.
Robert P. J. Day wrote:
>and for those who think it's too much work for red hat to do it this way,
>i submit that it's exactly the opposite. when there's a test release out
>in the wild, red hat should be spending their time dealing with bug
>reports that represent things that are just flat out *broken*. not stuff
>from rawhide, not RFEs, not wish lists. they should be focused on fixing
>stuff that's broken, and that means restricting their attention to just
>those things so that the testers' time is well spent. and that means not
>having to deal with rawhide. there should be a *separate* update channel
>purely for fixing broken things. and, no, i don't care if it takes red
>hat a few more minutes to set this up. it's not about *them*, it's about
>making the testers' time as productive as possible. but wait, there's
>more.
>
>
>
This would be excellent as well, maybe this would be taken under the
wing of the documentation project?
>anyway, what would be nice is if there was a real and comprehensive
>document for testers, explaining how releases work, how to query bugs, how
>to report bugs and so on. and by "comprehensive", i mean something a
>little more meaty than "file bugs at bugzilla against your current
>release."
>
>i'm convinced that the testing procedure deserves an update repo, and i'm
>just as convinced that that repo shouldn't be rawhide.
>
>
--
Jason Knight
Fedora Core 1 Test 1 *x86_64*
20 years, 3 months
up2date bug or feature?
by Gene C.
On FC1, I noticed that when up2date installed a new kernel that default- in
grub.conf was changed to point to the new kernel. This is not happening on
FC2. Is this a bug or a feature (that is a change)?
--
Gene
20 years, 3 months
Re: yum update problem
by Efthym
This is what I got when trying to update
error: Failed dependencies:
libavc1394 is needed by pwlib-1.6.3-0.pre1.0
librom1394.so.0 is needed by pwlib-1.6.3-0.pre1.0
libpt.so.1.5.0 is needed by (installed) gnomemeeting-0.98.5-1
removing pwlib-1.6.3.0 from update list solved my problem. No other
complains. I dont know exactly what pwlib provides, but upgrading pwlib-
1.5.0.3 (already installed) to pwlib-1.6.3.0.pre1.0 doesn't seem to have
backward complatibility, or gnomemeeting should be upraded as well (I
dont know if pwlib is used elsewhere)
20 years, 3 months
Re: upgrading rawhide
by Wes Shull
seth vidal <skvidal(a)phy.duke.edu> wrote:
> On Sun, 2004-02-22 at 20:15 +0100, Alex Thomsen Leth wrote:
> > i got a problem, when im trying to upgrade via rawhide i got this
> > message. what could be wrong. sometimes when im trying yum end op
> > hanging.
>
> This seems very odd. You're getting a traceback from deep in python
> urllib.
>
> Can you make this happen every time?
I (not the person to whom you were replying) have also had a crash in
python urllib while updating, except I was using up2date, not yum
directly.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115779
Not sure how much it may be related; sound like both up2date and yum
could use extra checking on what they get back from the server,
especially with (hearsay from this list) redhat's servers not
erroring gracefully when they're overloaded...
--
"TEST RELEASES EAT BABIES." --Jef Spaleta on the fedora-test-list
20 years, 3 months
Weirdness after up2date on FC2test1
by David Jansen
FC2 test1 was working reasonably well on my test box, until I used
up2date to update all packages. Test box is a very old system:
P II 350 MHz, 256 MB memory,
A couple of things I noticed:
1) the new kernel (2.6.3-1.97) does not become the default in grub
2) kudzu thinks the keyboard is a new piece of hardware (AT Translated
Set 2 keyboard)
No big deal, just weird.
3) after this upgrade, the graphical boot is gone, and so is X
when starting X the screen will go blank a couple of times and then a
text mode dialog will pop up stating that the mouse is not set up
correctly. it offers to run the mouse configuration utility, and this
utility offers the correct mouse type (generic wheel mouse PS/2)
but reconfiguration doesn't help, still no X. Which is correct in a
way, since the gpm service is not running.
However, the gpm init script gives a green OK when starting.
4) During the boot sequence, I get a message about firstboot already
having run on this machine with an explanation how to rerun it if you
want.
(NOTE: /etc/sysconfig/firstboot contains the one line:
RUN_FIRSTBOOT=NO
but this seems to be ignored in this kernel)
5) When sshd is starting, an error appears:
/sbin/ifup: configuration for sit0 not found.
Usage: ifup <device name>
(well, I can believe the configuration is not found, I only have the lo
and eth0 interfaces configured)
However, sshd is running despite this error
If I'm not mistaken, sit0 is a UPv6 tunnel interface. Is IPv6 mandatory
in kernel 2.6.3 ?
Rebooting back in the 2.6.1-1.65 kernel, X and rhgb are working correctly.
Kudzu thinks the "AT Translated set 2 keyboard" has been removed, and
when removing the configuration, the next screen says the exact same
type of keyboard has been added.
Again, no big deal, just more weirdness.
Also, the firstboot and sshd messages are gone, and gpm is working
correctly.
So, all of the new weird problems seem to be triggered/caused by the
2.6.3 kernel. Any additional configuration required to get this new
kernel to run.
David Jansen
20 years, 3 months