gptid's in fstab while installing FreeBSD using ISO
Hi All, How do I get gptid's as default in fstab while installing using FreeBSD iso file (Virtual,machine installation) ? Is this possible currently? if not how do I achieve this? I use guided partitioning while installing - If I were to tweak in to the source code which files or drivers I should be focusing on? which drivers write the contents of fstab? PS: any reason why we use device names in the place of gptid's as default in fstab. Thanks, Sainath. ___ 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: gptid's in fstab while installing FreeBSD using ISO
On Fri, 4 Oct 2013 20:04:09 +0530, varanasi sainath wrote: Hi All, How do I get gptid's as default in fstab while installing using FreeBSD iso file (Virtual,machine installation) ? Is this possible currently? As far as I know, the installer bsdinstall currently does not have this option included, but it already offers labeling the partitions as desired, so you could change the content of /etc/fstab manually to use labels instead of those device names. You could do this as a post-installation task while leaving the installer for the command shell and using an editor to do this. if not how do I achieve this? I use guided partitioning while installing - If I were to tweak in to the source code which files or drivers I should be focusing on? I haven't looked into the source yet, but I assume you should concentrate on the component doing the partitioning tasks as explained here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-partitioning.html which drivers write the contents of fstab? The corresponding installer's component itself which creates the file according to the partitioning layout at installation time. I assume the required data will actually be written when the installer performs the _real_ installation steps (committing to the installation). PS: any reason why we use device names in the place of gptid's as default in fstab. Because it's not always wanted or intended. Next to GPT partitioning with GPT labels, UFS partitioning is possible (both MBR and dedicated style), which _may_ have cases where it needs to be applied. Maybe this can happen when you have a very strange combination of striping, mirroring, encryption and other things that require metadata here and there... The different methods have different capabilities regarding labels (UFS labels, UFSIDs to be mentioned). You can find out more about them here: http://www.freebsd.org/doc/handbook/geom-glabel.html And read about the different methods of partitioning itself: http://www.wonkity.com/~wblock/docs/html/disksetup.html Even hardcoded device names could also be required, though I can't imagine such a situation at the moment. :-) It highly depends on the toolset you're using (the bsdinstall program, gpart, fdisk disklabel, newfs only). PS. I've trimmed the CC list to the freebsd-questions@ list for my reply, hope that's okay. -- 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: UUID in fstab.
On Monday, August 26, 2013 12:06:21 am varanasi sainath wrote: Thanks John, I have tried as you suggested using a Live CD and yes the partitions uuid's are present in gptid .. I found the UUID's in /dev/gptid - how do I determine which uid corresponds to which partition (ufs or swap or boot) (I used glabel status and after some trial and error I found them) edited the fstab accordingly and everything is working now .. The other way would be to examine the kern.geom.confxml output directly as I think you can probably use that to map between them. Is there a way to have both the /dev/XXXpYY and /dev/gptid/uuid present in /dev/ Not currently. freebsd-geom@ is probably the best place to ask that question. -- John Baldwin ___ 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: UUID in fstab.
In the last episode (Aug 26), John Baldwin said: On Monday, August 26, 2013 12:06:21 am varanasi sainath wrote: Thanks John, I have tried as you suggested using a Live CD and yes the partitions uuid's are present in gptid .. I found the UUID's in /dev/gptid - how do I determine which uid corresponds to which partition (ufs or swap or boot) (I used glabel status and after some trial and error I found them) edited the fstab accordingly and everything is working now .. gpart list will show detailed info for each provider, including the uuid for each GPT partition. -- Dan Nelson dnel...@allantgroup.com ___ 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: UUID in fstab.
Thanks John, I have tried as you suggested using a Live CD and yes the partitions uuid's are present in gptid .. I found the UUID's in /dev/gptid - how do I determine which uid corresponds to which partition (ufs or swap or boot) (I used glabel status and after some trial and error I found them) edited the fstab accordingly and everything is working now .. Is there a way to have both the /dev/XXXpYY and /dev/gptid/uuid present in /dev/ Thanks again for your support. On Sat, Aug 24, 2013 at 12:14 AM, John Baldwin j...@freebsd.org wrote: On Wednesday, August 21, 2013 4:38:00 pm varanasi sainath wrote: Thanks for the support. I want to use the uuid's found using sysctl -a in fstab. /dev/gptid/ has only uuid for boot partition. You probably have the other GPT paritions already mounted via another name which removes the names in /dev/gptid. Try booting an install CD or USB stick such that you use an alternate root fs and don't mount any of the partitions on your drive. Then you should be able to see the entries in /dev/gptid and update your fstab appropriately. If you console access you could also try to update your fstab to use /dev/gptid/uid directly instead of /dev/XXXpYY and reboot. If it works I believe the /dev/XXXpYY names will now be gone from /dev and the /dev/gptid names present instead. -- John Baldwin -- Sainath Varanasi Hyderabad 09000855250 *My Website : http://s21embedded.webs.com **Linked In Profile : http://in.linkedin.com/pub/sainathvaranasi .. .. * ___ 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: UUID in fstab.
On Wednesday, August 21, 2013 4:38:00 pm varanasi sainath wrote: Thanks for the support. I want to use the uuid's found using sysctl -a in fstab. /dev/gptid/ has only uuid for boot partition. You probably have the other GPT paritions already mounted via another name which removes the names in /dev/gptid. Try booting an install CD or USB stick such that you use an alternate root fs and don't mount any of the partitions on your drive. Then you should be able to see the entries in /dev/gptid and update your fstab appropriately. If you console access you could also try to update your fstab to use /dev/gptid/uid directly instead of /dev/XXXpYY and reboot. If it works I believe the /dev/XXXpYY names will now be gone from /dev and the /dev/gptid names present instead. -- John Baldwin ___ 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: UUID in fstab.
/dev/gptid/$UID maybe what you are looking for? Warner On Aug 21, 2013, at 12:16 AM, varanasi sainath wrote: Hello, How to find UUID's for Disk volumes. I have used sysctl -a | grep uuid and was able to find typefreebsd-swap/type rawuuidb55ff220-dcdd-11e2-a324-00155d55b20c/rawuuid typefreebsd-ufs/type rawuuidb55762fc-dcdd-11e2-a324-00155d55b20c/rawuuid are these the corresponding UUID's for swap and ufs. I din't find /dev/ufsid folder to get the UUID's I have used glabel and was able to create labels, system boots well, everything works fine but I don't want to use labels (operating constraint: to create labels I have to boot into single user mode, is there a way to create labels on mounted partitions (I hope not)). I found gptid folder which has boot UUID can this be used? How to use UUID's in fstab? I have tried using # DeviceMountpointFStype Options Dump Pass# uuid=b55762fc-dcdd-11e2-a324-00155d55b20c / ufs rw 1 1 that din't work. I found (from a post) /dev/ufsid/uuid should be used in fstab but I don't see ufsid in /dev. Do we need to create this or does the system does it? Note: Using FreeBSD 9.1. created partitions using the guided partition tool. Reason: using a SCSI storage driver which changes the drive name accordingly but freebsd installer (boot) is unable to find the drives which results in boot failure. Thanks, Sainath.* * * * *Learning is the key to excellence.* ___ freebsd-driv...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-drivers To unsubscribe, send any mail to freebsd-drivers-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
UUID in fstab.
Hello, How to find UUID's for Disk volumes. I have used sysctl -a | grep uuid and was able to find typefreebsd-swap/type rawuuidb55ff220-dcdd-11e2-a324-00155d55b20c/rawuuid typefreebsd-ufs/type rawuuidb55762fc-dcdd-11e2-a324-00155d55b20c/rawuuid are these the corresponding UUID's for swap and ufs. I din't find /dev/ufsid folder to get the UUID's I have used glabel and was able to create labels, system boots well, everything works fine but I don't want to use labels (operating constraint: to create labels I have to boot into single user mode, is there a way to create labels on mounted partitions (I hope not)). I found gptid folder which has boot UUID can this be used? How to use UUID's in fstab? I have tried using # DeviceMountpointFStype Options Dump Pass# uuid=b55762fc-dcdd-11e2-a324-00155d55b20c / ufs rw 1 1 that din't work. I found (from a post) /dev/ufsid/uuid should be used in fstab but I don't see ufsid in /dev. Do we need to create this or does the system does it? Note: Using FreeBSD 9.1. created partitions using the guided partition tool. Reason: using a SCSI storage driver which changes the drive name accordingly but freebsd installer (boot) is unable to find the drives which results in boot failure. Thanks, Sainath.* * * * *Learning is the key to excellence.* ___ 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: UUID in fstab.
Thanks for the support. I want to use the uuid's found using sysctl -a in fstab. /dev/gptid/ has only uuid for boot partition. Cheers Sainath On Wed, Aug 21, 2013 at 11:48 AM, Warner Losh i...@bsdimp.com wrote: /dev/gptid/$UID maybe what you are looking for? Warner On Aug 21, 2013, at 12:16 AM, varanasi sainath wrote: Hello, How to find UUID's for Disk volumes. I have used sysctl -a | grep uuid and was able to find typefreebsd-swap/type rawuuidb55ff220-dcdd-11e2-a324-00155d55b20c/rawuuid typefreebsd-ufs/type rawuuidb55762fc-dcdd-11e2-a324-00155d55b20c/rawuuid are these the corresponding UUID's for swap and ufs. I din't find /dev/ufsid folder to get the UUID's I have used glabel and was able to create labels, system boots well, everything works fine but I don't want to use labels (operating constraint: to create labels I have to boot into single user mode, is there a way to create labels on mounted partitions (I hope not)). I found gptid folder which has boot UUID can this be used? How to use UUID's in fstab? I have tried using # DeviceMountpointFStype Options Dump Pass# uuid=b55762fc-dcdd-11e2-a324-00155d55b20c / ufs rw 1 1 that din't work. I found (from a post) /dev/ufsid/uuid should be used in fstab but I don't see ufsid in /dev. Do we need to create this or does the system does it? Note: Using FreeBSD 9.1. created partitions using the guided partition tool. Reason: using a SCSI storage driver which changes the drive name accordingly but freebsd installer (boot) is unable to find the drives which results in boot failure. Thanks, Sainath.* * * * *Learning is the key to excellence.* ___ freebsd-driv...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-drivers To unsubscribe, send any mail to freebsd-drivers-unsubscr...@freebsd.org -- Sainath Varanasi Hyderabad 09000855250 *My Website : http://s21embedded.webs.com **Linked In Profile : http://in.linkedin.com/pub/sainathvaranasi .. .. * ___ 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 fstab Entry for Windows Share
Dear All , When a Windows XP share is mounted with the following command in FreeBSD 9.1 amd64 , it is working : # mount_smbfs -I 192.168.10.25 //user_name_in_Windows_Administrators@NetBIOS_NAME_in_Windows/Share_Name_in_Windows /mnt I could not be able to write an /etc/fstab entry to mount that share during boot . When examples in many documents from Internet are imitated , no one of them is working , or man pages are not much helpful. If an applicable , working statement is offered , it will be appreciated very much . Thank you very much . Mehmet Erol Sanliturk ___ 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: FreeBSD fstab Entry for Windows Share
When you say could not do an fstab entry, can you say what happens? Do you get any messages in logs? regards Dave -- http://www.marlinbrighton.com On 16/04/2013 08:45, Mehmet Erol Sanliturk wrote: Dear All , When a Windows XP share is mounted with the following command in FreeBSD 9.1 amd64 , it is working : # mount_smbfs -I 192.168.10.25 //user_name_in_Windows_Administrators@NetBIOS_NAME_in_Windows/Share_Name_in_Windows /mnt I could not be able to write an /etc/fstab entry to mount that share during boot . When examples in many documents from Internet are imitated , no one of them is working , or man pages are not much helpful. If an applicable , working statement is offered , it will be appreciated very much . Thank you very much . Mehmet Erol Sanliturk ___ 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 -- Dave Anderson Marlin Brighton Independent IT Consultancy Mob: 07710 537 909 email: d...@marlinbrighton.com mailto:d...@marlinbrighton.com web: www.marlinbrighton.com http://www.marlinbrighton.com ___ 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: FreeBSD fstab Entry for Windows Share
On Tue, 16 Apr 2013 00:45:24 -0700, Mehmet Erol Sanliturk wrote: I could not be able to write an /etc/fstab entry to mount that share during boot . When examples in many documents from Internet are imitated , no one of them is working , or man pages are not much helpful. Try to adapt the following configuration example I just copied from a system image which has been working many years ago: Edit the file /etc/nsmb.conf to contain access credentials if those are needed: [default] workgroup=THEGROUPNAMEHERE [WINPC] addr=192.168.123.456 [WINPC:Administrator] password=MYTOPSECRETPASSWORD In this example, WINPC is then name of the PC you want to mount the SMB shares from. Also Administrator will be the user account by which they are mounted. Please note that this might be a stupid practice. :-) Then add those entries to /etc/fstab: //Administrator@WINPC/a$ /smb/a smbfs rw,noauto 0 0 //Administrator@WINPC/c$ /smb/c smbfs rw,noauto 0 0 //Administrator@WINPC/d$ /smb/d smbfs rw,noauto 0 0 //Administrator@WINPC/e$ /smb/e smbfs rw,noauto 0 0 //Administrator@WINPC/f$ /smb/f smbfs rw,noauto 0 0 Of course you can be more specific by naming the shares by name. In this case here, the drive letters have been used to access the entire drives / logical partitions / whatever. If the shares should be mounted on boot time, remove ,noauto. If not, use mount /smb/c for example when needed. Of course make sure that the mount targets, /smb/[acdef] in this case, do exist. Finally, make sure that if you're using WINPC in /etc/fstab, put an IP for in in /etc/hosts, or it won't resolve: 192.168.123.456 WINPC This is also helpful as soon as you have to run network diagnostics as you can now use WINPC for the Windows PC in any commands. -- 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: FreeBSD fstab Entry for Windows Share
On Tue, Apr 16, 2013 at 1:13 AM, Polytropon free...@edvax.de wrote: On Tue, 16 Apr 2013 00:45:24 -0700, Mehmet Erol Sanliturk wrote: I could not be able to write an /etc/fstab entry to mount that share during boot . When examples in many documents from Internet are imitated , no one of them is working , or man pages are not much helpful. Try to adapt the following configuration example I just copied from a system image which has been working many years ago: Edit the file /etc/nsmb.conf to contain access credentials if those are needed: [default] workgroup=THEGROUPNAMEHERE [WINPC] addr=192.168.123.456 [WINPC:Administrator] password=MYTOPSECRETPASSWORD In this example, WINPC is then name of the PC you want to mount the SMB shares from. Also Administrator will be the user account by which they are mounted. Please note that this might be a stupid practice. :-) Then add those entries to /etc/fstab: //Administrator@WINPC/a$ /smb/a smbfs rw,noauto 0 0 //Administrator@WINPC/c$ /smb/c smbfs rw,noauto 0 0 //Administrator@WINPC/d$ /smb/d smbfs rw,noauto 0 0 //Administrator@WINPC/e$ /smb/e smbfs rw,noauto 0 0 //Administrator@WINPC/f$ /smb/f smbfs rw,noauto 0 0 Of course you can be more specific by naming the shares by name. In this case here, the drive letters have been used to access the entire drives / logical partitions / whatever. If the shares should be mounted on boot time, remove ,noauto. If not, use mount /smb/c for example when needed. Of course make sure that the mount targets, /smb/[acdef] in this case, do exist. Finally, make sure that if you're using WINPC in /etc/fstab, put an IP for in in /etc/hosts, or it won't resolve: 192.168.123.456 WINPC This is also helpful as soon as you have to run network diagnostics as you can now use WINPC for the Windows PC in any commands. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... Dear Polytropon , Your message has supplied important information . When their equivalent values are entered , they worked : WINPC : NetBIOS_NAME_in_Windows workgroup : Work_Group_NAME_in_Windows Administrator : user_name_in_Windows_Administrators F$ : Share_Name_in_Windows With the above values : /etc/nsmb.conf : - [default] Workgroup=Work_Group_NAME_in_Windows [NetBIOS_NAME_in_Windows] addr=192.168.10.25 - The following values are NOT required ( they are not taken into consideration ) : [WINPC:Administrator] password=MYTOPSECRETPASSWORD During boot , the password is asked . /etc/hosts : - 192.168.10.25 NetBIOS_NAME_in_Windows - /etc/fstab : - //user_name_in_Windows_Administrators@NetBIOS_NAME_in_Windows/Share_Name_in_Windows /mnt smbfs rw 0 0 - where /mnt is the mount directory in FreeBSD server , the sample IP number 192.168.10.25 will be replaced by actual IP number . Thank you very much . Mehmet Erol Sanliturk ___ 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: FreeBSD fstab Entry for Windows Share
On Tue, Apr 16, 2013 at 1:08 AM, Dave Anderson d...@marlinbrighton.comwrote: When you say could not do an fstab entry, can you say what happens? Do you get any messages in logs? regards Dave -- http://www.marlinbrighton.com On 16/04/2013 08:45, Mehmet Erol Sanliturk wrote: Dear All , When a Windows XP share is mounted with the following command in FreeBSD 9.1 amd64 , it is working : # mount_smbfs -I 192.168.10.25 //user_name_in_Windows_**Administrators@NetBIOS_NAME_** in_Windows/Share_Name_in_**Windows /mnt I could not be able to write an /etc/fstab entry to mount that share during boot . When examples in many documents from Internet are imitated , no one of them is working , or man pages are not much helpful. If an applicable , working statement is offered , it will be appreciated very much . Thank you very much . Mehmet Erol Sanliturk __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org -- Dave Anderson Marlin Brighton Independent IT Consultancy Mob: 07710 537 909 email: d...@marlinbrighton.com mailto:dave@marlinbrighton.**comd...@marlinbrighton.com web: www.marlinbrighton.com http://www.marlinbrighton.com Dear Dave , By using information from Polytropon's message , I could be able to define /etc/fstab entry correctly . With respect to your question : When an entry is erroneous in /etc/fstab file , booting is entering into single user mode . After correction of erroneous entry , a fast boot is restarting . The above cycle is continuing up to a completely correct /etc/fstab file is supplied . Thank you very much . Mehmet Erol Sanliturk ___ 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: FreeBSD fstab Entry for Windows Share
When you put the entry in fstab and then try to mount it with fstab providing the details, what happens? i.e. without doing a reboot, test fstab by doing the mounts from the command line with the details in fstab regards Dave http://www.marlinbrighton.com On 16/04/2013 10:34, Mehmet Erol Sanliturk wrote: Dear Dave , By using information from Polytropon's message , I could be able to define /etc/fstab entry correctly . With respect to your question : When an entry is erroneous in /etc/fstab file , booting is entering into single user mode . After correction of erroneous entry , a fast boot is restarting . The above cycle is continuing up to a completely correct /etc/fstab file is supplied . Thank you very much . Mehmet Erol Sanliturk ___ 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: FreeBSD fstab Entry for Windows Share
On Tue, Apr 16, 2013 at 2:41 AM, Dave Anderson d...@marlinbrighton.comwrote: When you put the entry in fstab and then try to mount it with fstab providing the details, what happens? i.e. without doing a reboot, test fstab by doing the mounts from the command line with the details in fstab regards Dave http://www.marlinbrighton.com On 16/04/2013 10:34, Mehmet Erol Sanliturk wrote: Dear Dave , By using information from Polytropon's message , I could be able to define /etc/fstab entry correctly . With respect to your question : When an entry is erroneous in /etc/fstab file , booting is entering into single user mode . After correction of erroneous entry , a fast boot is restarting . The above cycle is continuing up to a completely correct /etc/fstab file is supplied . Thank you very much . Mehmet Erol Sanliturk Dear Dave , My intention was to eliminate separate mount statement . For this , a noauto is not used . This is allowing login as a regular user into server , there is no any necessity to mount and umount statements . Therefore , I did not try noauto and then mount . Thank you very much . Mehmet Erol Sanliturk ___ 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: FreeBSD fstab Entry for Windows Share
On Tue, 16 Apr 2013 02:28:33 -0700, Mehmet Erol Sanliturk wrote: Your message has supplied important information . As I said, I did obtain it from a system that _has been working_ in that regards. :-) When their equivalent values are entered , they worked : WINPC : NetBIOS_NAME_in_Windows workgroup : Work_Group_NAME_in_Windows Administrator : user_name_in_Windows_Administrators F$ : Share_Name_in_Windows With the above values : /etc/nsmb.conf : - [default] Workgroup=Work_Group_NAME_in_Windows [NetBIOS_NAME_in_Windows] addr=192.168.10.25 - The following values are NOT required ( they are not taken into consideration ) : [WINPC:Administrator] password=MYTOPSECRETPASSWORD During boot , the password is asked . If this case of interactivity at system startup is _not_ intended, the information (username, password) can be obtained from the /etc/nsmb.conf file. It's important to pay attention to the file permissions. /etc/fstab : - //user_name_in_Windows_Administrators@NetBIOS_NAME_in_Windows/Share_Name_in_Windows /mnt smbfs rw 0 0 You could possibly add the late option (rw,auto,late) so in case of network problems, the boot process won't stop at the early stage (fstab error). -- 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: Can an ISO file be mounted from /etc/fstab at boot?
On Fri, Mar 15, 2013 at 04:04:23PM -0400, Lowell Gilbert typed: Oscar Hodgson oscar.hodg...@gmail.com writes: I'm pretty sure the answer is no, just write a local rc script to do that, but thought I'd check. Can't see any hint of that capability in the handbook or fstab(5). Really just looking for a single point of management for file systems I don't see a way offhand. You need to do the mdconfig before you can mount, and I don't think that can be done inside of fstab. I think that adding such a capability to mount(8) as a program option would be a fairly minor hack. If it was a standard (UFS) filesystem image (not ISO9600) it would be possible to mount from fstab with something like this: /dev/md0 /data/mfs mfs rw,-PF/path/to/some.img,async 0 0 Ruben ___ 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
Can an ISO file be mounted from /etc/fstab at boot?
I'm pretty sure the answer is no, just write a local rc script to do that, but thought I'd check. Can't see any hint of that capability in the handbook or fstab(5). Really just looking for a single point of management for file systems Thanks in advance. Oscar ___ 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: Can an ISO file be mounted from /etc/fstab at boot?
Oscar Hodgson oscar.hodg...@gmail.com writes: I'm pretty sure the answer is no, just write a local rc script to do that, but thought I'd check. Can't see any hint of that capability in the handbook or fstab(5). Really just looking for a single point of management for file systems I don't see a way offhand. You need to do the mdconfig before you can mount, and I don't think that can be done inside of fstab. I think that adding such a capability to mount(8) as a program option would be a fairly minor hack. ___ 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: How to list /etc/fstab in new BFSD label?
On Sun, 21 Oct 2012 17:00:13 -1000, Al Plant wrote: Aloha, I cant find any How TO on writing the hardware devices into /etc/fstab to mount and find how the DVD and CD players get connected. Open the file in your favourite editor and add the lines according to your needs, if this was the question. :-) (This happens to be with a test box FreeBSD 10.* which has worked fine other than that.) The BSD install I understand is also for FreeBSD 9.* as well. fd0, /floppy, acd0 /cdrom, acd1 DVD, do not come up although they are in /dmesg list. I thought FreeBSD would have removed the acd devices in favour of the SCSI-backed cd device drivers? If dmesg lists the devices as recognized, the required device files should be present in /dev. Ye olde sysinstall did add them to your first /etc/fstab, but you are free to add whatever you like manually. For the purpose of installation, they shouldn't be needed. And I have to admit that I've never actually seen them in one of the dialogs in the installer - only the hard disk related things are in there. The automatically generated /etc/fstab at least had them listed (for sysinstall, not tested for bsdinstall). However, modern HAL + DBUS combinations prefer not to have any media devices listed in /etc/fstab, because they're doing the stuff required on their own. -- 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
How to list /etc/fstab in new BFSD label?
Aloha, I cant find any How TO on writing the hardware devices into /etc/fstab to mount and find how the DVD and CD players get connected. (This happens to be with a test box FreeBSD 10.* which has worked fine other than that.) The BSD install I understand is also for FreeBSD 9.* as well. fd0, /floppy, acd0 /cdrom, acd1 DVD, do not come up although they are in /dmesg list. Any help would be appreciated. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ 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: Auto-mounting sshfs from /etc/fstab
Hello, Well, no I haven't -- I have tried only the fstab route which does serve the purpose for me. Thanks nonetheless :) OriS On Wednesday, September 5, 2012, andrew clarke wrote: On Wed 2012-09-05 19:38:54 UTC+0200, OriS ( site.free...@orientalsensation.com javascript:;) wrote: I've been trying to find a page on the Internet where an example is posted explaining how to mount sshfs from /etc/fstab, but I can't find any! Have you tried running sshfs from cron? eg. run crontab -e as a regular user and add: @reboot /usr/local/bin/sshfs remotehost: $HOME/mnt/remote Note: Untested. ___ 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
Auto-mounting sshfs from /etc/fstab
Hello all, I've been trying to find a page on the Internet where an example is posted explaining how to mount sshfs from /etc/fstab, but I can't find any! I'm on 9.1-PR amd64 and I've installed Fuse and sshfs, I have enabled Fuse in rc.conf and I can see /dev/fuse. Furthermore, using sshfs from the command line, I am even able to mount the remote file system. I can manually mount the remote file system using: *sshfs user@host:/ /mnt* Then, I do 'mount -p' and get: */dev/fuse0 /mnt fusefs.sshfs rw,sync 0 0* This isn't sufficient for mounting/unmounting from fstab since it's missing the authentication details I've used in sshfs. So.. the question is: How to add the authentication details to /etc/fstab so that I can mount the sshfs just by using: *mount /mnt* Thanks in advance, and kindly Cc me on your replies! /OriS ___ 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: Auto-mounting sshfs from /etc/fstab
On Wed 2012-09-05 19:38:54 UTC+0200, OriS (site.free...@orientalsensation.com) wrote: I've been trying to find a page on the Internet where an example is posted explaining how to mount sshfs from /etc/fstab, but I can't find any! Have you tried running sshfs from cron? eg. run crontab -e as a regular user and add: @reboot /usr/local/bin/sshfs remotehost: $HOME/mnt/remote Note: Untested. ___ 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: Auto-mounting sshfs from /etc/fstab
On Thu, 6 Sep 2012 07:43:38 +1000, andrew clarke wrote: On Wed 2012-09-05 19:38:54 UTC+0200, OriS (site.free...@orientalsensation.com) wrote: I've been trying to find a page on the Internet where an example is posted explaining how to mount sshfs from /etc/fstab, but I can't find any! Have you tried running sshfs from cron? eg. run crontab -e as a regular user and add: @reboot /usr/local/bin/sshfs remotehost: $HOME/mnt/remote Note: Untested. Also untested, but possible, if you want it to happen system-wide: Add a section to /etc/rc.local: echo -n sshfs /usr/local/bin/sshfs your parameters And to /etc/rc.shutdown.local: echo -n sshfs umount where it was mounted to Note that you can add additional configuration tweaks by using the rc.conf mechanism, and you can also add tests to increase reliability. -- 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: Auto-mounting sshfs from /etc/fstab
In the past I wanted to do so in my system. I had one server called pluto and I wanted to sshfs one directory from my laptop. The first thing I had to do was to make passwordless ssh from my laptop to the server (there are a lot of pages in the internet to explain how to do this, so I will not explain how-to...) When passwordless ssh login is possible then a line in your fstab like the following does the job: sshfs#your_username_here@pluto:/Common/ /Network_Folders/Pluto/ fuse BatchMode=yes,reconnect,allow_other,users,gid=users,umask=002 0 0 In this way the system automounts the directory /Common that exists in pluto in my local directory /Network_Folders/Pluto Of cource pluto must have a specific ip (or available through naming service e.t.c.). In my case it has a static IP so I had its declaration in /etc/hosts Hope this helped you 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 problem
2012-01-14 11:00, per...@pluto.rain.com skrev: Bernt Hanssonb...@bananmonarki.se 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
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 problem
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
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 g...@unixarea.de - 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
Bernt Hansson b...@bananmonarki.se 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: FreeBSD 8.2-RELEASE Install Failure: Unable to create a new /etc/fstab
Just following up...I resolved the issue by copying /etc/* to /stand/ in the mfsroot. On Tue, Oct 25, 2011 at 12:54 PM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am Installing 8.2-RELEASE via PXE and receive an error stating that sysinstall was unable to create new /etc/fstab. Everything appears to function correctly, in that, the system TFTP's the pxeboot and mfsroot files as needed. However, When I switch to the holographic shell and poke around a little, I can see that there is no /etc, despite it's existence in the mfsroot.gz. I must be missing something and am hoping that someone might be able to point in the right direction. -- Take care Rick Miller -- Take care Rick Miller ___ 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 8.2-RELEASE Install Failure: Unable to create a new /etc/fstab
Hi All, I am Installing 8.2-RELEASE via PXE and receive an error stating that sysinstall was unable to create new /etc/fstab. Everything appears to function correctly, in that, the system TFTP's the pxeboot and mfsroot files as needed. However, When I switch to the holographic shell and poke around a little, I can see that there is no /etc, despite it's existence in the mfsroot.gz. I must be missing something and am hoping that someone might be able to point in the right direction. -- Take care Rick Miller ___ 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: i messed up, need to do fsck and also uncomment the /usr line if /etc/fstab
Henry Olyer henry.ol...@gmail.com writes: I had an old FBSD 7.2 CD. good enough for this I thought. I booted from that but now I need to mount the file systems on my hard drive. How do I do that? I agree,, once I get the /etc file system mounted I can edit the file. Okay, next.. How do I do an fsck on the /usr file system when coming up? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RCCONF-READONLY ___ 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: i messed up, need to do fsck and also uncomment the /usr line if /etc/fstab
On 7 May 2011 04:31, Yuri Pankov yuri.pan...@gmail.com wrote: On Fri, May 06, 2011 at 10:06:31PM -0400, Henry Olyer wrote: Woe is me. First, I simply messed up, happens to us all from time to time. I lost power on an laptop running 8.2. Restarted it but for some reason the fsck didn't run and I lost some /usr files. I tried to do an fsck manually but because it's mounted I got nowhere. So I put a comment (#) in front of the /usr line for the /etc/fstab file. Now, I can't boot. I need what's on my disk -- of course! Boot to single user mode (4 in the boot menu), remount / read-write - mount -u -o rw /, edit /etc/fstab (you'll probably need to mount /usr manually if what's in /rescue doesn't work for you), reboot. You can run fsck from single user mode, as well. HTH, Yuri Easiest way in single user if vi complains about termcap and you don't understand ed... As Yuri suggested: # fsck / # mount -ie / Then you can just use sed in place; # sed -i.bak -e 's,#\(.*/usr\),\1,' /etc/fstab # fsck /usr # reboot Hope that helps! Chris ___ 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
i messed up, need to do fsck and also uncomment the /usr line if /etc/fstab
Woe is me. First, I simply messed up, happens to us all from time to time. I lost power on an laptop running 8.2. Restarted it but for some reason the fsck didn't run and I lost some /usr files. I tried to do an fsck manually but because it's mounted I got nowhere. So I put a comment (#) in front of the /usr line for the /etc/fstab file. Now, I can't boot. I need what's on my disk -- of course! ___ 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: i messed up, need to do fsck and also uncomment the /usr line if /etc/fstab
Boot to a boot disk.. anything... CD, DVD, USB Load up vi - you can probably do this from a live linux distro. Unedit the line. Save. Quit. Reboot. You're golden. On May 6, 2011, at 9:06 PM, Henry Olyer wrote: Woe is me. First, I simply messed up, happens to us all from time to time. I lost power on an laptop running 8.2. Restarted it but for some reason the fsck didn't run and I lost some /usr files. I tried to do an fsck manually but because it's mounted I got nowhere. So I put a comment (#) in front of the /usr line for the /etc/fstab file. Now, I can't boot. I need what's on my disk -- of course! ___ 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: i messed up, need to do fsck and also uncomment the /usr line if /etc/fstab
I had an old FBSD 7.2 CD. good enough for this I thought. I booted from that but now I need to mount the file systems on my hard drive. How do I do that? I agree,, once I get the /etc file system mounted I can edit the file. Okay, next.. How do I do an fsck on the /usr file system when coming up? On Fri, May 6, 2011 at 10:32 PM, Ryan Coleman edi...@d3photography.comwrote: Boot to a boot disk.. anything... CD, DVD, USB Load up vi - you can probably do this from a live linux distro. Unedit the line. Save. Quit. Reboot. You're golden. On May 6, 2011, at 9:06 PM, Henry Olyer wrote: Woe is me. First, I simply messed up, happens to us all from time to time. I lost power on an laptop running 8.2. Restarted it but for some reason the fsck didn't run and I lost some /usr files. I tried to do an fsck manually but because it's mounted I got nowhere. So I put a comment (#) in front of the /usr line for the /etc/fstab file. Now, I can't boot. I need what's on my disk -- of course! ___ 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: i messed up, need to do fsck and also uncomment the /usr line if /etc/fstab
On Fri, May 06, 2011 at 10:06:31PM -0400, Henry Olyer wrote: Woe is me. First, I simply messed up, happens to us all from time to time. I lost power on an laptop running 8.2. Restarted it but for some reason the fsck didn't run and I lost some /usr files. I tried to do an fsck manually but because it's mounted I got nowhere. So I put a comment (#) in front of the /usr line for the /etc/fstab file. Now, I can't boot. I need what's on my disk -- of course! Boot to single user mode (4 in the boot menu), remount / read-write - mount -u -o rw /, edit /etc/fstab (you'll probably need to mount /usr manually if what's in /rescue doesn't work for you), reboot. You can run fsck from single user mode, as well. HTH, Yuri ___ 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
Question about fstab
Hello all! I want use redundant scheme for booting my OS. For instance I have two ufs slices and each of them keep /boot folder. For example, I want use fstab like that: # DeviceMountpoint FStype Options Dump Pass# /dev/ad6s1b noneswapsw 0 0 /dev/ad6s1a /bootdirufs rw 1 1 /dev/ad4s1a/mnt/bootdirufs rw 1 1 That scheme will work unless one of ufs slices go out. After that I just select bootable disk in BIOS and reboot. But during boot process I have got error that one of slices can't be mounted. It's not convinient. How can I get decision? Thank all. ___ 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: Question about fstab
2010/4/14 Дмитрий Бехтерев dbehte...@gmail.com Hello all! I want use redundant scheme for booting my OS. Most would use gmirror, zfs mirror, or a hardware based solution instead of your approach. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html -- Adam Vande More ___ 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
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 http://www.netmusician.org j...@netmusician.org mailto: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 http://www.netmusician.org j...@netmusician.org mailto: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
fstab NFS mount option recommendations
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 http://www.netmusician.org j...@netmusician.org mailto: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
On Sun, 31 Jan 2010 00:35:02 +0200, Elias Chrysocheris elias...@cha.forthnet.gr 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
fstab syntax
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
Re: fstab syntax
On 30 January 2010 19:05, Jeff Laine wtf.jla...@gmail.com 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 syntax
On Sat, 30 Jan 2010 22:05:43 +0300 Jeff Laine wtf.jla...@gmail.com 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
On Sat,30-01-2010 [19:33:37], krad wrote: On 30 January 2010 19:05, Jeff Laine wtf.jla...@gmail.com 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
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: Partition naming, fstab, and geli
On Mon, 16 Nov 2009 13:01:26 -0500, Jerry McAllister jerr...@msu.edu wrote: I tend to use 'a' if the drive will be entirely one slice and one partition used for some special work or scratch space, but stick with 'd..h' if there will be more than one partition and just leave 'a' alone - for no other reason than habit. And I tend to omit the slice at all. :-) # newfs -U /dev/ad1 # mount /dev/ad1 /somewhere This is so easy because I very often use sysinstall for initializing the disk when installing, but any further disk adding is done via CLI as shown above, because it's much simpler - and I didn't see any reason to create a slice - even if I wanted to have more than one partition, which I often don't want. As for 'd' vs 'e', sometime a long time and many generations ago there was a convention of reserving 'd' for something. I don't remember what it was. It was pre FreeBSD 3 and pre 1997 and maybe even pre any FreeBSD and applied in some earlier Unix-en before the court cases, but not after. That old convention accounts for documentation starting with using 'e' for extra partitions and skipping 'd'. But, whatever that old convention was, it has not been used for so long that it is meaningless nowdays and 'd' can be used for whatever extra partition you want. You say it: I KNEW that there was something someone had on his mind when reserving 'd' for something special... but WHAT it exactly was, I don't know. -- 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: Partition naming, fstab, and geli
On Tue, Nov 17, 2009 at 02:45:15PM +0100, Polytropon wrote: On Mon, 16 Nov 2009 13:01:26 -0500, Jerry McAllister jerr...@msu.edu wrote: As for 'd' vs 'e', sometime a long time and many generations ago there was a convention of reserving 'd' for something. I don't remember what it was. It was pre FreeBSD 3 and pre 1997 and maybe even pre any FreeBSD and applied in some earlier Unix-en before the court cases, but not after. That old convention accounts for documentation starting with using 'e' for extra partitions and skipping 'd'. But, whatever that old convention was, it has not been used for so long that it is meaningless nowdays and 'd' can be used for whatever extra partition you want. You say it: I KNEW that there was something someone had on his mind when reserving 'd' for something special... but WHAT it exactly was, I don't know. If I remember correctly, NetBSD still uses (or did so until a few years ago) the 'd' partition to represent the whole disk, while 'c' is used in the usual way to represent the whole slice. Regards Thomas ___ 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: Partition naming, fstab, and geli
On Sun, Nov 15, 2009 at 07:23:15PM -0700, David Allen wrote: Say I have performed a standard installation of FreeBSD onto a single IDE drive with the following entries in /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d /var ufs rw 2 2 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 Then I added more drives. 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? It really doesn't matter. Just don't use 'c' and I usually skip using 'b' and even often use it for a little additional swap. But, just pick a habit that works for you and stick with it. /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Leave the fstype alone. Use the noauto option. Probably set dump and pass to 0 also. So, for example, if you do not want it to try and mount /dev/ad3f at boot time, the line would look like: /dev/ad3f /bar3 ufs rw,noauto 0 0 Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 Thanks. ___ 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: Partition naming, fstab, and geli
On Sun, 15 Nov 2009 19:23:15 -0700 David Allen the.real.david.al...@gmail.com wrote: 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 geli partitions can exist at mount time, but you either have to be present at the console to type-in the pass-phrase or configure it to use a passfile. If you attach your geli-partitions manually then you can either set the fstab entries to noauto, or omit them altogether. ___ 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: Partition naming, fstab, and geli
In freebsd-questions Digest, Vol 285, Issue 2, Message 2 On Sun, 15 Nov 2009 19:23:15 -0700 David Allen wrote: Say I have performed a standard installation of FreeBSD onto a single IDE drive with the following entries in /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d /var ufs rw 2 2 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 Then I added more drives. 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 If you added these with sysinstall (or sade) it will tend to choose 'd' for the first partition on other than the / partition (which is named 'a' on install). Or at least, it's always started with 'd' for me :) But if you're doing it manually starting with 'e' is fine. I suspect the handbook section you quoted to Polytropon later is more an example than definitive. You can happily mount an 'a' partition from another drive that was once a system disk; it's more of a convention really. 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 Yes. Here I must differ with Polytropon, though your format for the options isn't perhaps quite right. From an old fstab here: # DeviceMountpoint FStype Options DumpPass# /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdosfs ro,noauto 0 0 /dev/ad0s2b noneswapsw 0 0 /dev/ad0s2a / ufs rw 1 1 /dev/ad0s2d /varufs rw,noatime 2 2 /dev/ad0s2e /usrufs rw,noatime 2 2 /dev/ad0s4d /paqi4.5ufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 3 /dev/ad0s4e /paqi4.5/varufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 /dev/ad0s4f /paqi4.5/usrufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 # 25Apr06 ext 20Gb USB disk. DON'T autoadd these, deadly if da0 absent! # .. xx fsopts, everything incl fsck must ignore .. /dev/da0s3d /usbdsk ufs xx,noauto,nosymfollow 3 3 /dev/da0s3e /usbdsk/var ufs xx,noauto,nosymfollow 4 4 /dev/da0s3f /usbdsk/usr ufs xx,noauto,nosymfollow 4 4 # 26May06 shintaro 1G flashdrive .. just doc, can't mount using these .. /dev/da0s1 /flash/dos msdosfs xx,noauto 0 0 /dev/da0s2d /flash/ufs ufs xx,noauto,noatime 3 3 /dev/da0s3d /flash/pvt ufs xx,noauto,noatime 3 3 As you say they're useful for doc, and not hard to edit into action. Note the additions above were assigned starting at 'd' by sysinstall. cheers, Ian ___ 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: Partition naming, fstab, and geli
On Tue, Nov 17, 2009 at 03:04:27AM +1100, Ian Smith wrote: In freebsd-questions Digest, Vol 285, Issue 2, Message 2 On Sun, 15 Nov 2009 19:23:15 -0700 David Allen wrote: Say I have performed a standard installation of FreeBSD onto a single IDE drive with the following entries in /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d /var ufs rw 2 2 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 Then I added more drives. 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 If you added these with sysinstall (or sade) it will tend to choose 'd' for the first partition on other than the / partition (which is named 'a' on install). Or at least, it's always started with 'd' for me :) Generally, using 'a' for root is needed if the slice is a device and root (/) will be there. But, probably because of that, the tradition of reserving 'a' is strong enough that many people and some utilities just do it that way unless specifically directed otherwise. But, if it is a second (third, fourth, etc) slice/drive that will not have a root partition, it doesn't actually matter. I tend to use 'a' if the drive will be entirely one slice and one partition used for some special work or scratch space, but stick with 'd..h' if there will be more than one partition and just leave 'a' alone - for no other reason than habit. As for 'd' vs 'e', sometime a long time and many generations ago there was a convention of reserving 'd' for something. I don't remember what it was. It was pre FreeBSD 3 and pre 1997 and maybe even pre any FreeBSD and applied in some earlier Unix-en before the court cases, but not after. That old convention accounts for documentation starting with using 'e' for extra partitions and skipping 'd'. But, whatever that old convention was, it has not been used for so long that it is meaningless nowdays and 'd' can be used for whatever extra partition you want. jerry But if you're doing it manually starting with 'e' is fine. I suspect the handbook section you quoted to Polytropon later is more an example than definitive. You can happily mount an 'a' partition from another drive that was once a system disk; it's more of a convention really. 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 Yes. Here I must differ with Polytropon, though your format for the options isn't perhaps quite right. From an old fstab here: # DeviceMountpoint FStype Options DumpPass# /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdosfs ro,noauto 0 0 /dev/ad0s2b noneswapsw 0 0 /dev/ad0s2a / ufs rw 1 1 /dev/ad0s2d /varufs rw,noatime 2 2 /dev/ad0s2e /usrufs rw,noatime 2 2 /dev/ad0s4d /paqi4.5ufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 3 /dev/ad0s4e /paqi4.5/varufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 /dev/ad0s4f /paqi4.5/usrufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 # 25Apr06 ext 20Gb USB disk. DON'T autoadd these, deadly if da0 absent! # .. xx fsopts, everything incl fsck must ignore .. /dev/da0s3d /usbdsk ufs xx,noauto,nosymfollow 3 3 /dev/da0s3e /usbdsk/var ufs xx,noauto,nosymfollow 4 4 /dev/da0s3f /usbdsk/usr ufs xx,noauto,nosymfollow 4 4 # 26May06 shintaro 1G flashdrive .. just doc, can't mount using these .. /dev/da0s1
Partition naming, fstab, and geli
Say I have performed a standard installation of FreeBSD onto a single IDE drive with the following entries in /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d /var ufs rw 2 2 /dev/ad0s1e /tmp ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 Then I added more drives. 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 Thanks. ___ 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: Partition naming, fstab, and geli
On Sun, 15 Nov 2009 19:23:15 -0700, David Allen the.real.david.al...@gmail.com wrote: 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 The Handbook says in 18.3.1 sub 3: A disk can have up to eight partitions, labeled a-h. A few of the partition labels have special uses. The a partition is used for the root partition (/). Thus only your system disk (e.g, the disk you boot from) should have an a partition. The b partition is used for swap partitions, and you may have many disks with swap partitions. The c partition addresses the entire disk in dedicated mode, or the entire FreeBSD slice in slice mode. The other partitions are for general use. Note the last sentence. Due to this statement, I think the usage of 'e' is arbitrary, 'd' could be okay, too, but when the Handbook says 'e' in the example (maybe with the intention of 'e' like in 'example'?), you can use 'e', too, especially when you want to use more than one partition. I have to admit that I never put slices on extra hard disks, I'm always using the whole disk, so # newfs /dev/ad3 would give me /dev/ad3 (which is the same as /dev/ad3c), and the entry /dev/ad3 /foo ufs rw 2 2 would go into fstab. I'm sure you already know this because it seems that you read up until 18.3.2.2 - you're omitting slices, dedicated mode. :-) Bottom line: The naming convention mentioned in the Handbook and your examples are completely okay. 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. That's completely intended. :-) So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 I would say: No. The entry for those partitions should rather be: /dev/ad1e.eli /home/david/private ufs rw,noauto 0 0 /dev/ad3e /fakeufs rw,noauto 0 0 /dev/ad3f /reservedufs rw,noauto 0 0 The ufs in the FS field tells the system which FS to use when later mounting (e. g. with requiring a pass phrase from the operator), and noauto in the options field that prohibits mounting the file system at startup. If you used xx in the FS field, you could not easily # mount /reserved because the mount command wouldn't know which FS to use (allthough I think UFS might be a default here). -- 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: Partition naming, fstab, and geli
On 11/15/09, Polytropon wrote: On Sun, 15 Nov 2009 19:23:15 -0700, David Allen wrote: 1. The Handbook suggests there is a convention that when partitioning a a drive that's been added, to label the first new partition on that drive as 'e' as opposed to 'a' (which is reserved for the /root partition). Does the following satisfy that convention, or would starting with 'a' in each case make more sense? /dev/ad1e /foo1 ufs rw 2 2 /dev/ad1f /bar1 ufs rw 2 2 /dev/ad1g /baz1 ufs rw 2 2 /dev/ad2e /foo2 ufs rw 2 2 /dev/ad2f /bar2 ufs rw 2 2 /dev/ad3e /foo3 ufs rw 2 2 /dev/ad3f /bar3 ufs rw 2 2 The Handbook says in 18.3.1 sub 3: A disk can have up to eight partitions, labeled a-h. A few of the partition labels have special uses. The a partition is used for the root partition (/). Thus only your system disk (e.g, the disk you boot from) should have an a partition. The b partition is used for swap partitions, and you may have many disks with swap partitions. The c partition addresses the entire disk in dedicated mode, or the entire FreeBSD slice in slice mode. The other partitions are for general use. Note the last sentence. Due to this statement, I think the usage of 'e' is arbitrary, 'd' could be okay, too, but when the Handbook says 'e' in the example (maybe with the intention of 'e' like in 'example'?), you can use 'e', too, especially when you want to use more than one partition. Well, you and I seem to be on the same page, but I was referring to the following: 2.6.5 Creating Partitions Using Disklabel Table 2-3. Partition Layout for Subsequent Disks The rest of the disk is taken up with one big partition. This could easily be put on the a partition, instead of the e partition. However, convention says that the a partition on a slice is reserved for the filesystem that will be the root (/) filesystem. You do not have to follow this convention, but sysinstall does, so following it yourself makes the installation slightly cleaner. You can choose to mount this filesystem anywhere; this example suggests that you mount them as directories /diskn, where n is a number that changes for each disk. But you can use another scheme if you prefer. The 'e' partition is again used in the Handbook section 18.3 Adding Disks. I guess I'm looking for the pedantic answer, but I'll settle for less. I have to admit that I never put slices on extra hard disks, I'm always using the whole disk, so # newfs /dev/ad3 would give me /dev/ad3 (which is the same as /dev/ad3c), and the entry /dev/ad3 /foo ufs rw 2 2 would go into fstab. I'm sure you already know this because it seems that you read up until 18.3.2.2 - you're omitting slices, dedicated mode. :-) I'd prefer the same with the first disk, but sysinstall won't accomodate it, and on most installations, it's more work trying to work around sysinstall than it is using it. So non-dedicated it is. Bottom line: The naming convention mentioned in the Handbook and your examples are completely okay. Great. 2. My second question is in regards to using the 'xx' fstype to have the system ignore that device. Consider, for example, a geli encrypted partition. The .eli device doesn't exist at boot time. I discovered by accident that the system won't boot with an fstab entry for a device that doesn't exist. That's completely intended. :-) LOL. Surprised me. I figured a 'noauto' for a non-existent device would be acceptable. So if I was to record an entry in fstab, I couldn't use /dev/ad1e.eli /home/david/private ufs rw 0 0 Does that mean that the following is what's typically to record fstab entries for ignored devices? /dev/ad1e.eli /home/david/private xx rw 0 0 /dev/ad3e /fakexx rw 0 0 /dev/ad3f /reservedxx rw 0 0 I would say: No. The entry for those partitions should rather be: /dev/ad1e.eli /home/david/private ufs rw,noauto 0 0 /dev/ad3e /fakeufs rw,noauto 0 0 /dev/ad3f /reservedufs rw,noauto 0 0 But the eli device doesn't exist until after it's attached, which, in my case, will happen manually and on-demand after boot. The ufs in the FS field tells the system which FS to use when later mounting (e. g. with requiring a pass phrase from the operator), and noauto in the options field that prohibits mounting the file system at startup. A pass phrase from the operator? Not likely. It's not a desktop. Each of the following will result in the system not booting: # there is no ad4 /dev/ad4a /foo ufs rw,noauto 0 0
/etc/fstab + embedded spaces
I was attempting to create this entry in the /etc/fstab file. It is to a WinXP machine. //u...@bios/My Documents /laptop smbfs rw,noauto 0 0 It fails because 'fstab' does not allow embedded spaces in device names, not does it allow enclosing the name in quotes. I did some Googling and discovered that I am not the only one annoyed by this behavior. I discovered this patch that had been submitted awhile ago. http://lists.freebsd.org/pipermail/freebsd-bugs/2007-October/026469.html Changing the share name is not really an option. Is there some way of making this work in 'fstab'? I can use the name including spaces in 'mount_smbfs' so that is how I am currently mounting the share. It just seems strange that 'fstab' by not accepting the use of quoting is not in step with how FreeBSD usually operates. -- Carmel carmel...@hotmail.com |=== |=== |=== |=== | It is much easier to suggest solutions when you know nothing about the problem. ___ 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: /etc/fstab + embedded spaces
carmel_ny wrote: I was attempting to create this entry in the /etc/fstab file. It is to a WinXP machine. //u...@bios/My Documents /laptop smbfs rw,noauto 0 0 It fails because 'fstab' does not allow embedded spaces in device names, not does it allow enclosing the name in quotes. I did some Googling and discovered that I am not the only one annoyed by this behavior. I discovered this patch that had been submitted awhile ago. http://lists.freebsd.org/pipermail/freebsd-bugs/2007-October/026469.html Changing the share name is not really an option. Is there some way of making this work in 'fstab'? I can use the name including spaces in 'mount_smbfs' so that is how I am currently mounting the share. It just seems strange that 'fstab' by not accepting the use of quoting is not in step with how FreeBSD usually operates. Don't know if this works for fstab, but the normal way to escape spaces is with a \, like this: //u...@bios/My\ Documents /laptop smbfs rw,noauto 0 0 May not work in fstab but you can try it and see. -Mike ___ 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: /etc/fstab + embedded spaces
On Tue 2009-11-03 06:57:12 UTC-0500, carmel_ny (carmel...@hotmail.com) wrote: I was attempting to create this entry in the /etc/fstab file. It is to a WinXP machine. //u...@bios/My Documents /laptop smbfs rw,noauto 0 0 It fails because 'fstab' does not allow embedded spaces in device names, not does it allow enclosing the name in quotes. A workaround may be to run mount_smbfs from /etc/crontab (or perhaps the root user's crontab), eg. @reboot /usr/sbin/mount_smbfs -N //u...@bios/My Documents /laptop or similar. Regards Andrew ___ 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: /etc/fstab + embedded spaces
On Tue, 03 Nov 2009 12:13:24 -0500 Michael Powell nightre...@hotmail.com replied: carmel_ny wrote: I was attempting to create this entry in the /etc/fstab file. It is to a WinXP machine. //u...@bios/My Documents /laptop smbfs rw,noauto 0 0 It fails because 'fstab' does not allow embedded spaces in device names, not does it allow enclosing the name in quotes. I did some Googling and discovered that I am not the only one annoyed by this behavior. I discovered this patch that had been submitted awhile ago. http://lists.freebsd.org/pipermail/freebsd-bugs/2007-October/026469.html Changing the share name is not really an option. Is there some way of making this work in 'fstab'? I can use the name including spaces in 'mount_smbfs' so that is how I am currently mounting the share. It just seems strange that 'fstab' by not accepting the use of quoting is not in step with how FreeBSD usually operates. Don't know if this works for fstab, but the normal way to escape spaces is with a \, like this: //u...@bios/My\ Documents /laptop smbfs rw,noauto 0 0 May not work in fstab but you can try it and see. Thanks for the suggestion. Unfortunately, it doesn't work either. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | The most winning woman I ever knew was hanged for poisoning three little children for their insurance money. Sherlock Holmes ___ 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: /etc/fstab + embedded spaces
On Tue 2009-11-03 14:07:37 UTC-0600, Adam Vande More (amvandem...@gmail.com) wrote: windows path's have alternate eg c:\Test~1 Yes, files and paths may all have an MS-DOS 8.3 equivalent (I think this option can be disabled in NTFS), however Windows SMB shares do not. \\host\My Documents is valid, but not \\host\MYDOCU~1. ___ 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: /etc/fstab + embedded spaces
On Tue, Nov 3, 2009 at 2:20 PM, andrew clarke m...@ozzmosis.com wrote: On Tue 2009-11-03 14:07:37 UTC-0600, Adam Vande More ( amvandem...@gmail.com) wrote: windows path's have alternate eg c:\Test~1 Yes, files and paths may all have an MS-DOS 8.3 equivalent (I think this option can be disabled in NTFS), however Windows SMB shares do not. \\host\My Documents is valid, but not \\host\MYDOCU~1. google also say use \040 in place of space -- Adam Vande More ___ 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: /etc/fstab + embedded spaces
On Tue, Nov 3, 2009 at 2:02 PM, andrew clarke m...@ozzmosis.com wrote: On Tue 2009-11-03 06:57:12 UTC-0500, carmel_ny (carmel...@hotmail.com) wrote: I was attempting to create this entry in the /etc/fstab file. It is to a WinXP machine. //u...@bios/My Documents /laptop smbfs rw,noauto 0 0 It fails because 'fstab' does not allow embedded spaces in device names, not does it allow enclosing the name in quotes. A workaround may be to run mount_smbfs from /etc/crontab (or perhaps the root user's crontab), eg. @reboot /usr/sbin/mount_smbfs -N //u...@bios/My Documents /laptop or similar. Regards Andrew ___ 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 windows path's have alternate eg c:\Test~1 -- Adam Vande More ___ 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
mount_nfs and fstab options
Hi, I have mounted an NFS share like: mount_nfs -LisT 10.10.10.199:/vol/share /mnt but I can't use -LisT on fstab because man mount_nfs states: Historic -o Options Use of these options is deprecated, they are only mentioned here for compatibility with historic versions of mount_nfs. bg Same as -b. fg Same as not specifying -b. conn Same as not specifying -c. dumbtimer Same as -d. intr Same as -i. lockd Same as not specifying -L. nfsv2 Same as -2. nfsv3 Same as -3. rdirplus Same as -l. mntudp Same as -U. resvport Same as -P. soft Same as -s. hard Same as not specifying -s. tcpSame as -T. Thus since I can't give this in -o section at fstab how can I use -List at fstab .. I have used rw,lockd,intr,soft,tcp but that didn't work: 10.10.10.199:/vol/share/mnt nfsrw,lockd,intr,soft,tcp 0 0 Regards. ___ 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: mount_nfs and fstab options
On Tuesday 12 May 2009 14:33:00 Martin Badie wrote: Hi, I have mounted an NFS share like: mount_nfs -LisT 10.10.10.199:/vol/share /mnt but I can't use -LisT on fstab because man mount_nfs states: Yes you can. Just comma seperate the arguments without whitespace in the appropreate column. The only thing you cannot do in fstab(5) is use arguments containing whitespace, like mounting your music collection on My Music folder. -- Mel ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
Hi Mel, Sorry for not getting back to you earlier, I have been out of the office for some time... Does this one also have a link UP message after nfs mounting? If not, then there's your culprit: network isn't up at mountcritremote time. You should mark it 'late' in fstab The UP message came more or less at the same time. Marking it late fixed the problem, still leaving me puzzled why the NFS mounts work without problem on identical machines but not in this one. Anyhow, since it's not a critical fs, the late option works fine. Thanks. -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78) fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78 Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
On Tuesday 10 February 2009 01:34:47 Arjan van der Oest wrote: Hi Mel, Sorry for not getting back to you earlier, I have been out of the office for some time... Does this one also have a link UP message after nfs mounting? If not, then there's your culprit: network isn't up at mountcritremote time. You should mark it 'late' in fstab The UP message came more or less at the same time. Marking it late fixed the problem, still leaving me puzzled why the NFS mounts work without problem on identical machines but not in this one. Anyhow, since it's not a critical fs, the late option works fine. There's 2 scenarios for late NFS mounting: - local named: named gets started after mountcritremote, fixable with resolv.conf that has an additional nameserver or populate /etc/hosts. - slow network card and/or DHCP server causing the network card to be down or without IP address / invalid resolv.conf at mountcritremote. Not really fixable. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
Mel wrote: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. Yes, but I am not. I'm using the default kernel option which I believe is enabled with the mentioned rc.conf switch, or am I wrong here? And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Looks more like the server is not sending a success message or it got lost in transit. If this is 100% reproducable, look into compatibility issues, by scaling down the NFS version for the mount and check firewall rules on both ends. Firewall has been disabled and seems not the problem, since (even with the firewall enabled) the manual mount works fine. In case of fw problems this would be a problem too. Also what puzzles me is the fact that a new identical setup box has no problem. As I wrote earlier the only difference is that I did not select the 'enable nfs client' from the sysinstall this time. I have not used any of the mentioned flags on the second box too, so why does it work on that machine? -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78) Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution
I've done some further investigation and this is what happens: The mountcritremote script executes mount -a -t nfs and times out. If this script is aborted, the NFS export is mounted later by the mountlate script with mount -a -l, this succeeds. This is the reason that the export is mounted after sending ctrl-d, the initial mount never succeeds. From what I can see now this is neither a firewall nor a NFS-version issue, else it would not succeed in the mountlate script. I'm still puzzled why on other boxes this is not a problem, while it is at this box. -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78) fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78 -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Arjan van der Oest Sent: vrijdag 30 januari 2009 14:36 To: Mel; freebsd-questions@freebsd.org Subject: RE: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution Mel wrote: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. Yes, but I am not. I'm using the default kernel option which I believe is enabled with the mentioned rc.conf switch, or am I wrong here? And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Looks more like the server is not sending a success message or it got lost in transit. If this is 100% reproducable, look into compatibility issues, by scaling down the NFS version for the mount and check firewall rules on both ends. Firewall has been disabled and seems not the problem, since (even with the firewall enabled) the manual mount works fine. In case of fw problems this would be a problem too. Also what puzzles me is the fact that a new identical setup box has no problem. As I wrote earlier the only difference is that I did not select the 'enable nfs client' from the sysinstall this time. I have not used any of the mentioned flags on the second box too, so why does it work on that machine? -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78) Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.15/1924 - Release Date: 1/29/2009 5:57 PM Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
On Friday 30 January 2009 04:36:04 Arjan van der Oest wrote: Mel wrote: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. Yes, but I am not. I'm using the default kernel option which I believe is enabled with the mentioned rc.conf switch, or am I wrong here? Yes, but why should mount(8) check /etc/rc.conf? The relation is reverse, rc(8) should give services the right(tm) arguments. And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it Also what puzzles me is the fact that a new identical setup box has no problem. As I wrote earlier the only difference is that I did not select the 'enable nfs client' from the sysinstall this time. I have not used any of the mentioned flags on the second box too, so why does it work on that machine? Does this one also have a link UP message after nfs mounting? If not, then there's your culprit: network isn't up at mountcritremote time. You should mark it 'late' in fstab. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ 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
[7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
Hi, I’m puzzled and either I don’t understand the boot rc.d process or there is something wrong with it ☺ I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so NFS support is baked right into the kernel by default. In fsstab I have this entry: nfs server ip:/data/nfs-shares/S1018SR18 /nfs-mounts/backupsrv nfs rw00 Further, as per the handbook, I’ve set nfs_client_enable to “YES” in the rc.conf. During boottime the machine hangs on the console after stating “Mounting NFS filesystems:”. I notice that _immediately_ after that line there is a console message saying “em0: link state changed to UP”. Then the system repeats this line until eternity (well, the max I’ve been waiting has been 30 minutes), no . appears indicating the system has not yet completed the 'mount -a 't nfs' command from the mountcritremote script. [udp] nfs server ip:/data/nfs-shares/S1018SR18: RPGPROC_MNT: RPC: Timed out Hitting CTRL-C forces the machine to continue the boot process, aborting the mountcritremote script. What strikes me is that the actual NFS share has been mounted, although the boot-process seems to indicate otherwise... After doing a umount and mount –a –t nfs again the machine has no problem whatsoever. Something else that puzzles me, when I set the nfs_client_enable=”NO” line in the rc.conf, the same happens : console hangs on the mountcritremote script until I hit CTRL-C and after that the share has been mounted anyway? Shouldn’t the machine ignore nfs filesystems with this rc.conf config? I’ve removed the entry in fstab and set a line in rc.local and then the boot-process works fine without interruption. So I'm currently lost with these questions: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? - why does the system seems to hang on the mountcritremote script although there seems no valid reason for that. I can imagine the network has not been fully configured yet when executing (indicated by the link UP message right after the mouning NFS filesystems line) but why will the script not continue after a few timeouts? And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Any fingerpoints? -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78) ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution
To make it even stranger, a new fresh installed box has no problems with this configuration. The difference between these two : on the problem box I enabled NFS client during installation with sysinstall, on the working box I've just added the nfs_client_enable=YES flag manually to rc.conf. I would suspect that the sysinstall approach would do the same (as it looks like it) but now I suspect sysinstall does something else too that breaks the config. -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78) fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78 -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Arjan van der Oest Sent: donderdag 29 januari 2009 10:48 To: freebsd-questions@freebsd.org Subject: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution Hi, I’m puzzled and either I don’t understand the boot rc.d process or there is something wrong with it ☺ I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so NFS support is baked right into the kernel by default. In fsstab I have this entry: nfs server ip:/data/nfs-shares/S1018SR18 /nfs-mounts/backupsrv nfs rw00 Further, as per the handbook, I’ve set nfs_client_enable to “YES” in the rc.conf. During boottime the machine hangs on the console after stating “Mounting NFS filesystems:”. I notice that _immediately_ after that line there is a console message saying “em0: link state changed to UP”. Then the system repeats this line until eternity (well, the max I’ve been waiting has been 30 minutes), no . appears indicating the system has not yet completed the 'mount -a 't nfs' command from the mountcritremote script. [udp] nfs server ip:/data/nfs-shares/S1018SR18: RPGPROC_MNT: RPC: Timed out Hitting CTRL-C forces the machine to continue the boot process, aborting the mountcritremote script. What strikes me is that the actual NFS share has been mounted, although the boot-process seems to indicate otherwise... After doing a umount and mount –a –t nfs again the machine has no problem whatsoever. Something else that puzzles me, when I set the nfs_client_enable=”NO” line in the rc.conf, the same happens : console hangs on the mountcritremote script until I hit CTRL-C and after that the share has been mounted anyway? Shouldn’t the machine ignore nfs filesystems with this rc.conf config? I’ve removed the entry in fstab and set a line in rc.local and then the boot-process works fine without interruption. So I'm currently lost with these questions: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? - why does the system seems to hang on the mountcritremote script although there seems no valid reason for that. I can imagine the network has not been fully configured yet when executing (indicated by the link UP message right after the mouning NFS filesystems line) but why will the script not continue after a few timeouts? And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Any fingerpoints? -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78) No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.15/1921 - Release Date: 1/28/2009 6:37 AM Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
On Thursday 29 January 2009 00:47:49 Arjan van der Oest wrote: Hi, I’m puzzled and either I don’t understand the boot rc.d process or there is something wrong with it ☺ I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so NFS support is baked right into the kernel by default. In fsstab I have this entry: nfs server ip:/data/nfs-shares/S1018SR18 /nfs-mounts/backupsrv nfs rw00 - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. - why does the system seems to hang on the mountcritremote script although there seems no valid reason for that. I can imagine the network has not been fully configured yet when executing (indicated by the link UP message right after the mouning NFS filesystems line) but why will the script not continue after a few timeouts? Because you are not aware of the following mount_nfs flags, you can put in /etc/fstab: -b If an initial attempt to contact the server fails, fork off a child to keep trying the mount in the background. Useful for fstab(5), where the file system mount is not critical to multi- user operation. -R Set the mount retry count to the specified value. The default is a retry count of zero, which means to keep retrying forever. There is a 60 second delay between each attempt. -i Make the mount interruptible, which implies that file system calls that are delayed due to an unresponsive server will fail with EINTR when a termination signal is posted for the process. -s A soft mount, which implies that file system calls will fail after retrycnt round trip timeout intervals. And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Looks more like the server is not sending a success message or it got lost in transit. If this is 100% reproducable, look into compatibility issues, by scaling down the NFS version for the mount and check firewall rules on both ends. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ 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
NFS fstab style
Hi, I've posted this question on a few boards but couldn't get a solid confirmation: Can someone confirm that these two lines are the same -or- if one is preferred over the other ? Code: 192.168.1.8:/temp/tmp_nfs nfs rw,-b,-i 0 0 192.168.1.8:/temp/tmp_nfs nfs rw,bg,intr 0 0 Basically: -b vs bg and -i vs intr Thank you .Anthony.. ___ 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: NFS fstab style
Can someone confirm that these two lines are the same -or- if one is preferred over the other ? Code: 192.168.1.8:/temp/tmp_nfs nfs rw,-b,-i 0 0 192.168.1.8:/temp/tmp_nfs nfs rw,bg,intr 0 0 I've never seen the style of line 1 before, no idea whether it would work or not. ___ 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
mount_nfs from fstab with -L option?
Dear mailing list, What would be the correct way to do the following: mount_nfs -L server:/path mnt when using the /etc/fstab file? Greetings from Sweden /Roger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_nfs from fstab with -L option?
Roger Olofsson wrote: Dear mailing list, What would be the correct way to do the following: mount_nfs -L server:/path mnt when using the /etc/fstab file? Greetings from Sweden /Roger Any options passed to mount(8)may be added (comma separated) to the Options section in /etc/fstab. For example: # Device Mountpoint FSType Options Dump Pass# server:/path /mnt nfs rw,-L 00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_nfs from fstab with -L option?
Steve Polyack skrev: Roger Olofsson wrote: Dear mailing list, What would be the correct way to do the following: mount_nfs -L server:/path mnt when using the /etc/fstab file? Greetings from Sweden /Roger Any options passed to mount(8)may be added (comma separated) to the Options section in /etc/fstab. For example: # Device Mountpoint FSType Options Dump Pass# server:/path /mnt nfs rw,-L 00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.13/1826 - Release Date: 2008-12-03 09:34 Thank you Steve! /Roger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to pass nfs nolock option in /etc/fstab
Hello all, I have come across an issue where I attempted to mount my NFSroot FS with a nolock option in order to support a database application. In an attempt to do so, I edited my /etc/fstab as follows: 192.168.17.1:/export/images/00A0D1E35B7E/freebsd7_x64 / nfs rw,nolock 0 0 When I attempt to re-mount, I get the following error: mount -a mount_nfs: -o lock: option not supported ... Upon googling folks suggested to use the -L option ... but mention that this is not possible to pass on to /etc/fstab My question: is it possible to mount an NFSroot on FreeBSD and at the SAME time pass the nolock parameter? thanks in advance...! -- best, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ReiserFS and /etc/fstab: rw or ro?
Hi all. I just installed Ubuntu on a second hard drive. (Got fed up waiting for things like VMware Player 2.) I've booted into FreeBSD 6.3-PRERELEASE and I'm looking at my /etc/fstab. Is it safe to specify rw for my ReiserFS partitions, or should I stick with ro for now? (I have Googled this, but can't find anything recent on FBSD and ReiserFS.) TiA, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ReiserFS and /etc/fstab: rw or ro?
Adam J Richardson [EMAIL PROTECTED] writes: I just installed Ubuntu on a second hard drive. (Got fed up waiting for things like VMware Player 2.) I've booted into FreeBSD 6.3-PRERELEASE and I'm looking at my /etc/fstab. Is it safe to specify rw for my ReiserFS partitions, or should I stick with ro for now? (I have Googled this, but can't find anything recent on FBSD and ReiserFS.) Try man mount_reiserfs. I'm surprised that didn't come up when you Googled, but you should have it on your system as well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
Gary Kline wrote: On Sat, Nov 17, 2007 at 02:40:18PM -0800, Garrett Cooper wrote: Even though audio CDs use the ISO-9660 standard, they aren't really mountable (depends on how you look at the problem, i.e. what OS you use, and what audio playing app you use). Specifying the /dev node or mount point (via the application / plugin preferences), without trying to mount the actual disk, will most likely yield the results you want. Cheers, -Garrett Well, live 'n' learn. Of course, then mmore you think aboutit, the CD's and DVD's are read-only. No need to mount them. One of these decades, I'll write up a long article on how-to use these disks; and how to copy them as well. It alll works; it's just more autoomated under the Ubuntu fork of Debian gary Technically that was gnome / hald doing the work for you, not Linux :). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
David J Brooks wrote: On Friday 16 November 2007 08:23:21 pm Gary Kline wrote: I've googled aroound, and can't be sure what to add in the FStype column to get my DCD/CDROM burners to work. Ubuntu installed ny 2005 burner automagically. Nothing like that for FreeBSD, so can anybody clue me in what I substitute for udf and cd9660? This is the old and current fstable: # DVD drive (top) /dev/acd0 /media/cdroms/0 udf ro,noauto 0 0 # CD-burner (bottom) /dev/acd1 /media/cdroms/1 cd9660 ro,noauto 0 0 cd9660 is what you need. for the burner at least though, you'll want to make it rw rather than ro. As far as I know it's not possible to write a CD/DVD by copying stuff to the mount. cd9660 are always read-only. CD/DVD burning always goes right through the device /dev/acd0 or the CAM interface /dev/cd0. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On Nov 16, 2007, at 10:56 PM, Yeef wrote: this is work for me freebsd 6.2-RELEASE /dev/acd0 /cdrom cd9660 ro,noauto 0 0 you should use root mount it. Or set vfs.usermount to 1, if I remember right. I can't recall what's the proper method for setting it at boot, rc.conf or loader.conf. The default is 0, which is what I have it set to, more to annoy me than security(personal server behind a buggy router/firewall). I have a dvd-rw and cd-rw in the same box, and I haven't recalled any problems with access(except from dvd speed which I'm hoping for an answer or fix for) or writing. On Nov 17, 2007 12:50 PM, Gary Kline [EMAIL PROTECTED] wrote: On Fri, Nov 16, 2007 at 10:24:30PM -0500, Chris Hill wrote: I think I have this page bookmarked; can't find it. I'll try rw and ro. Can either you or David explain why I get a popup error: Can't mount volume. [?] When I clicked on the Details, it says: mount_cd9660: /dev/acd1: Operation not permitted I click on System (upper left) - Preferences - Removable Drives and Media Prederences and select every peermissions box. Nothing. (I'm using a data disk, not audio.) Ideas? True dat. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- new city new thoughts new men please choose the freesoftware 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] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
Gary Kline schrieb: Hopefully! I bought TWO burners, tho. My acd0 is a Pioneer, the acd1 is a cheaper Lite On (IIRC). Sh... I also have a Lite-On Drive (Combo-Drive) and I never managed to burn under FreeBSD... Reading though is fine. Greez, Tino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On 2007-11-16 22:24, Chris Hill [EMAIL PROTECTED] wrote: On Fri, 16 Nov 2007, David J Brooks wrote: On Friday 16 November 2007 08:23:21 pm Gary Kline wrote: This is the old and current fstable: # DVD drive (top) /dev/acd0 /media/cdroms/0 udf ro,noauto 0 0 # CD-burner (bottom) /dev/acd1 /media/cdroms/1 cd9660 ro,noauto 0 0 cd9660 is what you need. for the burner at least though, you'll want to make it rw rather than ro. Not really. When *mounted* even DVD-RW disks are read-only. Good point! Although my CD burner burns CDs just fine with either cdrecord or burncd, even with ro in its fstab line. That's because they are not written ``through the cd9660 filesystem driver'', but through cdrecord/burncd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On 2007-11-17 02:55, Joshua Isom [EMAIL PROTECTED] wrote: On Nov 16, 2007, at 10:56 PM, Yeef wrote: this is work for me freebsd 6.2-RELEASE /dev/acd0 /cdrom cd9660 ro,noauto 0 0 you should use root mount it. Or set vfs.usermount to 1, if I remember right. I can't recall what's the proper method for setting it at boot, rc.conf or loader.conf. The default is 0, which is what I have it set to, more to annoy me than security (personal server behind a buggy router/firewall). man sysctl.conf That's the proper place to put `vfs.usermount=1'. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On Sat, Nov 17, 2007 at 08:03:25PM +0200, Giorgos Keramidas wrote: On 2007-11-17 02:55, Joshua Isom [EMAIL PROTECTED] wrote: On Nov 16, 2007, at 10:56 PM, Yeef wrote: this is work for me freebsd 6.2-RELEASE /dev/acd0 /cdrom cd9660 ro,noauto 0 0 you should use root mount it. Or set vfs.usermount to 1, if I remember right. I can't recall what's the proper method for setting it at boot, rc.conf or loader.conf. The default is 0, which is what I have it set to, more to annoy me than security (personal server behind a buggy router/firewall). man sysctl.conf That's the proper place to put `vfs.usermount=1'. Okay, I've set vfs.usermount=1, but both totem and kmplayer refuse to play my audio-CD. Using #mount alone (as root) doesn't say anything about /dev/acd0. I have tried to mount the CD :: [EMAIL PROTECTED]:/dev# mount_cd9660 /dev/acd0 /media/cdroms/0 mount_cd9660: /dev/acd0: Invalid argument and [EMAIL PROTECTED]:/dev# mount_cd9660 /media/cdroms/0 /dev/acd0 mount_cd9660: /dev/acd0: not a directory In /, media and its subdirectories are mode 777, and in /dev, acd[01] are all 0666 char devices. Any more places to mouse-click on or files/directories to chown/chmod?? Oh: FWIW: [EMAIL PROTECTED]:/dev# mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad1s1d on /var (ufs, local) /dev/ad1s1f on /usr (ufs, local, soft-updates) /dev/ad1s1e on /home (ufs, local) /dev/ad1s1g on /store (ufs, local, soft-updates) gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
Gary Kline wrote: On Sat, Nov 17, 2007 at 08:03:25PM +0200, Giorgos Keramidas wrote: On 2007-11-17 02:55, Joshua Isom [EMAIL PROTECTED] wrote: On Nov 16, 2007, at 10:56 PM, Yeef wrote: this is work for me freebsd 6.2-RELEASE /dev/acd0 /cdrom cd9660 ro,noauto 0 0 you should use root mount it. Or set vfs.usermount to 1, if I remember right. I can't recall what's the proper method for setting it at boot, rc.conf or loader.conf. The default is 0, which is what I have it set to, more to annoy me than security (personal server behind a buggy router/firewall). man sysctl.conf That's the proper place to put `vfs.usermount=1'. Okay, I've set vfs.usermount=1, but both totem and kmplayer refuse to play my audio-CD. Using #mount alone (as root) doesn't say anything about /dev/acd0. I have tried to mount the CD :: [EMAIL PROTECTED]:/dev# mount_cd9660 /dev/acd0 /media/cdroms/0 mount_cd9660: /dev/acd0: Invalid argument and [EMAIL PROTECTED]:/dev# mount_cd9660 /media/cdroms/0 /dev/acd0 mount_cd9660: /dev/acd0: not a directory In /, media and its subdirectories are mode 777, and in /dev, acd[01] are all 0666 char devices. Any more places to mouse-click on or files/directories to chown/chmod?? Oh: FWIW: [EMAIL PROTECTED]:/dev# mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad1s1d on /var (ufs, local) /dev/ad1s1f on /usr (ufs, local, soft-updates) /dev/ad1s1e on /home (ufs, local) /dev/ad1s1g on /store (ufs, local, soft-updates) gary Even though audio CDs use the ISO-9660 standard, they aren't really mountable (depends on how you look at the problem, i.e. what OS you use, and what audio playing app you use). Specifying the /dev node or mount point (via the application / plugin preferences), without trying to mount the actual disk, will most likely yield the results you want. Cheers, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
Joshua Isom wrote: On Nov 16, 2007, at 10:56 PM, Yeef wrote: this is work for me freebsd 6.2-RELEASE /dev/acd0 /cdrom cd9660 ro,noauto 0 0 you should use root mount it. Or set vfs.usermount to 1, if I remember right. I can't recall what's the proper method for setting it at boot, rc.conf or loader.conf. The default is 0, which is what I have it set to, more to annoy me than security(personal server behind a buggy router/firewall). I have a dvd-rw and cd-rw in the same box, and I haven't recalled any problems with access(except from dvd speed which I'm hoping for an answer or fix for) or writing. On Nov 17, 2007 12:50 PM, Gary Kline [EMAIL PROTECTED] wrote: On Fri, Nov 16, 2007 at 10:24:30PM -0500, Chris Hill wrote: I think I have this page bookmarked; can't find it. I'll try rw and ro. Can either you or David explain why I get a popup error: Can't mount volume. [?] When I clicked on the Details, it says: mount_cd9660: /dev/acd1: Operation not permitted I click on System (upper left) - Preferences - Removable Drives and Media Prederences and select every peermissions box. Nothing. (I'm using a data disk, not audio.) Gary, I've watched for this to go awhile before i went and jumped in, to ask my question ... it's about my cdrom drive, whic is a sony, one that's been 100% reliable for me, I used it regularly under linux with k3b to burn stuff. Now, under FreeBSD, k3b won't even recognize it as a ro or rw cd drive at all. I can coax burncd to burn bootable disks successfully with it, but after the command completes, all further accesses to the drive return device busy, and I have to reboot FreeBSD in order to even eject the cd. The only way I even knew the disk was ok was because afterwards, it tried to boot the machine from the disk image of a FreeBSD boot disk (which is what I was burning, for a different machine, an AMD64 next to it). Lucky that this machine is even binarily compatible (the Intel box is a 64 bit processor, so it boots AMD64 fine, but I didn't install it that way). Anyhow, how could I either coax k3b to recognize it, or get burncd to let the disk go after it's finished with it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On Sat, Nov 17, 2007 at 02:13:19PM -0800, Gary Kline wrote: Okay, I've set vfs.usermount=1, but both totem and kmplayer refuse to play my audio-CD. You don't mount audio CDs. They don't carry a cd9660 filesystem. Try something like this with a CD in the drive; mplayer -cdrom-device /dev/acd0 cdda://1 Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp4MQ3EwQHzG.pgp Description: PGP signature
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On 2007-11-17 14:13, Gary Kline [EMAIL PROTECTED] wrote: On Sat, Nov 17, 2007 at 08:03:25PM +0200, Giorgos Keramidas wrote: On 2007-11-17 02:55, Joshua Isom [EMAIL PROTECTED] wrote: On Nov 16, 2007, at 10:56 PM, Yeef wrote: this is work for me freebsd 6.2-RELEASE /dev/acd0 /cdrom cd9660 ro,noauto 0 0 you should use root mount it. Or set vfs.usermount to 1, if I remember right. I can't recall what's the proper method for setting it at boot, rc.conf or loader.conf. The default is 0, which is what I have it set to, more to annoy me than security (personal server behind a buggy router/firewall). man sysctl.conf That's the proper place to put `vfs.usermount=1'. Okay, I've set vfs.usermount=1, but both totem and kmplayer refuse to play my audio-CD. Using #mount alone (as root) doesn't say anything about /dev/acd0. I have tried to mount the CD :: [EMAIL PROTECTED]:/dev# mount_cd9660 /dev/acd0 /media/cdroms/0 mount_cd9660: /dev/acd0: Invalid argument You are not trying to _mount_ an audio CD-ROM, right? If you are, then please read carefully the Handbook chapter about multimedia and CD-ROM/DVD-ROM disks. It will help a lot :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On Sun, Nov 18, 2007 at 12:14:51AM +0100, Roland Smith wrote: On Sat, Nov 17, 2007 at 02:13:19PM -0800, Gary Kline wrote: Okay, I've set vfs.usermount=1, but both totem and kmplayer refuse to play my audio-CD. You don't mount audio CDs. They don't carry a cd9660 filesystem. Try something like this with a CD in the drive; mplayer -cdrom-device /dev/acd0 cdda://1 Roland Closer, perhaps, but the stderr is Plaaying cdda://1. File not found: '1' So whatever it's looking fo r with cdda:// is missing. (There are 25, 35 tracks on this CD.) gary -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On Sat, Nov 17, 2007 at 02:40:18PM -0800, Garrett Cooper wrote: Even though audio CDs use the ISO-9660 standard, they aren't really mountable (depends on how you look at the problem, i.e. what OS you use, and what audio playing app you use). Specifying the /dev node or mount point (via the application / plugin preferences), without trying to mount the actual disk, will most likely yield the results you want. Cheers, -Garrett Well, live 'n' learn. Of course, then mmore you think aboutit, the CD's and DVD's are read-only. No need to mount them. One of these decades, I'll write up a long article on how-to use these disks; and how to copy them as well. It alll works; it's just more autoomated under the Ubuntu fork of Debian gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
Gary Kline wrote: Okay, I've set vfs.usermount=1, but both totem and kmplayer refuse to play my audio-CD. Using #mount alone (as root) doesn't say anything about /dev/acd0. I have tried to mount the CD :: Just start cdcontrol and enter play. You don't need any entries in /etc/fstab to play audio CDs. Only the rights to access the device /dev/acd0 have to be set. If other applications cannot play CD-audio, you just have to configure them to use the right device. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What do I put in fstab to get my DVD/CDROM burner to work?
I've googled aroound, and can't be sure what to add in the FStype column to get my DCD/CDROM burners to work. Ubuntu installed ny 2005 burner automagically. Nothing like that for FreeBSD, so can anybody clue me in what I substitute for udf and cd9660? This is the old and current fstable: # DVD drive (top) /dev/acd0 /media/cdroms/0 udf ro,noauto 0 0 # CD-burner (bottom) /dev/acd1 /media/cdroms/1 cd9660 ro,noauto 0 0 -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do I put in fstab to get my DVD/CDROM burner to work?
On Fri, Nov 16, 2007 at 09:51:33PM -0500, Chris Hill wrote: On Fri, 16 Nov 2007, Gary Kline wrote: I've googled aroound, and can't be sure what to add in the FStype column to get my DCD/CDROM burners to work. Ubuntu installed ny 2005 burner automagically. Nothing like that for FreeBSD, so can anybody clue me in what I substitute for udf and cd9660? This is the old and current fstable: # DVD drive (top) /dev/acd0 /media/cdroms/0 udf ro,noauto 0 0 # CD-burner (bottom) /dev/acd1 /media/cdroms/1 cd9660 ro,noauto 0 0 This works for me (6.3-PRERELEASE): /dev/acd1 /dvd cd9660 ro,noauto0 0 Obviously that would be acd0 in your case. HTH. Hopefully! I bought TWO burners, tho. My acd0 is a Pioneer, the acd1 is a cheaper Lite On (IIRC). So, using your schema: would I put /dev/acd0 /dvd cd9660 /media/cdroms0 ro,noauto0 0 and /dev/acd1 /dvd cd9660 /media/cdroms1 ro,noauto0 0 or is this at least *close*! gary -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
