Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.misc > #13685 > unrolled thread

empty /proc directory

Started byporparek@gmail.com
First post2015-02-14 13:55 -0800
Last post2015-02-15 10:54 -0500
Articles 6 — 6 participants

Back to article view | Back to comp.os.linux.misc


Contents

  empty /proc directory porparek@gmail.com - 2015-02-14 13:55 -0800
    Re: empty /proc directory Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2015-02-15 00:31 +0100
      Re: empty /proc directory William Unruh <unruh@invalid.ca> - 2015-02-15 04:10 +0000
        Re: empty /proc directory Aragorn <thorongil@telenet.be.invalid> - 2015-02-15 07:34 +0100
      Re: empty /proc directory Baho Utot <baho-utot@columbus.rr.com> - 2015-02-15 07:32 -0500
    Re: empty /proc directory "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-02-15 10:54 -0500

#13685 — empty /proc directory

Fromporparek@gmail.com
Date2015-02-14 13:55 -0800
Subjectempty /proc directory
Message-ID<a1d03113-d52d-4010-a3f0-a53e3cfa344b@googlegroups.com>
After booting the system the /proc dir is empty.
My system is very small. It is even hardly to call it a system. It is just a kernel, a few directories and small init program.
The kernel is the newest stable. The kernel config is default, generated by "make menuconfig". In particular:
grep PROC .config:
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_PROC_PID_CPUSET=y
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ACPI_PROCFS=y
# CONFIG_ACPI_PROCFS_POWER is not set
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_PROCESSOR=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_PROC_EVENTS=y
CONFIG_SCSI_PROC_FS=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_RTC_INTF_PROC=y
# CONFIG_STE_MODEM_RPROC is not set
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y

/etc/fstab contains:
proc /proc procfs rw,noauto 0 0

I also do the following in my init program:
const char* opts = "mode=0700, uid=0";
unsigned long mountFlags = MS_NODEV;
mount("proc", "/proc", "procfs", mountFlags, opts);
or
mount("none", "/proc", "procfs", mountFlags, opts);

"mount" returns an error "No such device"
Please write me what do I do wrong.

Thanks all of you for help.

[toc] | [next] | [standalone]


#13687

FromPascal Hambourg <boite-a-spam@plouf.fr.eu.org>
Date2015-02-15 00:31 +0100
Message-ID<mbolsc$2r68$1@saria.nerim.net>
In reply to#13685
porparek@gmail.com a écrit :
> 
> /etc/fstab contains:
> proc /proc procfs rw,noauto 0 0
> 
> I also do the following in my init program:
> const char* opts = "mode=0700, uid=0";
> unsigned long mountFlags = MS_NODEV;
> mount("proc", "/proc", "procfs", mountFlags, opts);
> or
> mount("none", "/proc", "procfs", mountFlags, opts);
> 
> "mount" returns an error "No such device"
> Please write me what do I do wrong.

The type is "proc", not "procfs".

[toc] | [prev] | [next] | [standalone]


#13689

FromWilliam Unruh <unruh@invalid.ca>
Date2015-02-15 04:10 +0000
Message-ID<mbp67h$ber$1@dont-email.me>
In reply to#13687
On 2015-02-14, Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> wrote:
> porparek@gmail.com a ?crit :
>> 
>> /etc/fstab contains:
>> proc /proc procfs rw,noauto 0 0

Mine has
none /proc proc defaults 0 0

Ie, what is proc that is supposed to be mounted there, and what is
procfs, as mentioned by Pascal?

>> 
>> I also do the following in my init program:
>> const char* opts = "mode=0700, uid=0";
>> unsigned long mountFlags = MS_NODEV;
>> mount("proc", "/proc", "procfs", mountFlags, opts);
>> or
>> mount("none", "/proc", "procfs", mountFlags, opts);
>> 
>> "mount" returns an error "No such device"
>> Please write me what do I do wrong.
>
> The type is "proc", not "procfs".

[toc] | [prev] | [next] | [standalone]


#13691

FromAragorn <thorongil@telenet.be.invalid>
Date2015-02-15 07:34 +0100
Message-ID<mbpekp$v44$1@dont-email.me>
In reply to#13689
On Sunday 15 February 2015 05:10, William Unruh conveyed the following 
to comp.os.linux.misc...

> On 2015-02-14, Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> wrote:
>> porparek@gmail.com a ?crit :
>>> 
>>> /etc/fstab contains:
>>> proc /proc procfs rw,noauto 0 0
> 
> Mine has
> none /proc proc defaults 0 0
> 
> Ie, what is proc that is supposed to be mounted there, and what is
> procfs, as mentioned by Pascal?

The keyword "none" in the device field is a placeholder [*].  One /can/ 
substitute it with "proc" if one wishes to.

Likewise, the keyword "defaults" in the mount options field is also only 
a placeholder [*] because the defaults will still apply for any mount 
with the exception of explicitly listed non-default options.  So for 
instance, if you put "noauto" there, then all the default mount options 
will still apply except for "auto" (if that is a default mount option 
for that particular filesystem and device).  What the default mount 
options are for each device and filesystem can be gleaned from the man 
page.

  $ man mount

"procfs" is a term used by the kernel developers ─ likewise for "sysfs" 
─ but the actual filesystem type as must be used in mount commands and 
in /etc/fstab is, indeed, "proc".


[*] Placeholders are needed because /etc/fstab is a database of records
    comprised of space-separated fields.  Therefore an attempt to leave
    a field blank by omitting a particular keyword would result in an
    incorrect parsing of the file.

-- 
= Aragorn =

         http://www.linuxcounter.net - registrant #223157

[toc] | [prev] | [next] | [standalone]


#13692

FromBaho Utot <baho-utot@columbus.rr.com>
Date2015-02-15 07:32 -0500
Message-ID<a8g6rb-li92.ln1@raspberry-pi.bildanet.com>
In reply to#13687
Pascal Hambourg wrote:

> porparek@gmail.com a écrit :
>> 
>> /etc/fstab contains:
>> proc /proc procfs rw,noauto 0 0
>> 
>> I also do the following in my init program:
>> const char* opts = "mode=0700, uid=0";
>> unsigned long mountFlags = MS_NODEV;
>> mount("proc", "/proc", "procfs", mountFlags, opts);
>> or
>> mount("none", "/proc", "procfs", mountFlags, opts);
>> 
>> "mount" returns an error "No such device"
>> Please write me what do I do wrong.
> 
> The type is "proc", not "procfs".

 Device                Mountpoint       FStype          Options Dump Pass
procfs                  /proc           procfs          rw      0       0

works for me

[toc] | [prev] | [next] | [standalone]


#13695

From"David W. Hodgins" <dwhodgins@nomail.afraid.org>
Date2015-02-15 10:54 -0500
Message-ID<op.xt3vs2bla3w0dxdave@hodgins.homeip.net>
In reply to#13685
On Sat, 14 Feb 2015 16:55:41 -0500, <porparek@gmail.com> wrote:

> After booting the system the /proc dir is empty.

$ mount|grep ^proc
proc on /proc type proc (rw,relatime)

$ grep proc /etc/fstab
none /proc proc defaults 0 0

Regards, Dave Hodgins

-- 
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

[toc] | [prev] | [standalone]


Back to top | Article view | comp.os.linux.misc


csiph-web