Re: fstab problem

[Bernt Hansson]

2012-01-14 11:00, per...@pluto.rain.com skrev:

Bernt Hansson  wrote:


This is an old machine (1997), not sure it will boot from usb.
I'll check.


If it can boot from floppy, Plop will boot it from USB.
http://www.plop.at/en/bootmanagers.html


Thank you. I'll have a look at it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab problem

[perryh]

Bernt Hansson  wrote:

> This is an old machine (1997), not sure it will boot from usb.
> I'll check.

If it can boot from floppy, Plop will boot it from USB.
http://www.plop.at/en/bootmanagers.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab problem

[Matthias Apitz]

El día Friday, January 13, 2012 a las 11:01:40AM +0100, Bernt Hansson escribió:

> Hello list!
>
> I've moved /etc/fstab to /etc/fstab.org
>
> When booting I get prompted with
>
> >mountroot
>
> Ok. I type ufs:ad0s1a
>
> The crap boot up. But I can't get the filesystem to become R/W
>
> Tried /sbin/mount -o rw /ad0s1a /
> /sbin/mount -o rw,force /ad0s1a /
> /sbin/mount -o force /ad0s1a /
>
> But /sbin/mount only shows ro.
>
> Don't really know what to do, except reinstall and that's a noop.

As a last resort, you could boot an USB livefs, mount the disk to /mnt
and do the change back in the root fs;

matthias

-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e  - w http://www.unixarea.de/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab problem

[Matthew Seaman]

On 13/01/2012 10:01, Bernt Hansson wrote:
> Hello list!
> 
> I've moved /etc/fstab to /etc/fstab.org
> 
> When booting I get prompted with
> 
>>mountroot
> 
> Ok. I type ufs:ad0s1a
> 
> The crap boot up. But I can't get the filesystem to become R/W
> 
> Tried /sbin/mount -o rw /ad0s1a /
> /sbin/mount -o rw,force /ad0s1a /
> /sbin/mount -o force /ad0s1a /
> 
> But /sbin/mount only shows ro.
> 
> Don't really know what to do, except reinstall and that's a noop.

fsck /dev/ad0s1a
/sbin/mount -u -o rw /dev/ad0s1a /

You should then be able to recover /etc/fstab, fix any problems within
it and then on exit, the system should continue with a normal multi-user
bootup.

Cheers,

Matthew


-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: fstab problem

[Frank Brendel]

Use  /dev/ad0s1a instead of /ad0s1a.

Frank

Am 13.01.2012 11:01, schrieb Bernt Hansson:

Hello list!

I've moved /etc/fstab to /etc/fstab.org

When booting I get prompted with

>mountroot

Ok. I type ufs:ad0s1a

The crap boot up. But I can't get the filesystem to become R/W

Tried /sbin/mount -o rw /ad0s1a /
/sbin/mount -o rw,force /ad0s1a /
/sbin/mount -o force /ad0s1a /

But /sbin/mount only shows ro.

Don't really know what to do, except reinstall and that's a noop.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"freebsd-questions-unsubscr...@freebsd.org"


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab NFS mount option recommendations

[Joe Auty]

Forgot to add,

I also need to do some NFS mounts from my VM host which is hosted on
CentOS. I know that this isn't a Linux based list, but if you could
kindly keep the information about wsize and rsize numbers general enough
so that I can apply this knowledge to my Linux box, that would be great :)

A lot of online resources I've come across suggest using various
numbers, but I don't really understand how these number are derived or
if they are even necessary at all...


Joe Auty wrote:
> Hello,
>
> I'm presenting NFS shares to some FreeBSD VM guests with the following
> mount options (from my /etc/fstab):
>
> nfsserverip:mymount /mountdir  nfs 
> rw,tcp,intr,noatime,nfsv3,-w=32768,-r=32768 0 0
>
>
> This seems to work well, except I have to manually load MySQL, Apache,
> and Postfix at boot time, as my /usr/local directory is hosted on my
> NFS share on this test server (these start up normally when /usr/local
> resides on a local hard drive). Is it generally a bad idea to host a
> share like this on NFS? I'm thinking that it probably is and am happy
> to serve this locally if this would be better. However, if this is not
> a red flag and there is a way to get these services to start up on
> their own at boot, could you please let me know?
>
> How about the wsize and rsize numbers? I was unable to find any
> resources for determining what these numbers best be set as for
> FreeBSD as a VM guest. Any pointers?
>
>
>
>
> Thanks in advance for your help!
>
>
> -- 
> Joe Auty, NetMusician
> NetMusician helps musicians, bands and artists create beautiful,
> professional, custom designed, career-essential websites that are easy
> to maintain and to integrate with popular social networks.
> www.netmusician.org 
> j...@netmusician.org 
>


