How We Made Shift 0.6 Gnome


Recommended Posts

Alright, it was asked for, so here it is. Shift was split in half for developing 0.6, so I was doing Gnome, and CrimsonRedMk was doing KDE and Lite (thanks, by the way :p). I'll tell you how I got Shift 0.6 Gnome made.

Get an awesome customizing program

For most of the time I was making Shift, I was inside a program called Reconstructor, even though most of the work was done via the command line. What's good about Reconstructor is that it takes a Ubuntu or Ubuntu-compatible ISO, and splits it into 3 parts: remaster (which is the actual bootable CD), root (the root of the filesystem, this is a full version of Ubuntu or Shift that will eventually end up on someone's system), and intrid (I didn't really touch this, but it is the initial ramdisk. Don't worry about it, we'll tell you when it's useful).

So, we loaded the ISO into Reconstructor, and we were greeted with a plethora of options. What did we do now?

Remove the stuff no one wants, add the stuff everyone wants

Our next step was to add and remove some packages. The best way to do that is by using the command line and apt-get. Another useful thing about reconstructor is that there is a little terminal icon at the bottom left of the window, which gives you command line access to a working Shift system. If you type in apt-get install packagename, packagename will be installed into the system, and added to the menus (if necessary).

It's the same for apt-get remove, except in reverse (things get taken out of menus, the apps get removed, etc.).

Another thing we did was an apt-get dist-upgrade. This will upgrade the entire system to the latest stable packages, but if there are instabilities with the system, this is probably the root of the problem. We looked at it from the perspective that this is not a stable distro yet, and we have time to fix the bugs, so we might as well be shipping everything up to date.

And finally, what are we supposed to do with all of those extra package files that were just downloaded? They've been installed, and we don't really have much use for them anymore, so we run an apt-get clean. If you have a 900MB ISO at one point, as I can tell you I did, it's because you forgot that single command :p .

Get everything branded

So, you've got a system that's working pretty well now, but it's not branded! How dare Ubuntu (or Shift) take your work and put their branding all over it? We'll just have to fight back.

But truth be told, branding can be a pain. Reconstructor helps, but you actually have to replace everything with a Ubuntu logo or name on it with the name of your distro, because of the trademark, and sometimes files hide in places they shouldn't. Shift is also a registered trademark, and thus if you are basing your distribution off of it, you need to have your own distribution name (unless you're working on Shift and not a derivative).

So, to get the easy stuff out of the way. There is a tab at the top of Reconstructor called Gnome, which is where you can add a theme, wallpaper, icon set, and set the default configuration for such things. There, easy part done. But there's still pesky little Ubuntu icons everywhere!

Go through /usr/icons/, and replace every single Ubutnu- or Shift-related icon with an icon for your distro. Yeah, it's a pain, I know. There's also some in /usr/pixmaps/ that you should replace, like the icon for Ubiquity (the Ubuntu/Shift installer). And when you're done, delete the icon cache and run a gtk-update-icon-cache on every icon set you've modified, (if you've added an icon set, run a gtk-update-icon-cache on that, too). This will change that little, stupid, irritating icon at the top left of your screen, next to the Applications menu. I spent 5 hours straight trying to change that from Ubuntu to Shift, at one point getting mad at the Ubuntu developers themselves in their IRC room (sorry guys! :p).

Useful tip: in your own terminal (not the terminal of the distro you're developing), run a sudo nautilus. The root, remaster, and intrid folders have big fancy permissions on them, but using that command, you can drag files in and out of the ISO using a nice file navigator. You need to be root (or elevated permissions a la sudo) to change things within those folders.

Config files

This is more of a pasteboard for me. When I find a config file, I honestly don't want to come in and explain it to everyone, but I want to remember where it is, and might as well share :p . So the following is useful links, commands, files, etc.

http://library.gnome.org/admin/system-admin-guide/2.20/

/usr/share/gconf/defaults -- Default gconf stuff.

gconftool-2 --dump <a directory in gconf> -- Useful for exporting things like a panel configuration

update-gconf-defaults -- writes files in /usr/share/gconf/defaults to a single, default gconf structure.

/etc/skel/ -- the default home folder for a user.

/etc/lsb-release is a text file that also needs to be changed. We recommend only changing the description, as the rest is probably still a pretty accurate description of your distro for programs that want to know.

Conclusion

You should also be clicking Apply on Reconstructor after you change anything within the interface (not from the Terminal, since that actually updates things as soon as you say "Do this"). You want to click Next after hitting Apply one last time, and name your distro, your ISO, etc. And now, you wait. And wait. And wait. And wait. And wait. And wait. And then you have an ISO sitting there for you to burn to a CD, or run ion a virtual machine. Congratulations, you just made a Linux distribution.

Thanks to the entire Shift Linux team, especially Barney, CrimsonRedMk, and Mephistopheles, and anyone who helped me out at some point in #neowin on irc.neowin.net or #ubuntu or its other channels on irc.ubuntu.com.

Edited by simon360
Link to comment
https://www.neowin.net/forum/topic/616205-how-we-made-shift-06-gnome/
Share on other sites

Cool guide! Please do post your guide to the config files when you get a chance.

I thought you went with UCK as your GUI tool. Do you think Reconstructor is better?

Well, I did most things via Nautilus and the command line. I tried UCK at one point, but it's more of a wizard than it is a tool iirc, and Reconstructor eflt better to me. Really, it's all about what the user likes more. I should have a link to UCK in there anyway...

Thanks for the guide.

Reconstructor only supports Gnome customization?

No, it also supports KDE, but I haven't worked on Shift KDE. I'm writing this purely from the perspective of a Gnome developer. You should be able to adapt most things in here to KDE.

Well, I did most things via Nautilus and the command line. I tried UCK at one point, but it's more of a wizard than it is a tool iirc, and Reconstructor eflt better to me. Really, it's all about what the user likes more. I should have a link to UCK in there anyway...

I'm actually using both Reconstructor and UCK to work on a live 'test' DVD with all the stuff (including nonfree codecs, etc) that I want. The reason for both is that UCK lets you add packages via Synaptics, so if you don't know the name of the package then it's easier (I think) to find it that way. Reconstructor is nicer in other ways I think.

The problem is that you've got to remake the ISO every time you leave one to start the other. Anyway, great guide!

  • 3 weeks later...
  • 2 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
    • Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      512
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!