Self-Introduction: Jose Pedro Oliveira
by Jose Pedro Oliveira
1. Full Legal Name: José Pedro Garcia de Oliveira
2. Country, City: Portugal, Braga
3. Profession: Teaching Assistant
4. University: Universidade do Minho
5. Goals in the Fedora Project
Maintain the syslog-ng/libol specfiles.
- Which packages do you want to see published?
Network and system administration related
(eg: Nagios, Snort, ...)
- Do you want to do QA?
Yes.
6. Historical qualifications
Worked as a Software Engineer in the industry.
- Computer languages:
Present: Perl, C
Past: SqlWindows, Visual Basic, Pascal, C++,
Assembly (80x86, Z80, 8051), Prolog,
- Other skills:
System administration
7. GPG KEYID and fingerprint
pub 1024D/91BD851B 2003-08-07 Jose Pedro Oliveira <jpo(a)di.uminho.pt>
Key fingerprint = F9B6 8D87 859D 1C94 48F0 84C0 9749 9EB5 91BD 851B
jpo
--
José Pedro Oliveira
* gpg fingerprint = F9B6 8D87 859D 1C94 48F0 84C0 9749 9EB5 91BD 851B *
20 years, 1 month
Building 2.6 kernels on FC1
by Michel Alexandre Salim
Hi all,
I have been trying to track down the problems with my Firewire external
drive unit, and thought I would try building a 2.6.3 kernel using Red
Hat's spec for UP i686 on FC1, using gcc32 and gcc 3.3, and copy the
result over.
The result, simply said, is interesting. This is taken using 2.6.3-mm3
with gcc 3.3, but other results are similar.
/lib/modules/linux-2.6.3-mm3: 376 MB
linux-2.6.3-mm3 build directory: 1.4G
linux-2.6.3-mm3/arch/i386/boot/bzImage: 1.5M
saying those were a bit on the large size would be a bit of an
understatement..
it turns out make modules_install is doing bizarre things; a listing of
kernel/drivers/acpi does this for instance:
total 1768
-rw-r--r-- 1 root root 7938 Feb 24 23:58 ac.c
-rw-r--r-- 1 root root 185294 Feb 24 23:58 ac.ko
-rw-r--r-- 1 root root 33213 Feb 24 23:58 asus_acpi.c
-rw-r--r-- 1 root root 204759 Feb 24 23:58 asus_acpi.ko
-rw-r--r-- 1 root root 20347 Feb 24 23:58 battery.c
-rw-r--r-- 1 root root 194175 Feb 24 23:58 battery.ko
-rw-r--r-- 1 root root 13126 Feb 24 23:58 button.c
-rw-r--r-- 1 root root 187411 Feb 24 23:58 button.ko
-rw-r--r-- 1 root root 6658 Feb 24 23:58 fan.c
-rw-r--r-- 1 root root 183526 Feb 24 23:58 fan.ko
-rw-r--r-- 1 root root 61229 Feb 24 23:59 processor.c
-rw-r--r-- 1 root root 240387 Feb 24 23:59 processor.ko
-rw-r--r-- 1 root root 35245 Feb 25 00:00 thermal.c
-rw-r--r-- 1 root root 206273 Feb 25 00:00 thermal.ko
-rw-r--r-- 1 root root 13610 Feb 25 00:00 toshiba_acpi.c
-rw-r--r-- 1 root root 189128 Feb 25 00:00 toshiba_acpi.ko
1) .c source files are installed
2) size bloat of an order of magnitude
I will try rebuilding the Fedora kernel next - on FC1 and FC2-devel,
gcc32 and gcc 3.3. Which reminds me - why does the kernel Makefile
define both HOSTCC and HOSTCXX ? IIRC the kernel contains zero LOC of C+
+.
Thanks,
- Michel
20 years, 1 month
(fwd) Perl/mod_perl test update
by Chip Turner
The perl update includes the virtual provides for perl modules to use
to rely on when they are built against it as discussed a couple weeks
ago. Anyone who can give this a whirl and let me know any breakages,
I'd appreciate it; should be a fairly safe update but I want to get
5.8.3 on all supported RHL/RHEL/Fedora releases that are currently in
the 5.8.x family.
Thanks,
Chip
--
Chip Turner cturner(a)redhat.com
Red Hat, Inc.
20 years, 1 month
chown xxx.yyy is now rejected
by Tim Waugh
The 'chown xxx.yyy' syntax has been deprecated for several releases
now, the correct syntax being 'chown xxx:yyy'.
The newly released stable version of coreutils, 5.2.0, now rejects the
old syntax unless _POSIX2_VERSION=199209 is found in the environment.
I have updated the spec files (in CVS HEAD) for all of the RPM
packages that I found using the old syntax, but I have not rebuilt
them. They will be rebuilt shortly -- I have notified the package
owners.
Once everything is settled down, perhaps we will be able to remove the
restriction that prevents user names containing '.'.
See also:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116536
Tim.
*/
20 years, 1 month
more borken deps
by Jurgen Botz
In current development dir...
* redhat-lsb requires /usr/bin/kill, which no longer exists because
it has been moved from coreutils to util-linux where it seems to
be /bin/kill
* gstreamer lib is updated but gnome-media, nautilus-media and
rhythmbox still require the old lib
--
Jürgen Botz | While differing widely in the various
jurgen(a)botz.org | little bits we know, in our infinite
| ignorance we are all equal. -Karl Popper
20 years, 1 month
rawhide report: 20040229 changes
by Build System
Updated Packages:
bind-9.2.3-8
------------
* Sat Feb 28 2004 Florian La Roche <Florian.LaRoche(a)redhat.de>
- run ldconfig for libs subrpm
* Mon Feb 23 2004 Tim Waugh <twaugh(a)redhat.com>
- Use ':' instead of '.' as separator for chown.
im-sdk-11.4-21
--------------
* Sun Feb 29 2004 Florian La Roche <Florian.LaRoche(a)redhat.de>
- mv /etc/init.d -> /etc/rc.d/init.d
* Fri Feb 27 2004 Jens Petersen <petersen(a)redhat.com> - 1:11.4-20
- make iiimf-server obsolete im-sdk
rpmdb-fedora-1.90-0.20040229
----------------------------
udev-018-2
----------
* Sun Feb 29 2004 Florian La Roche <Florian.LaRoche(a)redhat.de>
- move chkconv to preun
- nicer url
yum-2.0.5.20040224-2
--------------------
* Thu Feb 26 2004 Florian La Roche <Florian.LaRoche(a)redhat.de>
- mv /etc/init.d -> /etc/rc.d/init.d
20 years, 1 month
HI! New Project
by alexluca@inwind.it
Hi guy! I'm Luca Ferrari, an Italian fedora translator.
Using Fedora and its desktop-oriented I think one thing:
why don't we create an animated introduction that runs at the first
boot, where you can look the news, the features, the principal
functions... of Fedora (a little bit like WindowsXP or Lindows)?
I think that it will a great surprise!
What do you think? I had a reviews: go to
http://luka4e.fedoraitalia.org/ and look: what do you think about it?
There is a preview with a firstboot style at
http://luka4e.fedoraitalia.org/intro
BYE!!!!!! And answer!
20 years, 1 month
up2date, system-config-packages and synaptic
by David Wagoner
My question here is why is the fedora team wasting so
much time developing up2date and
system-config-packages when synaptic is already an
excellent replacement. Even though it uses apt, worst
case would be to get the latest source and code in
support for yum then. I have had nothing but problems
with up2date. I have had packages fail to install and
yet appear to be installed as far as up2date is
concerned, system-config-packages though its getting
better still has a ways to go before it has the
features that synaptic has. If the developers choose
to continue to use up2date and system-config-packages,
I will continue to use the products during the rest of
the test phase but when Fedora Core 2 is released I
plan on switching to synaptic. Synaptic is full of
features, stable and fast. I look foward to seeing
what everyone has to say on this subject.
__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
20 years, 1 month
Fedora.us QA (was: Re: Prelink success story :))
by Jef Spaleta
Toshio wrote:
> Jef, how would you feel if some bug day we had experienced QA'ers team
> with new QA'ers to nitpick packages? This could be a good first or
> second time QA experience: irc with a more experienced QA'er and pick
> apart the good and bad of a package. Or we could assemble a team of
> experienced QA'ers to do second reviews once a new user did the first
> one. This could be useful for a more advanced QA'er. Kinda have a
> short apprenticeship followed by a test what you know phase.
I strongly believe that a mentoring concept, can help the larger Fedora
effort turn users into contributors, better than that, creating
contributors and building a body of shared best practices through a
process of continuous self-examination of the process. Who learns more
about the subject when a lesson is taught...the teacher or the student?
Often times it can be the teacher. At least that's what I think.
But I am wary of doing exactly the sort of thing you have suggested..
prematurely. I really want to make sure there is a large enough group of
DEDICATED apprentice QA'ers to make sure the veterans do not feel like
making time to hold exactly that sort of irc session is a waste of their
time. I want to make sure the first one i weasel people into
participating in is worthwhile enough to build momentum and continued
interest in holding such events.
And frankly...i was waiting for someone else to suggest it....
because I don't think I have time to be the only community volunteer
thinking about and heading up exactly these sorts of experiments in
bridge building (and i would argue Red Hat as a managing entity needs to
hire someone, actually trained in exactly this sort of volunteer
management/coordination for these sorts of ideas to not fall through the
cracks and get lost). Let me state an essential truth, a lot of how
things are going to work in the new "fedora community" is about people
taking the initiative to state an idea AND follow through with it.
Basically...if you suggest an idea...you sort of own it..unless you are
clever and sneaky enough to convince someone else to take ownership of
the idea. I think your post proves I am clever and sneaky enough.....
> What I would like to see (for both QA and packager) is an RPM Best
> Practices Handbook. Accumulated wisdom about how to do things well
> organized by use cases with in depth justifications available as side
> passages for those who are curious why %{buildroot} and
> ${RPM_BUILD_ROOT} have such strong proponents on each side :-)
As interesting as this sounds as a historical non-fiction thriller novel
that I'd buy at the bookstore...i don't know how useful this would be to
a new QA'er. It would have some worth for the historical record....but
not much use as a functional educational document that re-enforces a
working process.
Let me instead suggest that what might be instructive are SHORT...
"anatomies of a QA review" case examples. A few good and a few bad
reviews that can highlight common issues...and that can suggest a
general flow of how things are suppose to work. A good example of this
sort of thing..is the Gnome Bugsquads triage examples.
http://developer.gnome.org/projects/bugsquad/triage/examples.html
I'd point to fedora triage examples...but we haven't gotten that far
yet. In fact, i could probably argue that building a set of case
examples would be VERY instructive to a small group apprentice QA'ers
almost as instructive as an active irc session with old-timers. And I
would argue that working on such a set of case examples would show a
level of dedication that might encourage established QA'ers to spend
time communicating more closely...which is what you sort of wanted in
the first place.
-jef"things would just go smoother if everyone would just agree now to
do my bidding without question or comment"spaleta
20 years, 1 month