-- 
Joe Auty, NetMusician
NetMusician helps musicians, bands and artists create beautiful,
professional, custom designed, career-essential websites that are easy
to maintain and to integrate with popular social networks.
www.netmusician.org 
j...@netmusician.org 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab syntax

[Polytropon]

On Sun, 31 Jan 2010 00:35:02 +0200, Elias Chrysocheris 
 wrote:
> Unfortunatelly, spaces are not allowed in fstab syntax.

Fortunately. :-)



Allow me a little sidenote about correct terminology:

> I also have tried it 
> before and figured out that there is no way to insert spaces in a folder or 
> device name.

Those are called directories, not "folders".



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab syntax

[Elias Chrysocheris]

On Saturday 30 of January 2010 21:05:43 Jeff Laine wrote:
> Hello,
> 
> My question is regarding /etc/fstab synax.
> How can I use spaces and quote symbols in my device name?
> I tried to use double quotes and backslash, but no luck so far.
> I.e. I'd like to put the following line:
> 
> /dev/msdosfs/MY FLASH /mnt/flash msdosfs rw,noauto 0 0
> 
> Any ideas?
> 
Unfortunatelly, spaces are not allowed in fstab syntax. I also have tried it 
before and figured out that there is no way to insert spaces in a folder or 
device name.

Elias
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab syntax

[Jeff Laine]

On Sat,30-01-2010 [19:33:37], krad wrote:
> On 30 January 2010 19:05, Jeff Laine  wrote:
> 
> > Hello,
> >
> > My question is regarding /etc/fstab synax.
> > How can I use spaces and quote symbols in my device name?
> > I tried to use double quotes and backslash, but no luck so far.
> > I.e. I'd like to put the following line:
> >
> > /dev/msdosfs/MY FLASH /mnt/flash msdosfs rw,noauto 0 0
> >
> > Any ideas?
> >
> >
> > --
> > Best regards,
> > Jeff
> >
> > | "Nobody wants to say how this works.  |
> > |  Maybe nobody knows ..."  |
> > |   Xorg.conf(5)|
> >
> 
> /dev/msdosfs/MY\ FLASH /mnt/flash msdosfs rw,noauto 0 0
> 
> or
> 
> "/dev/msdosfs/MY FLASH" /mnt/flash msdosfs rw,noauto 0 0
> 
> should work, but i guess you tried these?
> 
> The alternative way would be to use the UUID of the drive, as that wont have
> spaces in, and is more versatile than /dev/das1a type syntax


Yep, neither is working. 

After all I used glabel to generate a new label and avoid reformatiing my 
volume.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab syntax

[Jerry]

On Sat, 30 Jan 2010 22:05:43 +0300
Jeff Laine  articulated:

> Hello,
> 
> My question is regarding /etc/fstab synax. 
> How can I use spaces and quote symbols in my device name? 
> I tried to use double quotes and backslash, but no luck so far.
> I.e. I'd like to put the following line:
> 
> /dev/msdosfs/MY FLASH /mnt/flash msdosfs rw,noauto 0 0

As far as I know, that cannot be done. I saw something about that
here awhile ago. Perhaps, a patch has been submitted that will modify
its behavior by now.

-- 
Jerry
ges...@yahoo.com

|===
|===
|===
|===
|

Don't try to outweird me, three-eyes.  I get stranger things than you
free with my breakfast cereal.

Zaphod Beeblebrox

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab syntax

[krad]

On 30 January 2010 19:05, Jeff Laine  wrote:

> Hello,
>
> My question is regarding /etc/fstab synax.
> How can I use spaces and quote symbols in my device name?
> I tried to use double quotes and backslash, but no luck so far.
> I.e. I'd like to put the following line:
>
> /dev/msdosfs/MY FLASH /mnt/flash msdosfs rw,noauto 0 0
>
> Any ideas?
>
>
> --
> Best regards,
> Jeff
>
> | "Nobody wants to say how this works.  |
> |  Maybe nobody knows ..."  |
> |   Xorg.conf(5)|
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
>

/dev/msdosfs/MY\ FLASH /mnt/flash msdosfs rw,noauto 0 0

or

"/dev/msdosfs/MY FLASH" /mnt/flash msdosfs rw,noauto 0 0

should work, but i guess you tried these?

The alternative way would be to use the UUID of the drive, as that wont have
spaces in, and is more versatile than /dev/das1a type syntax
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: fstab & (local) mount -- FreeBSD Port: sysutils/fusefs-curlftpfs

[Alex Zbyslaw]

martinko wrote:


Hello,

This is from CurlFtpFS FAQ:

# *How can I make CurlFtpFS mount automatically at startup?*
You can add it to /etc/fstab. Example:

 curlftpfs#ftp.host.com /mnt/host fuse rw,uid=500,user,noauto 0 0
 


However, it does not work on FreeBSD -- mount fails with this complain:
mount: exec mount_fusefs not found in /sbin:/usr/sbin: No such file or
directory

Of course, we have it here: /usr/local/sbin/mount_fusefs
 

Make a symlink from either /sbin/mount_fusefs  or  
/usr/sbin/mount_fusefs to /usr/local/sbin/mount_fusefs


--Alex


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

Re: fstab & (local) mount -- FreeBSD Port: sysutils/fusefs-curlftpfs

[martinko]

Jerry McAllister wrote:
> On Fri, Oct 20, 2006 at 09:10:54PM +0200, martinko wrote:
>
>   
>> Hello,
>>
>> This is from CurlFtpFS FAQ:
>>
>> # *How can I make CurlFtpFS mount automatically at startup?*
>> You can add it to /etc/fstab. Example:
>>
>>   curlftpfs#ftp.host.com /mnt/host fuse rw,uid=500,user,noauto 0 0
>>   
>>
>> However, it does not work on FreeBSD -- mount fails with this complain:
>> mount: exec mount_fusefs not found in /sbin:/usr/sbin: No such file or
>> directory
>>
>> Of course, we have it here: /usr/local/sbin/mount_fusefs
>>
>> Is there any workaround or could this be fixed/amended somehow pls ??
>> 
>
> Looks like you need to add /usr/local/sbin to your path.
>
> jerry
>   

Hi,

I do not think that is the case:

$ env | grep PATH
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/home/mato/bin

It seems that mount(8) is hardcoded or something to look only in those
two directories, ignoring any /usr/local/sbin stuff.

So the original question remains -- what can be done about it ??

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

Re: fstab & (local) mount -- FreeBSD Port: sysutils/fusefs-curlftpfs

[Jerry McAllister]

On Fri, Oct 20, 2006 at 09:10:54PM +0200, martinko wrote:

> Hello,
> 
> This is from CurlFtpFS FAQ:
> 
> # *How can I make CurlFtpFS mount automatically at startup?*
> You can add it to /etc/fstab. Example:
> 
>   curlftpfs#ftp.host.com /mnt/host fuse rw,uid=500,user,noauto 0 0
>   
> 
> However, it does not work on FreeBSD -- mount fails with this complain:
> mount: exec mount_fusefs not found in /sbin:/usr/sbin: No such file or
> directory
> 
> Of course, we have it here: /usr/local/sbin/mount_fusefs
> 
> Is there any workaround or could this be fixed/amended somehow pls ??

Looks like you need to add /usr/local/sbin to your path.

jerry

> 
> Cheers,
> 
> Martin
> ___
> 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: fstab - mount_nfs - -L parameter

[Andrew P.]

On 1/10/06, Mathieu CHATEAU <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I need to mount an nfs volume with the "-L" params.
>
> It works great by hand :
> mount_nfs -L server:/share
>
> but fstab refuses the -L params...

really? What does it say? Do you have "ro" or "rw" present in the
options? Here's my line that works:

lan-217:/mnt/200a/mnt/200anfs-L,ro00
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab and bad hard drives

[Lowell Gilbert]

Brian Clark <[EMAIL PROTECTED]> writes:

> I searched and looked through the man pages and was unable to find
> any information on this. My question is, is there a way to make
> freebsd boot if it has problems mounting a hard drive listed in
> fstab? With NFS drives I use 'bg' so the system will continue to
> boot if the NFS drive is down or unavailable. I would prefer if a
> hard drive on the system was to stop working that the system would
> still boot and not hang in single user mode. This is for remote
> servers that are about 2 hours away and have had several instances
> where an extra drive on the system failed which caused the system to
> not reboot correctly... so then i have to drive down manually edit
> the fstab, (remove the entry) reboot and all is fine. In an ideal
> world, if the system reboots and an extra drive fails to mount then
> the system skips it and continues to load without the bad drive. Any
> ideas? I was considering noauto and have an rc.d script mount them
> but not for sure if it would still hang the system.

That last is the approach I would have suggested...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab and bad hard drives

[Jerry McAllister]

> 
> Oops my bad on the long lines, figured my client would break them.
> 
> Thanks for your help but booting into single user mode is not an
> option, this is the problem. Since the servers are at a colocation
> 2 hours away, I want to find a solution that will allow the server
> to continue to boot up if a hard drive is bad. This is all assuming 
> that the drive is an 'extra' drive. A hard drive that does not 
> contain any system files should not stop the system from booting. I 
> had 2 drives go out in one week, neither had any data, and both took
> down the server causeing it not to boot back up. So problem went from 
> no big deal to very big deal once the server could not reboot. Any other 
> ideas?

