upgrading RH 9 system->Fedora with iso files and apt only
by Didier Casse
I have the yarrow's iso files on my HD in a RH9 system. Let's say I want
to upgrade selected packages using an "apt-get install" pointing to my
iso-mounted files, how do I do it?
i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc..
Then what is the complete procedure to make my apt look into my own HD to
upgrade packages. Can anybody redirect me to the correct
resource or some literature hanging on the web? Thanks.
Assume also that I do not wish to burn CDs! I do not want to use
apt-cdrom. Thanks.
With kind regards,
Didier.
---
PhD student
Singapore Synchrotron Light Source (SSLS)
5 Research Link,
Singapore 117603
Email: slsbdfc at nus dot edu dot sg \or\
didierbe at sps dot nus dot edu dot sg
Website: http://ssls.nus.edu.sg
1 year, 4 months
autoconf breakage on x86_64.
by Sam Varshavchik
I don't know the right way to fix this, but something is definitely broken;
and something needs to be fixed, one way or the other. The question is what
exactly needs to be fixed.
Consider something like this:
LIBS="-lresolv $LIBS"
AC_TRY_LINK_FUNC(res_query, AC_MSG_RESULT(yes), AC_MSG_RESULT(no))
Here's what happens on x86_64:
gcc -o conftest -g -O2 -Wall -I.. -I./.. conftest.c -lresolv >&5
/tmp/ccW7EeDX.o(.text+0x7): In function `main':
/home/mrsam/src/courier/authlib/configure:5160: undefined reference to
`res_query'
collect2: ld returned 1 exit status
configure:5147: $? = 1
configure: failed program was:
[ blah blah blah ]
| /* We use char because int might match the return type of a gcc2
| builtin and then its argument prototype would still apply. */
| char res_query ();
| int
| main ()
| {
| res_query ();
| ;
| return 0;
| }
The same exact test on FC1 x86 will work.
The reason appears to be that you have to #include <resolv.conf> on x86_64
in order to succesfully pull res_query() out of libresolv.so. You don't
need to do this on x86, and the test program generated by AC_TRY_LINK_FUNC
does not include any headers, but uses a manual prototype.
So, what now?
16 years, 8 months
Zeroconf in FC5?
by Daryll Strauss
I saw zeroconf in action at a Mac based facility a while back and I have
to say I was impressed. It makes their networking setup very easy. The
biggest downside was that they knew very little about how their network
actually worked. That made my life integrating a Linux system in to
their environment much more difficult. So, I'd like to see zeroconf
really integrated in to FC5. I think it'll make network setup for a lot
of users much easier.
For those who don't know, zeroconf provides several functions:
*) Dynamically allocating an IP address to a system when it boots
(without requiring a DHCP server)
*) Translate between names and IP addresses (without any setup or
directory server)
*) Allows for the publishing and discovery of services such as DNS,
NFS, ftp, http, printers, whatever (without requiring any setup or
directory server)
*) Allocates multicast addresses (without a MADCAP server). (This part
isn't yet supported and I'm not sure I know what it means :))
Fedora ships with Howl which looks to be the framework for doing
zeroconf. It seems that what's needed is integrating howl in to all the
appropriate places.
- |Daryll
16 years, 10 months
Stateless linux and an idea of mine for SMALL networks without servers
by Nic
Disclaimer: I hope that this is the right mailing list, but I really
wanted to reach developers would can say if it's feasible and what to
use for that.
Anyway, I was fighting the usual problems with networks and came up with the
following dream to make my life easier as a network admin. Basically I
am tired of fixing things, of worrying if a hard disk will die, of
having to deal with data access, backup etc...
I was thinking this through by looking at how most of my coworkers,
friends, and small offices use their PCs in day-to-day operations and
applying that work flow to a solution.
Before, somebody screams, this means little or moderate daily data
generation so that, basically, a laptop drive could hold the entire
company's data. (This may require email-purge rules and other things
like that).
Anyway here it is: Basically, I suggest that (almost) all PCs in the
network be laptops with the exact same image. Furthermore, they
replicate their HD continuously (with possibly some delay).
This certainly applies to the user data and application. It may not
be necessary for the OS
I am not sure of the technology to use here, but I thought something
deriving from the P-to-P technology, some distributed file system,
some database replication technology or even freenet could be a
good base.
Since every laptop will contain ALL the data for the
whole network, every laptop uses hardware encryption
at the hard disk level using an external dongle/card/whatever to limit
the risk when a laptop is lost or stolen.
Additionally, every login ALSO uses a dongle/card for access to their
account. This makes it (almost) impossible for somebody stealing a
laptop to get access to the whole data. Additionally, it makes it
(alomst) impossible for somebody to fet to other people's data. If a
system dies, you just get a new one and sync it up. However, one main
idea is that you always have EVERYTHING you need right where you are,
no matter WHERE you are. Also, there is no UPS to worry about.
Communication between PCs could be implemented using VPN/IPSec or
whatever other protected mechanism. Internet access would have to be
"sandboxed", but UNIX based OSes allow for that easily. That's the
gist of it. A lot of things can be configured in many ways, but the
whole point here is to simplify people's life.
Look at it from a disaster recovery: a lot of people bring their laptop home.
Even if the company's building burns down as well as a few employees
homes, one surviving laptop is enough to bring the business back online.
Pros:
* seamless company disaster recovery
* seamless personal computer loss recovery (you lose everything since
the last sync)
* you can use ANY laptop and find YOUR own environment and files
* no central server/single point of failure
* no UPS except for the internet firewall (this comes from the PCs
being laptops)
Cons:
* sync across a lot of PCs might be tricky and needs to be tuned.
Maybe randonly select one as master like the SMB Master browser
election works?
* each laptop needs to have enough space for the whole company's data
* maybe not appropriate for disk intensive applications (video capture...)
I wanted to post it here for other people to use if they think it's a
good idea. (and also to preempt any proprietary company from saying
"me first")
It seems that Windows Vista is coming with some automatic
synchronization across two PCs so, that's one step towards it, but we
have different goals.
I posted this somewhere and somebody pointed me toward stateless linux
and it seems pretty cool and close to what I was thinking of. I'll
look smoe more into it, but does anybody see this as useful for VERY
SMALL networks? (I already got bashed by enterprise admins sneernig at
people who don't want a rack server, so if that's your intent, just
reply "me too").
Feel free to comment (I know people will).
Nick
17 years, 3 months
Kernel issues
by Trever L. Adams
During the FC4 development cycle I mistakenly asked for 2.6.12 to be
included because it "had" the ip_conntrack for ipv6. This was based on
something I read. It turns out the person was misquoting. The USAGI
project was promising this for a patch for 2.6.12. It was never included
at least to my knowledge.
My wish list for FC5 includes the following:
TARPIT target for IPTABLES (I think it is already included).
connlimit (and friends) matching for the kernel, this exists in
documentation but has not yet made the mainstream kernel. Help should be
given to get it there and it should be included.
ip6_conntrack (or whatever it's name is) should be given similar help
and should be included.
Other than that, most of my wishes are ready being addressed. I do think
these are very important for both desktop and server/firewall machines.
Thank you,
Trever Adams
--
"I conceive that a great part of the miseries of mankind are brought
upon them by the false estimates they have made of the value of things."
-- Benjamin Franklin
17 years, 4 months
system-config-sshd ?
by Arthur Pemberton
Hello,
I have been a Fedora user since FC1, and now I'd like to contribute to
the project. I know some Python, but no GUI (as yet). My more tested
programming skills lie is pascal and delphi. I am interested in building
a cnfiguration tool for sshd to help me learn the python language
better, and also to contribute to the fedora project. But I need some help:
Knowledge - HOWTOs, tutorial, whitepapers, etc that I need to read to
properly write a system-config applicat ion
Rules - Standards, and guidelines that I shoudl follow
Technologies - gui toolkits, modules, etc that I should stick to in
learning and building a system-config tool.
Thanks for your assistance and time.
PS: the fedora-config-list is dead, so I'm reposting here
17 years, 4 months
Suspend2
by Bojan Smojver
Looks like Suspend2 (http://www.suspend2.net/) is headed for the mm and
then mainline kernel (finally!). It's been working rather good for a
while now and it would be great if FC5 kernels had it once the release
hits the mirrors. I'm guessing most notebook (even desktop) users would
welcome it.
There are already excellent examples of those patches inside FC3/FC4/FC5
kernels as well as related stuff like mkinitrd, sysinit etc. here:
http://mhensler.de/swsusp/
Would Fedora kernel maintainers be willing to roll Suspend2 into the
development kernels?
--
Bojan
17 years, 8 months
samba 3.0.20 rpms
by Tom Diehl
Hi all,
Can anyone tell me if there are any plans to update the rawhide samba rpms to
3.0.20 anytime soon?
Regards,
Tom Diehl tdiehl(a)rogueind.com Spamtrap address mtd123(a)rogueind.com
17 years, 8 months
bugzilla
by Gene C.
As new packages get added to Fedora Core and Fedora Extras, they are not
always added to bugzilla. What is a "good" way to report these needed
bugzilla updates?
--
Gene
17 years, 9 months
Request for volunteers to help track down packages that use /usr/X11R6
by Mike A. Harris
Overview:
~~~~~~~~
The X.Org Foundation has finally changed X11 to install itself
into the /usr heirarchy by default instead of the /usr/X11R6
hierarchy. The basic rationale is that with modern packaging
systems like rpm, deb, etc., there is no need to isolate the
X Window System into its own private hierarchy on the filesystem.
Originally, the /usr/X11R6 directory was intended to strictly
be the location where X11R6 itself would get installed. Over
time however various other 3rd party software packages, addons
and other stuff has infiltrated into the /usr/X11R6 heirarchy
for no really good reason, and some of it still sits in there
today.
A year or two ago, I knew this change would be coming in the
future, and sent out email to inform other package maintainers
that they should update their packages to install their files
in FHS compliant directories instead of abusing the /usr/X11R6
heirarchy. I'm not sure how many people actually listened
though, so we're about to find out. ;o)
What's changing specifically:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X.Org X11 will no longer use the /usr/X11R6 directory hierarchy
at all. It uses /usr, and installs files where you'd expect
them to be found within that heirarchy more or less (although
it is a bit buggy in this regard currently, that'll be fixed
prior to X11R7's final release). The libraries, binaries,
fonts, config files, data files - everything is moving.
Along with this upstream X.Org change, there will be a number
of backward compatibility issues that we'll face, where we
may need to provide backward compatible symlinks for cases like
applications hard coding the path to X binaries instead of
using "which <appname>" and similar. We'll be keeping an
eye on such issues and considering where we should provide
compatibility links.
What we'd like volunteers to help with:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1) A lot of existing Fedora Core, Fedora Extras and other 3rd
party packages currently install themselves into /usr/X11R6,
need to be updated to install themselves in a more
appropriate location under /usr, using %{_datadir} and
friends in their rpm specfiles. Volunteers are needed who
are willing to take on the task of reporting bugs against
the offending packages, and preferably also attaching
patches to fix the rpms.
2) A number of packages might have shell scripts, .desktop
files, or other things with hard coded paths to binaries
such as /usr/X11R6/bin/xterm, or to data files, or other
files traditionally installed under /usr/X11R6. Please
report bugs against these packages, and where possible,
change them to use "which <appname>" instead of hard
coding the path to the executable/file directly. In some
cases dynamic solution might not work, so hard code the
new path in that case unless there's another appropriate
solution apparent.
3) If you can personally think of any application or compat
problems that might occur when the changeover is made,
please report them to me via email in advance, so we can
try to find a solution sooner than later.
This message is being sent out to encourage community
involvement in the process, and to help weed out problems
sooner in the development cycle than later on, as there
is likely to be a fair amount of package churn, so we'd
like to get things in order far far in advance of
FC5test1.
Thanks in advance for any feedback, and also to any
volunteers who decide to help out.
17 years, 9 months
