-
jbki remember having to do something like that with hp-ux 10.20
-
jbkwhere it relinked the kernel or such
-
jbkinto the 00s
-
sommerfeldrichlowe: I have this vague notion that it generated one or maybe a couple *.c files that defined global variables containing config parameters -- the sort of things we set in /etc/system today.
-
jbki found it amusing that they made such a big deal about when all of that went away
-
jbkand when you could set the sysv limits and just reboot
-
jbkin 11.x
-
jbkin like 2002
-
gitomat[illumos-gate] 18197 RFC1918 addresses get site-local scope defeating RFC 6724 destination selection -- Andy Fiddaman <illumos⊙fn>
-
gitomat[illumos-gate] 18212 mdb: nv_var_alloc() error: strcpy() 'name' too large for 'v->v_lname' -- Toomas Soome <tsoome⊙mc>
-
gitomat[illumos-gate] 17173 mdb: check sign expansion -- Toomas Soome <tsoome⊙mc>
-
alancyeah, as far as I remember, all it really compiled was a list of global variables and their values into a .o to be linked with the rest, before you could set values via /etc/system
-
jbkyeah that sounds a lot like what HP-UX did (at least through 10.20 until they finally moderinized a bit)
-
jbkthough they also unhelpfully didn't document the valid values you could set
-
jbkor at least well enough.. I think it was two sysv semaphores whose product had to be < 16386 (i.e. almost certainly fit in a int16_t)
-
jbkerr two sysv ipc semphore parameters
-
jbkand if they didn't... you just crashed