|
|
Post by Kevin McAleavey on Nov 4, 2011 23:49:37 GMT -5
I second that. I'm way behind the curve on KNOS and just found out that backup settings doesn't include Gnome stuff. I hate icon view and don't want double click. I think I'll have to paste (with glue) a list of my prefs on the real wallpaper  We did that by design since the design intent was a uniform "enforced" setup which adminstrator types prefer for corporate rollouts along with our intent to protect anything defaulted by the system from being changed for security purposes. In our new design, we've separated that stuff from the system level now and thus will be able to allow those settings to not necessarily be locked like we've done in previous public versions. Just a bit more flexibility in the design now without risking the absolute security model. |
|
|
|
Post by Kevin McAleavey on Nov 4, 2011 23:54:26 GMT -5
"" Watch your KNOS bootup carefully ... when the bootup starts hitting the networking stuff, you'll see: ipfw2 (+ipv6) initialized, divert enabled, nat loadable, rule-based forwarding disabled, default to accept, logging disabled ipfw0: bpf attached pflog0: bpf attached pfsync0: bpf attached '' On the hard drive it was too fast to catch it, so I did a diags and used the search in gedit. It found the first one (ipfw2), but no hits on ipfw0, pflog0, or pfsync0. Do these three not show up in diags, or is Lenovo messing me up yet again? The bpf does show up in 4 places: net.bpf.zerocopy_enable: 0 net.bpf.maxinsns: 512 net.bpf.maxbufsize: 524288 net.bpf.bufsize: 4096 but not as 'bpf attached'. The ipfw stuff doesn't show up in the diagnostics since it's thoroughly preset and non-configurable. All I needed to see in the diagnostics is the ipfw2 call happened since that pulls in our prefab configuration. The only thing relevant in the diagnostics would have been some sort of failure notice associated with it but that's always worked since day one. Sad to say you're going to have to look for it to go by on the screen since that doesn't get logged to the diagnostics data. Everything else you saw were actually kernel configuration internal settings ... if you booted from a DVD, it would definitely go by slowly enough to sit there long enough to read. But if you boot again, you WILL see what I posted back there as various network device adds get added to the ipfw stuff and filtered into it. It's in there ... I promise!  |
|
|
|
Post by pharrisire on Nov 5, 2011 6:16:01 GMT -5
"" It's in there ... I promise! "" Oh, I believe you - That was never in doubt. What I do doubt is this haunted irrational psychotic schizoid knuckle-headed Lenovo laptop, And the desktop is a space-cadet too!  |
|
|
|
Post by Kevin McAleavey on Nov 6, 2011 4:42:49 GMT -5
"" It's in there ... I promise! "" Oh, I believe you - That was never in doubt. What I do doubt is this haunted irrational psychotic schizoid knuckle-headed Lenovo laptop, And the desktop is a space-cadet too! Heh. Not much we can do about that ... but I'm a little disappointed. Lenovos were what I always bought, even back when they were called IBM.  Keep that eye peeled. ipfw2 is just the loader ... you should see some ipfw0's (that's the core piece) going by with "up, enabled, etc" while it's loading the networking stuff in text ... there's a a couple of them intermixed with all the network stuff coming up, but it's there ... |
|
