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.
In trying to get rid of any type of non-free software from my Slackware system (because its my system and I can do it, that's why) I noticed getty-ps is one of these I wish to remove although according to the slack-desc it seems important
getty-ps: getty-ps (console or terminal login)
getty-ps:
getty-ps: /sbin/getty and /sbin/uugetty.
getty-ps: These control the process of logging into your system, and may be used
getty-ps: instead of 'agetty', which is the default getty included with the
getty-ps: util-linux package. getty-ps supports a number of enhancements such as
getty-ps: ringback support.
getty-ps:
getty-ps: getty-ps was originally written by Paul Sutcliffe, Jr, and is
getty-ps: currently maintained by Christine Jamison.
getty-ps:
-------------------------------------------------------------------------------
Getty Kit, Version 2.0
Copyright (c) 1989,1990, Paul Sutcliffe Jr.
-------------------------------------------------------------------------------
Permission is hereby granted to copy, reproduce, redistribute,
or otherwise use this software as long as: there is no monetary
profit gained specifically from the use or reproduction or this
software, it is not sold, rented, traded or otherwise marketed,
and this copyright notice is included prominently in any copy
made.
The author make no claims as to the fitness or correctness of
this software for any use whatsoever, and it is provided as is.
Any use of this software is at the user's own risk.
-------------------------------------------------------------------------------
This being said, _unless_ you substituted /sbin/getty to /sbin/agetty in /etc/inittab or use it otherwise, you probably won't miss it. But if you do, just reinstall it.
Last edited by Didier Spaier; 11-21-2015 at 10:36 AM.
Yes, it's safe. The Virtual Consoles use agetty from util-linux. You won't need the extra features of getty-ps unless you're planning to do some sort of fancy dial-in setup using a modem.
I had getty-ps setup with a fancy 'ringback' config in the good old days. *starts feeling all nostalgic*
Hmmm.... thinking about it, I still have my USR Courier in the attic.
-------------------------------------------------------------------------------
Getty Kit, Version 2.0
Copyright (c) 1989,1990, Paul Sutcliffe Jr.
-------------------------------------------------------------------------------
Permission is hereby granted to copy, reproduce, redistribute,
or otherwise use this software as long as: there is no monetary
profit gained specifically from the use or reproduction or this
software, it is not sold, rented, traded or otherwise marketed,
and this copyright notice is included prominently in any copy
made.
The author make no claims as to the fitness or correctness of
this software for any use whatsoever, and it is provided as is.
Any use of this software is at the user's own risk.
-------------------------------------------------------------------------------
This being said, _unless_ you substituted /sbin/getty to /sbin/agetty in /etc/inittab or use it otherwise, you probably won't miss it. But if you do, just reinstall it.
It's restrictions monetizing/commercial use even though I am not not probably will never see myself using it in that way...unless iatndirectly (slackware would be like a capital good for me in that sense). My opinion of free software does not restrict commercial use.
Yes, it's safe. The Virtual Consoles use agetty from util-linux. You won't need the extra features of getty-ps unless you're planning to do some sort of fancy dial-in setup using a modem.
I had getty-ps setup with a fancy 'ringback' config in the good old days. *starts feeling all nostalgic*
Hmmm.... thinking about it, I still have my USR Courier in the attic.
Neat, I've removed it and blacklisted it, thanks for the info I appreciate it.
Permission is hereby granted to copy, reproduce, redistribute,
or otherwise use this software as long as: there is no monetary
profit gained specifically from the use or reproduction or this
software, it is not sold, rented, traded or otherwise marketed,
and this copyright notice is included prominently in any copy
made.
That's actually true free software. Basically it means, don't use my software to profiteer off my work. It doesn't mean using it with other software is bad though.
By the way, I would advise you to limit the non-free software removals to non-kernel and compiler related packages. Screwing with glibc, the kernel, drivers, firmware, and the libc can be very bad. Very, very bad.
What's so bad about wanting to not get profiteered off of?
That's actually true free software. Basically it means, don't use my software to profiteer off my work.
I think the BSD license is closer to my idea of free software. Or even the WTFPL.
Quote:
What's so bad about wanting to not get profiteered off of?
While that's certainly an author's right, it restricts some uses of the software. The way I see things, the more restrictions there are, the less free the software is.
That's actually true free software. Basically it means, don't use my software to profiteer off my work. It doesn't mean using it with other software is bad though.
By the way, I would advise you to limit the non-free software removals to non-kernel and compiler related packages. Screwing with glibc, the kernel, drivers, firmware, and the libc can be very bad. Very, very bad.
What's so bad about wanting to not get profiteered off of?
Whatever you mean by "free", it's not the same as FSF's "free" or OSI's "open-source". Both definitions regard restrictions to commercial use as no-go. There's nothing wrong about "wanting to not get profiteered off of" until the means to that end start infringing on the basic human rights. In the case of non-free software we are talking about the freedom of expression, which is fundamentally incompatible with copyright monopolies. My advice to all software writers out there is: if you don't want your users to be fully in control of the software you write, please do not write any software (at least, don't feel compelled to share it). We will do just fine without it.
My own advice with respect to Slackware would be to replace the kernel with linux-libre first of all, since the stock one contains blobs and so almost certainly malware, whereas the rest of non-free packages are obsolete and/or niche programs with source code, and so are perfectly harmless. Replacing the kernel may not be an option on hardware without free driver support, but otherwise it's seamless.
That's actually true free software. Basically it means, don't use my software to profiteer off my work. It doesn't mean using it with other software is bad though.
By the way, I would advise you to limit the non-free software removals to non-kernel and compiler related packages. Screwing with glibc, the kernel, drivers, firmware, and the libc can be very bad. Very, very bad.
What's so bad about wanting to not get profiteered off of?
Yeah I don't want to mess with the kernel or core stuff, I have just figured I would stick with it, I don't mind firmware so much either as its basically impossible to get around it nowadays, more so with the hardware I have running Slackware on. Oh and to answer your question, I don't really know, I just have a weird philosophy ATM at the moment that I want to minimize as much software as possible on my server that imposes any type of restrictions.
I think the BSD license is closer to my idea of free software. Or even the WTFPL.
While that's certainly an author's right, it restricts some uses of the software. The way I see things, the more restrictions there are, the less free the software is.
Hit the nail on the head pretty much. To me, free software lets you do whatever you want with it without regarding who you are or what you are using it for. I sometimes go back and forth with which is moree free between the BSD license (not sure which one) and the GPL license with how the GPL requires you to distribute the source code if you took a GPLed piece of software and based something else off that (I am being very loose simply because I am no master of these licenses, this is just what I have read briefly) and how the BSD license doesn't require such things. Hmm...I think in a way the BSD would offer more freedom, but at the same time, having to redistribute the source code doesn't necessarily take away a freedom? Well actually I guess it does as its saying you can't make anything based off this software without redistributing your source code....hmm kind of hard. I kind of like the GPL more in that regard just because it seems a bit more fair, imo.
I agree about the BSD license Patrick, though to me, I lean more towards the MIT license as ideal. The ISC license looks very favorable as well.
I think a sensible copyright law would be just powerful enough to enforce a BSD- or MIT-style license, and nothing else. Copyleft is pretty clever as a hack, but serves no useful purpose in the absence of copyright monopolies.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
