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.
So much drama. You were disrespectful and sarcastic to our maintainer.
I am very thankful for Pat's efforts. We are lucky that Pat has a dedicated development team.
Slackware 14.2 is going to be another stellar release; I am looking forward to it.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Sounds like someone should be running current or Arch etc...All of the stable distros take 2+ years for beta then RC etc....Also, have some consideration for the major changes that Linux had thrown on it and I am sure PV is working on avoiding if possible. That will take extra time as well.
PV, never mind the haters, you just keep doing what you are doing.
Well said. While having a new, shiny release is always nice, as far as I'm concerned I would be perfectly comfortable even if the release Patrick has in mind would need, say, another year in order to be ready. I can understand that some people can feel impatient about it, but hey, let's relax and try to do what we can (even if it's not much) to support the maintainer himself and the team. I guess that even having a peaceful ambiance here at LQ/Slackware might be of some help.
Well said. While having a new, shiny release is always nice, as far as I'm concerned I would be perfectly comfortable even if the release Patrick has in mind would need, say, another year in order to be ready. I can understand that some people can feel impatient about it, but hey, let's relax and try to do what we can (even if it's not much) to support the maintainer himself and the team. I guess that even having a peaceful ambiance here at LQ/Slackware might be of some help.
Philip
What are you? A communist?
Should there be a five year plan? Like they had/have in communist economies?
That's not the way to good productivity.
Next thing, we'll be playing yoga tunes and burning incense.
A little bit of "nudging" and a little bit of stress is very good for productivity and getting people to finish their tasks.
Isn't even Debian stable on a 2 year release cycle now, last time I heard? (someone correct me if I'm wrong).
A little bit of "nudging" and a little bit of stress is very good for productivity and getting people to finish their tasks.
Until the stress causes them to burn out or have a heart attack or other stress related health issues, at which point your productivity goes right down the toilet!
I just want say, I started testing the latest in KVM last night, seeing as how its now gone beta :-). Clean install. I like to test a few applications I must have build correctly and run before I upgrade my host.
Can't wait to order the release in the Slackware store! @Volkerdi and Slackware team - Thanks for all the hard work, and dedication to a solid distribution!
What are you? A communist?
Should there be a five year plan? Like they had/have in communist economies?
That's not the way to good productivity.
Next thing, we'll be playing yoga tunes and burning incense.
A little bit of "nudging" and a little bit of stress is very good for productivity and getting people to finish their tasks.
Isn't even Debian stable on a 2 year release cycle now, last time I heard? (someone correct me if I'm wrong).
Has anyone had any success with a custom generated initrd (regardless of custom or stock kernel)?
I'm glad I kept the old initrd's that I created since they come with the old udev stuff.
However, I am having having some time delay issues with an initrd generated with the eudev stuff.
First, a message (within in the initrd) like this appears:
Code:
udevd[173]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/75-tty-description.rules:7
udevd[173]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/75-tty-description.rules:11
udevd[173]:invalid key/value pair in file /lib/udev/rules.d/95-keymap.rules on line 97, starting at character 143 ('#')
udevd[173]:hint: comments can only start at beginning of line
Then, once I'm past the initrd:
Code:
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
About a minute goes by according to the kernel time info. (58 seconds on my last reboot) before I then see:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.