Core 3 Xinerama and KDE
by Jonathan Andrews
I've just upgraded from Redhat9 to Core 3. I've got a dual head g450
with dual monitors and I notice that KDE refuses to open windows onto
the second workspace. I can manually move the window onto the second
monitor, but the window manager refuses to use it automatically even if
its blank.
My question is who do I file this sort of bug with ?
Is it a window manager problem (kde) or an X problem (Xinerama) or some
Redhat tweak - is their a "general bugs" system I can file against ?
Cheers,
Jon
19 years, 3 months
ANNOUNCE: RULE installers for Fedora Core 3
by M. Fioretti
Greetings, everybody!
I am happy to announce that the RULE project is back, allowing to
install modern software like Fedora Core 3 on so-called "obsolete"
hardware. Details at
http://www.rule-project.org/breve.php3?id_breve=19
Users, testers and people helping us to update/check the documentation
are more than welcome!
Thanks for your attention,
Marco Fioretti
RULE project coordinator
--
Marco Fioretti mfioretti, at the server mclink.it
Red Hat & Fedora for low memory http://www.rule-project.org/
Don't think that a small group of dedicated individuals can't change
the world. it's the only thing that ever has. (read on /.)
19 years, 3 months
Why is sendmail bad?
by Kenneth Porter
There seems to be a lot of dissatisfaction with sendmail in the call to
replace it with Exim or Postfix, but I didn't see any specifics about why
people object to it. Anyone care to give details?
I'm using sendmail together with MIMEDefang to run SpamAssassin and ClamAV
against messages during the SMTP transaction so that I can reject obvious
spam and viruses before they're committed to a queue. MIMEDefang uses a
user-edited Perl script to establish the exact rules for acceptance, making
the system very flexible. How hard is that to set up in Postfix or Exim?
19 years, 3 months
2.6.11 ALPS Issue
by David Cary Hart
Just an unconfirmed heads up. I installed Korg 2.6.11 and it broke the
ability to "tap" mouse clicks on the touchpad. I tried to get someone to
confirm on the FC-list. So far no response.
--
Total Quality Management - A Commitment to Excellence
Fight Spam: http://www.tqmcube.com/rbldnsd.htm
Daily Updates: rsync -t \
tqmcube.com::spamlists/[README.htm][clients][dynamic][relays][asiaspam]
http://www.tqmcube.com/spam_trap.htm
19 years, 3 months
FC5 anaconda
by Gene C.
There have been a number of characteristics/functionality for anaconda in FC5
mentioned on this list. Is there some place where the plan is
described/discussed?
I currently subscribe to the anaconda-devel-list but only started in late
January so if there was discussion earlier, I missed it.
--
Gene
19 years, 3 months
I want more CDs in the distribution
by Daryll Strauss
Here's a counter idea for people to chew on. I'd like to see more CDs
in the distribution, I'd just like them all to be less full.
One of the problems we seem to be bumping up against is that although
a personal desktop, a workstation, and a server share a lot of
packages, there's also a lot of packages that are specific to one type
of use or another. Server's typically don't install OpenOffice, and
desktops don't install NetNews servers in most cases.
What if we break the distribution in to more CD's each with fewer
packages more tightly organized around usage. For a made up example:
CD1 & CD2 - Base OS (practically everyone uses)
CD3 - Core Server packages
CD4 - Core Dekstop packages
CD5 - Additional Server packages
CD6 - Additional Desktop packages
CD7 - Really bizarre packages (anything else we include for some reason)
ADVANTAGES:
If I'm installing a basic desktop or basic server I'm downloading
fewer packages.
The installer already seems to handle multiple discs and notifying
the user which ones are needed.
If you're downloading everything the total size really isn't
substantially bigger (just a smidge for ISO overhead)
If you install a minimal version and want to add packages later you
can do that via the Internet anyway. (We should encourage people to do
this if they have broadband)
DISADVANTAGES:
More files to download - I don't think this is an issue
More CDs required for the full distribution - Media costs are small
and you can put it all on one DVD if you really care. This probaby is
an issue for publishers.
More disk swapping to install everything - That's a real drawback,
but since you have to swap disks anyway I'm not sure it's a big deal.
More work categorizing end user usage and arguing over which
packages are in which category. - yes :)
Users need to figure out which disks to download.
>From my point of view that last one is the only one that a big
usability issue. The installer already tells me which disks are
required early on in the process but that's not when you want to find
out. It's just a failsafe. Documentation would help, but we know
people often don't read it. A web script that let a user pick what
packages they want to install and it tells them what discs to get
would be helpful and fairly easy. In reality we want the installer to
get stuff from repositories after the fact, but that's a more major
change.
What do you think?
19 years, 3 months
Current i386 install (boot.iso -> nfs) broken
by Matthias Saou
Hi,
I wanted to test a complete installation of the development tree from start
to end, but after booting off boot.iso and choosing to do a network install
from an nfs server, I got this error after entering the nfs server
parameters :
Traceback with last line being "from _rpm import *" and :
ImportError: libssl.so.4: cannot open shared object file: No such file or
directory
Then the install aborts.
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 3 (Heidelberg) - Linux kernel 2.6.10-1.770_FC3
Load : 0.05 0.11 0.18
19 years, 3 months
Re: fedora-devel-list Digest, Vol 12, Issue 108
by Martin Sevior
> Message: 9
> Date: Mon, 28 Feb 2005 20:32:22 -0500
> From: John Thacker <thacker(a)math.cornell.edu>
> Subject: Re: fedora-devel-list Digest, Vol 12, Issue 104
> To: fedora-devel-list(a)redhat.com
> Message-ID: <20050301013222.GA31096(a)thacker.dyndns.org>
> Content-Type: text/plain; charset="us-ascii"
>
> On Tue, Mar 01, 2005 at 01:18:01PM +1100, Martin Sevior wrote:
> >
> > The AbiWord community is as vibrant as ever. We committed over 300,000
> > LOC of changes to the code base over 14 months to produce AbiWord-2.2.
> > We implemented all sorts of cool stuff that neither MS Word or OOo has.
> > We implemented features that make the users job of creating documents
> > easier and more fun. We want that code to be seen and used and
> > appreciated by as many people as possible. We're in a position to be
> > widely deployed across heterogenic communities like Universities and
> > Schools since we have Windows, Mac and Linux clients.
>
> I otherwise like the program, but it's an incredible PIA for me to use
> because of its absolutely horrible CJK support. So I essentially never
> use it, even though a few years ago Japanese support (on Linux) went from
> "completely unavailable" to "laughably horrible." OOo has very nice,
> mature, professional CJK features.
>
> http://bugzilla.abisource.com/buglist.cgi?keywords=cjk
>
> Now I see that someone made it "not totally suck" on MacOSX recently,
> so maybe there's hope yet for AbiWord.
>
See the post from today.
http://www.abisource.com/mailinglists/abiword-dev/2005/Mar/0002.html
Join in. Be part of the solution. As I said we're a grass roots
organisation that responds to real people with real problems.
We're VERY responsive to people with patches.
AbiWord takes less than 10 minutes to build from scratch on a modern
computer so the threshold for testing stuff is not high. Just testing
and telling us what works for CJK and what doesn't is really useful.
Cheers
Martin
19 years, 3 months
writing zero bytes in bash
by Russell Coker
This message is intentionally sent to the fedora-devel-list and the SE Linux
list not the fedora-selinux-list. It is not related to Fedora specific SE
Linux functionality, but it is related to bash (a core part of Fedora) and SE
Linux kernel code.
To unset the fscreate or exec context you have to write zero bytes
to /proc/self/attr/fscreate or /proc/self/attr/exec respectively.
If you want to do this in a shell script you would do something like:
echo -n "" > /proc/self/attr/fscreate
However that shell command results in bash (both the version in rawhide and
the version in RHEL4) performing the following system calls:
open("/proc/self/attr/exec", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 3
fcntl64(1, F_GETFD) = 0
fcntl64(1, F_DUPFD, 10) = 10
fcntl64(1, F_GETFD) = 0
fcntl64(10, F_SETFD, FD_CLOEXEC) = 0
dup2(3, 1) = 1
close(3) = 0
dup2(10, 1) = 1
fcntl64(10, F_GETFD) = 0x1 (flags FD_CLOEXEC)
close(10) = 0
It opens the file with O_CREAT (so if you were to do `echo -n "" > /tmp/flag`
to create a flag file then it would work as expected), but never calls the
write(2) system call.
To unset the fscreate or exec context you have to call write(fd, X, 0) (the
value of X doesn't seem to matter as the kernel code doesn't dereference it).
It seems likely to me that there may be other bits of kernel code exporting an
interface under /proc where a write of 0 bytes may have a different meaning
to merely opening a file with write access and then closing it.
So it seems reasonable to me to consider this to be a bug in bash where it's
optimisation of shell code results in the action requested by the user not
being performed correctly.
It took a surprising amount of time for me to realise that bash wasn't doing
what I expected of it and ran strace to prove it. I expect that most
sys-admins would take even longer to work it out (if they ever did).
I expect that the bash developers may disagree with this assessment so I would
like some more input on the lists before I file a bug report.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
19 years, 3 months
