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.
BTW: I maintain my own plasma5 packages for more then three years now, independently from AlienBobs packages. I use Plasma5 as my default DE on my desktop and on my Lenovo-ThinkPad. And in my opinion it just "works". I really would like to see a list of issues that would make Plasma5 a "showstopper" for Slackware15... and "High-memory-usage" does not really count.
I checked out the vlan branch of*git://git.rlworkman.net/slacknetsetup on a new slackware64-current installation on my laptop (wlan0 with an IP and wlan0.4 with an IP address). This seems to work, as long as the configuration of wlan0 comes before wlan0.4.
Now I want to volunteer to start IPv6 support.
I already tested what would happen if I put a static IPv6 address instead of an IPv4 address in rc.inet1.conf, and the address actually gets assigned to the network interface. I don't think this is really an option for the long term because it doesn't solve anything for people who want to have both IPv4 and IPv6 addresses on a network card. There is also some IPv4-specific logic in the handling of IPADDR[0] etc.
I would suggest 2 new config variables:
IP6ADDRS[0] and IP6CONFIGTYPE[0].
IP6ADDRS[0] can contain one or more IPv6 addresses for static IP address assignment.
IP6CONFIGTYPE[0] (comparable to USE_DHCP[0] for IPv4) can contain either "Static" or "Autoconfig". I have no experience with DHCPv6, so maybe that needs to be a third option for IP6CONFIGTYPE[0].
What do you think?
I e-mailed my SSH public key to Robby Workman, so if he approves, I will start working on this.
If anyone else has ideas or wants to give me their DHCPv6 setup, that is also greatly appreciated.
I'm also entertaining the idea of building tunnels into rc.inet1 (like for https://www.tunnelbroker.net/), do you think that would be useful?
I checked out the vlan branch of*git://git.rlworkman.net/slacknetsetup on a new slackware64-current installation on my laptop (wlan0 with an IP and wlan0.4 with an IP address). This seems to work, as long as the configuration of wlan0 comes before wlan0.4.
Now I want to volunteer to start IPv6 support.
I already tested what would happen if I put a static IPv6 address instead of an IPv4 address in rc.inet1.conf, and the address actually gets assigned to the network interface. I don't think this is really an option for the long term because it doesn't solve anything for people who want to have both IPv4 and IPv6 addresses on a network card. There is also some IPv4-specific logic in the handling of IPADDR[0] etc.
I would suggest 2 new config variables:
IP6ADDRS[0] and IP6CONFIGTYPE[0].
IP6ADDRS[0] can contain one or more IPv6 addresses for static IP address assignment.
IP6CONFIGTYPE[0] (comparable to USE_DHCP[0] for IPv4) can contain either "Static" or "Autoconfig". I have no experience with DHCPv6, so maybe that needs to be a third option for IP6CONFIGTYPE[0].
What do you think?
I e-mailed my SSH public key to Robby Workman, so if he approves, I will start working on this.
If anyone else has ideas or wants to give me their DHCPv6 setup, that is also greatly appreciated.
I'm also entertaining the idea of building tunnels into rc.inet1 (like for https://www.tunnelbroker.net/), do you think that would be useful?
On one hand, I think it's a useful addition - it's IMHO the best office suite available.
On the other hand, having it outside the main tree makes it easier to keep it updated - quite frankly, I can almost promise that you won't see routine upgrades, even within a minor -stable series, if it goes into the main Slackware tree.
On the other hand, having it outside the main tree makes it easier to keep it updated - quite frankly, I can almost promise that you won't see routine upgrades, even within a minor -stable series, if it goes into the main Slackware tree.
That's mine opinion too.
The same goes for SMplayer (which I maintain at SBo) and Geany, which were requested here.
On the other hand, having it outside the main tree makes it easier to keep it updated - quite frankly, I can almost promise that you won't see routine upgrades, even within a minor -stable series, if it goes into the main Slackware tree.
I hope that the Slackware Team is well aware that those words apply well also to a particular Desktop Environment with a life cycle of roughly a month and so big that represents roughly half of our typical Slackware distribution.
Yeah, I talk about the glorious ugly Plasma 5.
As much I love the KDE, I cannot be not aware that the today KDE and the future Plasma is just like a Cancer which parasite our beloved Slackware.
Permit me to believe that this is proper way to threat also the "KDE5", aka Plasma 5: a separate repository, even it is an official one, able to follow its one month release cycle and to not pollute the main tree.
No, I do not want Patrick Volkerding to transform in a "Plasma packager", but to stay as he done in the last 25 years: a Linux packager and maintainer.
Heck! We arrived to be the biggest distribution which ship monolithic, partially blaming our lack of dependencies resolution, but mainly thanks of that huge tumor on the face of Slackware: KDE.
Let's be honest to ourselves: there are so many things beyond KDE. That Cancer should be extirpated with no mercy.
Last edited by Darth Vader; 01-02-2018 at 05:51 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.