Re: Mounting Linux Procfs at Boot

2006-08-31 Thread Boris Samorodov
On Thu, 31 Aug 2006 00:22:03 +0100 RW wrote:
 On Wednesday 30 August 2006 21:55, Gerard Seibert wrote:
  RW wrote:
   What's the canonical way of mounting the Linux procfs at boot-time?
  
   I've seen several recommendations to add the following to fstab:
  
   linproc/compat/linux/proc  linprocfs rw  0  0
  
   But in a standard installation, this mount-point is really under /usr,
   which isn't mounted until pass 2. If I change the pass number to 2, it
   fails with an unexpected inconsistencies error. I presume this is
   because mount is trying to fsck it, and failing to find fsck_linprocfs.
 
  This is what I have in my /etc/fstab file:
 
  linprocfs /compat/linux/proc  linprocfs rw   00
 
  Is this what you are referring to?

 I tried it and it didn't work. Irrespective of whether it should begin 
 linproc
 or linprocfs,  /compat is a link to /usr/compat, and /usr isn't mounted at 
 that point. Do you have a different arrangement?

Can't confirm that the problem exists:
$ uname -a
FreeBSD srv.sem.ipt.ru 6.1-STABLE FreeBSD 6.1-STABLE #2: Wed May 17 23:26:59 
MSD 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV  i386

But what do you mean /usr isn't mounted at that point?. Have you
read man fstab?

 BTW I'm running 6.1 (upgraded from an original 5.3 install)

Usually an output of uname -a is much more informative here. 6.1 may
mean release, release + security patches, stable... And a platform
also is of interest here.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-31 Thread Gerard Seibert
Boris Samorodov wrote:

  I tried it and it didn't work. Irrespective of whether it should begin 
  linproc
  or linprocfs,  /compat is a link to /usr/compat, and /usr isn't mounted at 
  that point. Do you have a different arrangement?

Would it be possible to submit the output of 'dmesg' here?

BTW, are you also attempting to load 'proc'?

// fstab //

[...]
proc  /proc procfsrw   00

// * //


-- 
Gerard Seibert
[EMAIL PROTECTED]

Think about it: The *average* American has one tit and one testicle.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-31 Thread RW
On Thursday 31 August 2006 10:09, Boris Samorodov wrote:
 On Thu, 31 Aug 2006 00:22:03 +0100 RW wrote:

 Can't confirm that the problem exists:
 $ uname -a
 FreeBSD srv.sem.ipt.ru 6.1-STABLE FreeBSD 6.1-STABLE #2: Wed May 17
 23:26:59 MSD 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV  i386

 But what do you mean /usr isn't mounted at that point?. Have you
 read man fstab?

Probably I mistinterpreted man fstab, but it's complaining that /compat/linux 
doesn't exist even though it does:

ls -ld /compat /usr/compat /usr/compat/linux
lrwxr-xr-x   1 root  wheel   10 Jun  7  2005 /compat - usr/compat
drwxr-xr-x   3 root  wheel  512 Jun  8  2005 /usr/compat
drwxr-xr-x  22 root  wheel  512 Aug 22 03:51 /usr/compat/linux


  BTW I'm running 6.1 (upgraded from an original 5.3 install)

 Usually an output of uname -a is much more informative here. 6.1 may
 mean release, release + security patches, stable... And a platform
 also is of interest here.

6.1-RELEASE-p4 i386 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-31 Thread Jerry McAllister
 
 On Thursday 31 August 2006 10:09, Boris Samorodov wrote:
  On Thu, 31 Aug 2006 00:22:03 +0100 RW wrote:
 
  Can't confirm that the problem exists:
  $ uname -a
  FreeBSD srv.sem.ipt.ru 6.1-STABLE FreeBSD 6.1-STABLE #2: Wed May 17
  23:26:59 MSD 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV  i386
 
  But what do you mean /usr isn't mounted at that point?. Have you
  read man fstab?
 
 Probably I mistinterpreted man fstab, but it's complaining that /compat/linux 
 doesn't exist even though it does:
 
 ls -ld /compat /usr/compat /usr/compat/linux
 lrwxr-xr-x   1 root  wheel   10 Jun  7  2005 /compat - usr/compat
 drwxr-xr-x   3 root  wheel  512 Jun  8  2005 /usr/compat
 drwxr-xr-x  22 root  wheel  512 Aug 22 03:51 /usr/compat/linux

I haven't followed this thread, so I may be way off here, but...

