Thanks for the reply, Eric. I look forward to that.

Some kind of Revision Control System manipulation of the sources tree.
Preferably git.

You can do that yourself.
rsync [options] mirror local
git commit

Workman, why is it in every post I've read you have debunked the requests as opinionated, unreasonable, or out-right outlandish?

It's the users that matter. Without us Slackware wouldn't be here. Who do you think is buying those shrink wrap subscriptions Pat sales?
I have a friend that is very visually impaired. Even Knoppler's wife has vision problems.

Some features are hard to get working especially for laptops.

Same with software. Times change and so does hardware.

If anything we're trying to make Slack better than what it is.

Maybe we are trying to polish a turd. Who cares.

In all honesty, you're a jerk dood. So you've been lurking around this thread what is your wish list for Slackware 13?

Oh, for God's sakes. Robby Workman is a Slackware developer! Robby knows Slackware, and I trust and respect his opinion. He builds our software.
Grow up or go away.

Answers may vary.
Perhaps the requests were opinionated.
Perhaps the requests were unreasonable.
Perhaps the requests were out-right outlandish.

Was that a rhetorical question?

Yes, the customer is always right [1].
[1] except when the customer is wrong.


Checking for relevance... not found.

Welcome back to reality. We were wondering when you'd join us again.

If the people who are responsible for development of Slackware don't agree that the proposed changes would make it better, then you have two choices:
1) convince them (us) that they (we) are wrong
2) accept it and
a) get over it
b) use another distribution

Your opinion has been noted. Should I call a waaaaambulance for you?

How about looking at all of my posts on this forum (not just the ones in this thread) and see if you can estimate how much of my personal time I dedicate to solving problems, answering questions, and other user support here?

Most of it went into the last batch of -current changes. A few more will go into the next batch. A few more are waiting for upstream releases. Others might show up on the radar as development continues on.

There is no need here for childish name-calling.

Robby, thank your for all your hard work and dedication without which Slackware would not be what it is.

What about udev during installation? The network.sh is written for linux-2.4. Slackware has long been moved to linux-2.6, so let's have udev!

And, it does NOT need a big change. Please see:

http://www.linuxquestions.org/questi...57#post3472257

Hi,

I'm not defending anyone. First please read the LQ rules again to get a perspective in what you stated. Forums have always brought out the traits that you discuss because thankfully we all interpret things differently. Hopefully we have constructive outcomes from our discussion here on lQ.

The users are not really the issue but the users ability to utilize the desired software. If you want your hand held then my friend you have select the wrong distribution. Slackware® is still the best stable distribution with a solid user base. Sure you may not have everything you as the users feels should be supported but remember the maintainer does decide how the project goes. Even with input from the users we still have the best. BTW, if you have something that is needed due to human accessibility then have you even looked to include something or do a build for your install then providing back to the community?

So does Slackware®! Look back in time and view what has evolved in just the last two decades. Heck, I remember the days of CP/M, UNIX and even poor old DOS and I'm not going into 'Unit records' or string programming. Look where we are now. Look at the first Slackware® release then tell me you have put the hours in to assist the evolution. Look how the industry has changed, the software as you call it has really changed. The programmers of today really are great in some ways but wasteful in others. We as you tend to speak of generally then please show me were you are included by the association. What are you doing to build up Slackware®? Sounds to me like you are sitting over your freshly burnt disc with anticipation.


Again, what are you doing to buildup? Myself, I will preview a lot of times before anticipation to see how things will move in such a controversial thread as this one. I don't always participate but when I do then my thoughts are presented honestly. That does depend on the meds though.
Perspective again dood ( I think you may have meant dude). robby, will have to defend this for his self. I will say one thing though, robby does provide the true Slackware® user with a great service that I for one appreciate. So slow down and use the Preview button but be sure to read for content and understanding.

Hi,
It would be nice if you would expand as to your issues with udev'? Not by pointing to your issue with initiation within another thread, this will only cloud the issue. Please provide us with the issue(s) you are referencing.

I found nothing wrong with udev, yet it's not included in the install ramdisk. That is the problem. The old network.sh in Slakcware install initrd.img is for linux-2.4. For more recent Slackware versions, using udev instead is a better choice. I did post to explain how to use udev during installation here twice, and also mailed Pat. to explain it.

The above link (to another thread) I posted is only an example to explain the benefit of using udev (headless installation on a machine without knowing the model of its network interface card). I'm sorry if it confused you.

guanx,

I'm with you on my feelings regarding NIC probing in the installer. IMHO, it's crap, mostly because it requires constant updating to probe the latest hardware and such. udev might very well solve these problems, but it might also introduce some unwanted side-effects. It's difficult to determine ahead of time how such changes will affect other users, especially those with hardware that's radically different from yours.

Would you be kind enough to grab the latest -current, edit the installer, add udev, and shove it somewhere that I can grab and test your changes? If they look solid to me, I'll ask Pat how he feels about including them, and see what I can do to help move this along if he's willing.

FYI to others who might be reading this post, that's a good way to get your wish-list included in the next release of Slackware. You do the leg work, put out the best thing you can, then introduce it to a member of the team for vetting.

Hello Alan, I tried it with the latest -current before I posted that article yesterday. Ref. -> http://www.linuxquestions.org/questi...57#post3472257

I tested it in kvm (qemu). A few months ago I also installed Slackware this way on an AOpen MiniPC MP945 (no keyboard) and a ThinkPad T42 (it's for sale and I don't want to leave fingerprints on it). No problem.

My network is very slow. It's a 40kbps GPRS connection. Could you download the two small patches I attached to that article, and the initrd.img from http://mirror.switch.ch/ftp and try yourself? Sorry for the inconvenience :-(

Yes I could, if those patches were complete. etc.diff looks like it's missing most of rc.udev (which should be easy to pull out of the package) and some other things. The other patch looks like it's been truncated as well.

Only the lines starting with + or - are really applied. The lines starting with a space are for context (to make sure changes are made in the right places).