tools/include/nolibc/sys/utsname.h

File Facts

System

Linux kernel

Corpus path

tools/include/nolibc/sys/utsname.h

Extension

.h

Size

756 bytes

Lines

43

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• ../nolibc.h
• ../sys.h
• linux/utsname.h

Detected Declarations

• struct utsname
• function __attribute__
• function __attribute__

Annotated Snippet

struct utsname {
	char sysname[65];
	char nodename[65];
	char release[65];
	char version[65];
	char machine[65];
	char domainname[65];
};

static __attribute__((unused))
int _sys_uname(struct utsname *buf)
{
	return __nolibc_syscall1(__NR_uname, buf);
}

static __attribute__((unused))
int uname(struct utsname *buf)
{
	return __sysret(_sys_uname(buf));
}

#endif /* _NOLIBC_SYS_UTSNAME_H */

Annotation

• Immediate include surface: `../nolibc.h`, `../sys.h`, `linux/utsname.h`.
• Detected declarations: `struct utsname`, `function __attribute__`, `function __attribute__`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.