FYI- no fedora-logos behaviour
by Jane Dogalt
For anyone interested-
I just tried doing an rpm -e --nodeps fedora-logos to a fresh system, to see
what would happen.
1) grub handled it very gracefully
2) rhgb handled it very gracefully
3) gdm handled it well, but not perfectly. I.e. threw up a dialog about the
missing theme, and then after clicking OK, went to it's default theme. Pretty
good though.
4) /usr/share/backgrounds/images/default.png is the 1600x1200 default gnome
fedora logo background, which is not owned by fedora-logos*.rpm
5) fedora main menu button is also not apparently owned by fedora-logos*.rpm
I'm guessing 4&5 are 'bugs'. And easily enough replaceable. Likewise I'm sure
3 is pretty trivial to fix as well.
I imagine it's far more challenging to make a fedora derivative distribution
that includes the anaconda installer, than it is to make a derivative livecd
which uses the installer during the derivation process, but not
post-distribution.
Basically what I'm saying is that this bodes very well for all the
livecd-generator output redistribution issues, which are apparently irrelevent
if you do an rpm -e --nodeps fedora-logos*.rpm to your system image before
distributing it.
-jdog
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
17 years, 12 months
Re: output redistribution issues again, was Re: [Fedora-livecd-list] Kadischi: roadmap from Board meeting ?
by Jane Dogalt
--- Jane Dogalt <jdogalt(a)yahoo.com> wrote:
> --- Chitlesh GOORAH <chitlesh(a)fedoraproject.org> wrote:
>
> > http://fedoraproject.org/wiki/Kadischi/Legal
>
> I hate to be obtuse here Chitlesh, but seeing as how finally someone (Chris)
> clearly has _precisely_ the same question as I do, I need to reiterate that
> your supplied legal link does not answer my question.
Ok. I _think_ that reading the bottom most section of the wiki page, that the
answer to my question is clearly "Yes, no problem".
And especially now that I read the link to the redhat/fedora trademark
guidelines, which I believe has changed signifgantly in the past 2 years, I
think the answer is really "absolutely, no problem".
My confusion, and I'm hoping to clear up other people's confusion here as well,
stemmed from what I believe was a historical guideline which forbid the
_inclusion_ of fedora/rh copyrighed artwork and trademarks in a derivative
distribution. In which case, merely having the fedora-logos.rpm files would
make something unredistributable. Perhaps this was never the case. Certainly
judging by the succinctness of the current trademark guidelines, and the
following quote, it appears that my #2 case, and Question: below, are
absolutely not a problem-
"Red Hat does not permit or consent to any use of its trademarks in any manner
that is likely to cause confusion by implying association with or sponsorship
by Red Hat."
Although the more specific question is- If people see a fedora logo on a gdm
login screen on an iso called jane_dogalt_is_the_coolest.iso, would that "be
likely to cause confusion by implying association with or sponsorship by Red
Hat"?
For my own purposes, I still think it will be wise for my own project to have a
post install script which removes the fedora-logos.rpm package, so that users
of my output needn't worry about splitting that legal hair.
-jdog
>
> I think in the archive post I referenced, the situation of #2, is very
> simple,
> and I can't seem to get a straight answer from fedora. Can you please
> specifically answer my question in the above Kadischi Legal Wiki, i.e.
>
> Question: If I as fedora/kadischi user, produce a livecd with kadischi (say
> nothing more than the supplied minimal.ks and a post install script that adds
> a
> motd of "jane dogalt is the coolest"), am I legally allowed to post that on
> my
> own website for mass distribution under the title
> "jane_dogalt_is_the_coolest.iso"?
>
> I.e. due to the default behavior of kadischi, fedora-logos*.rpm will be
> installed. Is that a problem? If so would simply removing that rpm in a
> post
> install script resolve the distribution problem?
>
> I don't think I can specify the question any clearer than that. And I for
> the
> life of me don't see an answer to that in the wiki-kadischi-legal you
> referenced.
>
> -jdog
>
> >
> > On 4/17/06, Chris Negus <cnegus(a)rucls.net> wrote:
> > > On Sun, 2006-04-16 at 23:29 -0500, Jasper O'neal Hartline wrote:
> > > > Jane Dogalt wrote:
> > > > Now this is really strange, Kadischi is a tool to yes, to create LiveCD
> > > > media..
> > > > but to create Fedora Core CD media. Although Rahul mentions running
> > > > Anaconda in Debian
> > > > may be possible, I don't think right now is the time to be focusing any
> > > > efforts on running Kadischi
> > > > on everything but Fedora Core. Likewise in this same respect, Kadischi
> > > > shouldn't be focusing
> > > > on allowing users to build thier own "distribution". It is a LiveCD
> tool
> > > > not a distribution tool.
> > >
> > > Actually, I think this is a good point. The Fedora project still hasn't,
> > > in my mind, clearly stated how to legally use its logos and trademarks.
> > > The Wiki says to make formal requests to use the logo. I've made two
> > > such requests and have not gotten a response back.
> > >
> > > So the question is not whether or not we want to help people build their
> > > own distributions from Kadischi. The question is how can someone legally
> > > redistribute "anything" built with Kadischi? If you change the splash
> > > screen or rebuild a package from source, is the resulting CD still
> > > Fedora? If not, do we legally have to remove references to Fedora?
> > >
> > > -- Chris Negus
> > >
> > > --
> > > Fedora-livecd-list mailing list
> > > Fedora-livecd-list(a)redhat.com
> > > https://www.redhat.com/mailman/listinfo/fedora-livecd-list
> > >
> >
> >
> > --
> > http://clunixchit.blogspot.com
> >
> > --
> > Fedora-livecd-list mailing list
> > Fedora-livecd-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-livecd-list
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
18 years
who needs unionfs!, was Re: [Fedora-livecd-list] experimental unionfs and initramfs code
by Jane Dogalt
> Or maybe they are playing devicemapper tricks that I've never even
> suspected...
>
> Very interesting, and very worth watching...
So apparently... You no longer need unionfs to have a union.
Very interesting... (if my guestimation and being too lazy to read up on
devicemapper are not leading to my misunderstanding)
-jdog
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
18 years
error during rpmbuil for gdm
by Jaswinder Singh
hi
when i tried to build rpm from tar.bz2 file of gdm in
/usr/src/redhat/SOURCE/ directory then it shows an error at then end.I am
putting that error here as follow:
M_PREFIX=/var/tmp/gdm-2.6.0.8-root/etc install
Making install in po
make[1]: Entering directory `/usr/src/redhat/BUILD/gdm-2.6.0.8/po'
make[1]: install_sh@: Command not found
make[1]: *** [install-data-yes] Error 127
make[1]: Leaving directory `/usr/src/redhat/BUILD/gdm-2.6.0.8/po'
make: *** [install-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.96523 (%install)
Please help me to solve this problem.
thanks
Jassy
18 years
experimental unionfs and initramfs code
by Jane Dogalt
Well, I managed to get my first proof-of-concept fedora core 5 based livecd iso
generated, which utilizes unionfs+squashfs via initramfs.
This is absolutely bleeding edge stuff which I only post as a helpful example
for others who may be interesting in similar hacking. I do have an iso online,
but I won't advertise it's location because I don't want to blow my hosting
bandwidth on a 700MB download which isn't really useful in and of itself. But
here are the nash and init modifications I made, which illustrate what I had to
do, and I'll briefly outline the rest of what I did to manually stitch together
the iso.
http://viros.org/releases/20060423a.dio/
So the nash I hacked on was the stock fedora core 5 one. And my modifcations
started from the truly elegant linux-from-scratch livecd init.c/init.h. Though
by the time I packaged it up, I had mostly made my custom vswitchroot and
vsetuproot match up pretty closely with the native setuproot and switchroot.
When I'm done polishing, there may only be a couple lines of different code,
and therefore an argument to those functions might be the right answer (for
me).
The init (nash script) I started out with was the basic one from a normal hard
disk install (via qemu, and not using lvm) fc5 initramfs. As you can tell by a
diff, the changes are fairly minimal. In fact, with the above mentions,
eventually the difference might just be an argument to setuproot, switchroot,
and a new function setupliveunion.
Otherwise, the rest of the base system is relatively unmodified, just added
unionfs, disabled selinux (it puked, and may not be happy with unionfs, or just
requires more polishing of the init sequence), and then changed fstab so it
wouldn't try to fsck root.
I'll post more progress as it happens (mostly after finals), and my experiences
using unionfs and qemu. I'm pretty sure I can get a sweet completely non-root
headless scripted build going as soon as I add a harmless 3-line patch to qemu.
Beyond that, since qemu is obviously painfully slow, I'll be going down the
route of only using kickstarts, and not anacondas gui, which again, for me is
the right answer, and especially almost necessary when working with qemu.
None of this really impacts kadischi except as idea fodder (my best
contribution), but I figure this isn't kadischi-devel-list, it's
fedora-livecd-list, so maybe some folks are interested in some other
alternatives.
Peace...
-jdog
P.S.- I can't wait to give a 3 layer union a shot, to see if my
early-boot-file-segregation idea really does improve non-emulated boot speed
due to reduced seek thrashing. (and beyond that, using mkisofs -sort to see if
there is a discernable speed increase from putting the boot files on the
outside tracks of the cdrom versus the inside).
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
18 years
Kadischi: roadmap from Board meeting ?
by Chitlesh GOORAH
Hello there,
The board meeting http://fedoraproject.org/wiki/Board/Meetings/2006-04-07:
Live CD (Kadischi) -- Lots of people like the idea of this project,
but there are still some problems to solve. We should empower people
to take the reins, but if they hit a roadblock we need to find a way
to assign them some help, without simply (a) taking the project away,
or (b) saddling Red Hat developers with new work. DECIDED: Jeremy will
take up the cause for Kadischi.
I have some questions concerning Kadischi's roadmap and how the
development will continue.
Everyone knows that Kadischi's development stalled, but it wasn't dead.
Some new features have been added on since, Squashfs, tuned with FC5,
man pages, bootsplash, Legal....
Some of us even did marketing for Kadischi
(http://clunixchit.blogspot.com/) or even popup'd some iso images for
trial.
Now what's NEXT ?
What is Kadischi's roadmap?
What do we want from Kadischi in the future?
Will we start meetings again?
Should contributors state in which area they want to get involved in
so as 2 contributors might not do the same thing.
What the Fedora Community looking for?
...... the list goes on.
Jeremy, can you share your intentions with us too?
It is now the time to discuss and share thoughts about how shall we
boost Kadischi :)
regards,
Chitlesh GOORAH
--
http://clunixchit.blogspot.com
18 years
ntp time skew and network failure pre post_install_scripts
by Adam Stokes
Anyone seen any issues with ntp clock skew and network interfaces going down
before the post install scripts are executed? I am trying to pinpoint the
cause of this but not to familiar with anaconda's interworkings.
Ive tried manually configuring the network device during install rather than
having kickstart do it automatically. Also this only seems to happen on this
box with 2 interfaces rather than my other machine with just one interface.
simply restarting the network allows me to continue with my post install
setup and the only network related scripts that i have residing in
post_install_scripts are some yum installs for custom applications.
--
· adam <astokes.org>
18 years
Kadischi and CF cards
by Hassan Aurag
Hello all,
I am interested in putting fc5 on a cf card that is part of an all in
one touch screen. Most of it should be read-only, but I want a small
piece of the CF (separate partition) to be read-write to save some basic
config info (ip-address etc....)
I would like to know if anyone else has tried before and how did he/she
go about it. Any hint is appreciated.
Regards
18 years
Fedora Core LiveCD Test x (Snapshot)
by J. Hartline
Hi.
On fedora-marketing-list I believe, Jeff Spaleta had made
a statement he wouldn't mind seeing ISOs built everyday to test out
how all of this LiveCD stuff is doing.
I have come up with the idea, that not a daily but a weekly snapshot can
be made
if it is something that would be beneficial to the community.
As of now this idea is in the making, and I'd like to hear people's
thoughts.
The advantages of doing this are these:
1) Simply testing
I have the bandwidth and server space needed to do this
along with just the cron spun ISOs from RAWHIDE tree
provide:
1) A SHA1SUM
2) A package list in plain text
The SHA1SUM for integrity, the package list to know what packages
are present. Of course this would need to be agreed upon, and since I am not
directly affiliated with Redhat, Inc. in any way, Logo and art packaging
removal would
probably need to be discussed. Albeit the CDs wouldn't be modified in
any way except
for what you see in Kadischi, a specific set of services, no firewall
and a standard non-root user.\
Flames, suggestions, questions and comments welcome.
J. Hartline
18 years
[Fwd: [stateless] readonly-root support]
by Jeremy Katz
Per Bill's mail (below), basic readonly root support is now in the
development tree. I have a working live CD that boots to a login prompt
with a root user basically with the bits I sent mail about earlier in
the week. I'm currently in the progress of pushing that to
hg.fedoraproject.org, which should hopefully be done shortly (I'll send
a follow-up mail with some info once it's up)
Also, I've got a test going now with more of a desktop install to see
how that's looking while at the same time trying to get rid of the need
for a special hacked anaconda and booty package
Jeremy
-------- Forwarded Message --------
From: Bill Nottingham <notting(a)redhat.com>
Reply-To: Development discussions related to Fedora Core
<fedora-devel-list(a)redhat.com>
To: fedora-devel-list(a)redhat.com
Subject: [stateless] readonly-root support
Date: Thu, 20 Apr 2006 16:28:39 -0400
Initial readonly root support will be in tomorrow's initscripts-8.33-1.
How to use:
- Edit /etc/sysconfig/readonly-root. Set 'READONLY' to 'yes'.
- Add any exceptions that need to be writable that aren't in the
stock /etc/rwtab to an /etc/rwtab.d file. (See below)
** NOTE: This does not currently work with SELinux. We're working on it. **
How it works:
- On boot, we mount a tmpfs (by default, at /var/lib/stateless/writable),
and then parse /etc/rwtab and /etc/rwtab.d/* for things to put there.
These files have the format:
<type> <path>
Types are as follows:
empty: An empty path. Example:
'empty /tmp'
dirs: A directory tree that is copied, empty. Example:
'dirs /var/run'
files: A file or directory tree that is copied intact. Example:
'files /etc/resolv.conf'
A stock rwtab is shipped with common things that need mounted. We're
currently investigating other things. If you come up with new ones,
please file a bug.
Problems should be filed in bugzilla at https://bugzilla.redhat.com/,
product Fedora Core, release devel, component initscripts.
Things we know need work:
- a simple 'prepare' script for a filesystem that is intended to
be mounted read-only - it will update various caches (beagle,
locate), clean out extraneous temporary files, and build the
SELinux policy module.
- using local storage automatically for swap, etc.
- the rest of http://fedoraproject.org/wiki/StatelessLinux :)
Bill
18 years
