minimal install
by Lonnie Cumberland
Hello All,
I have been an avid Linux user for a long time now, but must say that I
have been using Mandrake most of that time. That was because I thought
that it was a little more cutting-edge than Red Hat. Now it seems that
the price of that cutting edge was that things do not always work as
good as you would like.
Anyway, I am very eager to try Fedora and see if it is more stable and
compatible with various other applications.
I would like to know if someone could either tell me some of the
specifics, or direct me to some documentation on the Fedora installer.
I want to learn how things are done.
For example I would like to know where in the Stage2.img is the list of
install types and install messages that you see when it is running.
I would like to see what file Fedora uses to define what the "minimal"
install is, or "Server" install list of packages because I need the
absolute smallest install + XWindows and the smallest (simplest) window
manager.
Any suggestions would be greatly appreciated,
Thanks,
Lonnie
19 years, 8 months
Re: yum 2.1.x fails when using firewall
by daa
> when using what? an http1.0 authenticating proxy? Which proxy where?
> If this is a problem specific to the proxy you are using how does
> anyone reproduce this?
> Can you browse to the the primary.xml.gz file via another browser that
> can use the
> the same http proxy?
this is a HTTP1.0 authenticating proxy (Sidewinder 5.2
http://www.securecomputing.com)
browser ( IE or mozilla) has no problem getting to the dir and file)
dave
19 years, 8 months
rpmlint error messages
by Michael Thomas
I'm trying to build a fedora-compatible spec file for tclhttpd
(http://tclhttpd.sourceforge.net/), but I'm having trouble understanding
some of the message that rpmlint reports on the generated RPM file.
Here are the particular messages that are causing me trouble:
W: tclhttpd no-soname /usr/lib/libcrypt1.0.so
E: tclhttpd non-versioned-file-in-library-package
/usr/tclhttpd/htdocs/.tml
Is there a detailed description of rpmlint's messages anywhere?
--Wart
19 years, 8 months
Kerberos HTTP authentication in RHEL4/FC3/FC2
by Dax Kelson
One of the new features of Mozilla 1.7 touted in the release notes is:
"Support for Kerberos HTTP authentication using GSSAPI (benefits
Unix-like platforms including Linux and OS X)."
Single sign on rules.
Whats needed is the addition of --with-gssapi in the spec along with
adding krb5-devel to the BuildReq line.
I've filed a request in bugzilla.
mod_auth_kerb (http://modauthkerb.sourceforge.net/) for Apache makes a
nice companion to this.
Dax Kelson
Guru Labs
19 years, 8 months
FC3test2 candidate tree
by Elliot Lee
Hi all,
I've just started uploading the latest "release candidate" for FC3test2.
This is __________________NOT__________________ the final FC3test2 tree.
If you're interested in helping with testing for the FC3test2 milestone,
wait until it finishes uploading (there's 39G still to go, but hopefully
it will be done by tomorrow).
Right now we're down to "no broken dependencies" and "might install".
You'll have to find out for yourself. :-)
Especially useful would be reports on installs from CD or DVD. Unlike
rawhide, this tree has all the .iso images.
Where to get it when it's uploaded?
http://fedora.linux.duke.edu/FC3-re0903.0/
Cheers,
-- Elliot
The daring is in the doing
http://people.redhat.com/sopwith/
19 years, 8 months
Notes on Yum Changes
by seth vidal
Here are some notes I typed up this weekend on a plane and in a truly
dull airport about yum changes in the upcoming test release.
Here they are:
Making yum repositories now:
Yum repositories are no longer created by yum-arch. There is a new
program, createrepo (http://linux.duke.edu/metadata/generate), that
creates the metadata. The metadata for rpm packages is the information
that describes the data stored in the payload of the rpm. createrepo
takes the metadata from each rpm in the repository and stores it in an
xml format that is simple and expedient to load the data from. This
makes it easier and more efficient for yum to resolve dependencies
and find out other important information about the packages a user
would want to install.
To create your own repository install the createrepo rpm and run:
create-repo /path/to/the/packages
It will recursively go through the directory you specify, find all
the rpm packages, and retrieve the pertinent metadata. Once this
command completes you should have a directory named 'repodata'
created in the directory path you specified on the command line.
The repodata directory will contain at least 4 files. They are:
repomd.xml - stores the information about the other metadata
files. It is a meta-metadata file. :) It has checksums and
timestamps for each file of the metadata.
primary.xml[.gz] - stores the critical information for listing and
dependency solving packages. It is the core of information for the
repository and it is normally the smallest of the files containing
package metadata.
filelists.xml[.gz] - stores the complete file listing for each
package. It also contains some information describing the files.
It distinguishes between files, directories and ghosted files in
the package.
other.xml[.gz] - stores any other information that is available from
the package. This file is available for completeness and convenience.
In particular, this file stores all the changelog information for
each package.
If you specified the -g option to createrepo and listed a groups file
(a comps.xml format file) then this file will also be copied to
the repodata directory.
Yum Changes:
1. Yum will no longer work with repositories generated with yum-arch.
The new format and the old format do not conlict with each other so
if you want to run createrepo and yum-arch on a single repository
that will work just fine. However, the new yum will not support
old-style repositories and there are no plans at this time to make
it possible.
2. When specifying packages on the command line and in the exclude
lists you can use complete version and arch strings now. In addition
to specifying:
yum install mypackage
you can now also specify:
yum install mypackage-1.1
The following version/arch string formats are accepted:
name
name-ver
name-ver-rel
name.arch
name-ver-rel.arch
epoch:name-ver-rel.arch
3. The config file has been enhanced in a number of ways. Inside the
config file you can now specify include=url://some/location/file at
any point. This allows you to include one config file inside another.
The file is included literally, as though typed in place. The include
option takes any url that yum is capable of handling (http, https,
ftp and file).
4. In addition to the above config change, yum also offers an
optional /etc/yum.repos.d directory for configurations. Each file
named with a .repo extension will be parsed and added to the set of
repositories listed in the yum.conf file. The format of these files
is identical to the listing of a repository in the yum.conf file:
[repository-id]
name=repository name
baseurl=url://path/to/repository
...
5. New command line options:
--obsoletes - tell yum to include obsoletes in its update processing
--enablerepo=repository-id - tell yum to enable the repository of
that id this option can be specified
multiple times on the command line.
This will override the 'enabled' option
to a repository in the configuration
file.
--disablerepo=repository-id - The logical opposite of the above.
Other new features will be added and they'll be described in more
detail then. This should give users an overview of the major changed
items in yum, so far.
hope this helps people.
-sv
19 years, 8 months
Where to report a missing component in bugzilla?
by Matthias Saou
Hi,
Probably a stupid question, but where should I report a missing component
in bugzilla? Against what? I thought of doing it in the bugzilla product,
but got scared of being flamed by a bugzilla developer if that's not the
right place ;-)
My problem is that sysfsutils (which is from the sysfsutils source rpm,
I've checked) isn't listed in the current Fedora Core Development
components, and I need to report that it's missing /sbin/ldconfig scriplets
:-)
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 2 (Tettnang) - Linux kernel 2.6.8-1.521
Load : 0.16 0.58 0.55
19 years, 8 months
