Improving Slackware to a new Slackware based distro.
Dear Slackware and other Linux/GNU veterans,
I'm collecting information for a new Linux project and I need your help with this. As a starter, I'm placing a shutdown/reboot (rc.6) script here and I would like to hear from you what you're missing / added / changed in this script in your own distro and / or what you like to see in this script. Thank you for your help. -------------------------------------------------------------------------- Update 11-feb-08: -------------------------------------------------------------------------- - Code: Filled with new idea's. - People can cut and paste something useful from here. -------------------------------------------------------------------------- Code:
#! /bin/sh |
quite frankly, you are wasting your time. this kind of stuff has been done a thousand times before. naturally you are free to do whatever you fancy, but i;d propose that you divert your efforts to something more worthwile and submitting it upstream.
|
Welcome to LQ. :)
Wouldn't a pastebin is a much more appropriate place to post such a long script; & if you must post it here, please at least use "Code:" blocks. |
Welcome to the LQ Forums:-) Good luck with your project:-)
|
# clean tmp of old and stale files
echo "Cleaning temporary files" find /tmp -type f -mtime +5 -exec rm -f {} \; find /var/tmp -type f -mtime +30 -exec rm -f {} \; The above included in the shutdown script tends to keep your system cleaner Good luck with your idea |
Thank you for your help. I've placed it into the script where I think it should belong.
Quote:
|
I would like to collect everything here.. at one place. Not some good script lines scattered over the internet and spitted out lines by distro maintainers they don't want. Put the ideas together and do something with it. Remove the old. improve the new. quoted now.
Quote:
|
Thank you.. I think I need it:
Some will try to flame me. But I will not burn... Luckily there are always some people that do understand and they will reach out a hand. Quote:
|
Project died?
Move thread to graveyard? |
For some reason the whole thing from the first post, (this is my first time reading it), seems so violent. Almost like he is, (and I believe), unintentionally,(or I may be wrong), inviting a flame war.
|
Another attempt to ride on the coattails of Slackware - that's all.
If most of these "forks" were so damn good, they wouldn't have to throw around the "based on Slackware" stuff. I'll leave open the possibility that there's a rare exception to this, but as I see it, the "fork" distributions aren't truly even forks. They "re-branch" with every stable Slackware release, and one even issues point releases at various spots based on the -current development tree. Essentially, they add/remove/modify a few things, rebrand it, and pull mindshare/marketshare/users/whatever from Slackware. A parasite that is too effective kills its host, and then they both die. |
Quote:
|
Quote:
(Govt Health Warning! Not recommended for panty sniffers) |
Quote:
Most of them, as far as i have seen, just use other people's scripts (slacky.eu etc) to build the additional packages. I call that childish. Sure Pat V. says to have fun while doing it, learn, experiment. But is there really a point in releasing all those distros to public? There are around 20 Slackware clones that try to deal the same "gap". Package management (most of them using slapt-get) and having xfce instead of kde as their main desktop environment. When only 1 would suffice. Oh well... |
Quote:
In "worst case scenario" (for the entity of Slackware), say someone forked Slackware and the fork was so good that everyone switched away from Slackware. That would simply mean that Slackware is obsolete, and the fork is better. What you are assuming is that the fork = parasite and somehow it will die because of this. Nonsense I say. So far no fork has ever gained much popularity, and if it has then it's because it offers something Slackware does not, in many cases it is a port such as slamd64, slackintosh, etc. The notion of parasite is more in line with M$ / EULA / software patents mentality. You obviously do not have the right to fork Window$ ... |
Quote:
Now what I think the poster, whose posts, you are referring to meant was that they contribute little and, while they can because they have the right to, they do more harm then good. To be more clear, the impression that I got was that since they actually do very little and are for the most part 99% dependent on Slackware that a best case scenario for those types of distros are very bad for both them and Slackware. Quote:
O well, lol, my post is going no ware. Ignore my ramblings, that is all this is. I my self do not know what I am talking about. Really I was going off but I lost my thoughts. I do not think its something to worry about to say the least. I agree with this: Quote:
-----> Yet I do not see that happening any time soon. Especial if the "so called forks" are not them selves capable of being real forks and are, in fact, not a real fork, what ever all that means. Other thoughts: I must be real bored to have wrote all this none-sense ;p |
*cough* SLS *cough*
|
I don't think any of these forks pose a threat to "real" Slackware. Has Debian suffered to any extent since the birth of Ubuntu?
|
It's like improve pizza recipe, you can always add more stuff in a pizza, but be carefull or you will end with a non-well shaped, too thin crust :)
|
Quote:
http://distrowatch.com/index.php?dataspan=52 It shows hits per day and fluctuations in this. |
I can see the difference between a "parasite" and a "fork": a fork will take the original distro and do something different with it - look at the Red Hat/Mandriva/Novell distros, there are many similarities and many differences between them. you could even look to Ubuntu and Debian and see why it would not be feasible to try to feed Ubuntu type changes into the main Debian tree (mainly because you'd get a situation where the forks became pitchforks!).
A parasite is purely one that cannot live on it's own - if, tomorrow, Debian shut up shop, Ubuntu would be able to continue along. With the example that Robby made (post #11) you have a distro that cannot survive without Slackware - it doesn't do anything new apart from add in a package manager that may or may not break your system and it only updates whenever Slackware does. They probably find all the updated programs and change "slackware" to their own name whenever it is in the programs and add there own exetension. If Pat, Robby, Eric and the rest all stopped providing updates and programs the parasite would die. I think, personally, that there is enough choice out there that the forks can stop - unless you are doing something very different and can show that it can't be fed back into the real project, there's really not much point to doing a whole distro. In the case of the OP, why not just make your shutdown script public, explain what it does and let people decide for themselves whether to use it? |
Quote:
|
Not sure why such an old thread was resurrected...
Quote:
If anyone cranks out a distro of their own, regardless if it's a clone or not, they "give back". I report bugs upstream to their respective project developers all the time but yet I "ride the coattails" of DIY, Slackware, LFS and even Fedora. I've referenced GSB SVN on quite a few occasions for my Slackware Gnome 2.24.0 build. Reality check. This is how it works folks. 10:1, GSB has done the same. I've figured things out on my DIY build that I've later seen replicated verbatum in LFS.... What the real problem is, is when you have 2 very similar projects going on, there is ALOT of duplicated effort. 2 people arriving at the same conclusions and solutions on separate projects when they probably should just pool resources and work on one project. That is the only crux of a clone project. Some people need to get off their high horse and realize that this is GNU land and we all feed off each others work in one shape or another. PAT does it all time. So does Robby and so does Eric. I've seen lot's of "Fedora" esque' commands on Slackbuilds so the implied pretension isn't warranted here. If anyone has half a brain, and you find yourself in a jam, you'll be hitting Rawhide (or some other reputable source) pretty damn quick. |
Yes, there's nothing new under the sun. Everything's derived from something else.
Which distros are regarded as "forks" and which "parasites" of Slackware? |
Quote:
I won't call names here, because I'm not intending to single anyone out for good or bad, and perhaps there are some of the "forks" who do occasionally send feedback, but as a whole, they do not. Basically, it's just frustrating to know that we're doing the "heavy lifting," so to speak, with very little (if any) help from the "fork" people. I can think of quite a few things those folks could be doing which would *really* be helpful: find bugs in upstream software which affect us and work on them; find new implementations of various things that we'll have to move to later, and go ahead and try to get them working in Slackware. Actual examples of some of those should be easy to find *if* they're following upstream developments as opposed to just watching the Slackware ChangeLog. |
Yes, I agree. Anybody would feel the same frustration. And, as you said, about "illegal wrong", if something is not exactly illegal it may still be unethical.
|
Quote:
So.... Just because Slackware doesn't get bug reports from Vector, Slamd or who ever, doesn't mean they aren't helping the Slackware cause. One more distro is just one more group of people making things better for everyone. So, in that regard, I seriously doubt there is any true parasitic distro out there. On a semi-related note, I've known about a findutils/removepkg bug for atleast a year now but you guys probably haven't seen it because your still at 4.2... I could have reported it eons ago or I could continue to do the same thing I have done and let you guys hit it on your own.... I've taken the same stance on other Slackware issues I've found. Doesn't necessarily mean I, or anyone else, doesn't contribute tho. |
Still alive
No, I'm still building on my project, but rewriting codes, scripts, adding new stuff and testing takes a lot of my spare time. If I have any. That's why I need help with this if I want to release it within a year or so. And I don't need people that are crushing my distro to it's death even before it's released. That's not very motivating is it? If they are so smart, come up with something instead of complaining. Complaining is easy, working is not. Keep in mind that I'm doing this also for you... for free. Just like many other Linux developers. Without them, Linux will die.
And if you are shocked by my postings: I don't like people who can only complain and judge without any knowledge of what I'm doing. I'm just straight forward to these guys. Hate me or love me. The idea behind Linux is that everyone provides a building block. One man could never have all the knowledge or time to build the perfect distro. But on man can build a good distro with all those building blocks provided by experts on every level and his own expertise. My distro is based on Slackware just as Slackware is based on the Softlanding Linux System. The core of my Distro is totally rebuild for speed and security mostly from scratch. Only the extra programs will come directly from Slackware to save time so I can put all the effort into the core programs and thus making it Slackware comPATable if, but It can live without Pat's Slackware. Want Debian based? Done.. The only choice for Slackware is because it's clean and clear. This is not a real fork or parasite, this is called progress, development, evolution and merging the best of distro's. Why shall I re-invent the wheel? See my distro as a merge of Slackware, LFS (hardened), Engarde Linux, Hardened Linux, (Free)BSD, Zenwalk, Vector Linux, Fedora and Debian. It will fulfill the security you need today. Expect insane security where possible. Maybe it's not so user friendly to newbies and it will take some time to even get to the internet from your box. But believe me, it's worth the effort if you give a lot about your privacy and computer security. The only "problem" is, that you've to answer many (complicated) questions during install or configuration. If I can make profit from it, I'll end my current job and make this project my life. I'm open to new ideas or any reasonable suggestions. It will be a project of us all. Yes, maybe it will die young. But the last couple of years I studied the wishes of people and the state of operating systems from today and I think there is a good market for it. I even got an security solution for the so called "Cold Boot Attack" on encryption keys and passwords. I've got the solution on paper but not an easy way to implant it into my Distro because I need to rewrite and maintain parts of the kernel myself. To put this in another way: People who give a lot about privacy and security will love it. People who don't like to do some effort for it, won't. And these days my distro's encryption is not allowed anymore in the US and it's save against the UK's law to hand over your encryption key to the...... Even if tell the password, you've lost the key somewhere before and your data wlll be save to prying eyes. |
The additional spin-off or children distros exist because people find various aspects they do not like about the stock Slackware. There are several threads here at LQ addressing that issue. Various wish lists are an example of a certain level of dissatisfaction. Many people who stick with the stock Slackware modify the core installation in various ways. I have modified several rc.d scripts to my taste. I have added bash shell startup scripts. I have modified the startx script. Etc.
I have forwarded some of the mods to Pat. Whether he decides to incorporate the changes will not stop me from continuing with my modifications. The world is filled with approximately 6.5 billion people, which means 6.5 billion different opinions about how the world could spin. When a significant majority of people accept that simple fact then there will be far less conflict and violence in this world. That several spin-off distros exist is a good thing. Permutations and variety is how humans invent and innovate. Pat is free to incorporate those ideas and he is free not to. I have written a hundred or so shell scripts to fine-tune Slackware. I share many of them at my web site and here at LQ too. So have many others here at LQ. Yet I do not expect or demand Pat or anybody else to use those tweaks. I could convert those many tweaks into full-fledged packages, which users could install to their pleasure. In that respect, my effort is little different from the various children distros. I simply do not relabel my mods as a new distro. There was an allegation posted in this thread that the developers of the children distros do not contribute upstream. I would like to see actual evidence rather than allegations. First, because free software is open to everybody to study, Pat is free to adopt any idea used in the children distros. Second, I suspect the various developers of the spin-off distros occasionally discuss issues with Pat without publicizing those discussions. Third, as mentioned by jong357, often bugs are not Slackware specific but upstream in the core software. Slackware spin-off developers are not required to report those bugs to Pat. I raise my eyebrow whenever anybody uses the term parasite with respect to free software. As H_TeXMeX_H already shared, there is no such thing. If you want examples of human parasites, then look elsewhere outside of free software. The entire philosophy of statism is parasitical in nature and violent to the point of destroying this planet. Patents (software or otherwise) are examples of how statists promote this violence and destruction. The primary goal of patents and other statist supported monopolies is to stifle growth, individuality, independence, and to create indentured slaves of a majority of people. Healthy human parents encourage children to venture on their own, to explore, and to learn to think independently. Healthy parents are pleased and proud to watch children grow and develop as unique individuals. Free software encourages this same healthy approach. That the inner core Slackware developers and outer core Slackware users perform the "heavy lifting" is non-sequitur. Why should Slackers be emotionally upset if others benefit? Slackers get what they wanted. Users of spin-off distros get what they wanted. This argument is similar to how statists provoke emotional responses to justify various forms of theft under the color of law. This type of emotional response is based upon the free rider fallacy. There is always a spillover effect in every human interaction. Avoiding that effect is impossible. In any environment of free association and voluntary exchange, nobody receives less than they bargained. The spillover effect means some people get more, but nobody gets less than they bargained. The healthiest relationships are those that are reciprocating and mutually beneficial. Yes, if downstream beneficiaries offered their modifications upstream that would be more emotionally satisfying, but those downstream modifications are not required to be offered or accepted. One argument asks child distro developers to help more with the core Slackware, but a counter argument can be offered that Pat should incorporate more of the modifications created downstream. Isaac Newton often is cited for his statement Pigmaei gigantum humeris impositi plusquam ipsi gigantes vident: If I have seen a little further it is by standing on the shoulders of Giants. This statement describes the essence and philosophical core of free software. The term parasite does not apply well to free software. |
Quote:
http://www.linuxquestions.org/questi...9/#post3339774 |
Regarding the posted rc.6 script, I don't think it is an improvement to put commands in background while the system shuts down but YMMV of course
|
I have used Vector Linux for years now. I don't know if its a "fork" or not, but it is only through it that I learned of slackware. Dependent on gui programs, I look upon slackware with something akin to reverence. I suspect there are many who first learned of slackware through Vector Linux. Seems to me that they support each other. If not, as I have no intention of switching from VL, I suggest that the slackware folks propose something that I could do to help slackware. I really don't want to be a parasite. That "help" should probably not be by way of asking me to contribute to some slackware forum I don't know enough to be of much help.
|
Wow, this has turned into a fascinating thread, especially for psychologists and anthropologists :)
I think the term parasite is too strong. Are people who install and use slackware without subscribing, donating or contributing to it parasites too? I think the legal position of the GPL is closely aligned with its ethical position. When you release GPL'd software you can say you are the original author of it, but you are releasing it - letting go of it - and giving it a life of its own. Woodsman's child analogy seems very apt. Of course, the original author can voice disapproval of future usage and changes, but using the term parasite seems to miss the point of free software. I listened to the tllts interview with Pat the other day and he name checked Slax and I didn't detect any negativity towards it. The OP edited his 11-feb-08 edit in the original post yesterday to remove some rather impolite comments. BTW That "standing on the shoulders of giants" quote from Newton is now viewed as being meant as sarcastic- he had a pretty big ego! |
The reasons I restrict my input to this fine group to one reply every couple of years or so should, from the forgoing, be rather obvious.
|
Yeah I think there is a lot of misunderstanding. Any way maybe this might help
Quote:
Edit: Just to be clear I agree with the Free Software foundations stance. I am a huge GNU fan. |
Although I'm disagreeing with Robby here and also with Eric when he mentioned "parasite" on another thread a while ago, I do hugely appreciate and benefit from their contribution to slackware and slackbuilds.org. I might well feel differently if I'd put in the work that they have.
|
Quote:
I tried Vector once and found it to be very stable. If you ever want to try Slackware we will be happy to help you. Slackware can be a bit daunting for people more comfortable with a GUI than a shell prompt. The support documentation for Slackware is excellent. |
As an aside, you might note the fascinating rebuttals over at http://forum.vectorlinux.com/index.php?topic=7740.0 - assuming the childishness isn't edited away by now.
|
Quote:
|
Quote:
|
Quote:
Oh well - distro wars again.. ;) - Never a dull moment and all that.. Oh - and BTW this post is not supposed to be taken seriously..in case it's not obvious.. |
wow, that pic of rworkman is quite funny, although mean in a way.
Anyway, I'm sick of this thread. My last word: 'parasite' is a term incompatible with the GPL signing off... |
After considering carefully, I decided that deleting this post was more constructive than keeping it. If you PM me, I'll send it to you in private.
|
Quote:
The worst thing for any brand name is to have it taken away from the public eye. - Distros 'based' on Slackware is free advertising for a man who cannot afford to buy ads everywhere on teh nets and generally when someone uses a 'based on' distro they become curious as to how they real thing operates and usually stick with the original. So, that's a +++. Another benefit to Slackware is that these based on distros continue to show that Slackware is relevant against the onslaught of the 'best 1995 has to offer' slogan. As for calling someone who makes a rebranding etc of Slackware childish because most of the programs they use are from elsewhere --Have you ever looked at Slackware sources? P did not code everything in Slackware by hand - most of it's programs were written by other people which P then incorporates into the distro, so I guess by your meter Slackware itself is childish, sheesh! P.S No one can help upstream if they do not have a clue how Slackware works in the first place and a good way to learn is to have fun with your own distro --that way you can break things and move on. If, for instance, every Slackware noob was contributing software to the upstream not only would it clog and waste time but it would also result in a crappy Slackware! - Is that what you want? No offense but dude.. I mean lighten up. |
Quote:
No no! Slackware was written from scratch and all of it's userland and the Linux kernel itself was written by one man *rolls eyes* |
Thank you.
but what exactly your script do ? |
All times are GMT -5. The time now is 07:50 AM. |