Lines Matching refs:userdata
187 Directories (keys) under `userdata` are limited to 53 character length, and
188 data in `userdata/<key>/value` are limited to 200 bytes::
192 mkdir userdata/foo
193 echo bar > userdata/foo/value
194 mkdir userdata/qux
195 echo baz > userdata/qux/value
207 Preview the userdata that will be appended with::
209 cd /sys/kernel/config/netconsole/cmdline0/userdata
210 for f in `ls userdata`; do echo $f=$(cat userdata/$f/value); done
212 If a `userdata` entry is created but no data is written to the `value` file,
217 mkdir userdata/foo
218 echo bar > userdata/foo/value
219 mkdir userdata/qux
227 Delete `userdata` entries with `rmdir`::
229 rmdir /sys/kernel/config/netconsole/cmdline0/userdata/qux
235 mkdir userdata/testing
236 printf "val1\nval2" > userdata/testing/value
237 # userdata store value is called twice, first with "val1\n" then "val2"
239 cat userdata/testing/value
244 Task name auto population in userdata
248 `taskname_enabled` under the `userdata` directory. This file is used to enable
255 echo 1 > /sys/kernel/config/netconsole/target1/userdata/taskname_enabled
258 line in the userdata field with the format `taskname=<task name>`. This allows
272 Kernel release auto population in userdata
276 located in the `userdata` directory. This file controls the kernel release
278 to userdata dictionary in every message sent.
282 echo 1 > /sys/kernel/config/netconsole/target1/userdata/release_enabled
293 However, in this case, the release information is appended to the userdata
297 CPU number auto population in userdata
301 `cpu_nr` under the `userdata` directory. This file is used to enable or disable
307 echo 1 > /sys/kernel/config/netconsole/target1/userdata/cpu_nr
310 line in the userdata field with the format `cpu=<cpu_number>`. This allows the
325 If the user has set a conflicting `cpu` key in the userdata dictionary,
330 mkdir -p /sys/kernel/config/netconsole/target1/userdata/cpu
331 echo "1" > /sys/kernel/config/netconsole/target1/userdata/cpu/value
340 Message ID auto population in userdata
344 located in the `userdata` directory. This file controls the message ID
346 given target and appends the ID to userdata dictionary in every message sent.