Making the ViewSonic Tablet PC Run Linux

1. Open the YaST SCPM module on one desktop and the YaST Network cards configuration window on another (Figure 8).

Figure 8. Windows for YaST SCPM and Network Cards

2. Select the Add button on the SCPM screen to open the dialog for creating a new profile (Figure 9). Make the profile from the current system configuration and check the make the new configuration active box. Select the OK button.

Figure 9. Creating a New Profile

3. The Special profile settings screen should appear (Figure 10), where you can enter a name for the new profile and a short description. This screen also allows specifying pre- and post-start and stop scripts, which provide amazing flexibility when changing profiles. I was doing basic network settings changes, so these scripts are not needed.

Figure 10. Special Profile Settings

4. Going back to the YaST Network cards configuration screen, I made the changes I wanted in this profile. In this case, I disabled the RJ-45 network connection and configured the SMC wlan0 device. Select Finish on network changes to close that window. I now have the system configured the way I want the current profile to be stored, but the profile is not yet stored.

5. Now go back to the main SCPM page and Add a new profile. (It might seem like a step is missing here, but it is not.) When the new profile dialog comes up, it can be created either from the current system configuration or from another profile. If created from the current system configuration, do not make it the active profile. Select the OK button, enter a name and description for the new profile and commit the changes.

6. Back at the main SCPM window, select the newly created profile and click the Switch to... button. The changes to the network configuration made in step 4 are be seen by SCPM as modified from the current profile (not the one created in step 5), so I was asked if I wanted to save those changes to the current profile before unloading it (Figure 11). The default is to save the changes (note the X next to the network resource group), so I chose OK and the changes were saved to the current profile, the affected subsystems were stopped (networking in our case), the new profile from step 5 was made active/current and the stopped subsystems were restarted.

Figure 11. Saving the Current Profile

7. The system now has the newly created profile active. I now needed to go back to step 4 and make changes to the current profile before creating another new one and saving the current.