GFS-kernel cman-kernel dlm-kernel and gnbd-kernel FC4 x86_64 update
by Alessandro Brezzi
Hi all; first of all I apologize for my english.
After a relocation last year, only two week ago I regained ADSL
connectivity. My FC4 box was out of sync with all the update, so I
started a long process to fully update the software.
I use only the std repos.
I wnet in a little hell for dependency resolution: seem to me some
package in x86_64 do not declare correctly all the dependency in the
i386 version, resulting in the well know conflict. So I have to update
small portion of RPM at time, checking results, updating manually
dependency and conflicts etc. Lot of work for a supposed "dumb
procedure" to update all.
Finally I've got the result, with the ecxeption of some RPM
kernel-dependent pretending to find the
/lib/modules/2.6.15-1.1833_FC4. So, as far as I know, this is for an
older kernel; I'm running now kernel 2.6.17-1.2139_FC4.
My question is: my I remove this package from the system or I've
missed some things?
Thanks in advance
--
Alessandro Brezzi
17 years, 11 months
New Motherboard Install
by Don Maxwell
It appears that my current motherboard is flaking out on me. It is 6
yrs old so I got my money's worth out of it for sure!
What is the prevailing thought on replacing a MB in an existing system?
I really want to preserve what I can in terms of applications and
configurations. Obviously, all the I/O will be different. Video,
audio, and LAN concerns do give me pause.
The PC has two hard disks: One 30 GB where most everything resides
and one 80GB which is my /home partition.
The options seem to be:
1) Pop the new MB in and hope that Kudzu figures everything out
2) Reinstall FC5 over my existing setup
3) Blow away everything on my 30 GB disk and start mostly from
scratch, using my various backed up .conf files?
Thanks!
--Don
17 years, 11 months
Bind Zone Transfer Problem
by Charles Curley
I seem to be having a problem with zone transfer.
I have bind running inside my local domain (an experimental network
that the outside world never sees).
I set up the master as follows:
// We are authoritative for this zone.
zone "localdomain" IN {
type master;
file "localdomain";
allow-transfer {
# 192.168.1.12;
192.168.1.32;
192.168.1.4;
};
allow-update { none; };
};
For the same zone, the slave is as follows:
// We are authoritative for this zone.
zone "localdomain" IN {
type slave;
file "localdomain";
masters { 192.168.1.3; };
};
The transfer appears to start. The master reports, e.g:
Jul 3 17:46:14 charlesc named[27334]: client 192.168.1.4#48326: transfer of 'localdomain/IN': AXFR started
It never reports that the transfer ends.
Jul 3 17:46:16 dragon named[14083]: zone localdomain/IN: Transfer started.
Jul 3 17:46:16 dragon named[14083]: transfer of 'localdomain/IN' from 192.168.1.3#53: connected using 192.168.1.4#48326
Jul 3 17:46:16 dragon named[14083]: dumping master file: tmp-EYbYqUHud2: open: permission denied
Jul 3 17:46:16 dragon named[14083]: transfer of 'localdomain/IN' from 192.168.1.3#53: failed while receiving responses: permission denied
Jul 3 17:46:16 dragon named[14083]: transfer of 'localdomain/IN' from 192.168.1.3#53: end of transfer
What am I doing wrong?
--
Charles Curley /"\ ASCII Ribbon Campaign
Looking for fine software \ / Respect for open standards
and/or writing? X No HTML/RTF in email
http://www.charlescurley.com / \ No M$ Word docs in email
Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
17 years, 11 months
Re: Checking internet connection without a winbox
by Dotan Cohen
On 03/07/06, Roger Taranto <roger(a)rogflies.com> wrote:
> Given the other results you've posted to the list, I think you may be
> okay between the router and the NIC. I have an older DSL modem that
> uses different settings, but considering that you have auto-negotiation
> on, I would think that your settings are probably okay. You could
> google for the manual for your cable modem and see what settings it
> prefers for the ethernet port and see if that's what you have.
>
> But, I'd suggest following Joanne's advice (jdow) on using ping. She
> writes device drivers and probably knows what she's talking about. :)
>
> -Roger
>
Thanks, Roger. I so did, and got an interesting result. You can see
that as I work my way out, the ping time gets slowly longer, but on
the last one, it jumps from ~13 ms to ~88 ms. Does that seem unusual,
or is because it's going across a large way? I did ping a .co.il (my
country's domain extension) address, but that does not necessarily
mean that the site is hosted here.
traceroute: Warning: google.co.il has multiple addresses; using 216.239.37.99
traceroute to google.co.il (216.239.37.99), 30 hops max, 40 byte packets
1 192.168.123.254 (192.168.123.254) 0.656 ms 0.727 ms 0.443 ms
2 c1.actcom.co.il (192.114.47.218) 11.318 ms 10.208 ms 9.154 ms
3 rtr76.actcom.co.il (192.114.47.250) 10.096 ms 17.469 ms 8.018 ms
4 nv-act.ser.netvision.net.il (199.203.173.126) 14.279 ms 12.589
ms 11.864 ms
5 gi1-0.core1.hfa.nv.net.il (212.143.8.1) 15.324 ms 15.684 ms *
6 pos2-10.brdr1.lnd.nv.net.il (212.143.12.122) 88.808 ms 87.282 ms
$ ping -c 8 192.114.47.218
PING 192.114.47.218 (192.114.47.218) 56(84) bytes of data.
64 bytes from 192.114.47.218: icmp_seq=1 ttl=63 time=14.7 ms
64 bytes from 192.114.47.218: icmp_seq=2 ttl=63 time=19.2 ms
64 bytes from 192.114.47.218: icmp_seq=3 ttl=63 time=9.11 ms
64 bytes from 192.114.47.218: icmp_seq=4 ttl=63 time=10.7 ms
64 bytes from 192.114.47.218: icmp_seq=5 ttl=63 time=12.0 ms
64 bytes from 192.114.47.218: icmp_seq=6 ttl=63 time=9.92 ms
64 bytes from 192.114.47.218: icmp_seq=7 ttl=63 time=8.49 ms
64 bytes from 192.114.47.218: icmp_seq=8 ttl=63 time=11.4 ms
--- 192.114.47.218 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7026ms
rtt min/avg/max/mdev = 8.496/11.982/19.286/3.309 ms
$ ping -c 8 192.114.47.250
PING 192.114.47.250 (192.114.47.250) 56(84) bytes of data.
64 bytes from 192.114.47.250: icmp_seq=1 ttl=253 time=10.0 ms
64 bytes from 192.114.47.250: icmp_seq=2 ttl=253 time=10.9 ms
64 bytes from 192.114.47.250: icmp_seq=3 ttl=253 time=8.68 ms
64 bytes from 192.114.47.250: icmp_seq=4 ttl=253 time=11.6 ms
64 bytes from 192.114.47.250: icmp_seq=5 ttl=253 time=11.5 ms
64 bytes from 192.114.47.250: icmp_seq=6 ttl=253 time=16.7 ms
64 bytes from 192.114.47.250: icmp_seq=7 ttl=253 time=230 ms
64 bytes from 192.114.47.250: icmp_seq=8 ttl=253 time=235 ms
--- 192.114.47.250 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7029ms
rtt min/avg/max/mdev = 8.687/66.919/235.626/95.825 ms
$ ping -c 8 199.203.173.126
PING 199.203.173.126 (199.203.173.126) 56(84) bytes of data.
64 bytes from 199.203.173.126: icmp_seq=1 ttl=252 time=13.1 ms
64 bytes from 199.203.173.126: icmp_seq=2 ttl=252 time=13.5 ms
64 bytes from 199.203.173.126: icmp_seq=3 ttl=252 time=13.6 ms
64 bytes from 199.203.173.126: icmp_seq=4 ttl=252 time=16.4 ms
64 bytes from 199.203.173.126: icmp_seq=5 ttl=252 time=14.0 ms
64 bytes from 199.203.173.126: icmp_seq=6 ttl=252 time=14.4 ms
64 bytes from 199.203.173.126: icmp_seq=7 ttl=252 time=11.6 ms
64 bytes from 199.203.173.126: icmp_seq=8 ttl=252 time=13.8 ms
--- 199.203.173.126 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7032ms
rtt min/avg/max/mdev = 11.650/13.842/16.442/1.257 ms
$ ping -c 8 212.143.8.1
PING 212.143.8.1 (212.143.8.1) 56(84) bytes of data.
64 bytes from 212.143.8.1: icmp_seq=1 ttl=251 time=11.8 ms
64 bytes from 212.143.8.1: icmp_seq=2 ttl=251 time=13.6 ms
64 bytes from 212.143.8.1: icmp_seq=3 ttl=251 time=12.0 ms
64 bytes from 212.143.8.1: icmp_seq=4 ttl=251 time=16.1 ms
64 bytes from 212.143.8.1: icmp_seq=5 ttl=251 time=16.5 ms
64 bytes from 212.143.8.1: icmp_seq=6 ttl=251 time=14.0 ms
64 bytes from 212.143.8.1: icmp_seq=7 ttl=251 time=14.4 ms
64 bytes from 212.143.8.1: icmp_seq=8 ttl=251 time=13.0 ms
--- 212.143.8.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7035ms
rtt min/avg/max/mdev = 11.841/13.971/16.545/1.624 ms
$ ping -c 8 212.143.12.122
PING 212.143.12.122 (212.143.12.122) 56(84) bytes of data.
64 bytes from 212.143.12.122: icmp_seq=1 ttl=250 time=89.9 ms
64 bytes from 212.143.12.122: icmp_seq=2 ttl=250 time=88.6 ms
64 bytes from 212.143.12.122: icmp_seq=3 ttl=250 time=89.4 ms
64 bytes from 212.143.12.122: icmp_seq=4 ttl=250 time=87.2 ms
64 bytes from 212.143.12.122: icmp_seq=5 ttl=250 time=88.1 ms
64 bytes from 212.143.12.122: icmp_seq=6 ttl=250 time=91.2 ms
64 bytes from 212.143.12.122: icmp_seq=7 ttl=250 time=87.6 ms
64 bytes from 212.143.12.122: icmp_seq=8 ttl=250 time=86.9 ms
--- 212.143.12.122 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7036ms
rtt min/avg/max/mdev = 86.991/88.668/91.267/1.409 ms
$
Dotan Cohen
http://what-is-what.com
17 years, 11 months
Re: kmod-nvidia not working in kernel-2.6.17-1.2139_FC5
by Deepak
Thanks, it successfully removed the kmod-nvidia. There is no difference in
nvidia driver installed and not installled. Only display is shifted a bit. X
is working nice.
Thanks again!
On 7/4/06, Deepak Shrestha <d88pak(a)gmail.com> wrote:
>
> Thanks, I will give it a try.
>
> On 7/4/06, Scott R. Godin <scott.g(a)mhg2.com> wrote:
>
> > On Tue, 2006-07-04 at 22:43 +0800, Deepak Shrestha wrote:
> > I think my problem is not going to solve right away and I can live
> > without nvidia acceleration for now. By the way how can i safely
> > remove kmod-nvidia for now? Will "yum remove kmod-nvidia" will do? I
> > am asking this becasue I have upgraded the kernel ( to 2.6.17) and
> > removed my old kernel (2.6.15) already. So i don't know if I try to
> > remove this kmod-nvidia, I might end up without X or something like
> > that??? because I saw during kmod-nvidia, it changed several settings
> > of X.org configs.
> >
> >
> [massive snip including previous sig and pgp keys]
>
> run (sudo yum remove kmod-nvidia xorg-x11-drv-nvidia)
>
> then, edit and set /etc/inittab so that you boot to runlevel 3
> temporarily, and then reboot.
>
> it *should* set /etc/X11/xorg.conf back to original settings (it
> preserves the original); you can double check this by looking in the
> driver section. You should see the driver section show as "nv" instead
> of "nvidia".
>
> [Worst case scenario, you can trash the xorg.conf and re-run
> system-config-display, but save that for extreme desperate measures.]
>
> you can then run (startx) from your user account to test things. if all
> works well, re-edit /etc/inittab back to booting at runlevel 5.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.4 (GNU/Linux)
>
> iD8DBQBEqoIllfQeTCNIWLARAm6wAJ9WRWl+uhf2FebITjPJzNwNN7ks8gCffiOe
> ZYelsRlh+4091exucNKQpXo=
> =WPVE
> -----END PGP SIGNATURE-----
>
>
>
>
17 years, 11 months
Wireless does not wake up
by Mitja Mihelic
Hi!
I know this might be a specific problem, but perhaps there is someone
that could help me.
I am using a Prestigio Nobile 157 with FC5.
The notebook does not have a hardware button for turning the wireless on
or off.
It does howerver have a setting in BIOS, that enables it at boot time.
But after resuming from suspend to RAM the BIOS is not called and the
wireless stays off.
Does anyone know how I could enable the wireless once the notebook wakes
up from suspend ?
It should somehow be possible to do that, since a program exists for
(sorry for the word) Windows,
that does exactly that.
Thanks!
--
Mitja
17 years, 11 months
Bash Shell Scripting
by Kaushal Shriyan
Hi All
Do we have Mailing Lists for Bash Shell Scripting
Regards
Kaushal
17 years, 11 months
IO Redirection
by Kaushal Shriyan
Hi ALL
I am not able to understand IO Redirection in BASH SHELL SCRIPTING
Can any one point me to the correct docs in understanding this topic
Thanks and Regards
Kaushal
17 years, 11 months
Re: Kyum: /var/log/yum.log, could not be opened for reading.
by ron
On Mon, 2006-07-03 at 12:18 -0400, ron wrote:
But I still get:
"/var/log/yum.log could not be opened for reading."
I removed kyum, erased all remaining files, reinstalled kyum, and set
SELinux to permissive.
But still no luck.
On Mon, 03 Jul 2006 19:16:20 +0100, Paul wrote:
You are running it as root, right?
On Tue, 04 Jul 2006 05:50:00 -0400, ron wrote:
Yes, I'm running as root.
Package management works ok.
Permissions are:
-rw------- 1 root root 25262 Jul 3 13:05 yum.log
-rw-r--r-- 1 root root 30898 May 8 17:13 yum.log.1
On Tue, 04 Jul 2006 11:36:30 +0100, Paul wrote:
Does it work if you change the permissions to 644?
Paul,
No.
-ron-
17 years, 11 months
FC4 and FC5 smp version
by Joachim Backes
Hi,
Is it planned to continue smp kernel builds for FC4 and FC5? I saw that there are only single proc
kernels for the moment. I have therefore big problems on my 4xOpteron dual core server running FC4.
All load is concentrated to 1 processor, others are idleing.
Regards
--
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
University of Kaiserslautern,Computer Center [RHRK],
Systems and Operations, High Performance Computing,
D-67653 Kaiserslautern, PO Box 3049, Germany
--------------------------------------------------
Phone: +49-631-205-2438, FAX: +49-631-205-3056
http://hlrwm.rhrk.uni-kl.de/home/staff/backes.html
17 years, 11 months