In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/01 Report--
How to accurately design port in Fedora nfs, in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.
When learning Fedora, you may encounter Fedora nfs problems. Here we will introduce the solutions to Fedora nfs problems and share them with you here. Vmware installed another fedora7, this time installed gcome, the interface is super beautiful, but even a handful of Fedora nfs can not find port. Go back to the kde system (under the same xp, open it with the same vmware), and it worked. I hastened to snapshot for a moment, keep this correct state, and compare it to see what the problem is.
Correct status:
Param set linux_cmd_line "console=ttySAC0 root=/dev/nfs nfsroot=192.168.1.1:/yctek/root ip=192.168.1.12:192.168.1.1:192.168.1.1:255.255.255.0:www.yctek.com:eth0:off"
Eth0 is briaged.
Xp host ip 192.168.1.13 but ping is not available from the virtual machine, ping 192.168.1.1 from HyperTerminal, but 1.13 is also impassable, in short, ARM and Fedora nfs can ping each other (both Fedora nfs can ping But the problem is still the same) / etc/exports: / yctek/root * (rw, sync,no_root_squash) vmware eth0 both failed when starting two Fedora nfs, but it doesn't affect me to try the commands / etc/rc.d/init.d/portmap start and serivce portmap start on two Fedora nfs. As a result, I don't recognize both systems, and there is only nfs but no portmap in setup, which is different from redhat. But what should be successful is also successful. It seems that portmap has acquiesced in Fedora nfs.
After looking for it for a long time, I didn't find the problem. I'll go to vpc and have a look in redhat. The problem here is that you can find portmap, but console is active. This should not be the problem of nfs. First change / yctek/root to try the blood. I tested the required root file with .iso as I did under vmware, and there was a timestamp warning similar to that under Fedora nfs when I executed tar jxvf recover_system_pack.tar.bz2.
If you implement it, it will have an impact:
IP-Config: Complete:
Device=eth0, addr=192.168.1.12, mask=255.255.255.0, gw=192.168.1.1
Host=www, domain=, nis-domain=yctek.com
Bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.1
Looking up port of RPC 100005/1 on 192.168.1.1
Root-NFS: Server returned error-13 while mounting / yctek/root
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: test name =
VFS: fs_name =
VFS: fs_name =
VFS: fs_name =
VFS: fs_name =
VFS: tried fs_name = err=-2
VFS: Cannot open root device "nfs" or unknown-block (2pm 0)
Please append a correct "root=" boot option
Kernel panic-not syncing: VFS: Unable to mount root fs on unknown-block (2meme 0)
Fedora nfs goes up again and again, so put it first. In the original root put back / yctek, the error message is as follows:
Freeing init memory: 176K
/ etc/init.d/rcS: 20: / bin/hostname: Permission denied
Please press Enter to activate this console.
Bummer, could not run'/ bin/sh': Permission denied
Please press Enter to activate this console.
It seems that the problem still lies in the file / etc/init.d/rcS, which is exactly the same as the one in my vmware. It seems that this is not the problem.
In that kde, I copied the root directory of recover_system in .iso and released it into yctek with tar jxvf. Fedora nfs also had a timestamp warning, but it was very different from the warning in red hat. I tried to open HyperTerminal and active succeeded. But I was still worried that there was something wrong with the root, so I didn't execute the recover_system.
This is the answer to the question about how to accurately design port in Fedora nfs. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.