Return to Answer

procfs allows arbitrary file_operations, sysfs is more restricted

• procfs entries receive a file_operations struct, which contains function pointers that determine what happens to every file-based system call, e.g. open, read, mmap, etc., and you can take arbitrary actions from those.

  Minimal example: proc_create() example for kernel module | Stack Overflow

• sysfs is more restricted in the following senses:

  • you implement only two methods show and store, which Linux uses to implement open, close, read, write and lseek for you. See also: How to attach file operations to sysfs attribute in platform driver? | Stack Overflow
  • tightly coupled with kobject

  Minimal example: How to create a simple sysfs class attribute in Linux kernel v3.2 | Stack Overflow

procfs allows arbitrary file_operations, sysfs is more restricted

• procfs entries receive a file_operations struct, which contains function pointers that determine what happens to every file-based system call, e.g. open, read, mmap, etc., and you can take arbitrary actions from those.

  Minimal examples:

  • How does /proc/* work? | Super User
  • proc_create() example for kernel module | Stack Overflow

• sysfs is more restricted in the following senses:

  • you implement only two methods show and store, which Linux uses to implement open, close, read, write and lseek for you. See also: How to attach file operations to sysfs attribute in platform driver? | Stack Overflow
  • tightly coupled with kobject

  Minimal example: How to create a simple sysfs class attribute in Linux kernel v3.2 | Stack Overflow

procfs allows arbitrary file_operations, sysfs is more restricted

• procfs entries receive a file_operations struct, which contains function pointers that determine what happens to every file-based system call, e.g. open, read, mmap, etc., and you can take arbitrary actions from those.

  Minimal example: https://stackoverflow.com/questions/8516021/proc-create-example-for-kernel-module/18924359#18924359

• sysfs is more restricted in the following senses:

  • you implement only two methods show and store, which Linux uses to implement open, close, read, write and lseek for you. See also: https://stackoverflow.com/questions/37237835/how-to-attach-file-operations-to-sysfs-attribute-in-platform-driver
  • tightly coupled with kobject

  Minimal example: https://stackoverflow.com/questions/16245100/how-to-create-a-simple-sysfs-class-attribute-in-linux-kernel-v3-2/45367272#45367272

procfs allows arbitrary file_operations, sysfs is more restricted

• procfs entries receive a file_operations struct, which contains function pointers that determine what happens to every file-based system call, e.g. open, read, mmap, etc., and you can take arbitrary actions from those.

  Minimal example: proc_create() example for kernel module | Stack Overflow

• sysfs is more restricted in the following senses:

  • you implement only two methods show and store, which Linux uses to implement open, close, read, write and lseek for you. See also: How to attach file operations to sysfs attribute in platform driver? | Stack Overflow
  • tightly coupled with kobject

  Minimal example: How to create a simple sysfs class attribute in Linux kernel v3.2 | Stack Overflow

procfs allows arbitrary file_operations, sysfs is more restricted

• procfs entries receive a file_operations struct, which contains function pointers that determine what happens to every file-based system call, e.g. open, read, mmap, etc., and you can take arbitrary actions from those.

  Minimal example: https://stackoverflow.com/questions/8516021/proc-create-example-for-kernel-module/18924359#18924359

• sysfs is more restricted in the following senses:

  • you implement only two methods show and store, which Linux uses to implement open, close, read, write and lseek for you
  • tightly coupled with kobject

  Minimal example: https://stackoverflow.com/questions/16245100/how-to-create-a-simple-sysfs-class-attribute-in-linux-kernel-v3-2/45367272#45367272

procfs allows arbitrary file_operations, sysfs is more restricted

• procfs entries receive a file_operations struct, which contains function pointers that determine what happens to every file-based system call, e.g. open, read, mmap, etc., and you can take arbitrary actions from those.

  Minimal example: https://stackoverflow.com/questions/8516021/proc-create-example-for-kernel-module/18924359#18924359

• sysfs is more restricted in the following senses:

  • you implement only two methods show and store, which Linux uses to implement open, close, read, write and lseek for you. See also: https://stackoverflow.com/questions/37237835/how-to-attach-file-operations-to-sysfs-attribute-in-platform-driver
  • tightly coupled with kobject

  Minimal example: https://stackoverflow.com/questions/16245100/how-to-create-a-simple-sysfs-class-attribute-in-linux-kernel-v3-2/45367272#45367272