On Tue, 2003-09-23 at 10:02, Phillip Compton wrote:
And what about;
And rhdb config/admin tools ? Would be
nice to have those for PostgreSQL.
Vennlig hilsen/Best Regards
Nils Olav Selåsdal
w w w . u t e l s y s t e m s . c o m
I was wondering if there was any policy doc on BuildRequires for Red Hat
rpms, I've been playing with mach and severn srpms from fedora CVS and
due to the very minimal nature of the mach environment I get missing
I'm aware of the policy for fedora which seems slightly stricter than
that for Red Hat rpms.
Is there a document or guide for the minimal build environment for
building Red Hat rpms, or should missing BuildRequires go straight to
This would be useful from two perspectives - using mach to build
severn/cambridge in an consistent environment, secondly as a start to
trying to bootstrap severn from an SRPM/CVS repository it'd be a useful
As an example:
bash requires byacc and texinfo to build successfully in a severn mach
i saw rawhide has yum. if fedora is going to have
yum(i think this is essential) it would good to
central apt enabled repostries maintained by redhat
while others can have third party repostries for non
free and patented stuff like xmms-mp3 plugins aka
yum may be dumped in redhat support versions or
offered as a unsupported alternative.
how about some home user focus. wouldnt that be
* single cdrom with one or more optional packages in
*the installer includes the ability to resize
partitons(fat and ntfs)
*ntfs support enabled by default
* automatically mount windows partitions in dual boot
systems and put icons on the desktop
*include rpms from kde-redhat.sf.net with just the
theme changed to bluecurve(no changes in the
drop kde or gnome altogether and focus on one GUI and
polish it to the maximum possible(no redundant menu
entries or applications - something like ark or jamd)
there might have been other changes that i have
missed. these changes are not currently very
profitable to redhat now but would help increase its
user base by many folds
Yahoo! India Matrimony: Find your partner online.
Go to http://yahoo.shaadi.com
Hi, Marcelo has been incorporating a lot of Andrea's VM patches into
mainline. Given that RH has stated that it would like to stay close to
mainline. What does this bode for the rmap patches ?
I see a number of bugzilla reports with the summary marked as (VM) and
quite a few reports which state that RH 2.4.20-xx kernel's seem to swap
more than RH 2.4.18-xx kernels. Would like to have Cambridge with a
I am going to try Phil K's test script in bug number 104562 and see how
it behaves with various kernels
If you're not using Firebird, you're not surfing the web
you're suffering it
The kudzu program has a problem while the graphical boot is running.
When it detects new hardware that has to be configured, the program
runs, but there is no opportunity for the user to make the selection
whether or not to configure the hardware. Not even ctrl-alt-bksp will
get you to the right screen. Depending on how much hardware needs to be
configured, this could cause delays upward of three minutes or more. As
a solution, I suggest this change to the kudzu startup script. This
should run kudzu without requiring any user input.
if [ $RUNX ]; then
if [ "$SAFE" != "no" ]; then
if [ $RUNX ]; then
On Sun, 2003-09-21 at 21:55, Bill Nottingham wrote:
> A default taroon AS installation creates a set of firewall rules that block
> "unreachable - need to frag" icmp packets. This severely breaks the linux
> TCP/IP's stack patch MTU discovery and also makes it impossible to use RHEL
> behind a NAT firewall over DSL or cipe.
> Among some other types mentioned as well...
I think the author of the above doesn't understand how the statefulness
of IP tables works.
The use of "RELATED" matches the "unreachable - need to frag" ICMP error
regarding conversations that the machine is involved in.
With the rules I originally supplied, if an ICMP error message (need to
frag, port unreachable, source quench, redirect, etc) arrives
out-of-the-blue, it will be blocked. This is good.
If an ICMP error messages arrives at the machine and that ICMP error
message is about (ie, RELATED) to an existing conversation the machine
is involved in, then the message will be allowed. This is good.
ICMP messages come in two flavors, QUERY and ERROR.
>From a security standpoint, one should block all QUERY messages as they
violate the principle of least disclosure. From a practical standpoint,
ICMP echo-request messages should be allowed to be a good LAN citizen
and play nice with the DHCP servers who want to double check IP address
Generally, one should not block ICMP error messages as they allow your
IP stack to respond quickly in the face of failures, and can be critical
to the operation of IP (eg, need to frag). However, with Linux we can do
better. You can allow ICMP error messages regarding real conversations
that your computer is is involved in and drop all others. This is ideal.
The previous rules (pre bugzilla #104561) implemented such a setup. IMO,
the current change is a regression.
When designing an IPv6 extension to initscripts, we came across this one
particularly knotty problem.
There seem to be no way to select the order in which the interfaces would
be brought up by e.g. "network start", except by naming hacks. (There are
also this, nowadays smaller, problem of on-demand dial-up interfaces..)
There seems to be no facility to run a script "in the second pass" i.e.,
after all the interfaces have been brought up.
Both of these facilities would seem to be useful, espcially being able to
say "run these commands after interface X has been brought up".
Have I missed something, or is this impossible at the moment (without
gluing more stuff in init.d/network)? Would such mechanisms be useful in
other contexts as well?
(This could be achieved, it seems, at least by using an '/sbin/ifup xxx
2ndpass' argument, and only specified commands would be run when doing the
Thoughts, ideas, comments?
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
I think nobody have tested installing Red Hat 9 on 3.2 GB hard disk.
Last week, I tried to install Red Hat Linux 9 on Winchip 200 machine with 64 MB RAM and 3.2 GB hard disk. The installation step went well. At the stage of selecting the installation option, I select Server and continue. The server installation is about 1.4 GB, and it went well until after transferring install image to hard disk.
As soon as the transferring install image to hard disk complete, error message is displayed stating that my machine does not have enough disk space.
I reboot again the computer, starting again the installation, but this time selecting Custom and then uncheck all the group listed. The installation size is now around 550 MB, and then transferring install image continued. Still after completing transferring install image to hard disk, error message being displayed stating that the machine does not have enough disk space.
Re-installing the machine with Red Hat 8 yesterday, it went smooth even though I select Server with installation size of 1.4 GB. I really suspect the transferring image is the problem.
My HD partitioning info is:
/boot 100 MB
/swap 200 MB
/ 2.9 GB
1. Why this thing happened? Does anybody have any experience with it?
2. Why it is still fail even though the installation size is 500 MB?
3. Should I report it on Bugzilla?
4. Could I suggest that anaconda have another option like "Minimal install" where nothing is installed, except the base package just to run Linux
Sharuzzaman Ahmat Raslan
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
Get AOL Instant Messenger 5.1 free of charge. Download Now!
I have received an IBM Thinkpad R40e (2684 QVG) and I'm trying to install
Linux on it. I have tried the latest Severn, Taroon, and the official Redhat
9 - all gives the same problem - a keyboard lockup...
Here's what I'm doing: I'm putting the CD inside and boot the thinkpad. When
I'm getting the "media check" stage - the keyboard is totally locked, and I
cannot do anything (other then shut the machine down)...
I tried to boot into Linux rescue using the 1st CD - it stuck, again, when I
needed to select language (the first menu)..
I did try to install Mandrake 9.1 - and haven't spotted those problems there
(but I hate mandrake and I want to use redhat)
Any suggestions? tips?