SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Original Poster
Rep:
slackpkg+ and plans for future
Slackpkg+ repo has been made.
You will need to add below settings for the repo.
and do not forget to place the repo in the rest of the config
A 2 mirrors will be rsynced soon on download.dlackware.com (EU based) bart.dlackware.com (US based)
We plan to make a stable release starting with the next stable Slackware, 14.2 or 15.0 (whatever number PV gives) - x86_64 only
our gnome3 version will be mainly decided for these releases by the gtk+3 version shipped in that release. (this could change)
The current tree will follow gnome releases, so we can keep versions updated of rebuilds that should be updated in Slackware's -current tree
as systemd will replace udev, its advised to manually upgrade this package
A slackpkg installation would look like this:
First make sure to download the lastest systemd-2xx version from the repo
Code:
# please unselect systemd
slackpkg install systemd-minimal
# lets replace udev
upgradepkg --reinstall --install-new udev%systemd-2*.txz
# lets upgrade all rebuild packages
slackpkg upgrade-all
# now install the new packages
slackpkg install gnome-deps
slackpkg install gnome-systemd
make sure to checkout the settings.sh file (change it to your likes before applying)
the settings.sh file be updated to reflect the default settings (any changes for default settings can be requested)
Thanks for setting this up!
I'm only interested in testing PAM at the moment, so I have a few questions:
1) What are the minimal packages required to PAMify my slackware?
2) Is the default config set to allow traditional flat file authentication?
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Original Poster
Rep:
Quote:
Originally Posted by Slax-Dude
Hello bartgymnast,
Thanks for setting this up!
I'm only interested in testing PAM at the moment, so I have a few questions:
1) What are the minimal packages required to PAMify my slackware?
2) Is the default config set to allow traditional flat file authentication?
Slax-dude,
for purely pam, I suggest you ask ivandi.
he has a pure pam packages not build against systemd.
if not mistaken, cracklib, pam, rebuild shadow is all really needed.
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Original Poster
Rep:
Hi All,
git has been branched as current-3.14 # This will be most likely the version for next stable Slackware
git master has been updated to 3.15.90
This is the 3.16 beta
Our planning is to start with this release to build with Wayland as default backend instead of X
The branch for this testing with Wayland will be targeted for the Slackware release after next.
I have built Dlackware from a clean current install. One issue I'm running into is that I cannot login to Gnome from the GDM menu. I can do so fine when I'm using startx in the multi-user.target. The problem I have is that after entering the password, the screen goes black and it kicks me back out to the GDM screen. I even tried create a new test user with a clean environment, with the same result. Could this be PAM related? I'm looking through the log files, but nothing is sticking out so far. Any ideas?
I have built Dlackware from a clean current install. One issue I'm running into is that I cannot login to Gnome from the GDM menu. I can do so fine when I'm using startx in the multi-user.target. The problem I have is that after entering the password, the screen goes black and it kicks me back out to the GDM screen. I even tried create a new test user with a clean environment, with the same result. Could this be PAM related? I'm looking through the log files, but nothing is sticking out so far. Any ideas?
Yes, it can be Pam,we had a problem with the configuration some time ago, but wr fixedit already.
Another thing, after you selected your user you have to choose gnome wayland session. It won't work with the standard gnome session. We haven't yet found a way to set wayland to default option.
Yes, it can be Pam,we had a problem with the configuration some time ago, but wr fixedit already.
Another thing, after you selected your user you have to choose gnome wayland session. It won't work with the standard gnome session. We haven't yet found a way to set wayland to default option.
I have tried all 3 options and it's still a no-go. This is the latest git version that I used to build it.
I take that back. On my virtual machine, using wayland works fine. However, on my desktop with an nvidia card, it does not. I'm thinking that this is more of an issue with wayland and nvidia.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.