Skip to content

L
lxc
Switch branch/tag
  1. 11 Mar, 2020 1 commit
  3. 12 Oct, 2019 3 commits
    • Update lxc.containers.conf(5) in Japanese · 8f6d5e9c
      KATOH Yasufumi authored 
      Update for commit 767bd70aSigned-off-by: 's avatarKATOH Yasufumi <karma@jazz.email.ne.jp>
    • Merge pull request #3159 from Rachid-Koucha/patch-1 · 0065a2fd
      Stéphane Graber authored 
      Bad sgml/man translation
    • Bad sgml/man translation · 767bd70a
      Rachid Koucha authored 
      When calling "man lxc.container.conf", an internal "man" keyword is displayed :

$ man lxc.container.conf
[...]
lxc.mount.entry
              Specify a mount point corresponding to a line in the fstab format.  Moreover lxc supports mount  propagation,  such  as
              rslave  or  rprivate, and adds three additional mount options.  optional don't fail if mount does not work.  create=dir
              or create=file to create dir (or file) when the point will be mounted.  relative source path is taken to be relative to
              the mounted container root. For instance,

dev/null proc/kcore none bind,relative 0 0
              .fi     <-----------------------------------UNEXPECTED KEYWORD !!!!

The problem seems to come from the missing blanks before "dev/null proc/kcore none bind,relative 0 0"

Moreover, for homogeneity purposes, it is better to use the "programlisting" tag used in the rest of the text instead of  "screen".
Signed-off-by: 's avatarRachid Koucha <rachid.koucha@gmail.com>
  5. 11 Oct, 2019 3 commits
  7. 10 Oct, 2019 1 commit
  9. 09 Oct, 2019 3 commits
  11. 07 Oct, 2019 2 commits
  13. 04 Oct, 2019 6 commits
  15. 03 Oct, 2019 2 commits
  17. 01 Oct, 2019 1 commit
  19. 30 Sep, 2019 1 commit
  21. 27 Sep, 2019 1 commit
  23. 24 Sep, 2019 1 commit
  25. 20 Sep, 2019 2 commits
  27. 19 Sep, 2019 1 commit
  29. 18 Sep, 2019 2 commits
  31. 16 Sep, 2019 1 commit
  33. 06 Sep, 2019 1 commit
  35. 05 Sep, 2019 1 commit
    • utils: Copying source filename to avoid missing info. · a70c9e85
      Julio Faracco authored 
      Some applications use information from LOOP_GET_STATUS64. The file
associated with loop device is pointed inside structure field
`lo_file_name`. The current code is setting up a loop device without
this information. A legacy example of code checking this is cryptsetup:

    static char *_ioctl_backing_file(const char *loop)
    {
        struct loop_info64 lo64 = {0};
        int loop_fd;

        loop_fd = open(loop, O_RDONLY);
        if (loop_fd < 0)
            return NULL;

        if (ioctl(loop_fd, LOOP_GET_STATUS64, &lo64) < 0) {
            close(loop_fd);
            return NULL;
        }

        lo64.lo_file_name[LO_NAME_SIZE-2] = '*';
        lo64.lo_file_name[LO_NAME_SIZE-1] = 0;

        close(loop_fd);
        return strdup((char*)lo64.lo_file_name);
    }

It will return an empty string because lo_file_name was not set.
Signed-off-by: 's avatarJulio Faracco <jcfaracco@gmail.com>
  37. 03 Sep, 2019 1 commit
  39. 02 Sep, 2019 1 commit
  41. 29 Aug, 2019 3 commits
  43. 28 Aug, 2019 2 commits