FORMAT(1so)
π FORMAT(1so) β the 1-wire ID representation page, bestie β¨
Okay so the whole mission here is: choose the representation of the 1-wire unique identifiers. OWFS uses these identifiers as unique directory names, periodt. π
Although several display formats are selectable, all must be in form [literal missing in this excerpt], unlike some other programs and the labelling on iButtons, which are form [literal missing in this excerpt]. π
Display format for the 1-wire devices. Each device has a 8byte address, consisting of:
family code,1 byteID number,6 bytesCRC checksum,1 byte
Possible formats are (default, 01.A1B2C3D4E5F6), and [literal missing in this excerpt]. All formats are accepted as input, but the output will be in the specified format. No cap. β¨
The address elements can be retrieved from a device entry in owfs by the properties [literal missing in this excerpt], and as a whole with [literal missing in this excerpt]. The reversed id and address can be retrieved as [literal missing in this excerpt] and [literal missing in this excerpt]. π¦
Thatβs the tea from FORMAT(1so), bestie πβ¨ The excerpt didnβt include the source/version/date footer, so Iβm not gonna invent receipts β no cap π«Ά
π¦ where this page comes from
- alpine 3.24: owfs-doc 3.2_p4-r1 Β· GPL-2.0-only
- nixos 26.05: libow 3.2p4
- nixpkgs unstable: libow 3.2p4
- Copyright (c) 2003-2004 Paul H Alfille, MD
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms