The idea is to create a bootable medium (eg. pendrive) that allows:
- Selection of either SLES, Leap or Tumbleweed.
- Autoinstallation of the OS.
- NIS setup if workstation, unison/sync setup if laptop.
- Corporate VPN setup in the default desktop (GNOME).
- Thunderbird setup.
- IRC setup (eg. X-chat GNOME).
- Shortcuts.
- Browser bookmarks, intranet or bookmark page as home-page.
- Mumble
- VoIP
- etc
The goal is to have the employee being to work and participate from day #1. More unusual customisations can be done by the employee later (alternative WMs, mail clients, etc).
Implementation ideas:
- Create a Salt formula that can be managed as an integral opensource project and enhanced over time.
- Initial test infrastructure with terraform/vagrant so that it can be run in a VM or dry-run mode.
- Enhance YaST/AutoYaST to be able to apply the formula at boot/firstboot (a project on its own)
This project is part of:
Hack Week 15 Hack Week 16
Activity
Comments
-
over 8 years ago by joachimwerner | Reply
Duncan, would the YaST/AutoYaST approach be mandatory? I'm thinking of an image-based install (via Kiwi's OEM USB image) plus Salt as an alternative. May be a bit less flexible with detecting all the hardware, but easier to maintain. The image would only have to be minimal, because all other patterns/packages can be installed later from a Salt state.
-
-
Similar Projects
pudc - A PID 1 process that barks to the internet by mssola
Description
As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:
- The backend is written in a mixture of C and RISC-V assembly.
- The backend is actually PID1 (for real, not within a container).
- We poll and parse incoming HTTP requests ourselves.
- The frontend is a mere HTML page with htmx.
The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.
I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.
Goals
- Have a better understanding of different Linux features from user space down to the kernel internals.
- Most importantly: have fun.
Resources