A fuse based initfs
by Jon Nettleton
This all started with a some what simple task. I wanted to start rhgb/gdm
as early in the boot process as possible. Basically kernel->disk->gui. How
hard could it be? Well not fun really. My finally solution, which is
unacceptable for fedora right now is patching the kernel with unionfs and
using that as an overlay for /var and /tmp. That gave me the transparent
filesystem overlay I needed to be able to start up a nice gui and allow
things like fsck to happen underneath without disturbing things. Even with
this solution I still don't have init restarting gdm if it dies.
So I thought, and discarded and thought some more. Now I want anyone
willing to comment on my thoughts.
My proposal is a user-land based filesystem that is specifically built to
work with sysvinit to give it more functionality without changing it. You
want a standard sysvinit Unix boot just don't pass a parameter to the kernel
commandline, no problemo. However, with it enabled you would
"theoretically" get the following.
1) Basic cached ram overlay. This could possibly be used to replace our
readahead scripts for disk caching. The more immediate need is a temporary
ram file-system to allow system processes to write logs, status, pipes to
before we have had a chance to verify disk integrity. This should get us
the ability to provide nice X based gui tools for first boot, system
recovery, and possibly encryption unlocking.
2) Better init logging. With /var writable ( at-least in ram ) we can
start syslog nice and early.
Just those two things give us a nicer gui boot screen and possibly cut the
time of launching X twice off our boot sequence. Now we go one step
further.
3) We use the abstraction layer to manipulate the startup scripts that init
sees in /etc/rcX.d .
This would require
A) Netlink support. Do we or don't we have a network interface. If
we don't then automatically remove all network
dependant services from init. If Network comes up later in the
process and init is still running ( we know that
because we can keep track of /var/lock/subsys ) the filesystem
re-adds them later in the process.
B) General dependencies. Like I mentioned we can keep track of what
has started using /var/lock/subsys or
/var/run. If Something fails remove the dependent scripts out
of the way so init doesn't try to start them.
C) Ability to maximize IO throughput. Well this is just a thought.
Right now we see one of the major bottlenecks
in our init process as overloading the IO subsystem. With an
intelligent read only overlay we could do basic
metrics and possibly wait a second longer to start the next
process knowing it will shorten the time to launch
the next service by 2 seconds. I have no proof this will work,
but after looking at those bootchart graphs
enough some crazy ideas cross your mind.
4) After the init process is done, the filesystem flushes itself to the
lower layer writables disks and disappears.
First, sorry if this is wrapped horribly. I am using gmail and it doesn't
lend itself to formatting long mails like this.
Second, Let's talk about it. Like I said this just came to my mind as
something that doesn't exist, and might possibly help us build a better
system around what we already have.
Jon
16 years, 10 months
rebuild fails, previous build worked, c open macro bug?
by Till Maas
Aloas,
one of my packages does not want to be built, the error message is:
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -D_FILE_OFFSET_BITS=64 -D_REVISION=`./evalrev`
src/aireplay-ng.c src/common.c src/crc.c -o aireplay-ng
src/aireplay-ng.c: In function 'open_sysnofcs':
src/aireplay-ng.c:327: error: size of array '__open_missing_mode' is negative
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -D_FILE_OFFSET_BITS=64 -D_REVISION=`./evalrev`
src/airodump-ng.c src/common.c -o airodump-ng
The package built the last time I built it[1], but now[2] it does not. Is this
fallout from the change of the open function, too? When someone knows how to
fix this, please send me a patch or apply it to cvs when I do not respond to
it tomorrow, because I am on vacation beginning on Saturday.
Regards,
Till
[1] http://koji.fedoraproject.org/koji/getfile?taskID=51682&name=build.log
[2] http://koji.fedoraproject.org/koji/getfile?taskID=122290&name=build.log
16 years, 10 months
cssed license question
by Rafał Psota
Cssed is under GPLv2+, but some part of code is under this license
http://scintilla.sourceforge.net/License.txt :
"License for Scintilla and SciTE
Copyright 1998-2003 by Neil Hodgson <neilh(a)scintilla.org>
All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation.
NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS, IN NO EVENT SHALL NEIL HODGSON BE LIABLE FOR ANY
SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE
OR PERFORMANCE OF THIS SOFTWARE. "
What should I use in the License tag?
16 years, 10 months
Re: Fedora Crypto Consolidation Project
by Rich Megginson
On Thu, 23 Aug 2007 at 12:23:36 +0100, Joe Orton wrote:
> On Wed, Aug 22, 2007 at 05:51:20PM -0700, Robert Relyea wrote:
> > Steve Grubb wrote:
> > >I wanted to announce a new Fedora Project that will span several distro
> > >releases and outline the reasons why we are starting this project. I
> > >believe this issue affects the whole Open Source Community. But don't
> > >think anyone has explained all the issues.
> >
> > >We're looking for people interested in enabling NSS in their packages and
> > >feeding the changes upstream.
> > >
> > A list of packages that need to be looked at can now be found at:
> > https://fedoraproject.org/wiki/CryptoConsolidationScorecard
>
> Switching OpenLDAP to use NSS may be painful because of the exposure of
> the SSL_CTX * in the API via LDAP_OPT_X_TLS_CTX, though I don't know how
> widely that is used. Would it be less painful to switch from OpenLDAP
> to the Mozilla LDAP toolkit (now part of the FDS?) at the same time?
>
I'm the current maintainer of the Mozilla LDAP SDK in Fedora as well as
being one of a very small number of upstream maintainers. We (the
upstream maintainers and I) will be in the near future investigating NSS
support in OpenLDAP. I encourage people to send me comments, questions,
and suggestions about how to approach this. If there is enough interest
I will create a page at wiki.mozilla.org to track this issue.
> <snip>
> joe
16 years, 10 months
Gnome Network Manager Applet issue?
by Mark
Hey,
i've just installed Fedora 8 Test 1 on my acer notebook and was
surprised to see that the resolution of my screen was used during the
installation (1280x800). Good job there!!
Once Fedora 8 Test 1 was installed and started i ran into some problems..
I was used to kNetworkManager (the KDE network manager) but had no
idea what gnome's manager was for this.. (nothing was started for
this..!!!) so i looked in the session settings for gnome and there i
saw: "Network Manager" and enabled.. so it should have started right?
well it didn't it did start when i opened a console and typed the line
that is in the Network Manager session command line: "nm-applet
--sm-disable"
Once that was started and once i had entered my wlan information it
was working all over again.. than the updates window popped up.. it
said that there where 280!!! updates!! so i did the update and tested
it again (NetworkManager) and it's still not booting up when Fedora
boots not even now when i write this post.
So is this done intentionally or is it a bug? and if it is.. is it
worth reporting it or already known? Also nearly no programs in the
session list (applets) seem to start except the power manager, sound
and update things.
And about Fedora 8 so far (just a few hours)
I know it's a test release and i know that it can be expected that
some bugs are in it but i just like to test out the latest stuff and
help a little where possible.
It looks good (specially the new icon theme (not everywhere applied
yet!?) and the window decorations. Fedora is gonna get a nice
authentic look in this release (or so it seems).
Good job so far!!
16 years, 10 months
Disabling atime
by Rahul Sundaram
Hi
http://kerneltrap.org/node/14148
Looks like we get a good performance boost and only tmpwatch and mutt
with mbox seems to be affected. A simple patch to tmpwatch has been
posted on the same thread.
Thoughts on disabling it?
Rahul
16 years, 10 months
Rebuilds needed for Fedora 8
by Jesse Keating
There are currently two technical issues that require rebuilding of
packages.
1) a bad binutils was used in buildroots for almost two months that
caused all ppc32 binaries to need execmem. SELinux rightfully denies
this. We need to rebuild the effected packages so that ppc and SELinux
work again.
2) build-id (http://fedoraproject.org/wiki/Releases/FeatureBuildId)
Any binary package with a debuginfo package that hasn't been built
after the good build-id stuff landed needs to be rebuilt so that it has
a build-id.
The unique combination of these two has led to a list of 2845 packages
that will need to be rebuilt.
(http://jkeating.fedorapeople.org/really-need-to-rebuild) That's 598
packages that need rebuilding for the ppc32 issue, and 2831 that need
building due to the build-id issue (there is obviously some crossover).
At the absolute minimum we need the ppc32 builds done before Test2,
which has a freeze date in one week. We'd /like/ to have them all done
as build-id is an important feature of Fedora 8 and Test2 is the
Feature Freeze and if you're building 600 packages, might as well build
3K.
A less technical but a nonetheless important rebuild issue is correct
package licensing. We have a goal to have all our packages with (a)
correct License(s) tag in the spec file, and a build with that correct
tag. I do not have the numbers currently as to how many still need
updating, it is not a small number. Also important to note is that for
the above technical issues no changes are needed in the package beyond
a release bump and a build. But for the license tag issue there is a
significant number of packages that still have the invalid license and
need auditing and changing.
Given that with just the fully technical issues we're at just a bit
over 1/2 the package set for Fedora we've got some hard choices to
make. Obviously we'd like to rely upon the maintainers to rebuild
their packages, however with just a week to accomplish this that may be
nearly impossible. It's also a rather large number of packages to try
and automate over, with a large degree of different $release values to
try and automatically bump (especially without resorting to just
plonking a ".1" to the end of everything which is against the
guidelines). There is also a rather large list of things that failed
to rebuild during Matt Domsch's last rebuild test, and I don't know how
many of those have been fixed. That can cause some delays as well.
So I ask you, great Fedora Community, how do we want to handle this
situation? I'm open for suggestions, but we should decide something
before the end of the day given our time constraints.
I'm going to continue working on these lists and keeping them updated,
perhaps getting a mapping of maintainer to package, or whatever format
the community finds useful.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 10 months
build/koji/update documentation reorganization?
by Patrice Dumas
Hello,
I have something to add to the update/build/koji doc, but it is not
easy to do since there are a lot of duplication in the wiki on that
subject.
1. In http://fedoraproject.org/wiki/Koji, subsection 'Package
Organization'
there are some useful infos about tags and package lists (not
the very beginning, but roughly beginning at 'A build target
specifies ...'), but for advanced uses of koji.
2. In http://fedoraproject.org/wiki/Koji/UsingKoji there are information
about the web interface, setting up koji in the client and koji build
commands.
3. in http://fedoraproject.org/wiki/Infrastructure/KojiBuildSystem
there are very brief infos about the web interface, setting up koji
in the client, precise informations about the certificates and
setup, some commands, and info about make targets koji related.
4. In
http://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo
there is a brief explantation about how to update a package including
make tag, make build, koji, and bodhi. There is a link to 5.
5. In http://fedoraproject.org/wiki/PackageMaintainers/UsingCvsFaq
there is a detailed explanation on how to update a package.
Also some misc informations, including info about make targets.
It links to 6.
6. On http://fedoraproject.org/wiki/PackageMaintainers/BuildRequests
there are info about plague builds
I think that things should be simplified. In my opinion 1. 2. and 3.
should be merged in a page about builds in Fedora. With a part about
setting up koji, a part about the web infrastructure, a part
about koji commands and a last one regarding the make shortcuts,
including some info from 5.
Maybe the make shortcuts may be explained before koji commands.
I also think that 5. should be merged in 4., with links from 5. to 4.
4. should point to koji stuff.
6. Should be renamed otherwise, and linked from other places with
a text saying that it is about a procedure for F-6 only.
I am volunteering to do at least part of the reorganization I
propose.
(The info I would like to add is about inheritance in koji and
make chain-build.)
Comments?
--
Pat
16 years, 10 months
GDM Session bug
by Mark
Hey,
The bug is quite simple.
Install Fedora 8 Test 1 with the latest updates + gnome + kde
Change the session during login to KDE and get in KDE.
Logout and log back in. you will notice that you than start in GNOME
instead of KDE while you start up in KDE (last used session or
something like it) but instead you get gnome.
Good luck,
Mark
16 years, 10 months
Problems with NetworkManager and autofs/NFS
by Orion Poplawski
NetworkManager is currently (in devel and F7) unusable with autofs and
NFS mounts. This is because NetworkManager is stopped very early in the
shutdown process (K02) and brings down the network with it. Then when
autofs attempts to unmount any automounted nfs mounts, they fail because
the remote machine is not accessible. Eventually the machine hangs
trying to unmount the last nfs mounted directory. I suppose it might
timeout eventually, but it's beyond my patience to wait that long.
Questions:
- Why is NetworkManager shutdown so early?
- Should autofs/nfs shutdown do a forced unmount if needed? Would that
work?
- Do we need tighter NIS/autofs integration into NetworkManager?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
16 years, 10 months
