Unsolved
This post is more than 5 years old
13 Posts
0
10866
Wyse R50 Suse Linux - Addons Not Enabled by Default?
Wyse R50 Suse Linux - Addons Not Enabled by Default?
We're currently utilizing about 150 R50 units in production, running on 11.1.052. In our Addons folder, we have 2 addons:
dhclient_hostname-1-0.sletc11sp1.rpm
xset_no_blank-1-0.sletc11sp1.rpm
What we're experiencing is, out of the box and configured for first use, the devices pull down their INI as expected, and within Novell Addon Manager inside the Linux OS, we see the Addons there. However, we're always seeing the no_blank add on not enabled. We have to manually go in, check it, execute it, and restart the terminal. On the dhclient addon, this isn't the case.
I've attached pictures of what we're seeing. Has anyone experienced this? Is it working as designed or is there something I am missing?
Thanks in advance.
epa80
13 Posts
0
May 25th, 2015 09:00
I discovered our issue. Our ini has always been set as:
NewAddons=dhclient_hostname-1-0.sletc11sp1.rpm
NewAddons=xset_no_blank-1-0.sletc11sp1.rpm
I never realized the NewAddons line had to be 1 line, with each addon separated with a comma, as seen below:
NewAddons=dhclient_hostname-1-0.sletc11sp1.rpm,xset_no_blank-1-0.sletc11sp1.rpm
Upon testing this out, it looks like it is now working like we expect. I flashed a Terminal back to out of the box, applied this change, and both addons came up enabled.