fstab

0 views
Skip to first unread message

David

unread,
Aug 3, 2025, 11:42:59 PMAug 3
to freebsd-...@freebsd.org
Hullo,


Installing FreeBSD to an Optiplex 980.

On installing Gnome as a desktop, and restarting, I get a fault to the
effect that the FStype is wrong.

I'm following directions in the handbook.

What I have is:


# Device              Mountpoint FStype               Options         
Dump          Pass#

proc                     /proc procfs                  rw              
   0                   0


I can't see what's wrong.

Can anybody point to what I'm missing?

Thanks for any time and trouble.


Alexey Vyskubov

unread,
Aug 4, 2025, 3:08:13 AMAug 4
to ques...@freebsd.org, freebsd-...@freebsd.org
> proc                     /proc procfs                  rw                  0
>                   0
>
>
> I can't see what's wrong.

Does mount -t procfs proc /proc work?

--
Alexey
I cannot receive HTML mail at this account.
Hi, I am a signature virus. Add me to your signature to help me spread.

David

unread,
Aug 4, 2025, 6:01:57 AMAug 4
to ques...@freebsd.org

On 4/8/25 17:07, Alexey Vyskubov wrote:
>> proc                     /proc procfs                  rw                  0
>>                   0
>>
>>
>> I can't see what's wrong.
> Does mount -t procfs proc /proc work?


No, it doesn't appear to.

I'm short on time, and will have to come back to this when I have more
time, I think.

Thanking you for time and trouble.

>

Rupesh Pilania

unread,
Aug 4, 2025, 6:51:14 AMAug 4
to David, freebsd-...@freebsd.org

Hello David,

Your fstab configuration looks fine and should work as expected. One possibility is that you're using a custom kernel that doesn't have PROCFS support enabled.

Could you please verify whether PROCFS is included in your kernel configuration? Additionally, try mounting the filesystem manually( mount -t procfs proc /proc) and let me know the exact error message you receive.

If you can share the exact FreeBSD version and platform (e.g., architecture or hardware model), I’ll be happy to try and reproduce the issue on my end.

If the module is supposed to be loaded dynamically then please check kldstat output as well and see required modules are loaded.

Thanks & Regards,
Rupesh Pilania

--
Thanks & Regards
Rupesh Pilania

Arthur Chance

unread,
Aug 4, 2025, 1:06:24 PMAug 4
to Rupesh Pilania, David, freebsd-...@freebsd.org
On 04/08/2025 09:50, Rupesh Pilania wrote:
> Hello David,
>
> Your |fstab| configuration looks fine and should work as expected. One
> possibility is that you're using a custom kernel that doesn't have |
> PROCFS| support enabled.
>
> Could you please verify whether |PROCFS| is included in your kernel
> configuration?

If you're not familiar with doing this, a quick way is "kldstat -v |
grep procfs". Here's one of my machines:


root@arthur:1 ▶ kldstat -v | grep procfs
351 procfs

I've no idea what the number is for, yours may be different, it's the
presence of procfs that matters.

--
We should have listened when the modems screamed at us.

Paul Procacci

unread,
Aug 4, 2025, 1:49:59 PMAug 4
to Arthur Chance, Rupesh Pilania, David, freebsd-...@freebsd.org
Had you not piped the output you would see exactly what the number is for.

You can avoid the pipe entirely with '-m module' and it'll preserve the headers.
You can then read kldstat(8) for even further information on what each
field represents if you desire.

~Paul
--
__________________

:(){ :|:& };:

Karl Vogel

unread,
Aug 5, 2025, 12:12:06 AMAug 5
to freebsd-...@freebsd.org
>> On Sun 03 Aug 2025 at 23:42:53 (-0400), David wrote:

> Installing FreeBSD to an Optiplex 980. What I have is:
>
> #Device Mountpoint FStype Options Dump Pass#
> proc /proc procfs rw 0 0
^^^^

I think your device is wrong. My fstab:

#Device Mount FStype Options Dump Pass#
procfs /proc procfs rw 0 0
fdesc /dev/fd fdescfs rw 0 0
tmpfs /tmp tmpfs rw,mode=1777,noexec,nosuid 0 0

--
Karl Vogel I don't speak for anyone but myself

Women like silent men, they think they're listening. --George Carlin

Doug Hardie

unread,
Aug 5, 2025, 12:26:11 AMAug 5
to vog...@pobox.com, freebsd-...@freebsd.org
> On Aug 4, 2025, at 21:11, Karl Vogel <vog...@pobox.com> wrote:
>
>>> On Sun 03 Aug 2025 at 23:42:53 (-0400), David wrote:
>
>> Installing FreeBSD to an Optiplex 980. What I have is:
>>
>> #Device Mountpoint FStype Options Dump Pass#
>> proc /proc procfs rw 0 0
> ^^^^
>
> I think your device is wrong. My fstab:
>
> #Device Mount FStype Options Dump Pass#
> procfs /proc procfs rw 0 0
> fdesc /dev/fd fdescfs rw 0 0
> tmpfs /tmp tmpfs rw,mode=1777,noexec,nosuid 0 0

man procfs
PROCFS(5) FreeBSD File Formats Manual PROCFS(5)

NAME
procfs – process file system

SYNOPSIS
proc /proc procfs rw 0 0

DESCRIPTION
This functionality is deprecated. Users are advised to use
libprocstat(3) and kvm(3) instead.

The process file system, or procfs, implements a view of the system
process table inside the file system. It is normally mounted on /proc.


I can't find anything that uses procfs anymore.

-- Doug


Matthias Fechner

unread,
Aug 5, 2025, 12:42:50 AMAug 5
to ques...@freebsd.org
Am 05.08.2025 um 07:24 schrieb Doug Hardie:
> I can't find anything that uses procfs anymore.

I remember that openjdk is using procfs


Matthias


David

unread,
Aug 7, 2025, 1:19:27 AMAug 7
to freebsd-...@freebsd.org
On Mon, 2025-08-04 at 16:20 +0530, Rupesh Pilania wrote:
> Hello David,
> Your fstab configuration looks fine and should work as expected. One
> possibility is that you're using a custom kernel that doesn't have
> PROCFS support enabled.

No, the vanilla kernel as supplied with the 14.3 install.

> Could you please verify whether PROCFS is included in your kernel
> configuration?

Yes, I ran that.

> Additionally, try mounting the filesystem manually( mount -t procfs
> proc /proc) and let me know the exact error message you receive.
> If you can share the exact FreeBSD version and platform (e.g.,
> architecture or hardware model), I’ll be happy to try and reproduce
> the issue on my end.
> If the module is supposed to be loaded dynamically then please check
> kldstat output as well and see required modules are loaded.

I think it wound up being a gdm problem.
It didn't seem to want to load.
I've dropped gnome, now, and xfce is working - for the most part - I
just have to do some fine tuning.
I'm sending this with evolution on the new install.
Thanking you.

David

unread,
Aug 7, 2025, 1:23:04 AMAug 7
to Matthias Fechner, ques...@freebsd.org
It's noted in the handbook as a prerequisite for Gnome-desktop, also.
Cheers!

Reply all
Reply to author
Forward
0 new messages