| Summary: | net-fs/nfs-utils should check kernel config not [only] in init-script, but during installation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sergey S. Starikoff <Ikonta> |
| Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sergey S. Starikoff
2013-05-10 14:37:25 UTC
what messages are you talking about exactly ? i'm not keen on adding kernel config checks to the ebuild as i'm not convinced they're that useful. (In reply to SpanKY from comment #1) > what messages are you talking about exactly ? i'm not keen on adding kernel > config checks to the ebuild as i'm not convinced they're that useful. Bug was opened years ago, at that time I've built needed modules and got operable NFS client. The minimal solution would be to show einfo messages with remind to check kernel config. In the complete I think reasonable to see minimal USE for this package, when +minimal installing only client, when -minimal installing both client and server. In all cases first mandatory check is CONFIG_NFS_COMMON value. For client also should be checked CONFIG_NFS_FS, with echoing supported protocol versions for CONFIG_NFS_V2 and CONFIG_NFS_V3. When enabled nfsv4* USE — also for CONFIG_NFS_V4. And similiar check for server (-minimal): CONFIG_NFSD, CONFIG_NFSD_V3 and USE-dependent CONFIG_NFSD_V4 for server's available protocols. With einfo comment about other kernel-version dependent options for fine tuning NFS. (In reply to Sergey S. Starikoff from comment #2) checking/warning about uncommon options is one thing, but it's kind of unreasonable i think to say "make sure to turn on NFS if you want to use NFS". we don't do that in most other packages either. (In reply to SpanKY from comment #3) > checking/warning about uncommon options is one thing What options are common and what not? This bug is the result of my system's migration on new hardware with complete review of kernel's configuration. Finally, after I've needed to restore NFS client I was woundered discovering that NFS-support became (possibly reasonable) uncommon options. Generally I see the question: what kernel options we consider being common (skipping check) and what not? Or even the question about common Linux kernel configuration guide. |
