RPM and files installed
by Daniel Yek
Hi,
How do I make sure that files created during rpm installation are being
recorded as belonging to the package? I'm not sure, but I think if rpm
%post install script created some symbolic links, they might not be
recorded as installed by the rpm package. (Or are they?)
How RPM keeps track of files created by scripts? Does it trap system calls
to record all created files and symbolic links? If not, what one needs to
do to make sure that all files and symbolic links created are being
accounted for properly?
Thanks.
--
Daniel Yek
17 years, 4 months
Smarter install - Headless
by Jerry Williams
I have noticed that when you boot from the DVD that if you don't do anything
it acts like you hit enter.
How hard would it be to change that to do the following.
Check to see if the system has a keyboard.
If not look for a floppy with ks.cfg on it.
If it finds it act like the user typed: linux ks=floppy
If no floppy, look for usb device and do the same.
Linux ks=usb/ks.cfg kind of thing.
If no usb start network with dhcp and look for
Web server linux ks=http://fedora7.<domain from dhcp>/ks.cfg
Or maybe linux ks=http://fedora7.<domain from dhcp>/<mac address>.cfg
If no web server then run:
Linux vnc vncpassword=Fedora7
If it has a keyboard just do the normal thing.
This would make it so you don't really have to change the dhcp server.
Maybe add an alias for a web server.
Then the install would happen and when completed would eject DVD.
Take out the DVD and power cycle the box and be done.
17 years, 4 months
Fedora 7
by Bill Nottingham
It's time to bite the bullet.
There will be no more releases of Fedora Core or Fedora Extras.
Wait! Where are you going? Come back!
I'm serious. We've talked all along about how there should be
no differences in how packages are treated whether they are
in Core, or they are in Extras; no differences depending on who
maintains the package. The best solution to this?
Eliminate the distinction between Core and Extras entirely.
Starting with Fedora 7, there is no more Core, and no more Extras;
there is only Fedora. One single repository, built in the community
on open source tools, assembled into whatever spins the Fedora community
desires.
Are we there yet right now? No. There's a lot of work to be done,
and we're looking for help. What's left of the Core Steering Committee
is going to work with the Fedora Board and FESCO to figure out just
how this new combined repository is going to be governed and managed.
In the meantime, just because we're not going to have a release of
Core or Extras doesn't mean we're not going to have a release.
Hence, Fedora 7. Name TBD, but probably not 'Bride of Zod'.
http://fedoraproject.org/wiki/Releases/7
The current schedule is:
23 January 2007 | F7 Test1 development freeze
30 January 2007 | F7 Test1 Release
20 February 2007 | F7 FEATURE Freeze
| F7 string freeze
| F7 Test2 development freeze
27 February 2007 | F7 Test2 release
19 March 2007 | F7 translation freeze
| F7 Test3 development freeze
26 March 2007 | F7 Test3 release
... Continual freeze. Only critical bugs fixed ...
5 April 2007 | Final devel freeze.
26 April 2007 | F7 General Availability
And, what would a release be without features. We've identified
28 features that we'd like to include in the release, available
at http://fedoraproject.org/wiki/Releases/7/Features:
- Modify the build system to support this new paradigm
- Merge Core and Extras in source control
- Use the new pungi tool to spin all releases
- A Fedora Desktop spin
- A Fedora Server spin
- A Fedora KDE spin
- Make LiveCDs as a part of the distribution release process
- Ability to customize non-packaging distrubution parameters
- Switch to libata drivers for PATA support
- Speedup of bootup and shutdown
- Make wireless rock-solid
- Add wireless firmware for all the chipsets we can
- CodecBuddy
- Fixing the proliferation of dictionary packages
- Support encrypted filesystems
- Fast user switching in the desktop
- Fix the firewire stack
- Switch to a tickless kernel by default
- Fix unnecessary wakeups across the distribution
- Add KVM virtualization support to our tools
- Investigate (but probably don't switch to) new init technologies
- Add the nouveau drivers for nVidia cards
- Speed up Yum and RPM
- Add support for RandR 1.2
- Switch to syslog-ng
- Make the update system useable by all
More information on each of these features is available on the
wiki, including responsible people and plans. If you'd like to
chip in on these features, please, do!
If you've got new features you'd like to add, and you are willing
to do the work, or have the ability to get others to do the work
for you, we can add them too. Note that Test2 is the feature freeze.
Here's to making Fedora 7 the best release yet!
Bill
17 years, 4 months
Build rescue image for USB sticks
by Ralf Ertzinger
Hi.
How much work would be involved to create a rescue image that could be
written to an USB flash drive (like the one in os/images/diskboot.img),
so that a complete rescue system could be booted from the stick, without
need for network access?
USB media are pretty cheap these days :)
17 years, 4 months
Fedora Core 7 - Compiz vs Beryl
by Otto Rey
What do you think about to replace Compiz with Beryl, and merge "Desktop Effects" with "Beryl Manager" in FC7?
My vote: +1
Otto Rey
__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar
17 years, 4 months
Fedora for UMPC, tablets, PDA etc. ?
by Anuj Verma (Kevin)
Hello
Reading the below(bottom) mentioned story I am curious to know more
point of views, "FC6 shrunk to 150MB" !
This time while Fedora 7, is being planned and discussed and while UMPC
is getting lot popular, I am just curious to know point of views here,
if this is a good time for Fedora to also host a UMPC project ?
Does it seems Fedora be good for UMPC types example, Orgami, Nokai 770/800 etc.
Hoping that the lessons and improvements gained out of OLPC can be put
out for a wider community cattering, development & cross pollination.
Regards,
Kevin
--
http://www.linuxtoday.com/infrastructure/2007010902326NWHWEV
"The software is based on Fedora Cora 6, put on an diet to reduce it to
150 MB, and leverages Python heavily. According to Bletsas, both
Microsoft (WinCE) and Apple (OS X) offered their operating systems, but
neither fit the footprint or security requirements that the XO demanded.
In addition, the closed-source nature of those operating systems wasn't
a good fit to the OLPC philosophy.
The application environment looks nothing like a typical X-Window GUI
that you or I have ever seen. Written menus are totally replaced with
icons. In one example screen, the child can view all the other meshed
XOs around them (the mesh is good point to point to about 600 meters),
and see what activities the other children are involved in. Almost all
activities can be done collaboratively. So, for example, multiple
children can work on the same document or browse the web together. The
distributions are fully open source, and can be downloaded and played
with now at laptop.org. Also included will be a Gecko-based browser that
Bletsas told me should be capable of displaying Flash-enabled web
pages."
17 years, 4 months
Fwd: Outage tonight
by Mike McGrath
Outage tonight (see below). This will effect pretty much everything
except the wiki and torrents.
-Mike
---------- Forwarded message ----------
From: Stacy J. Brandenburg
Date: Jan 16, 2007 8:07 AM
Subject: Outage tonight
To: Fedora Infrastructure <fedora-infrastructure-list(a)redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am not sure if anyone has let you know or not yet, but we have a
planned outage of all services in the DC tonight. It starts at 9:00p
Eastern and lasts for up to 6 hours.
This will affect www.redhat.com, rhn.redhat.com, and all of the fedora
infrastructure.
I hope it will not really be 6 hours. I am applying a microcode upgrade
to some of the blades in the 65xx chassis as well as installing 2 new
border routers.
Please be patient tonight. If you notice any problems after the window,
please let me know via email and I will take a look.
Thanks,
17 years, 4 months
rawhide report: 20070116 changes
by Build System
Removed package diskdumputils
Removed package netdump
Updated Packages:
arpwatch-14:2.1a15-3.fc7
------------------------
device-mapper-multipath-0.4.7-9.fc7
-----------------------------------
* Mon Jan 15 2007 Benjamin Marzinksi <bmarzins(a)redhat.com> - 0.4.7-9.fc7
- Fixed spec file.
* Mon Jan 15 2007 Benjamin Marzinski <bmarzins(a)redhat.com> - 0.4.7-8.fc7
- Update to latest code (t0_4_7_head2)
* Wed Dec 13 2006 Benjamin Marzinski <bmarzins(a)redhat.com> - 0.4.7-7.fc7
- Update to latest code (t0_4_7_head1)
gawk-3.1.5-14.fc7
-----------------
* Mon Jan 15 2007 Karel Zak <kzak(a)redhat.com> 3.1.5-14
- sync with double-free upstream fixes
- fix #222531: Replace dist by ?dist
gdb-6.5-27.fc7
--------------
* Mon Jan 15 2007 Jan Kratochvil <jan.kratochvil(a)redhat.com> - 6.5-27
- Fix the testsuite results broken in 6.5-26, stop invalid testsuite runs.
* Sat Jan 13 2007 Jan Kratochvil <jan.kratochvil(a)redhat.com> - 6.5-26
- Fix unwinding of non-debug (.eh_frame) PPC code, Andreas Schwab (BZ 140532).
- Fix unwinding of debug (.debug_frame) PPC code, workaround GCC (BZ 140532).
- Fix missing testsuite .log output of testcases using get_compiler_info().
* Fri Jan 12 2007 Jan Kratochvil <jan.kratochvil(a)redhat.com> - 6.5-25
- Fix unwinding of non-CFI (w/o debuginfo) PPC code by recent GCC (BZ 140532).
gnucash-2.0.4-1.fc6
-------------------
* Mon Jan 08 2007 Bill Nottingham <notting(a)redhat.com> - 2.0.4-1
- update to 2.0.4
gzip-1.3.9-1.fc7
----------------
* Mon Jan 15 2007 Ivana Varekova <varekova(a)redhat.com> 1.3.9-1
- rebuild to 1.3.9
- spec cleanup
libselinux-1.33.4-3.fc7
-----------------------
* Mon Jan 15 2007 Dan Walsh <dwalsh(a)redhat.com> - 1.33.4-3
- Add Ulrich NSCD__GETSERV and NSCD__SHMEMGRP for Uli
libwmf-0.2.8.4-12
-----------------
* Tue Jan 16 2007 Caolan McNamara <caolanm(a)redhat.com> 0.2.8.4-12
- Resolves: rhbz#222734 no need for Makefiles in doc dirs
logwatch-7.3.2-3.fc7
--------------------
* Tue Jan 16 2007 Ivana Varekova <varekova(a)redhat.com> 7.3.2-3
- Resolves: 222263
sshd script problem
parted-1.8.2-1.fc7
------------------
* Fri Jan 12 2007 David Cantrell <dcantrell(a)redhat.com> - 1.8.2-1
- Upgrade to GNU parted-1.8.2
pyparted-1.8.3-1.fc7
--------------------
* Fri Jan 12 2007 David Cantrell <dcantrell(a)redhat.com> - 1.8.3-1
- Required parted-1.8.2 or higher
system-config-printer-0.7.48-1.fc7
----------------------------------
* Mon Jan 15 2007 Tim Waugh <twaugh(a)redhat.com> 0.7.48-1
- 0.7.48:
- Updated translations.
system-config-samba-1.2.39-1.fc7
--------------------------------
* Mon Jan 15 2007 Nils Philippsen <nphilipp(a)redhat.com> - 1.2.39
- handle synonyms and inverted synonyms gracefully (#222595)
vnc-4.1.2-10.fc7
----------------
* Mon Jan 15 2007 Adam Tkac <atkac redhat com> 4.1.2-10.fc7
- fixed render crashing when run in 8bpp
w3m-0.5.1-15.fc6
----------------
* Mon Jan 15 2007 Parag Nemade <pnemade(a)redhat.com> - 0.5.1-15
- Resolves: rh#221484
wireshark-0.99.5-0.pre2.fc7
---------------------------
* Mon Jan 15 2007 Radek Vokal <rvokal(a)redhat.com> 0.99.5-0.pre2
- another 0.99.5 prerelease, fix build bug and pie flags
Broken deps for ia64
----------------------------------------------------------
mkinitrd - 6.0.6-1.ia64 requires libparted-1.8.so.0()(64bit)
nash - 6.0.6-1.ia64 requires libparted-1.8.so.0()(64bit)
Broken deps for ppc64
----------------------------------------------------------
mkinitrd - 6.0.6-1.ppc64 requires libparted-1.8.so.0()(64bit)
nash - 6.0.6-1.ppc64 requires libparted-1.8.so.0()(64bit)
Broken deps for s390
----------------------------------------------------------
mkinitrd - 6.0.6-1.s390 requires libparted-1.8.so.0
nash - 6.0.6-1.s390 requires libparted-1.8.so.0
systemtap - 0.5.10-1.fc7.s390 requires kernel >= 0:2.6.9-11
systemtap-runtime - 0.5.10-1.fc7.s390 requires kernel >= 0:2.6.9-11
Broken deps for s390x
----------------------------------------------------------
mkinitrd - 6.0.6-1.s390x requires libparted-1.8.so.0()(64bit)
nash - 6.0.6-1.s390x requires libparted-1.8.so.0()(64bit)
nash - 6.0.6-1.s390 requires libparted-1.8.so.0
Broken deps for i386
----------------------------------------------------------
mkinitrd - 6.0.6-1.i386 requires libparted-1.8.so.0
nash - 6.0.6-1.i386 requires libparted-1.8.so.0
Broken deps for ppc
----------------------------------------------------------
mkinitrd - 6.0.6-1.ppc requires libparted-1.8.so.0
nash - 6.0.6-1.ppc requires libparted-1.8.so.0
Broken deps for x86_64
----------------------------------------------------------
mkinitrd - 6.0.6-1.x86_64 requires libparted-1.8.so.0()(64bit)
nash - 6.0.6-1.i386 requires libparted-1.8.so.0
nash - 6.0.6-1.x86_64 requires libparted-1.8.so.0()(64bit)
17 years, 4 months
proposal: mailing list reorganization
by Thorsten Leemhuis
Hi all!
Find below a proposal for a mailing list reorganization the board asked
me to work on. It can also be found in the wiki at
http://www.fedoraproject.org/wiki/ThorstenLeemhuis/MailingListReorganization
and until now was only discussed slightly on the semi-private on
fedora-advisory-board. This is the first public discussion. Happy flamefest!
CU
thl
P.S.: We want to create the fedora-qa list (without the "-list" postfix
-- see the end of the document) quite soon (early next week!). If you
really dislike that part yell *now*. The other stuff will at least get a
second public discussion.
###############################
= Mailing list reorganization =
A lot of people yelled "there are to many mailing lists; that is
contra-productive and leads to a lot of confusion" (this is the short
explanation without all the boring details). Thus the idea came up to
revisit the Fedora mailing lists that got created in the past years
since Fedora was born and do some adjustments. That means mainly: shut
some down and adjust the usage model of some others. That's needed in
parts for the Core and Extras merge in any case. This will be a really
complex task and we won't make everybody happy with it, but we hope to
improve the situations.
The Fedora Board asked me, ThorstenLeemhuis (thl), to drive this task.
You can find my proposal below, comments appreciated. Feel free to write
a counter proposal if you think I did stuff (totally) wrong or if you
think I ignored your comments (I read them all, but as I wrote: we can't
make everyone happy -- but I'm trying my best to find a compromise thats
better that what we have today and is acceptable for most of us).
----
= Main end Goal =
The details how this goal is going to achieved can be found below, but
here is a quick summary for those that don#t care about the details.
The other goal is to get rid of those lists:
* fedora-devel-list
* fedora-maintainers
* fedora-extras-list
* fedora-test-list
* fedora-triage-list
* fedora-extras-commits
* fedora-desktop-list
* fedora-extras-steering
* fedora-dsco-list
In parallel we create some new:
* fedora-devel -- For devel discussion. The "old" fedora-devel-list
became quite noise and we want to avoid that with the new list. Thus the
plan is to restrict it to well known open-source or project contributors
and make it moderated for the rest of the world. Support questions
regarding devel stuff are off topic here.
* fedora-devel-discuss -- We need an open devel list for users as
fedora-devel is restricted. Support questions regarding devel stuff are
on topic here, too.
* fedora-qa -- for wwoods and the QA group
* fedora-project -- for discussions about the project as a whole that
in the past often happend on the moderated/semi-closed
fedora-advisory-board list (that will stay for now and hopefully gets
removed in the long term).
= Details how to achieve that end-goal =
Some lists get renamed (users thus don't have to care about
re-subscribing) and sone get closed.
== Shut down ==
Meaning: Send a EOL message with some informations to the list and
disallow further postings. Archieves remain accessible. Users get
pointed to the new lists.
=== fedora-extras-list ===
Well, the "Core packages gets merged into the Extras framework" is
official. The name "Extras" get obsolete by that and thus this list
becomes obsolete. Users get pointed to two different lists instead:
* topics regarding maintaining packages in the repo go to fedora-devel
* questions regarding packaging and the guidlines around it shall be
send to fedora-packaging in the future
=== fedora-test-list ===
A lot of people never got the difference between fedora-devel and
fedora-test list and ask users support questions on fedora-devel. One of
the reasons for this is that it was not obvious what "testing" means.
Another reason: we answered those users question on fedora-devel, even
if they were not on topic (and thus users asked again and again). And
the topics for -devel and -test are to similar; sometimes the same
things get discussed in parallel on both lists. Users get pointed to
fedora-devel-discuss instead.
=== fedora-triage-list ===
Not used much anymore. Users ge pointed to fedora-qa-list instead (see
below).
=== fedora-extras-commits ===
No difference between core and extras anymore. Send the stuff to
fedora-cvs-commits in the future. (see below)
=== fedora-extras-steering ===
No FESCo anymore in the future, no private list for it anymore. An new
list will be create for the FESCo successor when that got decided.
=== fedora-desktop-list ===
Not much traffic, seems the project has not much need for a dedicated
list atm. If that changes again in the future create
fedora-devel-desktop, to make its usage more obvious.
=== fedora-dsco-list ===
Not much traffic and it seems the Fedora Documentation Steering
Committee agreeds to close this list.
----
== Create ==
We need some new lists, too.
=== fedora-qa ===
Create a fedora-qa to be used by wwoods efforts and his recruits. Will
be created quite soon, probably before this discussion is finished,
because the QA group asked for it quite some time ago already. Will get
a seperate "topic" on the list where the qa-reports will get send; users
then can subscribe to the qa-list, but can choose if they want to get
the automatic reports..
=== fedora-project ===
We until now have no real list where Ambassadors, packagers,
programmers, art-people and other contributors can talk to each other
about general stuff that's important to the project as a whole without
getting lost in the noise or scared away with "this is off topic on this
list" calls. fedora-advisory-board somehow was this list until now in
parts, but it's moderated and thus even some project contributors that
were not subscribed feel excluded (bad).
Summaries from the project meetings (Ambassadors, Infrastructure, FESCo
successor) shall get send to the list so people know what's going on in
the project as a whole.
=== fedora-maintainers-announce ===
Created already, but not used until now. This is not a real mailing list
for discussion, it's rather meant as a way to get really important
information (policy changes, announcements for mass rebuilds, ...) out
to all maintainers -- e.g. low traffic, normally less then 3-5 mails a
months. The plan is to subscribe users semi-automatically from the
accounts system to make sure we reach everyone.
Some people question the use of this list; they want people subscribed
to fedora-maintainers instead. But important informations can get lost
there in the noise easily, and that would be bad. And some of our
maintainers (e.g. upstream maintainers that co-maintain the fedora
package) are not interested in all those discussions that happened on
fedora-maintainers in the past.
Reply-to of this list will be set to fedora-devel; that list will also
get subscribed to fedora-maintainers-announce. Users can't unsubscribe
manually from fedora-maintainers-announce list -- being on it is
mandatory for all package contributors.
----
== Change policy ==
=== fedora-advisory-board ===
The list remains for now, but we want to move most of the discussion
into the wider public. fedora-project should thus be used for most of
the stuff that got discussed on fedora-advisory-board in the past. But
the advisory-list will remain for the purpose it was created for: a
communication channel between important project contributors. We'll
close it later if we notice that this is not needed anymore (that what
some people hope)
=== fedora-cvs-commits ===
All commits should go here, but separated into topics (web, docs, F7,
devel, ...), similar how we do it for how we do for
fedora-packaging-announce
----
== Rename ==
=== fedora-devel-list to fedora-devel-discuss ===
fedora-devel-discuss shall to a major part replace fedora-test-list an
fedora-devel. Users can help each other here (and developers should
keep any eye on it his list, too) if they have problems with running
development or testing-channels. They can also discuss Fedora
development there freely.
=== fedora-maintainers to fedora-devel ===
Rename to fedora-devel. Free to post for all fedora contributors (being
in ambassadors, mentors, packagers, ...). Moderated for the rest of the
world (we need a whole team of moderators for it). Be liberal and allow
good-guys to post without being moderated, even if they are no
fedora-contributors; that includes:
* people that are well know and active in open-source land somewhere
* people who work on upstream apps we package
* people that have shown to be constructive after their posts got
moderated for a while
Enforce the devel topics and never ever answer support questions on that
list -> those are on topic for fedora-devel-users.
=== fedora-laptop-list ===
Rename to fedora-hardware. Some people suggested to get rid of this
completely, but having a dedicated list for hardware issues might be
acceptable.
----
== Not sure ==
There are some list where I'm not sure if we still need them and/or need
to adjust their policy.
=== fedora-list ===
This is mostly a list where users help he other. fedora-users would thus
be a proper name that would make its use obvious.
=== Others ===
Some people questioned the needs for these lists.
* fedora-games-list
* fedora-r-devel-list
* fedora-art
* fedora-xen
* fedora-websites
Ask the list-maintainers if separate lists really make sense for these
topics. fedora-games-list for example
----
== Miscellaneous ==
=== Mailman guidelines ===
While at it let's define a standard look-and-feel for mailing lists,
too. (FIXME: some mailman experts around? Is this sane?). Mailing list
admins are strongly encouraged to follow this guidelines, but they don't
have to if there are good reason for it (no, "I don't like it" is not a
good reason!). Suggested setting (can all be found on the first mailman
settings page)
* the reply-to should not be modified by mailman (first_strip_reply_to
= no)
* the reply-to should point to the list (reply_goes_to_list = this list)
* no explicit Reply-to-Address (reply_to_address = <empty> )
* no tagging (subject_prefix = <empty> )
=== Legacy ===
Jesse will close fedora-legacy and fedora-legacy-announce in the near
future.
=== To -list or not to list ===
Some of our mailing lists have the "-list" postfix, other not. I think
all new lists should be created without it.
=== rawhide reports ===
We create another channel in fedora-package-announce where those kind of
reports get mailed to. Don't send them to any other lists.
Side note: A channel for the important packages might be helpful,
because the reports will get quite long in the future after the extras
and core merge. How about a channel that lists only changes in packages
that are part of our most important spins Gnome, KDE and Server?
== Notes ==
Ubuntu has similar problems; they splitted ubuntu-devel into
ubuntu-devel and ubuntu-devel-discuss:
https://lists.ubuntu.com/archives/ubuntu-devel/2006-December/023022.html
EOF
17 years, 4 months
yum roll back option?
by Jerry Williams
Since there has been a lot of talk about servers.
I was wondering about a way to recover back to a previous working system.
The yum updates that I installed today broke my 3c590 network card.
I can look at /var/log/yum.log and see what was installed, but I am not sure
what versions I had before that.
I ended up swapping the network card with a 3c905 card and it works okay.
The only thing I can think to do is do a rpm -qa >rpm.txt before I run yum
and then one after so I can do a diff on the files and know what the
previous version was.
On other unix boxes I work on there is the option to save files that are
replaced and then you can clean that out after you know things are working.
Or if things don't work you can put those files back.
Also might be nice to change the yum.log to show what version was updated to
the new version instead of just what the new version is.
Example:
/var/log/yum.log
Jan 12 19:59:10 Updated: tar.i386 2:1.15.1-24.fc6
Would look like:
Jan 12 19:59:10 Updated: tar.i386 1.15.1-23.fc6 2:1.15.1-24.fc6
17 years, 4 months
