• qqq@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    2 days ago

    This is a good argument for shipping an empty config file.

    Your point stands, but this also isn’t completely unintuitive. There is pattern there: you installed samba and the config is in /etc/samba/. System level installs will almost always install their config in /etc/ and the sub directory will typically match the name somewhat.

    There is likely a general thought that if you’re going to administer a samba server, you’ll also be comfortable with conventions and man pages. Although, funnily enough, in the particular case of samba, man smb.conf doesn’t show the path lol

    • Lv_InSaNe_vL@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      That’s the thing though, when you install Samba it does create an empty config file at \etc\samba\smb.conf, or at least I’ve never created one

      • qqq@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 days ago

        I see why it does this now. Debian does

        CONFIG=/etc/samba/smb.conf
        # stuff
        ucf --three-way --debconf-ok /usr/share/samba/smb.conf "$CONFIG"
        

        in the postinit inside the .deb file to create the /etc/samba/smb.conf file. They do it this way so they don’t nuke an already created file. I take back that they should be shipping an empty file, this way is better, but it also means you’ll never be able to query it without some changes to the packaging tools.

        The man page should mention the path though that’s a bit lame.