Well, once you are dead you will have to make the drive to fix it.

For future things you could do two things anyway.   One is to make
those "extra" drives not automatically mount on boot - eg edit the 
fourth field in /etc/fstab  to 'noauto'  or probably actually  'rw,noauto'
Then, after the machine comes up each time you would have to manually
mount those file systems.

Another thing is to set up a remote console using the serial port
and some hardware that would also hang on the net and let you log
in and talk to that serial port.  Then you could do the single user
stuff from where you are.   There are various offerings of hardware
from companies that will do that.

jerry

> 
> Thanks,
> Brian
> 
> 
> On Wed, 17 Aug 2005 11:30:09 -0400 (EDT)
> Jerry McAllister <[EMAIL PROTECTED]> wrote:
> 
> > > 
> > > 
> > First, PLEASE PLEASE break your lines at around 70 characters?   These all
> > run together texts are hard to deal with.   Most Email clients can be
> > set for this and if yous can not, then just hit RETURN or ENTER near the
> > end of the page.   Your whole message is one long hardly manageable line.
> > 
> > > I searched and looked through the man pages and was unable to find any 
> > > information on this. My question is, is there a way to make freebsd boot 
> > > if it has problems mounting a hard drive listed in fstab? 
> > 
> > Boot in to single user and remount root and then edit fstab to 
> > comment out the entry for the filesystem that has a problem.
> > Then you can do whatever you want.
> > 
> > Booting to single user is covered in the handbook and many other 
> > pieces of documentation.   
> > Basically:
> >   hit the space bar when it is doing the countdown early in boot
> >   then do:
> > boot -sand wait for it to finish to a prompt
> > fcsk -pclean up possible problems
> > mount -u / remounts root with write ability
> > swapon -a  
> > 
> > vi /etc/fstab do the editing to exclude bad file system from 
> > mounting.
> > 
> > From here you can do more in single user or reboot.
> > 
> > > Thanks in advance,
> > > 
> > > Brian
> 

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

Re: fstab option to 'skip' a file system?

[Glenn Dawson]

At 08:16 PM 6/11/2005, Marc G. Fournier wrote:

Is there an option that I can add to fstab (or some way of doing it?) 
that, when a server reboots, it will 'ignore' that file system, but I can 
still do a 'mount /fs' after the fact?


in the options column in fstab specify noauto

-Glenn


I have remote servers that I'd like to manually fsck one of the file 
systems after it comes up, but I don't have a serial console enabled on 
them (yet!) ... so, i'd like it to ignore that one file system on reboot, 
but still have it listed in /etc/fstab ...


Setting 'passno' to 0, I believe, will cause it to fail to boot due to an 
unclean file system, so that doesn't appear to be an option ...


Is that possible?

Thanks ...

Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED]   Yahoo!: yscrappy  ICQ: 7615664
___
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: fstab option to 'skip' a file system?

[Marc G. Fournier]

On Sat, 11 Jun 2005, Bob Bomar wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Marc G. Fournier wrote:
|
| Is there an option that I can add to fstab (or some way of doing it?)
| that, when a server reboots, it will 'ignore' that file system, but I
| can still do a 'mount /fs' after the fact?
|
| I have remote servers that I'd like to manually fsck one of the file
| systems after it comes up, but I don't have a serial console enabled on
| them (yet!) ... so, i'd like it to ignore that one file system on
| reboot, but still have it listed in /etc/fstab ...
|
| Setting 'passno' to 0, I believe, will cause it to fail to boot due to
| an unclean file system, so that doesn't appear to be an option ...
|
| Is that possible?
|

~From the fstab(5) man page:

...
If the option ``noauto'' is specified, the file system will not be auto-
~ matically mounted at system startup.
...

Just add noauto to the Options for that fs.


Perfect, thanks ... I've used that for cdrom, not sure why I didn't think 
of it for a regular file system :(



Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED]   Yahoo!: yscrappy  ICQ: 7615664
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab option to 'skip' a file system?

[Bob Bomar]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Marc G. Fournier wrote:
|
| Is there an option that I can add to fstab (or some way of doing it?)
| that, when a server reboots, it will 'ignore' that file system, but I
| can still do a 'mount /fs' after the fact?
|
| I have remote servers that I'd like to manually fsck one of the file
| systems after it comes up, but I don't have a serial console enabled on
| them (yet!) ... so, i'd like it to ignore that one file system on
| reboot, but still have it listed in /etc/fstab ...
|
| Setting 'passno' to 0, I believe, will cause it to fail to boot due to
| an unclean file system, so that doesn't appear to be an option ...
|
| Is that possible?
|

~From the fstab(5) man page:

...
If the option ``noauto'' is specified, the file system will not be auto-
~ matically mounted at system startup.
...

Just add noauto to the Options for that fs.


- --
Bob Bomar
[EMAIL PROTECTED]
http://www.bomar.us/~bob
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCq6379Jm/aTrtdKoRAtj3AJ9UidrCbllUnJ7yXV22P/NWMW5DaQCfdg2+
rwkKV3b+NnKKUxCn7V9SZXw=
=yVIT
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab - why different file systems nummers?

[Andrew J Caines]

Marcel,

> and i am stick with another prolbem. so far i've read that the md
> driver can be used to mound a file in an filesystem. before i could
> use mdconfig. buti don't have mdconfig on my branch (4.10)

On 4.x you can use md, but it's easier to use mfs. In the vfstab, you
simply put the swap device in place of "md", eg.

/dev/ad0s1b /tmpmfs -s=655360   0

See mount_mfs(8), aka. newfs(8).


-Andrew-
-- 
 ___
| -Andrew J. Caines-   Unix Systems Engineer   [EMAIL PROTECTED]  |
| "They that can give up essential liberty to obtain a little temporary |
|  safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 |
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab - why different file systems nummers?

[Marcel.lautenbach]

Guten Tag Dan Nelson,

am Freitag, 27. August 2004 um 21:37 schrieben Sie:

DN> In the last episode (Aug 27), Marcel.lautenbach said:
>> well, i new to freebsd but i didn't find help in the newbelist. and
>> since i got this daily message from the list i think this is the
>> right place to go.
>> 
>> i am at the point to change my /etc/fstab file. well, there i can set
>> two numbers 1 for root file system; 2 for another ufs file system and
>> 0 for everythin else. so, in my example here: why ist a ms-dos file
>> system set to 2 and not to 0? it isn't a ufs file
>> system...*wondering*
>> 
>> also, why to distinguish between 1,2 and 0. there is a file system
>> declaration in the third column. so, i don't get it with the
>> differences and reasons for these three numbers. but i would like to
>> understand :-)

DN> Run "man fstab", and read the descriptions of the fifth and sixth
DN> columns.

>> so, can someone help?
>> 
>> and, what does the term "userland" mean for freebsd?

DN> Any user programs, headers, libraries, etc (anything that's not the
DN> kernel).


Hi Dan,

thanks for the help. i will check the man then :-)

and i am stick with another prolbem. so far i've read that the md
driver can be used to mound a file in an filesystem. before i could
use mdconfig. buti don't have mdconfig on my branch (4.10), not even
a man entry.

-- 

mailto:[EMAIL PROTECTED]


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

Re: fstab - why different file systems nummers?

[Dan Nelson]

In the last episode (Aug 27), Marcel.lautenbach said:
> well, i new to freebsd but i didn't find help in the newbelist. and
> since i got this daily message from the list i think this is the
> right place to go.
> 
> i am at the point to change my /etc/fstab file. well, there i can set
> two numbers 1 for root file system; 2 for another ufs file system and
> 0 for everythin else. so, in my example here: why ist a ms-dos file
> system set to 2 and not to 0? it isn't a ufs file
> system...*wondering*
> 
> also, why to distinguish between 1,2 and 0. there is a file system
> declaration in the third column. so, i don't get it with the
> differences and reasons for these three numbers. but i would like to
> understand :-)

Run "man fstab", and read the descriptions of the fifth and sixth
columns.

> so, can someone help?
> 
> and, what does the term "userland" mean for freebsd?

Any user programs, headers, libraries, etc (anything that's not the
kernel).

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

Re: fstab

[Jerry McAllister]

> 
> 
> > It would be whatever you used in the disklabel run (or the one done
> > for you if you use sysinstall).   'd' is unlikely and so is 'c'
> 
> d is highly likely and is what you get if you use sysinstall in 5.x.  I 
> have about 25 drives with a d partition.
> d certainly is unlikely in 4.x
> c will appear in the list but shouldnt be used to mount

Well, another 5.x thing I guess.

If I could get all the 4.9 stuff out of the way, and free up a machine, I
might get started looking at 5.xxx.

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

Re: fstab

[Anubis]

It would be whatever you used in the disklabel run (or the one done
for you if you use sysinstall).   'd' is unlikely and so is 'c'
d is highly likely and is what you get if you use sysinstall in 5.x.  I 
have about 25 drives with a d partition.
d certainly is unlikely in 4.x
c will appear in the list but shouldnt be used to mount

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

Re: fstab

[Jerry McAllister]

> 
> > asuming that you have done the whole fdisk/disklabel/newfs you can list
> > the contents of /dev thus, ls /dev to find out.  It will be ad1s1d oassume
> > something like that
> 
> I do have several ad1* devices in /dev but I can not mount them. So I
> asume they are just there to be there?
> 
> Why would it be ad1s1d? If the whole drive is being used wouldn't it be
> ad1s1a?

It would be whatever you used in the disklabel run (or the one done
for you if you use sysinstall).   'd' is unlikely and so is 'c'

jerry

> 
> 
> Thank you,
> Joshua Lewis
> 
> 
> 
> Anubis
> > Joshua Lewis wrote:
> >>>/dev/ad1s1 what?  a, d, e, f,g ??
> >>
> >>
> >> Do I specify? I am using the whole drive. should I change it to
> >> /dev/ad1s1a?
> >>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab

[Joshua Lewis]

> asuming that you have done the whole fdisk/disklabel/newfs you can list
> the contents of /dev thus, ls /dev to find out.  It will be ad1s1d oassume
> something like that

I do have several ad1* devices in /dev but I can not mount them. So I
asume they are just there to be there?

Why would it be ad1s1d? If the whole drive is being used wouldn't it be
ad1s1a?


Thank you,
Joshua Lewis



Anubis
> Joshua Lewis wrote:
>>>/dev/ad1s1 what?  a, d, e, f,g ??
>>
>>
>> Do I specify? I am using the whole drive. should I change it to
>> /dev/ad1s1a?
>>
>>
>> Thank you,
>> Joshua Lewis
>>
>>
>>
>> Anubis
>>
>>>Joshua Lewis wrote:
>>>
The last time I edited this file my system ceased to boot. I have made
what
looks to me like a valid entry. This is the same thing I entered in
 last
time. I am not going to save this but does it look valid to anyone out
there?


# DeviceMountpoint  FStype  Options Dump
Pass#
/dev/ad0s1b noneswapsw  0
0
/dev/ad0s1a /   ufs rw  1
1
/dev/ad0s1f /tmpufs rw  2
2
/dev/ad0s1g /usrufs rw  2
2
/dev/ad0s1e /varufs rw  2
2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0
0
/dev/acd1c  /cdrom1 cd9660  ro,noauto   0
0

This is the line I added
/dev/ad1s1  /disk2  ufs rw  2
 2


proc/proc   procfs  rw  0
0

>>>
>>>/dev/ad1s1 what?  a, d, e, f,g ??
>>>
>>>
>>>
>>
>>
>>
>
> asuming that you have done the whole fdisk/disklabel/newfs you can list
> the contents of /dev thus, ls /dev to find out.  It will be ad1s1d or
> something like that
>
>
>

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

Re: fstab

[Jerry McAllister]

> 
> The last time I edited this file my system ceased to boot. I have made what 
> looks to me like a valid entry. This is the same thing I entered in last 
> time. I am not going to save this but does it look valid to anyone out there?
> 
> 
> # DeviceMountpoint  FStype  Options DumpPass#
> /dev/ad0s1b noneswapsw  0   0
> /dev/ad0s1a /   ufs rw  1   1
> /dev/ad0s1f /tmpufs rw  2   2
> /dev/ad0s1g /usrufs rw  2   2
> /dev/ad0s1e /varufs rw  2   2
> /dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
> /dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0
> 
> This is the line I added
> /dev/ad1s1  /disk2  ufs rw  2  2

Well, did you really create a file system on ad1s1 - the whole
slice.   Probably, best if you also go in to disklabel(8) and
make at least one partition on that slice.
 
do   "disklabel -e -r ad1s1"

Edit the file.   I think it should come up with a c: line that has a type
called 'unused' (it has been quite a while since I added a virgin disk so 
my memory may be flakey here).   It would look something like:

 c: 780598350unused0 0 # (Cyl.0 - 4858)

Copy that c: line and hange it to something like:

 a: 7805983504.2BSD0 0 # (Cyl.0 - 4858)

Leave all the numbers the same - just change the 'c:' to 'a:' and 
the 'unused' to '4.2BSD'

Then use newfs(8) to create a filesystem on it:

do   "newfs /dev/ad1s1a"

If the number of inodes it automatically creates or some other
such thing doesn't suit you, then you will need to insert some
parameters on the newfs command, but usually just the bare newfs
like that will work just fine.

and then put the following in your fstab:

/dev/ad1s1a  /disk2  ufs rw  2  2

I think you can talk to it as the whole slice without a partition
but it is not the usual way and not worth bothering with so, just
do as indicated.
 
