tag:blogger.com,1999:blog-6049190145500307703.post3252305940402694268..comments2012-08-28T00:34:18.784+03:00Comments on daChaac's development activities: Guide to get WPA-PSK working on PS3 - YDL 5.0.2daChaachttp://www.blogger.com/profile/07011801319322762492noreply@blogger.comBlogger98125tag:blogger.com,1999:blog-6049190145500307703.post-70349656635199104322009-02-08T21:41:00.000+02:002009-02-08T21:41:00.000+02:00ok i've gotten my internet working. my problem is ...ok i've gotten my internet working. my problem is getting it to stay after i reboot. u say "To get it working automatically you must modify two files:<BR/> /etc/sysconfig/networking/devices/ifcfg-eth0<BR/> /etc/sysconfig/networking/devices/keys-eth0" but how do i edit them? reading through the comments on your step by step, i noticed people saying to create the files and then to edit them. someone else said to do it in nano. i'm so confused. when i type in the ''/etc/sysconfig/networking/devices/ifcfg-eth0'' it says permission denied. do i need to run it as a command? plz explain to me how to go about doing this. thnx in advance!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-70879174996649654962009-01-22T22:58:00.000+02:002009-01-22T22:58:00.000+02:00take a look here:http://www.yellowdog-board.com/vi...take a look here:<BR/>http://www.yellowdog-board.com/viewtopic.php?f=19&t=4416Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-20098310809016950502009-01-05T13:43:00.000+02:002009-01-05T13:43:00.000+02:00Hi CalvinSince this guide is over a year old, and ...Hi Calvin<BR/><BR/>Since this guide is over a year old, and it is based on a version of YDL from a while ago (v5.0.2), it is a good starting point, but quite out of date. So that's why I felt the need to put up my notes on how I got things working with the current version of Yellowdog. It is certainly not the only way, but it seems to at least get things working for now until someone can help find a more efficient and effective method.<BR/><BR/>Some quick pointers:<BR/>- YDL 6.1 has more recent versions of the software packages already installed. So you can ignore daChaac's tips on getting the packages downloaded and installed. The current version has all the right software to get things working, it is just odd that for some reason the easy way of doing things doesn't seem to work (well, it doesn't work for some of us at least). Hence the need to break out a bash shell and start typing stuff at the command line (unfortunately!).<BR/>- eth0 is conventionally assigned by Linux systems as the name for the first Ethernet device into which you plug a LAN cable for networking. By definition, that device/port/socket (whatever you want to call it) does not perform wireless networking. So that is why you get nothing when you try to get iwconfig to probe that device.<BR/>- wlan0 is one of the typical names given to a wireless networking device. So that is why iwconfig DOES give you details when you tell it to probe that device. <BR/>- to reinforce the obvious here: there is one Ethernet device (eth0) and one Wifi device (wlan0) on the PS3 [by the way, there is also another device name for the Bluetooth device on the box which does a form of wireless communication, but I won't get into that as it'll confuse things further]<BR/>- since iwconfig is showing info for wlan0 it proves, amongst other things, that: a) the wireless tools software is installed and working fine; b) the device is properly recognised by the operating system. You should therefore be able to get basic unencrypted wifi networking, or even WEP encrypted wifi networking going quite easily (although I didn't try this, as I use WPA now for my network.. as I expect you do too, otherwise you would never have ended up reading this thread)<BR/><BR/>Please do try my tips on getting it going. I know it looks quite scarily advanced (it is not really that scary nor advanced), but one of the main reasons I put in so much detail was to (hopefully) help anyone who is a bit unsure to see what the output of the commands should look like, instead of just talking about typing something without you seeing an example of what I mean.<BR/><BR/>If you follow the steps on my blog page from where I have "-- 1. Created the startup link in runlevel 3".<BR/><BR/>You should be able to follow each step from there - the prompt should look the same or quite similar (ending in the '#' sign) and you type the commands in from there as I typed them in. You should see the same or similar out put. For each command you are not sure of what it is or means, try google for the manual page info (e.g. google for: man cd) and you will get an idea of what things like the following are doing: cd, ln, ls, mv, cat<BR/><BR/>To edit files like wpa_supplicant.conf you will probably do best to use the Gnome Text Editor "gedit", i.e. at the command line type: gedit /etc/wpa_supplicant/wpa_supplicant.conf<BR/><BR/>When you are done, save and close it, then use cat to display (or "catalogue") the contents of the file to confirm your changes.<BR/><BR/>Similarly, to edit the interface configuration file for eth0 to change that "ONBOOT" setting, edit the file with: gedit /etc/sysconfig/networking/devices/ifcfg-eth0<BR/><BR/>And in the interface configuration file for wlan0 (/etc/sysconfig/networking/devices/ifcfg-wlan0) the key ones to worry about should be: DEVICE=wlan0; BOOTPROTO=dhcp; ESSID=YourWifiNetworkName; TYPE=Wireless; MODE=Auto; RATE=Auto<BR/><BR/>And when I talk earlier on about modifying the /etc/init.d/wpa_supplicant file, try that also with: gedit /etc/init.d/wpa_supplicant<BR/><BR/>If you do not login to the GNOME desktop, it may be worth you trying that too: at the graphical login prompt, there is a "Session" button/menu where you can select "GNOME" before you input your user ID and password to login.<BR/><BR/>Good luck in your Linux crash-course!<BR/><BR/>;->Stephen Venterhttps://www.blogger.com/profile/12678130247024659821noreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-44327467519873652712009-01-05T02:41:00.000+02:002009-01-05T02:41:00.000+02:00hey thanks for the write-up. hopefully someone wi...hey thanks for the write-up. hopefully someone will read this problem i'm having and can assist me.<BR/><BR/>as a reference, i have an 80 gb ps3 with backward compatibility (the mgs4 bundle) with ydl 6.1 installed.<BR/><BR/>i followed three people's guides: daChaac, 151 (it's in the comments, posted july 8 2008) and Ward (it's in the comments, posted november 21 2008). <BR/><BR/>so anyways following Ward's comment: <BR/>in terminal i logged in as root, then typed cd Desktop to go to desktop, then i typed <B>rpm -Uvh wireless-tools-29-2.fc9.ppc64.rpm --force</B> because i had that file waiting on the desktop. it was recognized and had the 100% notifications.<BR/><BR/>following 151's comment:<BR/>i typed cd /sbin and was in that directory.<BR/><BR/>this is where i'm jammed up:<BR/>when i typed <B>./iwconfig eth0</B> this error came up: <B>no wireless extensions</B>. basically what daChaac said in his step about iwconfig eth0, i'm not getting that. but when i typed in <B>./iwconfig wlan0</B> some stats came up about that, similiar to what daChaac wrote about eth0. so then i just typed <B>./iwconfig</B> and a list of things came up: <B>lo no wireless connection, eth0 no wireless connection, wlan0</B> and the data for wlan0. my question is, why is it saying no wireless connection? and what can i do to fix it? i'm pretty sure if i fix that i can complete this whole process.<BR/><BR/>what i tried doing all ready:<BR/>-jumping ahead to step 3 in daChaac's guide and modifying those two files. didn't do anything.<BR/>-reinstalling the OS. the first time i installed it, at the screen with the network connections, i had the wlan0 box checked and eth0 box unchecked. the second time i installed the OS, i had wlan0 unchecked and eth0 checked.<BR/>-typing slowly. still got the same error.<BR/><BR/>i would really like to try the guide that stephen venter (above) wrote but since this is only my second day of using linux (my first day being yesterday when i first installed ydl in my ps3) i don't think i'm as advanced to do that. but basically yeah if someone can help me with this "no wireless connection" problem i'm getting with the eth0 then that would help. thank you. i'll be checking this blog daily.<BR/><BR/>thanks to everyone that put in their input. i'm slowly getting there.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-80957128289694670822008-12-22T04:12:00.000+02:002008-12-22T04:12:00.000+02:00Edit: because this was getting a bit long to post ...Edit: because this was getting a bit long to post as a comment, I've posted this, together with more detail, here: http://stephenventer.blogspot.com/2008/12/getting-wpa-psk-working-on-ps3.html <BR/><BR/>I recently got YDL 6.1 going and was struggling with getting WPA encryption working when connecting to my WiFi router.<BR/><BR/>I found that it worked for me when I ran the wpa_supplicant command as follows, and left it running:<BR/>[root@ps3ydl devices]# wpa_supplicant -dd -Dwext -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf &<BR/><BR/>Then when I did a restart of networking with "service network restart", now everything stayed connected. So I found that the best way for me to get my wifi connecting correctly at boot time, was by modifying the startup script for the wpa_supplicant service.<BR/><BR/>I modified the "daemon" line in the "start()" section of my /etc/init.d/wpa_supplicant file so that it creates a process with options like the one I ran manually.<BR/>This is what the "daemon" line in the "start()" section was BEFORE I changed it:<BR/>daemon $prog -c $conf $INTERFACES $DRIVERS -B $OTHER_ARGS<BR/><BR/>This is what it looks like now:<BR/>daemon $prog -Dwext -iwlan0 -c $conf $INTERFACES $DRIVERS -B $OTHER_ARGSStephen Venterhttps://www.blogger.com/profile/12678130247024659821noreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-37297602361922650522008-12-22T03:53:00.000+02:002008-12-22T03:53:00.000+02:00To confirm that you are running as root at the ter...To confirm that you are running as root at the terminal, use the "id" command. You should see the output start with "uid=0":<BR/><BR/>[root@ps3ydl ~]# id<BR/>uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)<BR/>[root@ps3ydl ~]#Stephen Venterhttps://www.blogger.com/profile/12678130247024659821noreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-4927867778735793882008-11-29T02:32:00.000+02:002008-11-29T02:32:00.000+02:00Hi, just installed yellow dog 6.0 on the ps3 and w...Hi, just installed yellow dog 6.0 on the ps3 and went through all the steps and getting i get a ip address and can get on the internet. But when i go in to edit the script to work on boot up /etc/sysconfig/networking/devices/ifcfg-eth0 it says access denied. Im loged in as root and still says access denied. It does the same when i try to access the scripts also. /etc/sysconfig/network-scripts. Im stuck and im doing everthing i can but will not let me access the files???? Please any help would be great..ThanksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-21311847037597853392008-11-21T22:43:00.000+02:002008-11-21T22:43:00.000+02:00Thanks to daChaac for the thorough writeup as well...Thanks to daChaac for the thorough writeup as well as the other folks for adding their invaluable comments, otherwise I wouldn't have gotten this to work, but I did.<BR/><BR/>Some advice that took me about 4 days of trying to compile....<BR/>download the wireless tools 29.2.fc9.ppc64.rpm from one of the sites listed in above comments- the older one may have worked too, but this worked for me. And on the reboot setup, I used the network-scripts directory and then created the files from scratch-then it worked for me.<BR/><BR/>Go to the terminal on your shelf in Linux and double click on it.<BR/><BR/>type in su<BR/><BR/>then type in your root password.<BR/><BR/>Change your directory to the Desktop with- cd Desktop<BR/><BR/>then type in the rpm -Uvh wireless-tools-29-2.fc9.ppc64.rpm --force<BR/><BR/>that will start you off. then use ./(then the command of daChaacs), for example-./iwconfig eth0) for each command you do....follow daChaac's directions CAREFULLY (trust me, the slower you go at first the more time and frustration you will save) after that, making sure you are checking if your MAC address was associated and then that you got an IP address after the dhclient command.<BR/><BR/>if you did get an IP address you are successful at accessing the internet now, but you have to continue if you want it to start up automatically on reboot.<BR/><BR/>I had to look up some linux commands to be able to create some files, because the ifcfg-eth0 file wasn't there, as well as the keys-eth0 file.<BR/><BR/>if you got an IP address with the dhclient eth0 command then...<BR/><BR/>change directory to /etc/sysconfig/network-scripts<BR/>then create the files by typing in cat > ifcfg-eth0 <BR/>and hit enter. it will then allow you to type in the lines as daChaac has indicated (for example DEVICE=eth0). after each line hit enter. when you are finished with that hold down ctrl D. you are now done with the ifcfg-eth0 file and you should get the root prompt again.<BR/><BR/>Next type in cat > keys-eth0<BR/>and type in the lines as daChaac indicated, hitting enter after each line. When you are finished with that, hold down ctrl D again.<BR/><BR/>when you get the prompt again, finish up the the ./ifdown eth0 and ./ifup eth0 and you should be all set.<BR/><BR/>good luck I needed itAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-89795155715087148452008-11-16T16:00:00.000+02:002008-11-16T16:00:00.000+02:00Thomas, have you downloaded or transfered "wireles...Thomas, have you downloaded or transfered "wireless-tools-28-1.ppc64.rpm" - and installed it?<BR/>Make sure that you are the user "root". you can type: "su -" (without ") and you will be promted for roots password - the first one you entered during YDL-installation.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-30782969331573312332008-11-15T20:42:00.000+02:002008-11-15T20:42:00.000+02:00Running YDL_6 on a 60GB 2.51.Wpa-psk works perfect...Running YDL_6 on a 60GB 2.51.<BR/>Wpa-psk works perfect, but I cant find the ipcfg file, so I´m using Phils init.d script instead.<BR/>Thanx Thanx ThanxAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-25017835290452748682008-11-15T19:32:00.000+02:002008-11-15T19:32:00.000+02:00after a succesfull installation i can't find the t...after a succesfull installation i can't find the tools. please help. iwconfig not found, etc. none of the files can be found. i installed as root, looked in /usr/bin, etc. folders nothing found. no iwconfig, no ifconfig, etc. PLEASE HELP. thanksUnknownhttps://www.blogger.com/profile/09612486709351206868noreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-17642507741106800282008-10-30T16:28:00.000+02:002008-10-30T16:28:00.000+02:00I have the new 2.50 PS3 firmware installed with 80...I have the new 2.50 PS3 firmware installed with 80Gig HD and YDL 6xx installed. <BR/>I try this guide but is it impossible to go with this steps guide instructions... and wifi with WPA2 with AES security doesn't work... I can't put any router cable (100 feet!!!0 bullshittttttttttt!"/$%?&*()_animauxperdushttps://www.blogger.com/profile/02485420625291244080noreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-88402207292680310592008-10-22T15:35:00.000+03:002008-10-22T15:35:00.000+03:00must the key be in the form s:PassPhrase ?i tried ...must the key be in the form <BR/>s:PassPhrase ?<BR/><BR/>i tried a hex like <BR/><BR/>iwconfig eth0 key 831E3A9FBB1E0831AEADA10CB5FFA3B06EE5EB61887C8DDBFFB5389316A4C00A<BR/>could this be why it wont work.<BR/><BR/>or is it the fact that iwlist scan finds 15 networks, but the ESSID of mine is wrong, i just see the last 5 letters out of 8 like this:<BR/>say my essid war hamburgr iwlist scan shows<BR/>Cell 07 - Address: 00:00:00:68:61:6D <BR/>ESSID:"burgr "<BR/><BR/>the hex-savvy can see that the last hex part of the Address is in fact the letters h:a:m<BR/><BR/><BR/>YDL 6<BR/>PS3 80 GB PALAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-75305780107423353392008-10-16T01:31:00.000+03:002008-10-16T01:31:00.000+03:00step 1 install? i did it once but now i cant im us...step 1 install? i did it once but now i cant im using an sd card to tranfer the files then i dont know wat to do in the terminal to install. i drag n drop the files in there dat didnt work then i tried typing <BR/>rpm -Uvh wireless-tools-28-1.ppc64.rpm--force while im logged in as root but i still get no such file or directory. can u help me just with this first step pleaseeeeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-75262576985381042362008-10-07T21:30:00.000+03:002008-10-07T21:30:00.000+03:00At: http://www.terrasoftsolutions.com/support/advi...At: http://www.terrasoftsolutions.com/support/advisories.shtml<BR/><BR/>It shows:<BR/>Known Issues with GameOS 2.43<BR/>At this time, it is not recommended to update to GameOS 2.43 due to known issues with wifi and usb drives. In addition, there is an issue with using the "Boot Game OS" menu option to switch from YDL to GameOS. Note that you can switch to Game OS by shutting down YDL and pressing the power button. <BR/><BR/>I am one of those who has upgraded to 2.43 firmware and also recieve for ap_sec=0402 because my router is configured for:<BR/><BR/>Security Mode: WPA-Personal<BR/>WPA Mode: WPA+WPA2 <BR/>Cipher Type: TKIP and AES<BR/>A Passphrase is used not a hex key like in WEP security<BR/>(Router: Trendnet TEW-GR633)<BR/><BR/>A wierd thing I notice that during boot kboot prompt reports being able to get an IP address. <BR/><BR/>Has anyone had any success with a scenario like mine. I will try with the latest wireless tools rpm package: wireless-tools-29-2.fc9.ppc64.rpm <BR/><BR/>I will post updates if I get anywhere with this, otherwise I will follow other published posts to get the wired ethernet port to work instead of the wireless. <BR/><BR/>I wonder why hypervisor prevents you from using both at the same time.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-33793390012725334202008-10-06T22:15:00.000+03:002008-10-06T22:15:00.000+03:00I love you my friend.Works very fine :)I love you my friend.<BR/>Works very fine :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-25200993931014795062008-09-27T07:21:00.000+03:002008-09-27T07:21:00.000+03:00This thread was a life saver! I'm a complete newbi...This thread was a life saver! I'm a complete newbie at this Yellowdog thing and this was really straight forward. All the extra comments about what folders to go to and having to be in the root, etc...were REALLY helpful and I couldn't have made it without all of them! Thank you and keep up the great work!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-4346667765071138742008-09-08T20:22:00.000+03:002008-09-08T20:22:00.000+03:00Success on PS3. Everything you need is in the guid...Success on PS3. Everything you need is in the guide and the forums. I have the lastest firmware on the PS3 and had no problems getting YDL6 to run wireless following the guide to the [b]tee[/b]. I used the original wireless tools package and these worked just fine. Only took about 10 minutes once I got all the commands down and replaced some batteries...<BR/> Linux is very picky about file directories. If you place the wireless package on your desktop you need to specify that file location for the rpm cpmmand to find the file i.e after you are root type cd Desktop (or where ever you put the file. Also note that the directories are case sensitive. A lower case "D" on desktop will not work.) Then run the rpm command from the correct directory. After the file installs successfully use the cd /sbin command to get to the sbin directory. From here continue with the guide. Make sure you place ./ before the commands ie "./ifconfig eth0 up". <BR/>Again, 99% of this is listed in the above forums. Take some time, print the whole thing out and follow the directions exactly. <BR/><BR/> I used nano for editing the files for the reboot to work. For example, when you are in root under /sbin, enter: nano /etc/systemconfig/networking/devices/ifcfg-eth0 to begin editing the file. When done hit ctrl x, then y then enter to save the changes.<BR/><BR/>Remember the ssid is case sensitive and to type the commands exactly as you see them. Also, if yo uare using a wireless keyboard, make sure the batteries are fresh. Seems trivial, but for speedy typers this can be a big pain when half your carachters are not registering lol. Hope this helps some more of you out.<BR/><BR/>Thanks alot for this guide and all of the great forum posts people.Unknownhttps://www.blogger.com/profile/17343318291616598484noreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-33491042302909662902008-09-03T09:48:00.000+03:002008-09-03T09:48:00.000+03:00Tried this after MANY attempts to get 6.0 YDL on m...Tried this after MANY attempts to get 6.0 YDL on my PS3.<BR/>Now, it works!!<BR/><BR/>Note.....<BR/>Being new to LINUX, I kept typing -force instead of --force !!!<BR/>the biggest hurdle I had was in the routers name...the name was<BR/>blah's network<BR/>it seems LINEX didn't like the ' in the name. I logged on as root, edited the ifcfg-eth0 file, MANUALLY added in " at the begining and the end of the ESSID name....and Bingo!!<BR/><BR/>Thanks for the guide pal!! Very helpful for a complete bozo like me! Without out this guide I would be bald by now!!<BR/><BR/>Cheers,<BR/><BR/>Beeblebrox (PSN name)Beeblebroxhttps://www.blogger.com/profile/14003593590151528326noreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-25618616956695399752008-09-01T20:20:00.000+03:002008-09-01T20:20:00.000+03:00I can't seem to get this to work. I have to repeat...I can't seem to get this to work. I have to repeat the steps in the guide to get any connection. All attempts to get it to work on boot up fail. Please help.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-33390987808471704632008-08-31T07:48:00.000+03:002008-08-31T07:48:00.000+03:00This guide is too confusing. Proberbly tried it 10...This guide is too confusing. Proberbly tried it 10 times today and still no succes. Always get to the 'dhclient eth0' and then it claims that everything fails. Puts me understress for no reason.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-61460899383330492392008-08-23T16:41:00.000+03:002008-08-23T16:41:00.000+03:00Worked like a charm! Thanks for your consideration...Worked like a charm! Thanks for your consideration on writing such a good guide.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-88037923591224432492008-08-23T16:26:00.000+03:002008-08-23T16:26:00.000+03:00I've also had problems with the reboot. I had it a...I've also had problems with the reboot. I had it all working previously but I switched from TKIP to AES, also used the new wireless-tools-28-4.fc7.ppc64.rpm then the reboot seemed stopped working (don't think i stuffed anything else up). So I've just put a temporary startup script together until the real fix comes along.<BR/><BR/>ie<BR/>Create a file phileth0 (contents below) in /etc/init.d/<BR/><BR/>#!/bin/sh<BR/>iwpriv eth0 set_alg ?<BR/>iwconfig eth0 key s:passphrase<BR/>iwconfig eth0 essid ESSID<BR/>dhclient eth0<BR/>exit 0<BR/><BR/><BR/>then run...<BR/>ln -s /etc/init.d/phileth0 /etc/rc5.d/S99phileth0<BR/><BR/>and finally...<BR/>chmod 775 /etc/init.d/phileth0<BR/><BR/><BR/>I should also mention i changed ONBOOT=no in the ifcfg-eth0 file because doesn't work and slows up my startup by retrying.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-31040218688384677322008-08-18T17:48:00.000+03:002008-08-18T17:48:00.000+03:00There seems to be a lot of people having trouble g...There seems to be a lot of people having trouble getting this to work on reboot. Is there something we are all missing. Everything works find up to the last ifup eth0.<BR/><BR/>If anyone could help there would be a lot of happy people on this site, including me.<BR/><BR/>THanks...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6049190145500307703.post-44804234754984885902008-08-06T23:18:00.000+03:002008-08-06T23:18:00.000+03:00please update ur blog with this infos:if you DONT ...please update ur blog with this infos:<BR/>if you DONT use the --force flag with the RPM command I doubt anything is going to work... so the command I ran was:<BR/><BR/>rpm -Uvh wireless-tools-28-1.ppc64.rpm --force<BR/><BR/>be SURE you are ROOT before doing anything.<BR/><BR/>thanksUnknownhttps://www.blogger.com/profile/12988097949128384483noreply@blogger.com