Changeset dfb8516
- Timestamp:
- 12/31/2022 04:23:56 PM (16 months ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc
- Children:
- 1e6c82b, d8ec0ed
- Parents:
- 06df566
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter09/usage.xml
r06df566 rdfb8516 250 250 to trigger at retry time. To find the subsystem of a device, use 251 251 <command>udevadm info --attribute-walk <device></command> where 252 <device> is an absolute path in /dev or /sys such as /dev/sr0or252 <device> is an absolute path in /dev or /sys, such as /dev/sr0, or 253 253 /sys/class/rtc.</para> 254 254 … … 284 284 set to local time. If the output from <command>hwclock</command> is not local 285 285 time, chances are it is set to UTC time. Verify this by adding or subtracting 286 the proper number of hours for thetime zone to the time shown by286 the proper number of hours for your time zone to the time shown by 287 287 <command>hwclock</command>. For example, if you are currently in the MST 288 288 time zone, which is also known as GMT -0700, add seven hours to the local
Note:
See TracChangeset
for help on using the changeset viewer.