pdcs_auto_write(9)
π pdcs_auto_write(9) β the Kernel API Manual, but make it make sense π
okay so bestie, welcome to pdcs_auto_write(9), straight out of the Kernel API Manual β¨ this is the little corner of the kernel that handles your autoboot/search flag modifying and honestly? it's giving "small function, big responsibilities" π
β¨ NAME β¨
pdcs_auto_write β this function handles autoboot/search flag modifying π
like, that's literally the whole job. it writes the flag. it's an icon, it's a legend, it IS the moment π«Ά
πΈ SYNOPSIS πΈ
ssize_t pdcs_auto_write (struct kobject *kobj , struct kobj_attribute
*attr , const char *buf , size_t count , int knob );
so the return type is ssize_t (yes girl, a signed size, don't question it π), and it takes five whole arguments. five! main character energy fr fr π
π¦ ARGUMENTS π¦
kobjβ thekobjectused to share data with userspace. this is the little bridge between kernel-land and the userspace girlies, and we respect her for it πattrβ the kobject attributes. the vibes and metadata of the situation, basically πbufβ the input buffer to read from. this is where the actual data hangs out π₯countβ the number of bytes to be read. she's keeping track so nobody reads past the end, we love a boundaries queen β¨knobβ thePF_AUTOBOOTorPF_AUTOSEARCHflag. so it's one of those two, no cap, those are the options π (note the capital letters, they're literal names of flags, copy them exactly bestie)
π§ DESCRIPTION π§
okay so here's the tea β we will call this function to change the current autoboot flag. that's the whole errand. that's the assignment. and she ate π₯
and listen β the kernel is not flexible about this one. we expect a precise syntax:
that's it. that's the end of the paragraph. the page literally says "We expect a precise syntax:" and then... nothing π no syntax shown, no example, no nothing. iconic of her honestly π if you need the exact format, go read the source, because this manpage is leaving us on read π
π SEE ALSO π
the whole friend group, in one very long group chat π¬ plus a very specific kernel file:
Kernel file ./drivers/parisc/pdc_stable.c
pdcspath_fetch(9)pdcspath_store(9)pdcspath_hwpath_read(9)pdcspath_hwpath_write(9)pdcspath_layer_read(9)pdcspath_layer_write(9)pdcspath_attr_show(9)pdcspath_attr_store(9)pdcs_size_read(9)pdcs_auto_read(9)pdcs_autoboot_read(9)pdcs_autosearch_read(9)pdcs_timer_read(9)pdcs_osid_read(9)pdcs_osdep1_read(9)pdcs_diagnostic_read(9)pdcs_fastsize_read(9)pdcs_osdep2_read(9)pdcs_autoboot_write(9)pdcs_autosearch_write(9)pdcs_osdep1_write(9)pdcs_osdep2_write(9)pdcs_register_pathentries(9)pdcs_unregister_pathentries(9)
like, that's twenty-four references, we are THOROUGH π
quick vibe check reminder: this page is from ./drivers/parisc in the kernel tree π§ go look at the real source before you go poking at autoboot flags, iykyk π
and that's the page bestie!! π«Ά this little writeup lives in ./drivers/parisc and it's dated October 2026 β so mark your calendars, she's from the future βπ slay, periodt, go read pdcs_auto_read(9) next for the matching read side π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms