![]() ![]() If you are using a graphical desktop environment in your Rawhide install, you may wish to install several of them. You can disable SLUB debugging for those builds for which it is enabled by passing slub_debug=- to your kernel command line in /etc/default/grub (and re-generating your GRUB config, or just adding it directly).Īdditionally, you can run kernels in the Rawhide Kernel Nodebug repo that have all debugging disabled. See Kernel Debugging Strategy for details on exactly what debugging code is enabled for which kernel builds. Rawhide kernels are often built with varying degrees of debugging code enabled, which will result in worse performance and increased resource usage. Look for '' subjects or reports of issues.Īdditionally, if you find a problem and are not sure what to file bugs against, you can open a discussion there. Try to at least skim them before doing your daily Rawhide updates. Read and understand the Dracut troubleshooting steps.įollow the test and devel lists for Rawhide issues. This allows you to test the boot up process and packages related to it, as well as newer kernels. Reboot often (preferably whenever new kernels arrive). If you apply a week of Rawhide updates at once, you have many more packages to examine to narrow down issues. This allows you to more easily narrow down when a problem or issue appeared. You should update frequently (preferably every day). If you can’t reboot often, consider using a stable release instead.īe willing and able to report bugs to Bugzilla as you find them and help maintainers gather information to fix them. ![]() Rawhide packages stick closely to upstream projects, so interfaces and command-line options are subject to frequent changes.īe willing to reboot frequently to test new kernel versions and confirm functionality of the boot process. Have time and desire to learn new interfaces and changes. You need a good understanding of dnf and how to downgrade packages, as well as boot time troubleshooting. Rawhide gets hundreds of updates a day, and applying those updates on a regular basis allows you to more easily isolate when a bug appeared and what package(s) are responsible.īe willing and able to troubleshoot problems.įrom time to time there are problems with Rawhide packages, and you will need strong troubleshooting skills and the ability to gather information for bug reports. Thanks for that write up, I'm going to go spelunking in this repositoryĪnd come up with a plan on how to support an approach like this toĭefine editions/spins in blueprints so there's no wall in front of usįor future building of those images as well.Be willing to update on an almost daily basis. ![]() ![]() The fedora-kickstarts repo to get a feel for everything. So, there's a lot going on with the inheritance stuff. Pare that file down to just `-hplip` now, but that's still there as I I kinda disliked that pattern and I've managed to There's also a 'minimization' pattern where several kickstarts inheritįrom fedora-live-minimization.ks, which does/did some shared Īstronomy_KDE and Scientific_KDE, obviously, inherit from the KDE For e.g., the Design Suite lab isīased on Workstation, so it inherits from fedora-live-workstation.ks. Then we have things like labs/spins that are based on desktop We're not doing them twice between the lives and the disk images. So things that are 'basic' to each particular type of image are shared,īut also things that are 'basic' to each edition or spin are shared, so for Workstation, we have these chains:įedora-live-workstation.ks inherits from fedora-live-base.ks andįedora-disk-workstation.ks inherits from fedora-disk-base.ks, fedora-ĭisk-xbase.ks and fedora-workstation-common.ks Is that we share a lot of stuff between live image and disk imageĭefinitions. There is a bit of "defining base Fedora" - that's what fedora-live-īase.ks does - but there is other stuff too. Package set that was needed for the live installer that can be built by Thanks, yes I saw this when I ran ksflatten on it to come up with the We dropped reiserfs-utils from comps long ago, but the gfs2-utils The reiserfs-utils exclusion could actually be dropped as Two packages that usually get pulled in as part of the installerĮnvironment. Images but which Workstation doesn't want to include, and it excludes So it excludes three groups that are part of the 'standard' for live The current Workstation live has the package exclusions from fedora. To: Subject: Re: F39 Change Proposal: Build Fedora Workstation live ISO with Image Builder (System-Wide).Re: F39 Change Proposal: Build Fedora Workstation live ISO with Image Builder (System-Wide) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |