1. Forum
  2. DOVE-Net
  3. Unix

  • Samba + kernel question

    From MIKE POWELL@CAPCITY2/CAPCITY to ALL on Sunday, October 06, 2019 10:34:00
    In order to use nfs, certain options have to be set when compiling the
    kernel (and most distros default to the nfs settings being ON). In order
    to use samba, are there any options that have to be set when the kernel was compiled, or should it work with just a generic kernel?

    Thanks!
    Mike

    ---
    ■ SLMR 2.1a ■ Goodness! That was close! I almost gave a damn.
    ---
    ■ BgNet 1.0ß12 ≈ moe's tavern * 1-502-875-8938 * moetiki.ddns.net:27
  • From Bencollver@CAPCITY2 to MIKE POWELL on Monday, October 07, 2019 10:49:45
    Re: Samba + kernel question
    By: MIKE POWELL to ALL on Sun Oct 06 2019 10:34:00

    kernel (and most distros default to the nfs settings being ON). In order
    to use samba, are there any options that have to be set when the kernel was compiled, or should it work with just a generic kernel?

    Based on my reading, samba just requires networking plus filesystem
    support for ACL, which are normally already included in a generic kernel.

    https://wiki.samba.org/index.php/File_System_Support#ext4

    One exception is when you want to use the kernel CIFS client. The
    kernel option CONFIG_CIFS is not enabled by default.

    https://wiki.samba.org/index.php/LinuxCIFS

    https://is.gd/kkz8t4

    Peace,
    Ben

    ---
    ■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Dumas Walker@CAPCITY2 to BENCOLLVER on Monday, October 07, 2019 16:44:00
    Based on my reading, samba just requires networking plus filesystem
    support for ACL, which are normally already included in a generic kernel.

    https://wiki.samba.org/index.php/File_System_Support#ext4

    One exception is when you want to use the kernel CIFS client. The
    kernel option CONFIG_CIFS is not enabled by default.

    https://wiki.samba.org/index.php/LinuxCIFS

    https://is.gd/kkz8t4

    Ben,
    Thanks. I did some reading also but was not sure what the difference
    between the using the samba client and using the CIFS client are. I will
    have to play around with it some and see what happens.

    The kernel in question is a custom kernel for a single board pc. So far, I have figured out for sure that it indeed has the kernel nfs all turned off, which is not the usual default for generic kernels these days.

    ---
    ■ SLMR 2.1a ■ DalekDOS error: (I)Obey (V)ision impaired (E)xterminate
    ■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Bencollver@CAPCITY2 to Dumas Walker on Tuesday, October 08, 2019 11:27:44
    Re: Samba + kernel question
    By: Dumas Walker to BENCOLLVER on Mon Oct 07 2019 16:44:00

    Thanks. I did some reading also but was not sure what the difference between the using the samba client and using the CIFS client are. I will have to play around with it some and see what happens.

    The samba client is in the userland. You either use it at the
    command-line, or you can use a graphical file manager that has
    built-in client code. It's comparable to FTP.

    The CIFS client is in the kernel. You mount it like you do NFS.
    The filesystem is available to all applications just like NFS.

    Best regards,
    Ben

    ---
    ■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Dumas Walker@CAPCITY2 to BENCOLLVER on Tuesday, October 08, 2019 16:55:00
    The samba client is in the userland. You either use it at the
    command-line, or you can use a graphical file manager that has
    built-in client code. It's comparable to FTP.

    The CIFS client is in the kernel. You mount it like you do NFS.
    The filesystem is available to all applications just like NFS.

    Well, rats! :) Looks like the kernel needs CIFS and I am betting it is
    not turned on.

    Thanks!

    ---
    ■ SLMR 2.1a ■ Sushi: known to the rest of the world as 'Bait'
    ■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP