I am using SUSE Studio to make a custom version of openSUSE with the KDE 4 desktop. A small problem is that the background is set by default to the chameleon light bulb. I suspect I can fix this manually by adding a line to the script that runs at the end of a build. So, what is this command, if it exists?

so i used SUSEstudio to create a small distro and while i use testdrive the kernel boots up and shows the following screen: so my question is (a very silly one,sorry) how do i press yes or no,like which key,i possibly tried all combinations and even googled it,but of no avail,

How can I write an openSUSE script that will change my boot menu.lst file and add nomodeset automatically both to failsafe and normal boot option? This script is for SUSE Studio I'm going to write it under the "Run script whenever the appliance boots" for the first boot.

Does anyone know where ifconfig is for SLES made in SUSE studio? It does not exist in any of the main repositorys, or in the included repos for ZYPPER. As well it cannot be found in /sbin/zypper where it normally is for suse linux.

I have been very recently introduced to UNIX/LINUX and I am overwhelmed by the sheer power. I am a CS Graduate student and for my final year project I want to make an artificially intelligent Linux Distro. While I can achieve the AI Part, I am confused about the customizing and OS. My initial thought was to use SUSE Studio to create a custom version to suit my needs, however I have a few queries. - Say I install the SUSE in a virtual machine and customize it to it's brim and add middleware software to it. Then can I make it a distro from the installed version? - If it is not possible with SUSE what would be your suggested oS? - I would like to customize everything that is graphically visible to an user (boot screen, UI etc) and I would like to add my own software that starts up with the OS or as a background service. - I will not customize the kernel although there is a probability that I might need to tweak it.

I see that $ du -h /boot/initrd-2.6.37.6-0.5-pae 3.9M /boot/initrd-2.6.37.6-0.5-pae $ du -h /boot/vmlinuz-2.6.37.6-0.5-pae 4.1M /boot/vmlinuz-2.6.37.6-0.5-pae $ du -sh /boot 17M /boot So why does the "kernel-default" package on SUSE Studio come with 114MB?

I'm considering a number of desktop distros for use in our office. It seems like SLED matches what I want more than any other distro, especially home user focused distros. In an attempt to learn more about it, I made a SUSE Studio account and got to playing just to learn what I can. I have at least an above average amount of Linux experience. I run it on my home machines exclusively (running ArchLinux) and manage our Linux server at work just fine. My knowledge is a bit lacking in Linux server/workstation interactions, especially when it comes to SUSE (which I haven't used before). Now my goal here is threefold: 1. All workstations should be running an identical OS with identical software. This part seems easy. If I make a SUSE Studio appliance for all our machines and use that, mission accomplished. 2. I should be able to make system-level changes remotely to all our machines at once (as opposed to SSHing them one by one). I haven't played with it much but I've read that YaST is designed to do such things? 3. I want user information to be stored on our (non SUSE) server. This is where things get especially fuzzy for me. If each workstation's software is identical then in theory if the user's home folder is stored on the server, a user could log in from any machine on the network and have all their stuff right there. This also greatly simplifies the backup process since all user data is in one spot (/home on the server). I don't know if this is a bad idea or not but it seems really cool. In SUSE Studio I only saw options to manually add users so I don't know of SLED supports anything like this out of the box or not. I'd appreciate if somebody could clear up my confusions here and point me down the right path to have smooth server-workstation integration in our office.