If you are using /stand/sysinstall to run the fdisk, disklabel and newfs
commands for you, then make the related decisions - eg create one large
slice for FreeBSD on the ad1 disk, don't make it bootable or have any MBR 
(that's fdisk), then partition the slice with just one partition (a), use 
the 'c' for create partition and then just put all the blocks in to it and 
make it a file system (FS) with the mount point you want to use (that covers
the disklabel, newfs and editing fstab).  Back out and select Commit and 
it should take care of everything else for you.   Some prefer sysinstall
but I generally prefer doing the fdisk, disklabel, newfs and fstab myself
for disks beyond the initial install slice.   It's that control thing.

jerry

> 
> proc/proc   procfs  rw  0   0
> 
> -- 
> Thank you,
> Joshua
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 

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

Re: fstab

[Anubis]

Joshua Lewis wrote:
/dev/ad1s1 what?  a, d, e, f,g ??

Do I specify? I am using the whole drive. should I change it to /dev/ad1s1a?
Thank you,
Joshua Lewis

Anubis
Joshua Lewis wrote:
The last time I edited this file my system ceased to boot. I have made
what
looks to me like a valid entry. This is the same thing I entered in last
time. I am not going to save this but does it look valid to anyone out
there?
# DeviceMountpoint  FStype  Options Dump
Pass#
/dev/ad0s1b noneswapsw  0
0
/dev/ad0s1a /   ufs rw  1
1
/dev/ad0s1f /tmpufs rw  2
2
/dev/ad0s1g /usrufs rw  2
2
/dev/ad0s1e /varufs rw  2
2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0
0
/dev/acd1c  /cdrom1 cd9660  ro,noauto   0
0
This is the line I added
/dev/ad1s1  /disk2  ufs rw  2  2
proc/proc   procfs  rw  0
0
/dev/ad1s1 what?  a, d, e, f,g ??



asuming that you have done the whole fdisk/disklabel/newfs you can list 
the contents of /dev thus, ls /dev to find out.  It will be ad1s1d or 
something like that

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

Re: fstab

[Joshua Lewis]

> /dev/ad1s1 what?  a, d, e, f,g ??

Do I specify? I am using the whole drive. should I change it to /dev/ad1s1a?


Thank you,
Joshua Lewis



Anubis
> Joshua Lewis wrote:
>> The last time I edited this file my system ceased to boot. I have made
>> what
>> looks to me like a valid entry. This is the same thing I entered in last
>> time. I am not going to save this but does it look valid to anyone out
>> there?
>>
>>
>> # DeviceMountpoint  FStype  Options Dump
>> Pass#
>> /dev/ad0s1b noneswapsw  0
>> 0
>> /dev/ad0s1a /   ufs rw  1
>> 1
>> /dev/ad0s1f /tmpufs rw  2
>> 2
>> /dev/ad0s1g /usrufs rw  2
>> 2
>> /dev/ad0s1e /varufs rw  2
>> 2
>> /dev/acd0c  /cdrom  cd9660  ro,noauto   0
>> 0
>> /dev/acd1c  /cdrom1 cd9660  ro,noauto   0
>> 0
>>
>> This is the line I added
>> /dev/ad1s1  /disk2  ufs rw  2  2
>>
>>
>> proc/proc   procfs  rw  0
>> 0
>>
>
> /dev/ad1s1 what?  a, d, e, f,g ??
>
>
>

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

Re: fstab

[Anubis]

Joshua Lewis wrote:
The last time I edited this file my system ceased to boot. I have made what 
looks to me like a valid entry. This is the same thing I entered in last 
time. I am not going to save this but does it look valid to anyone out there?

# DeviceMountpoint  FStype  Options DumpPass#
/dev/ad0s1b noneswapsw  0   0
/dev/ad0s1a /   ufs rw  1   1
/dev/ad0s1f /tmpufs rw  2   2
/dev/ad0s1g /usrufs rw  2   2
/dev/ad0s1e /varufs rw  2   2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
/dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0
This is the line I added
/dev/ad1s1  /disk2  ufs rw  2  2
proc/proc   procfs  rw  0   0
/dev/ad1s1 what?  a, d, e, f,g ??
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab

[Andreas Carnaily]

If new disk is not preformatted and have no filesystem it wil not boot.
On Mon, 7 Jun 2004 21:39:52 -0700, Joshua Lewis <[EMAIL PROTECTED]> 
wrote:

The last time I edited this file my system ceased to boot. I have made 
what
looks to me like a valid entry. This is the same thing I entered in last
time. I am not going to save this but does it look valid to anyone out 
there?

# DeviceMountpoint  FStype  Options Dump
Pass#
/dev/ad0s1b noneswapsw  0   0
/dev/ad0s1a /   ufs rw  1   1
/dev/ad0s1f /tmpufs rw  2   2
/dev/ad0s1g /usrufs rw  2   2
/dev/ad0s1e /varufs rw  2   2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
/dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0

This is the line I added
/dev/ad1s1  /disk2  ufs rw  2  2
proc/proc   procfs  rw  0   0

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab

[Andreas Carnaily]

On Mon, 7 Jun 2004 21:39:52 -0700, Joshua Lewis <[EMAIL PROTECTED]> 
wrote:

The last time I edited this file my system ceased to boot. I have made 
what
looks to me like a valid entry. This is the same thing I entered in last
time. I am not going to save this but does it look valid to anyone out 
there?

# DeviceMountpoint  FStype  Options Dump
Pass#
/dev/ad0s1b noneswapsw  0   0
/dev/ad0s1a /   ufs rw  1   1
/dev/ad0s1f /tmpufs rw  2   2
/dev/ad0s1g /usrufs rw  2   2
/dev/ad0s1e /varufs rw  2   2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
/dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0

This is the line I added
/dev/ad1s1  /disk2  ufs rw  2  2
If new disk placed on similar IDE than first - All right!
ad0 - Primary Master(IDE0)
ad1 - Primari Slave (IDE0)
ad2 - Primary Master(IDE1)
ad3 - Primary Slave (IDE1)
proc/proc   procfs  rw  0   0
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab spezial

[Lowell Gilbert]

Martin Klaffenboeck <[EMAIL PROTECTED]> writes:

> Yes, that would be a good idea, the problem is, it is not possible to
> mount on /floppy from a user because it isn't own by a user.

That's what fbtab(5) is for.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab spezial

[Antoine Jacoutot]

Selon Martin Klaffenboeck <[EMAIL PROTECTED]>: 
> I want to have a mechanism where some different non root users can  
> mount a floppy (and a cdrom, but lets start with a floppy) which are  
> all in the same group. 
>  
> And it should be easy with an fstab entry. 
>  
> How would you do that? 
 
I use amd, the automounter. 
 
Antoine 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab spezial

[Martin Klaffenboeck]

Am 2003.07.07 21:22 schrieb(en) Bill Moran:
Martin Klaffenboeck wrote:
Hello,

Is it possible to make an fstab entry which matches to all users?  
Something like:

/dev/fd0 ${HOME}/floppy msdos   dev,rw,noauto   0   0

But this does not work, and I couldn't find the correct one in the 
documentation.
I don't believe it's possible.

Look at scripting in the user's login script, or (probably easier) 
just
symlink each users ~/floppy to /floppy and mount the disk on /floppy.
Yes, that would be a good idea, the problem is, it is not possible to 
mount on /floppy from a user because it isn't own by a user.

I want to have a mechanism where some different non root users can 
mount a floppy (and a cdrom, but lets start with a floppy) which are 
all in the same group.

And it should be easy with an fstab entry.

How would you do that?

Martin

--
If you've got an idea and need help,
or just need general encouragement,
write me a message. ;-)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab spezial

[Bill Moran]

Martin Klaffenboeck wrote:
Hello,

Is it possible to make an fstab entry which matches to all users?  
Something like:

/dev/fd0 ${HOME}/floppy msdos   dev,rw,noauto   0   0

But this does not work, and I couldn't find the correct one in the 
documentation.
I don't believe it's possible.

Look at scripting in the user's login script, or (probably easier) just
symlink each users ~/floppy to /floppy and mount the disk on /floppy.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fstab entries??

[Patrick J Okui]

On Sat, 13 Jul 2002, Remington L. wrote:

> Im curious to know what this means
>    Dump  Pass#
>    0   0
>    1   1
>
> Will someone please explain this

from the man page (man fstab)...

---BEGIN MAN PAGE-

The fifth field, (fs_freq), is used for these filesystems by the dump(8)
command to determine which filesystems need to be dumped.  If the fifth
field is not present, a value of zero is returned and dump will assume
that the filesystem does not need to be dumped.

The sixth field, (fs_passno), is used by the fsck(8) program to determine
the order in which filesystem checks are done at reboot time.  The
root filesystem should be specified with a fs_passno of 1, and other
filesystems should have a fs_passno of 2.  Filesystems within a drive
will be checked sequentially, but filesystems on different drives will be
checked at the same time to utilize parallelism available in the hardware.
If the sixth field is not present or is zero, a value of zero is
returned and fsck(8) will assume that the filesystem does not need to be
checked.

--END MANPAGE--
hth,
Patrick.

Patrick J Okui
One2net Limited


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message