Re: 9-STABLE doesn't boot: can't load 'kernel'
loader.conf was empty and there's no 4k gnops, geli, anything like that. This is a 100% normal install. Although, since you mentioned 4k blocks, I did leave a gap between ada0p1 and ada0p2 to start the root partition on a 4k boundary. (It's an SSD that will almost never be written to once installed, so that might be a bit silly, but it's a habit already.) I decided to try this again without the gap, and that seems to have worked. I made it through install and partitioning and OS updating to 9-STABLE and installing new boot blocks and it seems to have worked. I even got it to work with a ZFS root. Here's the partition table I ended up with: = 34 234441581 ada0 GPT (111G) 34990 1 freebsd-boot (495k) 1024 226051072 2 freebsd-zfs (107G) 2260520968389519 3 freebsd-swap (4.0G) I'm not sure why this would make a difference, but either it does or doing it cleared out whatever else was wrong. This box will be stress tested and rebooted quite a bit in the next few days, so I will report back if it comes unglued. :) Thanks for the suggestion! ___ 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: Fwd: how access inside from outside when nat is done from inside to outside
thanks Danny, but i'm using pf to define rules and pfctl to apply them. first of all it is so important for me to understand what should exactly happen and what is the correct behavior in freebsd. i mean when i define nat from inside to outside, should outside system can access inside systems or not? (for example ping them). i am so confused what is the correct manner. any hints or comments that help to clear it for me, is really appreciated. SAM On 4/4/13, Daniel O'Callaghan da...@clari.net.au wrote: On 4/04/2013 6:41 PM, s m wrote: request packets: src:192.168.2.1 dst: 192.168.1.1 reply packets: src: 192.168.2.50 dst:192.168.2.1 This sort of thing tends to happen when the the packets are not being sent via divert socket properly. Look carefully, step by step, at your ipfw rules which send packets to natd. Also, run natd -v in a separate window instead of running it as a daemon, and it will show you the packets which go through natd, and what is done with them. regards, Danny ___ 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: ZFS mounting failed with error 2
2013/4/16 Beeblebrox zap...@berentweb.com: one thing I'm not sure about is that some people create a dataset root but that actually mounts at / (and not /root) and some just create others mount points directly on the zpool You can do this either way. A ZFS dataset is created at the same time and with the same name as the zpool. You can use the zpool-named-dataset as root without any problem. As I recall, the separate root dataset was a work-around for some old problem, so it is not necessary any longer. That said, you can place and name the zfs root dataset anywhere you want, as long as you have the 'vfs.root.mountfrom=' path set correctly. In your example, it is set correctly. Now as to why you cannot boot - from my experience, the problem is your last command: '# zpool export tank' will leave the pool in an exported state, and when the system tries to boot, it will not be able to locate the zpool because the pool is in exportland. The solution is different. After you are finished with all your settings you should # zfs umount -a (unmount all tank child datasets in /mnt) # zfs set mountpoint=/ tank # reboot Thank you so much, you made my day :-) For me I thought that export was a kind of unmounting so I should have never found if you didn't helped me on that case :p. At step 2, dataset tank should not try to re-mount its self and remain un-mounted. The older versions of ZFS did not behave this way and would immediately mount the zpool on root. If this happens, you have to hard-reset and such because the system will freeze up. If all goes well, before reboot you can also check (zfs get all tank) and make sure that canmount=on is set for tank. The best zfs guide is FreeBSD's own docs: https://wiki.freebsd.org/RootOnZFS -- Demelier David ___ 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
pwd.db/spwd.db file corupption when having unsafe system poweroff
hi everyone, i wanna know what exactly happens for freebsd files and processes, when we shutdown system via pressing hardware power key for 3 seconds? here's what has happened to me, recently: i've faced a strange problem.. on one of my bsd servers, one of my coworkers had defined and edited some system users, and then, instead of safe shutdown, he kept pressing power-button for 3 seconds!.. after next startup, we couldn't login anymore! we had to replace pwd.db and spwd.db files, via bootable-freebsd Fixit mode, and then, everything was fine! we know that we are, for sure, better to use safe shutdown, but i can't guarantee it always happens. what if sudden power off makes same problem??so i can't leave my servers in such situations.. My questins are: what has happened exactly? just in-used corrupted files ?? is there any way to prevent this situation? (instead of having a read-only FS.. i can't apply it on this server for now..). i'm sorry if my question seems dummish! i'm trying to increase my bsd knowledge, but i'm just on my way.. for sure, i appreciate any ideas or answers :) ___ 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: pwd.db/spwd.db file corupption when having unsafe system poweroff
Hi, I think if you hold down the power button for several seconds, it's the PSU you are switching off -- directly, without the operating system involved. Or else, it couldn't be the last resort when the OS hangs. As for preventing such things to happen during power outages -- use UPS; it will protect from short power failures. For longer power failures, UPS control and monitoring systems can help you, such as sysutils/nut or sysutils/upsd (also depends on UPS model). They usually have a function of initiating graceful shutdown after user-predefined time of AC failure (you calculate the time depending on how long the batteries endure the load). -Jeff - Original Message - From: Tak Tak Sent: 04/16/13 12:06 PM To: freebsd-questions@freebsd.org Subject: pwd.db/spwd.db file corupption when having unsafe system poweroff hi everyone, i wanna know what exactly happens for freebsd files and processes, when we shutdown system via pressing hardware power key for 3 seconds? here's what has happened to me, recently: i've faced a strange problem.. on one of my bsd servers, one of my coworkers had defined and edited some system users, and then, instead of safe shutdown, he kept pressing power-button for 3 seconds!.. after next startup, we couldn't login anymore! we had to replace pwd.db and spwd.db files, via bootable-freebsd Fixit mode, and then, everything was fine! we know that we are, for sure, better to use safe shutdown, but i can't guarantee it always happens. what if sudden power off makes same problem??so i can't leave my servers in such situations.. My questins are: what has happened exactly? just in-used corrupted files ?? is there any way to prevent this situation? (instead of having a read-only FS.. i can't apply it on this server for now..). i'm sorry if my question seems dummish! i'm t rying to increase my bsd knowledge, but i'm just on my way.. for sure, i appreciate any ideas or answers :) ___ 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
dvd recorder audio cd problems
Hi, Regarding audio playback via cdcontrol ... requires a seperate internal wiring (CD audio wire) to the sound card. Thanks: Using an older dvd drive, so that's probably the problem. On my linux I once had that cable to the mobo. on FreeBSD 8 you would have something like this in your kernel configuration:# ATA and ATAPI devices You seem to be using 8.* while I am on 10-current (info provided in my signature). Unfortunately there are a number of important hardware driver changes between 8-9-10. these are the only options allowed: # ATA controllers device ahci# AHCI-compatible SATA controllers device ata # Legacy ATA/SATA controllers # ATA/SCSI peripherals device scbus # SCSI bus (required for ATA/SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct ATA/SCSI access) device ses # Enclosure Services (SES and SAF-TE) #device ctl # CAM Target Layer In GENERIC, 'option ctl' is disabled because pulling in any one of the da/cd/pass etc also enables/calls ctl. For the same reason, '# atacontrol list ' = ATA_CAM option is enabled in kernel. Please use camcontrol instead. $ ll /dev/cam = crw--- 1 root operator 0x3f Apr 16 19:36 ctl So it seems, after playing around that 'acd_' is deprecated in 10. As to why /dev/cd0 does not show up in Brasero, it is probably related to my other thread on user-level permissions. Since my user cannot mount the cd0, brasero has not enabled access to it (problem valid for all GUI-based-apps unless root starts running a GUI) Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/dvd-recorder-audio-cd-problems-tp5803899p5804272.html Sent from the freebsd-questions mailing list archive at Nabble.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
FreeBSD as Samba Server and Windows as Client
Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . 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 as Samba Server and Windows as Client
On Tue, Apr 16, 2013 at 12:20 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . All I can tell you is that it is definitely possible using FreeBSD. The FreeNAS folks do exactly that as does the company I work for. I do not have the time to spend helping you get it going and I note that you do not tell us which version of Samba you are using, but it does work. Have you tried setting the permissions correctly on the directory you are sharing? Do you know if it is getting Access Denied trying to access the Share or trying to create a file. -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ 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
Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Dear FreeBSD savvies I am (still) struggling to understand how to keep my FreeBSD system up to date (world/system, not ports). I want to track RELEASE (not a development branch) and I want to receive security related updates. And I want to run a custom kernel. From what I understand I cannot use freebsd-update in this case because it will invariably either overwrite my custom kernel (if I have Components kernel in the config file) or not update the kernel sources in /usr/src/sys (when I do not have Components kernel in the config file). See [1]. This leaves me with the only possibility to use SVN to update /usr/src, right? I have a copy of the SVN sources (for the outdated RELEASE-9.0.0 but that's a different story), see below for svn info). As I understand [2] I cannot mix freebsd-update and SVN, right? So I can run svn update in /usr/src whenever I like. But what then? Do I need to rebuild the world and my custom kernel every time I run svn update (and there are some updates)? I'm on a low powered consumer device and it takes considerable amount of time to build the world and kernel (plus I still don't feel comfortable doing such tasks remotely). Is this really the way to do it or am I missing something? There are quite some posts, websites and threads out there (see [3] or [4] for example) about this topic but (surprisingly?) I could not (yet) find a conclusive answer. Any hints, help, tutorials or corrections would be greatly appreciated. Kind regards andreas [1] http://lists.freebsd.org/pipermail/freebsd-questions/2013-January/247763.html [2] http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250461.html [3] http://forums.freebsd.org/showthread.php?t=26140 [4] http://forums.freebsd.org/showthread.php?t=3 - # svn info Path: . Working Copy Root Path: /usr/src URL: https://svn0.us-east.freebsd.org/base/release/9.0.0 Repository Root: https://svn0.us-east.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 248546 Node Kind: directory Schedule: normal Last Changed Author: kensmith Last Changed Rev: 229307 Last Changed Date: 2012-01-02 19:59:55 +0100 (Mon, 02 Jan 2012) - Ps.: Is there a way I can contact someone (Tom Rhodes?) about the outdated freebsd-update documentation (concerning the custom kernel handling) in the Handbook (FreeBSD Update [5])? [5] http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.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: pwd.db/spwd.db file corupption when having unsafe system poweroff
On Tue, 16 Apr 2013 13:36:42 +0430, Tak Tak wrote: hi everyone, i wanna know what exactly happens for freebsd files and processes, when we shutdown system via pressing hardware power key for 3 seconds? Actually no shutdown happens in this situation. The normal programming for the power button is: press for short time: send ACPI signal to OS to perform action action: usually shutdown -p now press for 4 seconds: forced power off, no signal sent to OS equivalent: pull power plug Check the BIOS settings if this is actually the programming in your case. (This has been discussed recently on this list, check the archives to find the corresponding thread.) There are only very few occassions where you _need_ to press the power button for 4 seconds, i. e. if the OS is hanging in a totally dysfunctional state (usually massive hardware errors cause this). Whenever possible, perform a clean shutdown controlled by the OS. here's what has happened to me, recently: i've faced a strange problem.. on one of my bsd servers, one of my coworkers had defined and edited some system users, and then, instead of safe shutdown, he kept pressing power-button for 3 seconds!.. after next startup, we couldn't login anymore! we had to replace pwd.db and spwd.db files, via bootable-freebsd Fixit mode, and then, everything was fine! If the plain text files /etc/passwd and /etc/master.passwd, it could have been possible to construct the binary databases with the pwd_mkdb program (see man pwd_mkdb for details). we know that we are, for sure, better to use safe shutdown, but i can't guarantee it always happens. You should. :-) what if sudden power off makes same problem??so i can't leave my servers in such situations.. Suddenly and _unintendedly_ powering off a computer (or better: a server) should be somthing worth thinking about. It's definitely not a good idea. However, you can apply some file system tweaks to _hope_ to make the impact less severe -- for example, you can use journaling for the filesystem so it should be in a good condition. My questins are: what has happened exactly? You probably disconnected the _essential_ power during a write operation (performed by the disk). just in-used corrupted files ?? That's quite possible. is there any way to prevent this situation? (instead of having a read-only FS.. i can't apply it on this server for now..). As I said, make sure power is provided constantly. Maybe add a UPS to the mix. Use a safe shutdown, prevent accidental forced power off, maybe by disabling the power button (or putting a protector on it). If possible, use a software command (shutdown, reboot, halt). Add journaling to the file system. Make sure to perform a fsck _prior_ to going live (i. e., put the setting background_fsck=NO in /etc/rc.conf because you NEVER know). i'm sorry if my question seems dummish! No, it doesn't. It's just important that you recognize what you are actually doing, and what it implies for the OS and the tasks it performs. i'm trying to increase my bsd knowledge, but i'm just on my way.. This is to be considered basic hardware knowledge. :-) -- 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, 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: FreeBSD as Samba Server and Windows as Client
On Tue, Apr 16, 2013 at 12:34 PM, Richard Sharpe realrichardsha...@gmail.com wrote: On Tue, Apr 16, 2013 at 12:20 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . All I can tell you is that it is definitely possible using FreeBSD. The FreeNAS folks do exactly that as does the company I work for. I do not have the time to spend helping you get it going and I note that you do not tell us which version of Samba you are using, but it does work. Have you tried setting the permissions correctly on the directory you are sharing? Do you know if it is getting Access Denied trying to access the Share or trying to create a file. -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) Samba Version : FreeBSD 9.1 amd64 package . There is no fault in FreeBSD because from a Linux computer , it is possible to access the Samba service . I tried FreeNAS , but installation did not work ( It was my first install , therefore , it is very likely that I made some mistakes ) . Windows is not able to see directory contents of Samba server . When directory is not visible , it is not possible to write into it . Perhaps in the Windows XP , some settings may be wrong or missing . For that reason , I wanted to have a COMPLETE settings applied , working example. There are the following pages : http://www.samba.org/samba/docs/using_samba/toc.html Using Samba, 2nd Edition http://www.samba.org/samba/docs/using_samba/ch02.html Chapter 2. Installing Samba on a Unix System http://www.samba.org/samba/docs/using_samba/ch03.html Chapter 3. Configuring Windows Clients http://www.samba.org/samba/docs/using_samba/ch05.html Chapter 5. Unix Clients Some Linux distributions have very well designed graphical Samba configuration applications . No one of them is working in the Windows side . My opinion is that , Samba installation is correct , but Windows side has problem which I do not know how to isolate it and to correct it . Only a working complete set up may be useful , because all of the examples are partial explanatory demonstrations . 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: dvd recorder audio cd problems
On Tue, 16 Apr 2013 10:16:29 -0700 (PDT), Beeblebrox wrote: Hi, Regarding audio playback via cdcontrol ... requires a seperate internal wiring (CD audio wire) to the sound card. Thanks: Using an older dvd drive, so that's probably the problem. On my linux I once had that cable to the mobo. The ability to transmit audio via data lines has been present already with parallel ATA drives. I'm not sure how this is handled with SATA, but I assume it's done similarly because the internal CD audio connectors (and worse, the respective cables) do not seem to be common anymore. on FreeBSD 8 you would have something like this in your kernel configuration:# ATA and ATAPI devices You seem to be using 8.* while I am on 10-current (info provided in my signature). Unfortunately there are a number of important hardware driver changes between 8-9-10. This is correct. The old ATAPI infrastructure (acd, acdXtY) has been deprecated. these are the only options allowed: # ATA controllers deviceahci# AHCI-compatible SATA controllers deviceata # Legacy ATA/SATA controllers # ATA/SCSI peripherals devicescbus # SCSI bus (required for ATA/SCSI) devicech # SCSI media changers deviceda # Direct Access (disks) devicesa # Sequential Access (tape etc) devicecd # CD devicepass# Passthrough device (direct ATA/SCSI access) deviceses # Enclosure Services (SES and SAF-TE) #device ctl # CAM Target Layer In GENERIC, 'option ctl' is disabled because pulling in any one of the da/cd/pass etc also enables/calls ctl. For the same reason, '# atacontrol list ' = ATA_CAM option is enabled in kernel. Please use camcontrol instead. So this tool is also deprecated, and I assume it has taken cdcontrol and maybe even burncd with it. $ ll /dev/cam = crw--- 1 root operator 0x3f Apr 16 19:36 ctl So it seems, after playing around that 'acd_' is deprecated in 10. True, it is. As to why /dev/cd0 does not show up in Brasero, it is probably related to my other thread on user-level permissions. I highly assume this is the case, because specific permissions have to be granted. Also check if this Gnome program requires additional fiddling with DBUS or HAL (or something similarly deprecated), or with specific groups your username has to be a member of. Since my user cannot mount the cd0, brasero has not enabled access to it (problem valid for all GUI-based-apps unless root starts running a GUI) It should not be _that_ drastic. When you are logged in with your regular user account, and running X, open an X terminal and enter the command su -m, and confirm the password. Then start brasero or any other GUI program you want to check from that command line. The -m option will preserve your user's environment; see man su for details. That could be worth a try (and a partial solution). Anyway, check the permissions. What you're attempting _is_ possible. I've been able to do all this stuff as a regular user after proper configuration (on a v4, v5 and v7 system). -- 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: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
On Tue, 16 Apr 2013 21:38:16 +0200, andreas scherrer wrote:
Dear FreeBSD savvies
I am (still) struggling to understand how to keep my FreeBSD system up
to date (world/system, not ports). I want to track RELEASE (not a
development branch) and I want to receive security related updates. And
I want to run a custom kernel.
Without actually havint tested it, it seems that if you want
to use freebsd-update (binary updating), you should note this:
In /etc/freebsd-update.conf, you should have the line for what
to update as Components src world.
This should prevent overwriting of the kernel, but you need to
compile your kernel and install it. The component src will
make sure you have the proper kernel sources. I assume a custom
kernel configuration file in /usr/src/sys/{i386|amd64}/conf/
is _not_ being overwritten by freebsd-update.
Use the -r option of freebsd-update to specify the correct
release if required. It should follow -RELEASE-pN for the
currentl patchlevel N (which you intend to follow) normally.
From what I understand I cannot use freebsd-update in this case
because it will invariably either overwrite my custom kernel (if I have
Components kernel in the config file) or not update the kernel sources
in /usr/src/sys (when I do not have Components kernel in the config
file). See [1].
As far as I read from man freebsd-update.conf, the src component
will not exclude kernel sources; kernel refers to the kernel and
the modules as binary stuff.
This is the relevant text passage:
The components are ``src''
(source code), ``world'' (non-kernel binaries),
and ``kernel''; the sub-components are the indi-
vidual distribution sets generated as part of
the release process (e.g., ``src/base'',
``src/sys'', ``world/base'', ``world/catpages'',
``kernel/smp''). Note that prior to
FreeBSD 6.1, the ``kernel'' component was dis-
tributed as part of ``world/base''.
So src will include src/sys which is the kernel sources you
will need to build your custom kernel.
This leaves me with the only possibility to use SVN to update /usr/src,
right?
No, but it might be the more advanced alternative, and it should
work. Note that in _this_ case, you will also have to rebuild the
world, so kernel and world are in sync after an update. Refer to
the comment header of /usr/src/Makefile for the whole process that
has to be performed after updating (or see in the Handbook: the
section about updating by source).
I have a copy of the SVN sources (for the outdated RELEASE-9.0.0
but that's a different story), see below for svn info). As I
understand [2] I cannot mix freebsd-update and SVN, right?
It could cause trouble. Deciding for _one_ way should be better.
So I can run svn update in /usr/src whenever I like. But what then? Do
I need to rebuild the world and my custom kernel every time I run svn
update (and there are some updates)?
Yes, or better: As soon as it is required. This depends on _what_
has been part of the update. For example, kernel updates _can_
require updates of userland programs or libraries, but it's also
possible that it's not the case. To be sure, rebuild.
I'm on a low powered consumer
device and it takes considerable amount of time to build the world and
kernel (plus I still don't feel comfortable doing such tasks remotely).
In this case, use freebsd-update as explained at the beginning of
my message: Update components world and src, leave out kernel,
the rebuild the kernel by source and install it. Then reboot.
Is this really the way to do it or am I missing something?
There are _several_ ways to do it. :-)
There are quite some posts, websites and threads out there (see [3] or
[4] for example) about this topic but (surprisingly?) I could not (yet)
find a conclusive answer.
This is because the answer depends on what you actually want to do
(follow RELEASE, STABLE, CURRENT), and how you want to do it (binary,
by source).
--
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: pwd.db/spwd.db file corupption when having unsafe system poweroff
Tak Tak wrote: hi everyone, i wanna know what exactly happens for freebsd files and processes, when we shutdown system via pressing hardware power key for 3 seconds? here's what has happened to me, recently: i've faced a strange problem.. on one of my bsd servers, one of my coworkers had defined and edited some system users, and then, instead of safe shutdown, he kept pressing power-button for 3 seconds!.. after next startup, we couldn't login anymore! we had to replace pwd.db and spwd.db files, via bootable-freebsd Fixit mode, and then, everything was fine! we know that we are, for sure, better to use safe shutdown, but i can't guarantee it always happens. what if sudden power off makes same problem??so i can't leave my servers in such situations.. My questins are: what has happened exactly? just in-used corrupted files ?? is there any way to prevent this situation? (instead of having a read-only FS.. i can't apply it on this server for now..). i'm sorry if my question seems dummish! i'm trying to increase my bsd knowledge, but i'm just on my way.. for sure, i appreciate any ideas or answers :) At the risk of illustrating what I'm fuzzy on, possibly those with more in- depth skill can fill in the blanks or tidy up some with more accurate and complete details. Pressing the power button for 4 seconds as described is invoking the ACPI layer to stimulate call(s) down to the system BIOS. Whatever is set in the BIOS wrt to power control and various power-savings modes are passed through the ACPI layer. The problem with this is the acpi module in FreeBSD may, or may not, be a perfect implementation for every possible piece of hardware in existance. The piece of that which really concerns me are individual manufactuer BIOS quirks can be just enough 'off' so as to misbehave even when the FreeBSD acpi implentation is basically sound. The jist of this is (IMHO here - YMMV) is I consider it a bad procedure to turn off a server as you've described. Use the shutdown command properly instead. I would never do what your coworker did to any of my servers. Caveat being sometimes you have no other choice but to do a hard power-down. A hard power-down is done by using the switch on the power supply, and not using the ACPI/BIOS from pressing the power switch on the front. When you do have an 'uh-oh' like this, FreeBSD normally boots back into an unclean file system with corresponding whinings and complaints about how the file system(s) were not properly dismounted. Normally a background fsck ensues after 60 seconds of idle. In your case whatever files were left open and not properly closed this background fsck, had it been allowed to run and complete, would have cleaned this up. The problem starts when someone presses the power off button again, and again, before this process completes. Using the power button ACPI/BIOS only compounds this situation. I have had at one time or another, power failures that occurred almost back to back, only with a few minutes in between. So what happened was on first boot after power came back the power went down again right in the middle of this background fsck. Two more of these and my file system(s) were in pretty not-so-good shape. Luckily I was running gmirror and one of the drives was consistent. So the mirror got rebuilt from the drive with the consistent file system automagically (takes a while), then the system continued to boot, and then the background fsck finally kicked in. Gmirror saved my bacon here. Journaling is also supposed to provide similar error recovery features. I've had this happen twice on 2 different boxen. Needless to say, 2 broken UPS units were scrapped and replaced as a result. I would recommend you do NOT use the power button as you described above. Period. In any event pay particular attention to that very first boot after an 'uh-oh' power off event. Look at top and watch for the background fsck to kick off and complete, returning the machine to quiescent state BEFORE you do ANYTHING else to it. This includes pressing the button on the front. Just my $.02 - but I've had a couple of experiences like this and survived them successfully by doing things my way. -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
9.1 Postfix problem
When building postfix under 91. I am running into an odd problem. I use the INST_BASE option, which seems to cause the problem (it worked fine with 9.0). The 'make' goes fine, but the 'make install' fails when trying to install the startup script to /usr/etc/rc.d instead of /etc/rc.d. It works fine if INST-BASE is disabled. I looked through the Makefile but could not suss out how that difference in configuration was actually causing the problem. Has anyone else run into this problem and what was the fix (or did you just install into /usr/local) ? -- Paul Kraus Deputy Technical Director, LoneStarCon 3 Sound Coordinator, Schenectady Light Opera Company ___ 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 as Samba Server and Windows as Client
On 4/16/2013 2:20 PM, Mehmet Erol Sanliturk wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . Thank you very much . Mehmet Erol Sanliturk My guess is your firewall. Samba uses tcp and udp, you have to allow udp on ports 137 and 138. Turn off your firewall and try again. It's frustrated me a couple times when I've first set it up. Either that, or add `guest ok = Yes` lines to the shares. If you have a second non-windows computer available, I'd try with that. Windows makes some assumptions about what to remember, and sort of assumes the server's working properly from the beginning. Using another computer will make testing faster. ___ 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: 9.1 Postfix problem
On Tue, 16 Apr 2013 17:16:20 -0400, Paul Kraus wrote: When building postfix under 91. I am running into an odd problem. I use the INST_BASE option, which seems to cause the problem (it worked fine with 9.0). The 'make' goes fine, but the 'make install' fails when trying to install the startup script to /usr/etc/rc.d instead of /etc/rc.d. It works fine if INST-BASE is disabled. I looked through the Makefile but could not suss out how that difference in configuration was actually causing the problem. Has anyone else run into this problem and what was the fix (or did you just install into /usr/local) ? No problems at all for me with Postfix on 9.1-RELEASE, which I just install with the defaults. My postfix is in /usr/local/sbin. Why would you want to do things differently? ___ 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: 9-STABLE doesn't boot: can't load 'kernel'
On 4/16/2013 1:36 AM, J David wrote: loader.conf was empty and there's no 4k gnops, geli, anything like that. This is a 100% normal install. Although, since you mentioned 4k blocks, I did leave a gap between ada0p1 and ada0p2 to start the root partition on a 4k boundary. (It's an SSD that will almost never be written to once installed, so that might be a bit silly, but it's a habit already.) I decided to try this again without the gap, and that seems to have worked. I made it through install and partitioning and OS updating to 9-STABLE and installing new boot blocks and it seems to have worked. I even got it to work with a ZFS root. Here's the partition table I ended up with: = 34 234441581 ada0 GPT (111G) 34990 1 freebsd-boot (495k) 1024 226051072 2 freebsd-zfs (107G) 2260520968389519 3 freebsd-swap (4.0G) I'm not sure why this would make a difference, but either it does or doing it cleared out whatever else was wrong. This box will be stress tested and rebooted quite a bit in the next few days, so I will report back if it comes unglued. :) Thanks for the suggestion! I'd say file a bug report, since subtly hidden parts of the disk can be beneficial in the right circumstances. That, and it should just work. Does your drive report the blocks as 512 bytes or 4k? If you're using zfs now, run `zdb | grep ashift` and it should list 12 if it's 4k. Otherwise, you can get a performance hit if the drive's 4k native. Two of my drives are 4k native but report as 512b, so I had to trick zfs with gnop. ___ 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 as Samba Server and Windows as Client
On Tue, Apr 16, 2013 at 2:40 PM, Joshua Isom jri...@gmail.com wrote: On 4/16/2013 2:20 PM, Mehmet Erol Sanliturk wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/**pipermail/freebsd-questions/** 2013-April/250500.htmlhttp://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/**pipermail/freebsd-doc/2013-**April/021857.htmlhttp://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . Thank you very much . Mehmet Erol Sanliturk My guess is your firewall. Samba uses tcp and udp, you have to allow udp on ports 137 and 138. Turn off your firewall and try again. It's frustrated me a couple times when I've first set it up. Either that, or add `guest ok = Yes` lines to the shares. If you have a second non-windows computer available, I'd try with that. Windows makes some assumptions about what to remember, and sort of assumes the server's working properly from the beginning. Using another computer will make testing faster. In Windows , Firewall is OFF . There is no any other firewall in the network . From a Linux computer , it is possible to connect . Guest is allowed . In Windows , in its menus , during my settings , I could not see any mention of Ports . Therefore , it is necessary to know how to set such ports . It seems that , some values are not set in Windows . In documents , sometimes their writers , are not mentioning some points . These points may be not important for them but may be critical for a newly starter person . Documentation write-ups are full of such missing expertise information . 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
zdb queries give error on healthy zpools
I have 3 pools and all zdb queries for these pools or child datasets return with an error message. All 3 pools are healthy and functioning correctly. # zpool list NAMESIZE ALLOC FREECAP DEDUP HEALTH ASHIFT bsds 48.8G 16.0G 32.8G32% 1.29x ONLINE 12 mylib 266G 740M 265G 0% 1.00x ONLINE 9 tank0 49.8G 19.1G 30.7G38% 1.00x ONLINE 12 '# zdb -C' works, but that command without any poolname reads data from zpool.cache. Pool or on child dataset-specific queries (while using any of -b -d -D -C -i -h ) give this: # zdb -vvv -h bsds zdb: can't open 'bsds': Device not configured zdb: can't open 'bsds/usr': Device not configured zdb: can't open 'mylib': Invalid argument zdb: can't open 'tank0': Invalid argument I also have a faulted zpool in the list: bsdr - - - - - FAULTED - But I do not think that this faulted status will cause such zdb problems. Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/zdb-queries-give-error-on-healthy-zpools-tp5804408.html Sent from the freebsd-questions mailing list archive at Nabble.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