In the above, /compat is a link to usr/compat.  (note the - symbol)
I suspect that you cannot mount on a link, and that mount
doesn't follow links.

You probably would have to mount on /usr/compat directly
or make /compat a real directory and not a link or something.

jerry

 
 
   BTW I'm running 6.1 (upgraded from an original 5.3 install)
 
  Usually an output of uname -a is much more informative here. 6.1 may
  mean release, release + security patches, stable... And a platform
  also is of interest here.
 
 6.1-RELEASE-p4 i386 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-31 Thread Boris Samorodov
On Thu, 31 Aug 2006 15:44:39 +0100 RW wrote:
 On Thursday 31 August 2006 10:09, Boris Samorodov wrote:
  On Thu, 31 Aug 2006 00:22:03 +0100 RW wrote:

  Can't confirm that the problem exists:
  $ uname -a
  FreeBSD srv.sem.ipt.ru 6.1-STABLE FreeBSD 6.1-STABLE #2: Wed May 17
  23:26:59 MSD 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV  i386
 
  But what do you mean /usr isn't mounted at that point?. Have you
  read man fstab?

 Probably I mistinterpreted man fstab,

If you show us what did you misinterpret, we may be able to help you.

 but it's complaining that /compat/linux 

Who? Can you provide us with some more info? Any logs? You mentioned
that it's complaining... for the first time. And show us your
/etc/fstab, please.

 doesn't exist even though it does:

 ls -ld /compat /usr/compat /usr/compat/linux
 lrwxr-xr-x   1 root  wheel   10 Jun  7  2005 /compat - usr/compat
 drwxr-xr-x   3 root  wheel  512 Jun  8  2005 /usr/compat
 drwxr-xr-x  22 root  wheel  512 Aug 22 03:51 /usr/compat/linux

   BTW I'm running 6.1 (upgraded from an original 5.3 install)
 
  Usually an output of uname -a is much more informative here. 6.1 may
  mean release, release + security patches, stable... And a platform
  also is of interest here.

 6.1-RELEASE-p4 i386 

OK.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-31 Thread RW
On Thursday 31 August 2006 16:26, Boris Samorodov wrote:
 On Thu, 31 Aug 2006 15:44:39 +0100 RW wrote:
  On Thursday 31 August 2006 10:09, Boris Samorodov wrote:
   On Thu, 31 Aug 2006 00:22:03 +0100 RW wrote:

  but it's complaining that /compat/linux

 Who? Can you provide us with some more info? Any logs?

I don't know how to get the logs written to disk,  the startup process aborts 
before /var is mounted.

I see the output from fsck -p -F , it then says:

   mount: /usr/compat: no such file or directory
   mounting /etc/fstab filesytems failed, startup aborted

I'm then given the prompt to pick a shell.

Avoiding the symlink by using /usr/compat/linux/proc still causes a failure. 
However, if I use a mountpoint on the root partition it mounts correctly. 

 And show us your /etc/fstab, please.

fstab is below, 

-
$ cat /etc/fstab.f
# DeviceMountpoint  FStype  Options DumpPass#
/dev/ad4s1b.bde noneswapsw  0   0
/dev/ad6s1b.bde noneswapsw  0   0

proc/proc   procfs  rw  0   0

linprocfs /compat/linux/proc  linprocfs  rw0   0

/dev/ad4s1a /   ufs rw  1   1
/dev/ad4s1g /home   ufs rw  2   2
/dev/ad4s1e /tmpufs rw  2   2
/dev/ad4s1f /usrufs rw  2   2
/dev/ad4s1d /varufs rw  2   2
/dev/acd0   /dvdrw  cd9660  ro,noauto   0   0
/dev/acd1   /dvdcd9660  ro,noauto   0   0

/dev/ad6s1d /data  ufs rw  2   2

/dev/ad0s2a /oldufs rw  2   2
/dev/ad0s2g /old/home   ufs rw  2   2
/dev/ad0s2d /old/varufs rw  2   2
/dev/ad0s2f /old/usrufs rw  2   2


/dev/ad0s1  /dos/c  msdos   rw  0   0
/dev/da0s1  /mnt/cammsdos   rw,noauto   0   0
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-31 Thread Boris Samorodov
On Thu, 31 Aug 2006 21:31:33 +0100 RW wrote:
 On Thursday 31 August 2006 16:26, Boris Samorodov wrote:
  On Thu, 31 Aug 2006 15:44:39 +0100 RW wrote:
   On Thursday 31 August 2006 10:09, Boris Samorodov wrote:
On Thu, 31 Aug 2006 00:22:03 +0100 RW wrote:

   but it's complaining that /compat/linux
 
  Who? Can you provide us with some more info? Any logs?

 I don't know how to get the logs written to disk,  the startup process aborts 
 before /var is mounted.

 I see the output from fsck -p -F , it then says:

mount: /usr/compat: no such file or directory
mounting /etc/fstab filesytems failed, startup aborted

 I'm then given the prompt to pick a shell.

Oh, you should say it at the very first letter!

 Avoiding the symlink by using /usr/compat/linux/proc still causes a failure. 
 However, if I use a mountpoint on the root partition it mounts correctly. 

  And show us your /etc/fstab, please.

 fstab is below, 

 -
 $ cat /etc/fstab.f
 # DeviceMountpoint  FStype  Options DumpPass#
 /dev/ad4s1b.bde noneswapsw  0   0
 /dev/ad6s1b.bde noneswapsw  0   0

 proc/proc   procfs  rw  0   0

 linprocfs /compat/linux/proc  linprocfs  rw0   0

Move this line down and place it after mounting of /usr.

 /dev/ad4s1a /   ufs rw  1   1
 /dev/ad4s1g /home   ufs rw  2   2
 /dev/ad4s1e /tmpufs rw  2   2
 /dev/ad4s1f /usrufs rw  2   2
 /dev/ad4s1d /varufs rw  2   2
 /dev/acd0   /dvdrw  cd9660  ro,noauto   0   0
 /dev/acd1   /dvdcd9660  ro,noauto   0   0

 /dev/ad6s1d /data  ufs rw  2   2

 /dev/ad0s2a /oldufs rw  2   2
 /dev/ad0s2g /old/home   ufs rw  2   2
 /dev/ad0s2d /old/varufs rw  2   2
 /dev/ad0s2f /old/usrufs rw  2   2


 /dev/ad0s1  /dos/c  msdos   rw  0   0
 /dev/da0s1  /mnt/cammsdos   rw,noauto   0   0


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-31 Thread RW
On Thursday 31 August 2006 22:12, Boris Samorodov wrote:

 Move this line down and place it after mounting of /usr.

Thanks.

That was actually one of the first things I tried, I guess I must have 
screwed-up something else at the time.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Mounting Linux Procfs at Boot

2006-08-30 Thread RW
What's the canonical way of mounting the Linux procfs at boot-time?

I've seen several recommendations to add the following to fstab:

linproc/compat/linux/proc  linprocfs rw  0  0

But in a standard installation, this mount-point is really under /usr, which 
isn't mounted until pass 2. If I change the pass number to 2, it fails with 
an unexpected inconsistencies error. I presume this is because mount is 
trying to fsck it, and failing to find fsck_linprocfs.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-30 Thread Gerard Seibert
RW wrote:

 What's the canonical way of mounting the Linux procfs at boot-time?
 
 I've seen several recommendations to add the following to fstab:
 
 linproc/compat/linux/proc  linprocfs rw  0  0
 
 But in a standard installation, this mount-point is really under /usr, which 
 isn't mounted until pass 2. If I change the pass number to 2, it fails with 
 an unexpected inconsistencies error. I presume this is because mount is 
 trying to fsck it, and failing to find fsck_linprocfs.


This is what I have in my /etc/fstab file:

linprocfs /compat/linux/proc  linprocfs rw   00

Is this what you are referring to?

-- 
Gerard Seibert
[EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting Linux Procfs at Boot

2006-08-30 Thread RW
On Wednesday 30 August 2006 21:55, Gerard Seibert wrote:
 RW wrote:
  What's the canonical way of mounting the Linux procfs at boot-time?
 
  I've seen several recommendations to add the following to fstab:
 
  linproc/compat/linux/proc  linprocfs rw  0  0
 
  But in a standard installation, this mount-point is really under /usr,
  which isn't mounted until pass 2. If I change the pass number to 2, it
  fails with an unexpected inconsistencies error. I presume this is
  because mount is trying to fsck it, and failing to find fsck_linprocfs.

 This is what I have in my /etc/fstab file:

 linprocfs /compat/linux/proc  linprocfs rw   00

 Is this what you are referring to?

I tried it and it didn't work. Irrespective of whether it should begin linproc  
  
or linprocfs,  /compat is a link to /usr/compat, and /usr isn't mounted at 
that point. Do you have a different arrangement?

BTW I'm running 6.1 (upgraded from an original 5.3 install)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]