Skip to content

phreaknet.sh: more openSUSE compatibility patches #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
InterLinked1 merged 8 commits into from
Jan 13, 2026
Merged

phreaknet.sh: more openSUSE compatibility patches #70

InterLinked1 merged 8 commits into from
Jan 13, 2026
+16 −3

Conversation

@htravis123
Copy link
Contributor

@htravis123 htravis123 commented Jan 13, 2026

This pull request fixes several problems that were preventing DAHDI from installing/working properly on openSUSE Leap 16.0 (though it may help for other releases of Leap, as well as Tumbleweed; it's just that Leap 16.0 is what I have on hand).

In commit order:

  1. openSUSE places kernel source code in /usr/src/linux-*, which was not checked for in the script, causing kernel header detection to fail. I added the aforementioned path to the ls command run by this portion of the script.
  2. An additional package, kernel-default-devel, is required to build kernel modules. It was added to the DAHDI pre-requisite list for zypper.
  3. The path to the kernel Makefile patched by PhreakScript when DAHDI is to be installed uses a hard-coded path of /usr/lib/linux-kbuild-major.minor. openSUSE does not use this path, instead using the source path mentioned in 1. I added a scrappy check for the default path being missing, in which case it will set it to an openSUSE path.
  4. The pre-requisite list for Zypper doesn't explicitly list Autoconf/Automake, and Libtool, which resulted in them not getting installed, causing the DAHDI build to fail very early on. I added these packages to the list.
  5. By default, in openSUSE (and SLE as well), the loading of kernel modules deemed "unsupported" (e.g. those not signed by SUSE) is disabled. Zypper users will now see a message on enabling unsupported modules after installation, if DAHDI was installed.

@htravis123
Update phreaknet.sh
104928b 
Added a check for openSUSE Leap in the package manager detector section.
@htravis123
Merge branch 'InterLinked1:master' into master
789fe51
@htravis123
install: Add kernel header detection for openSUSE
4d3182e 
openSUSE uses a different path format for kernel headers that was not checked for by install_kernel_headers(), resulting in an error. This commit adds detection for these paths.
@htravis123
install: Add missing kernel package for zypper
5386813 
In openSUSE, one of the "kernel-*-devel" packages is required to build kernel modules, otherwise PhreakScript fails to find the kernel build directory. This commit adds the "default" version (a safe assumption, given it's for the standard kernel) of this package to the list of kernel module-related packages that zypper is told to install.
@htravis123
install: Check for build directory on openSUSE
b0b21d0 
openSUSE does not place kernel build directories in /usr/lib/linux-kbuild-*. This commit adds a check for /usr/src/linux-*, where it is located, in case the first path doesn't exist.
@htravis123
install: add a missing newline to the previously-added build director…
5743757 
…y code

I forgot a newline in the "no build directory found" message, so I added one.
@htravis123
install: zypper: added autoconf
ae2273e 
Because autoconf wasn't installed, the DAHDI tools installation failed, so I added it to the list of packages.
@htravis123
install: add two more zypper packages, add message for zypper users o…
de9d257 
…n unsupported modules.

After installing libtool and automake, DAHDI finally built sucessfully, so I added them to the prereqs.
I also discovered that openSUSE disables the loading of "unsupported" (i.e. external, not signed by SUSE) kernel modules, so I added a message that displays on zypper-based systems that have installed DAHDI that tells the user how to enable loading them, otherwise DAHDI won't work.
InterLinked1
InterLinked1 requested changes Jan 13, 2026
View reviewed changes
htravis123
htravis123 commented Jan 13, 2026
View reviewed changes
Copy link
Contributor Author

@htravis123 htravis123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I placed the packages in the main prerequisite list to match the existing code. The branches for the other package managers also install the same packages regardless of whether or not DAHDI was selected to be installed, so I figured I'd do the same here.

@InterLinked1
Copy link
Owner

InterLinked1 commented Jan 13, 2026

I placed the packages in the main prerequisite list to match the existing code. The branches for the other package managers also install the same packages regardless of whether or not DAHDI was selected to be installed, so I figured I'd do the same here.

You're right, it's not consistent... hardly surprising given how organically this has grown.

I'll let it pass for now, there are some upcoming changes to Asterisk that will require autotools when building from Git now, so it's not the end of the world if they get installed.

InterLinked1
InterLinked1 approved these changes Jan 13, 2026
View reviewed changes
Copy link
Owner

@InterLinked1 InterLinked1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Installing autotools packages on all path okay for now

@InterLinked1 InterLinked1 merged commit 316d5e2 into InterLinked1:master Jan 13, 2026
29 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@InterLinked1 InterLinked1 InterLinked1 approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@htravis123 @InterLinked1