I just finished updating my Desktop, from CentOS 5.2 to 5.3 (32 bit). There were a lot of error messages (from sbin/ldconfig ?) about 2 files, in usr/lib/lib ending in .so "is not an ELF file - It has the wrong magic bytes at the start." There were also a lot of messages I believe have to do with SELinux. I'd read the Release Notes and thought I was OK, since this box is dual boot with M$ Windows XP, thinking I had the latest and greatest way to access the NTFS partition. However, when I rebooted the box, I saw warning messages: "modprobe fuse as root" and here is the result of that: [root@dell2400 ~]# modprobe fuse [root@dell2400 ~]# exit logout [lanny@dell2400 ~]$ and another message "ntfs-3g-mount fuse device is missing" As expected, after viewing the above messages; I can't see what's on the NTFS partition. I will read the Release Notes, again, in the morning. This box has GNOME and KDE on it and I was getting messages from PUP that 185 packages were available. The update, after updating glibc, was 268 packages. A big thank you, to everyone who spent so much of their valuable and very limited time working on this update!
On Fri, Apr 10, 2009 at 9:44 PM, Lanny Marcus lmmailinglists@gmail.com wrote:
I just finished updating my Desktop, from CentOS 5.2 to 5.3 (32 bit).
<snip>
believe have to do with SELinux. I'd read the Release Notes and thought I was OK, since this box is dual boot with M$ Windows XP, thinking I had the latest and greatest way to access the NTFS partition. However, when I rebooted the box, I saw warning messages: "modprobe fuse as root" and here is the result of that:
<snip>
and another message "ntfs-3g-mount fuse device is missing" As expected, after viewing the above messages; I can't see what's on the NTFS partition. I will read the Release Notes, again, in the morning. This box has GNOME and KDE on it and I
<snip>
Follow on: I read the 5.3 Release Notes (again) and the NTFS "Tips and Tricks" on the Wiki (again) and started following the instructions, again. I am not sure whether it was trying to install the NTFS packages again, or the shutdown last night and cold boot this morning, but now I can write to the NTFS partition again. :-)
[root@dell2400 ~]# yum install fuse fuse-ntfs-3g dkms dkms-fuse Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile * epel: archive.linux.duke.edu * rpmforge: apt.sw.be * base: mirror.skiplink.com * updates: mirrors.rit.edu * addons: mirror.sanctuaryhost.com * extras: styx.biochem.wfubmc.edu 1589 packages excluded due to repository priority protections Setting up Install Process Parsing package install arguments Package fuse-2.7.4-1.el5.rf.i386 already installed and latest version Package fuse-ntfs-3g-2009.2.1-1.el5.rf.i386 already installed and latest version Package dkms-2.0.20.4-1.el5.rf.noarch already installed and latest version Package dkms-fuse-2.7.4-1.nodist.rf.noarch already installed and latest version Nothing to do [root@dell2400 ~]#
On Sat, Apr 11, 2009 at 5:15 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
Follow on: I read the 5.3 Release Notes (again) and the NTFS "Tips and Tricks" on the Wiki (again) and started following the instructions, again. I am not sure whether it was trying to install the NTFS packages again, or the shutdown last night and cold boot this morning, but now I can write to the NTFS partition again. :-)
[root@dell2400 ~]# yum install fuse fuse-ntfs-3g dkms dkms-fuse
Parsing package install arguments Package fuse-2.7.4-1.el5.rf.i386 already installed and latest version Package fuse-ntfs-3g-2009.2.1-1.el5.rf.i386 already installed and latest version Package dkms-2.0.20.4-1.el5.rf.noarch already installed and latest version Package dkms-fuse-2.7.4-1.nodist.rf.noarch already installed and latest version Nothing to do [root@dell2400 ~]#
Good to hear things are working again. When you boot to a new kernel, dkms kicks in and rebuilds kernel modules automatically. You probably saw some delay during the first boot to the updated kernel while dkms was doing its job.
Akemi
On 4/11/09, Akemi Yagi amyagi@gmail.com wrote:
On Sat, Apr 11, 2009 at 5:15 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
Follow on: I read the 5.3 Release Notes (again) and the NTFS "Tips and Tricks" on the Wiki (again) and started following the instructions, again. I am not sure whether it was trying to install the NTFS packages again, or the shutdown last night and cold boot this morning, but now I can write to the NTFS partition again. :-)
<snip>
Good to hear things are working again. When you boot to a new kernel, dkms kicks in and rebuilds kernel modules automatically. You probably saw some delay during the first boot to the updated kernel while dkms was doing its job.
Akemi: I believe it is also very possible that after I did "modprobe fuse" as root last night, that I did not reboot. I believe the reboot is required, to get that running? This is critical, because I have files for our web sites on the NTFS partition that I cannot write to a CD-RW while using Windows. :-) The Windows SW gets into a loop and the estimated time just keeps increasing and increasing. I can write those files with K3b, without any problems. :-) I am getting more SELinux alerts now, after the upgrade to 5.3. Lanny
Lanny Marcus wrote:
Akemi: I believe it is also very possible that after I did "modprobe fuse" as root last night, that I did not reboot. I believe the reboot is required, to get that running? This is critical, because I have files for our web sites on the NTFS partition that I cannot write to a CD-RW while using Windows. :-) The Windows SW gets into a loop and the estimated time just keeps increasing and increasing. I can write those files with K3b, without any problems. :-) I am getting more SELinux alerts now, after the upgrade to 5.3. Lanny
You may not need them now, but other approaches that might work would be having a fat partition that both windows and linux could access, or running one or the other under VMware or Virtualbox so you don't have to reboot between OS versions and can use either samba or the VM folder sharing to access files on the other side.
On 4/11/09, Les Mikesell lesmikesell@gmail.com wrote:
Lanny Marcus wrote:
Akemi: I believe it is also very possible that after I did "modprobe fuse" as root last night, that I did not reboot. I believe the reboot is required, to get that running? This is critical, because I have files for our web sites on the NTFS partition that I cannot write to a CD-RW while using Windows. :-) The Windows SW gets into a loop and the estimated time just keeps increasing and increasing. I can write those files with K3b, without any problems. :-) I am getting more SELinux alerts now, after the upgrade to 5.3. Lanny
You may not need them now, but other approaches that might work would be having a fat partition that both windows and linux could access, or running one or the other under VMware or Virtualbox so you don't have to reboot between OS versions and can use either samba or the VM folder sharing to access files on the other side.
Les: Years ago (before CentOS 5?), I did have a FAT partition like that. The current SW available for CentOS, for NTFS, has been doing a great job for me. I don't recall having this problem, with previous CentOS upgrades, and it was easy to cure. To clarify what I meant by the reboot, after "modprobe fuse', I meant rebooting Linux, to get fuse started. Wish I had a box with more RAM, so I could try VMware or Virtualbox. That is something I want to try, but this box only has 512 MB of RAM. Lanny
On Sat, Apr 11, 2009 at 11:35 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
Les: Years ago (before CentOS 5?), I did have a FAT partition like that. The current SW available for CentOS, for NTFS, has been doing a great job for me. I don't recall having this problem, with previous CentOS upgrades, and it was easy to cure. To clarify what I meant by the reboot, after "modprobe fuse', I meant rebooting Linux, to get fuse started.
Years ago, use of FAT was the recommended way. One main reason was that writing to NTFS partitions from Linux was dangerous. This has changed and now it is regarded safe to do so by using ntfs-3g.
I do not know exactly what failed in your case. I have yet to update my CentOS-5 laptop that has WIndows on one partition (NTFS). Will see how it goes.
Akemi
On Sat, 2009-04-11 at 13:35 -0500, Lanny Marcus wrote:
Wish I had a box with more RAM, so I could try VMware or Virtualbox. That is something I want to try, but this box only has 512 MB of RAM. Lanny
---- Download VirtualBox from Sun. Im pretty sure you can run it. On CentOS that is. Just use 254MB for the Host and the gueat. Just split it up. Below is tops output when runing win$ server 2003 while doing domainprep and forestprep for active directory. Processor is a P4 1.7 533MHz Bus UDMA 100 Disks. Although the virtual machine images run on:
hdd1 4.13 106.04 157.34 14226701 21109552,,
I run one image per drive and not on the system drive. The device block sizes are 4096 and they run the Deadline Scheduler. By no means it not like lightning but it runs better than some on native hardware and serves my purpose. Basically it's a testing machine. I also run CentOS 5.2 on it all on top of CentOS 5.3. Bottom line is I think it is doable with 512MB of RAM. Also this is an older board ICH4 Chipset
top - 17:32:45 up 1 day, 13:12, 2 users, load average: 1.50, 1.75, 1.46 Tasks: 107 total, 2 running, 105 sleeping, 0 stopped, 0 zombie Cpu0 : 6.8%us, 74.5%sy, 10.2%ni, 0.4%id, 6.6%wa, 1.1%hi, 0.5%si, 0.0%st Mem: 775132k total, 767532k used, 7600k free, 34268k buffers Swap: 524280k total, 102956k used, 421324k free, 230584k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10211 root 15 0 353m 296m 14m S 72.5 39.2 51:23.37 VirtualBox
JohnStanley
On Sat, Apr 11, 2009 at 4:44 PM, JohnS jses27@gmail.com wrote:
On Sat, 2009-04-11 at 13:35 -0500, Lanny Marcus wrote:
Wish I had a box with more RAM, so I could try VMware or Virtualbox. That is something I want to try, but this box only has 512 MB of RAM. Lanny
Download VirtualBox from Sun. Im pretty sure you can run it. On CentOS that is. Just use 254MB for the Host and the gueat. Just split it up. Below is tops output when runing win$ server 2003 while doing domainprep and forestprep for active directory. Processor is a P4 1.7 533MHz Bus UDMA 100 Disks. Although the virtual machine images run on:
Thank you for the information. I will check out Virtual Box from Sun! This box is a Celeron 2.6 GHz. Integrated Intel stuff on the motherboard, which was made for Dell by Foxconn I think. I think it is the only one of our 4 Dell Dimension boxes that had a rather stock ATX motherboard and PSU. The PSU was replaced after New Years Day with one that just plugged right in. No proprietary connectors. :-) I won it in a raffle from Colgate Palmolive, in the superstore where we do most of our shopping. It came with 256 MB of RAM and I bought another 256 MB for it. I think, possibly, it can hold up to 1 GB of RAM. I need to check that out. One of these days I will take the time to try to get audio out of the microphone, with the Skype Beta for Linux. Other people have it working, so I believe it is one or more configuration settings, somewhere, that are incorrect.
On Sat, Apr 11, 2009 at 6:26 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
On 4/11/09, Akemi Yagi amyagi@gmail.com wrote:
Good to hear things are working again. When you boot to a new kernel, dkms kicks in and rebuilds kernel modules automatically. You probably saw some delay during the first boot to the updated kernel while dkms was doing its job.
Akemi: I believe it is also very possible that after I did "modprobe fuse" as root last night, that I did not reboot. I believe the reboot is required, to get that running?
You can run the dkms command manually. But this is usually not necessary because ... you cannot update the running kernel without rebooting the machine. And dkms is run as part of the booting process. Therefore, everything is automatic (supposedly), hence no need for a manual run of dkms.
Akemi
On Sat, Apr 11, 2009 at 2:06 PM, Akemi Yagi amyagi@gmail.com wrote: <snip>
Akemi: I believe it is also very possible that after I did "modprobe fuse" as root last night, that I did not reboot. I believe the reboot is required, to get that running?
You can run the dkms command manually. But this is usually not necessary because ... you cannot update the running kernel without rebooting the machine. And dkms is run as part of the booting process. Therefore, everything is automatic (supposedly), hence no need for a manual run of dkms.
Thank you. Probably it kicked in, after the boot into Linux this morning. Apparently, it did not begin working, after the first reboot following the big update from 5.2 to 5.3 last night. CentOS 5.3 (32 bit) is working fine now, on my Desktop. I had been getting SELinux alerts previously, after the update to 5.3, but I just powered up, after a hailstorm where we lost power and now I'm not seeing the SELinux alert. :-)
-
Akemi Yagi -
JohnS -
Lanny Marcus -
Les Mikesell