Davy,
Mounting a file system does not write into /etc/fstab, only(?) /etc/mtab.
Check to make sure that your proc file system is really mounted:
ls /proc
On my system, this yields:
ls /proc
1 214 281 4286 463 531 5652 bus interrupts mdstat
self
1023 218 291 4298 464 532 5655 cmdline ioports meminfo
slabinfo
1024 222 3 430 472 533 5677 config.gz kcore misc
stat
132 226 3314 4300 497 534 5697 cpuinfo kcore_elf modules
swaps
146 227 3980 4405 5 535 570 dasd kmsg mounts
sys
150 228 4 4435 506 549 572 devices ksyms net
tty
162 229 4051 4516 514 5513 573 dma loadavg partitions
uptime
2 262 4081 457 529 5648 6 filesystems locks s390dbf
version
213 269 424 461 530 5650 616 fs lvm scsi
Then ls /proc/net
arp dev_stat ip_fwnames netlink route snmp tr_rif
dev igmp ip_mr_cache netstat rpc sockstat udp
dev_mcast ip_fwchains ip_mr_vif raw rt_cache tcp unix
Mark Post
-----Original Message-----
From: Davy Michiels [mailto:davy@;industria.be]
Sent: Tuesday, October 22, 2002 12:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Boot problem SLES 7 net-pf-x module
We set our mount command verbose
the output is '/proc on /proc type proc (rw)'
So the mount command is succesfull
Because the disk is Read-Only at that moment (later on an Read-Write
volume is bind mounted) no output is written in /etc/mtab !
However the error of 'Warning: cannot open /proc/net/dev (No such file or
directory). Limited output.' still appears....
Does the line'/proc /proc proc defaults 0 0'
has to be in /etc/fstab always, or is it written there by the mount
command?
Greetz
Davy
On Tue, 22 Oct 2002, Post, Mark K wrote:
> Davy,
>
> I doubt your missing modules are causing the problem.
> net-pf-3 = Amateur Radio AX.25
> net-pf-9 = X.25
>
> It sounds more like your /proc file system is not mounted. Do you have
the
> following in /etc/fstab?
> /proc /proc proc defaults 0 0
>
> Does it show up if you do a mount command?
>
> Mark Post
>
> -----Original Message-----
> From: Davy Michiels [mailto:davy@;industria.be]
> Sent: Tuesday, October 22, 2002 10:47 AM
> To: [EMAIL PROTECTED]
> Subject: Boot problem SLES 7 net-pf-x module
>
>
> Hi,
>
> We're trying to set up a SLES7 on z/VM Version 4 Release 2.0.
> We use CTC as network connection to VM.
>
> We're implementing the methods described in the Redbook SG24-6824-00
'Large
> Scale Linux Deployment' to build a basevolume/guestvolume system.
> The bind mounting works fine...
> We just have a problem with some kernel modules: net-pf-3 and net-pf-9
> They can not be found when ipl'ing the system.
> We tried to put them 'off' in /etc/modules.conf but still there was a
> problem
> with the network
>
> As you can see in the log beneath, the /proc/net/dev cannot be found.
> Thus the network cannot be initialized ....
>
> Our question is: what causes what?
> Are the missing modules (net-pf-x) the cause of our network problems or is
> something else wrong??
>
> If you now anything that can help, let us know
>
>
> ------Output during booting ----
> IPv6 v0.8 for NET4.0
> IPv6 over IPv4 tunneling driver
> modprobe: modprobe: Can't locate module net-pf-3
> modprobe: modprobe: Can't locate module net-pf-9
> CTC driver Version: 1.51 initialized
> ctc0: read: ch 0800 (irq 0001), write: ch 0801 (irq 0002) proto: 0
> modprobe: modprobe: Can't locate module net-pf-3
> modprobe: modprobe: Can't locate module net-pf-9
> Warning: cannot open /proc/net/dev (No such file or directory). Limited
> output.
>
> ...ctc0: connected with remote side
> ...done
> Setting up routing
> (using /etc/route.conf)/etc/init.d/rc3.d/S07route: /proc/net/dev: No such
> file
> or directory
> /etc/init.d/rc3.d/S07route: /dev/fd/62: No such file or directory
> ..done
> /proc/net/route: No such file or directory
> ----------------------------------
>
>
>
> Thx in advance
>
> Davy Michiels
> Stijn Eulaerts
>
> Group T Leuven Engineering School
> www.groupt.be
>
-------------------
[EMAIL PROTECTED]
0478/719675
-------------------
