l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
October 7: Social gathering
Next Installfest:
TBD
Latest News:
Aug. 18: Discounts to "Velocity" in NY; come to tonight's "Photography" talk
Page last updated:
2003 Jun 10 04:03

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox-tech] "correct" way to enable run-time configuration of Linux?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox-tech] "correct" way to enable run-time configuration of Linux?



--S66JdqtemGhvbcZP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

There are a few methods in place for run-time configuration of Linux:

- /proc bunch of files
  (like as in /proc/sys/net/ipv4/*, writing a integer number into=20
   those files changes the value that the kernel uses at run time(

- /proc one big file
  (like /proc/ide/hda/settings, writing some magic string=20
   "breada_readahead:16" into the file changes the seeting)

- sysctl
  (a command you can run given a variable name to change from one=20
   value to the next)

There are also at least two non-runtime change methods:

- .config
  (when configuring the kernel a constant is defined which is the
   setting like CONFIG_APM_REAL_MODE_POWER_OFF)

- kernel command line
  (when the kernel boots, lilo or grub feed it the settings to use
   like ide0=3Ddma, for automatic use dma mode).


  Lately I've been running into a number of configuration changes which=20
require me to recompile or reboot the kernel to be able to take effect.
For example the number of times the kernel retries bad block reads, and
which method the kernel attempts to power off the machine.  Looking=20
at the code there is *NOTHING* that would prevent those settings from
being run-time set, internally the "value" is stored as an int, and
the compiled kernel binary is identical regardless of which way they=20
are set, just no one wrote a /proc or sysctl interface for the variable.

  I know historically /proc was a wonderful thing, at some point I think
it started to go out of favor and sysctl was good, then maybe both are
"okay"... but I stopped paying attention.  So now I'm wondering=20

- What method of kernel run-time configuration is most in favor?

--=20
GPG key: http://simons-clan.com/~msimons/gpg/msimons.asc
Fingerprint: 524D A726 77CB 62C9 4D56  8109 E10C 249F B7FA ACBE

--S66JdqtemGhvbcZP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+33RS4Qwkn7f6rL4RAibtAKCVkTfCWqgEtAyzSnlZ1orBzdGrYwCgou7G
T2GjCEX/6b5Df4QBDvOzVuI=
=JwyQ
-----END PGP SIGNATURE-----

--S66JdqtemGhvbcZP--
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech








LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.