During regular L3 work I often don't find enough time to work on the command line disk partitioner parted which I maintain.
Changes often directly affect yast-storage(-ng) and libstorage(-ng). @aschnell opens bugs faster than I can solve them. Upstream is often slow and often wants patches differently.
We are at SLE15 Beta 3 submission already. So such bugs are starting to get urgent.
This project is about using Hackweek to be able to work on parted without interruptions by L3s.
Buglist SLE15:
- bsc#1058667 (cannot resize used/busy partitions) in SLE15 Beta 4
- bsc#1064446 (NVDIMM/pmem devices not supported) in SLE15 Beta 4
- bsc#1065197 (s390x BLKRRPART ioctl on FBA DASD issue) active devel
- bsc#1066467 (
parted -m $dev pdoesn't escape ':' separator) in SLE15 Beta 4 - bsc#1067435 (s390x BLKRRPART ioctl on ECKD DASD issue) YaST bug, DASD limitations
Buglist SLE11-SP4 (lower priority but much older):
- bsc#887474 (cannot create msdos disk label if gpt disk label exists) only confirmed
Rather relevant to openSUSE:
- bsc#959181 (fatresize: incorrect /dev/mmcblk* path) patch sent to upstream, submitted to Factory
- bsc#1072479 (parted: fatresize 0.1 needs an upgrade to 1.0.3) WONTFIX - too many bugs
Looking for hackers with the skills:
This project is part of:
Hack Week 16
Activity
Comments
-
almost 8 years ago by sparschauer | Reply
bsc#1064446 (NVDIMM), bsc#1066467 (Escaping ':') in Factory bsc#1058667 (resizepart) submitted to Factory bsc#1067435 (BLKRRPART ECKD DASD) became P1 but is not a parted bug -> DASD limitations, YaST bug
Similar Projects
SUSE Health Check Tools by roseswe
SUSE HC Tools Overview
A collection of tools written in Bash or Go 1.24++ to make life easier with handling of a bunch of tar.xz balls created by supportconfig.
Background: For SUSE HC we receive a bunch of supportconfig tar balls to check them for misconfiguration, areas for improvement or future changes.
Main focus on these HC are High Availability (pacemaker), SLES itself and SAP workloads, esp. around the SUSE best practices.
Goals
- Overall improvement of the tools
- Adding new collectors
- Add support for SLES16
Resources
csv2xls* example.sh go.mod listprodids.txt sumtext* trails.go README.md csv2xls.go exceltest.go go.sum m.sh* sumtext.go vercheck.py* config.ini csvfiles/ getrpm* listprodids* rpmdate.sh* sumxls* verdriver* credtest.go example.py getrpm.go listprodids.go sccfixer.sh* sumxls.go verdriver.go
docollall.sh* extracthtml.go gethostnamectl* go.sum numastat.go cpuvul* extractcluster.go firmwarebug* gethostnamectl.go m.sh* numastattest.go cpuvul.go extracthtml* firmwarebug.go go.mod numastat* xtr_cib.sh*
SUSE KVM Best Practices by roseswe
Description
SUSE Best Practices around KVM, especially for SAP workloads. Early Google presentation already made from various customer projects and SUSE sources.
Goals
Complete presentation we can reuse in SUSE Consulting projects
Resources
KVM (virt-manager) images
SUSE/SAP/KVM Best Practices
- https://documentation.suse.com/en-us/sles/15-SP6/single-html/SLES-virtualization/
- SAP Note 1522993 - "Linux: SAP on SUSE KVM - Kernel-based Virtual Machine" && 2284516 - SAP HANA virtualized on SUSE Linux Enterprise hypervisors https://me.sap.com/notes/2284516
- SUSECon24: [TUTORIAL-1253] Virtualizing SAP workloads with SUSE KVM || https://youtu.be/PTkpRVpX2PM
- SUSE Best Practices for SAP HANA on KVM - https://documentation.suse.com/sbp/sap-15/html/SBP-SLES4SAP-HANAonKVM-SLES15SP4/index.html
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