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.
Thanks you. In fact, I mind very well my own business, which needs (or will go better with) that LinuxPAM and Kerberos.
And so sorry that I insulted your religious beliefs, but like my TM says:
Gentlemen, please keep your religious opinions for the church, mosque or whatever. There we discuss only and only about hardware and software.
And I guess that his take works well, as in our team works and collaborates Christians, Muslims, Buddhists, and if I remember right, even a Shintoist.
I proposed a set of packages for inclusion in the official Slackware distribution, that would in my opinion improve its attractiveness for people from my primary domain of work, that is scientific computing. (For the record, while it would be certainly easier for me too if these are official packages, I can certainly keep living with installing them through SBo.) I'm well aware that this thread is mostly for pointing to new releases of packages already in Slackware, still there were some proposals alike to mine on this thread in the past, and some of these packages actually eventually landed in Slackware. I mentioned packages that are well known, not that big, and may be useful to significant audience. Probably none of these will go in, but I had nothing but good intentions, and I think I haven't offended anyone.
Then you come, obviously mocking my proposal by bringing into attention highly controversial packages, that are discussed to each miniscule detail already on this thread, and that are from completely different domain of use from packages that I mentioned. So it seems natural for me to ask: what is your problem here? What would my proposal have to do with your business of having or not having PAM and Kerberos in Slackware? And what the heck was that rant about religion, what was that supposed to mean?
I think that Darth Vader didn't mock at all your proposal proposing (yes, again) PAM and Kerberos. I rather assume that his post was not an answer to yours in any way. Thus I didn't understand why you asked him to mind his own business, and found that rather rude.
Last edited by Didier Spaier; 11-30-2017 at 10:09 AM.
Well, I talked about the religious aspects of that "highly controversial packages", where are no real reasons of controversy, excluding the ol'good "BOB said so" or whatever.
And I do not mocked you in any way, you can ask any old user hanging on this forum, probably starting with our BDFL, everyone knows about my passion for Linux-PAM and its pal, Kerberos.
@Didier Spaier just demonstrated that no one missed my opinions about Linux-PAM. Thanks, Didier!
Last edited by Darth Vader; 11-30-2017 at 10:11 AM.
Well, I talked about the religious aspects of that "highly controversial packages", where are no real reasons of controversy, excluding the ol'good "BOB said so" or whatever.
And I do not mocked you in any way, you can ask any old user hanging on this forum, probably starting with our BDFL, everyone knows about my passion for Linux-PAM and its pal, Kerberos.
@Didier Spaier just demonstrated that no one missed my opinions about Linux-PAM. Thanks, Didier!
You have omit your passion for 'plasma5' cheers......
Excluding a handful of illuminated ones, like P.V., Eric, Robert, and so on, I think you can consider all of rest of 99% of the users being some "toxic users" who has nothing to offer ...
Last edited by Darth Vader; 12-01-2017 at 12:18 PM.
Reading through README_CRYPT.TXT today (my hard drive is making funny noises on my laptop so I just ordered a new hard drive - thought I'd take the opportunity to try out encryption) I noticed two things:
1. "avery" should be "every".
2. This one might be more controversial : "can not" should be "cannot". Some people consider this more a style issue, but at least "cannot" is used consistently in the other README*.TXT files over "can not". (See the description for the step package in PACKAGES.TXT for a scenario where "can" and "not" should remain as separate words.)
Code:
--- README_CRYPT.TXT 2016-06-24 15:57:45.000000000 -0700
+++ README_CRYPT.new.TXT 2017-12-01 09:38:56.884978238 -0700
@@ -57,7 +57,7 @@
from, and the initrd image that is needed with encrypted volumes. You need
to install LILO either to the MBR - or if that is not possible, into the
root sector of this small unencrypted partition. You will probably guess
-why we can not use an encrypted partition for this...
+why we cannot use an encrypted partition for this...
Using cryptsetup during Slackware installation
@@ -151,7 +151,7 @@
names of the devices you will select for your target partitions. Be sure
to read until the end of the story though, because we will have to do some
postprocessing in order to make your encrypted partitions available after
-reboot (setup can not yet do all of this automatically).
+reboot (setup cannot yet do all of this automatically).
* In setup, under "ADDSWAP", proceed as usual and configure a normal
unencrypted swap partition, even if you want to have your swap encrypted.
@@ -244,7 +244,7 @@
There is no need to ever enter a passphrase!
NOTE: having an encrypted swap like this causes a re-format of the swap
- partition on avery boot-up and shutdown. This is perfectly OK as long
+ partition on every boot-up and shutdown. This is perfectly OK as long
as you do not change the order of your hard disks. If you add a disk,
or move this disk to another computer, the device name may change (for
instance from sda to sdb) and if you forget to modify '/etc/crypttab'
@@ -337,7 +337,7 @@
present, make sure that the label you use ('linux' in the example above)
is unique in the configuration file.
-* If you have another OS on your computer and can not install lilo to the
+* If you have another OS on your computer and cannot install lilo to the
MBR, you will have selected "Install to superblock (Root)" instead. In
that case, we have one additional change to make, and that is almost at the
top of the file. Look up the line that says "boot = /dev/mapper/cryptroot"
@@ -378,7 +378,7 @@
We are assuming that Slackware will be the only Operating System on your
computer. In case you already have an OS installed (such as MS Windows), the
-procedure may be a little different because you can not always install lilo to
+procedure may be a little different because you cannot always install lilo to
the MBR. After booting from the Slackware installation medium, we will
create a small unencrypted partition that will contain the Linux kernels and
the initrd image(s). The rest of the disk's free space will be dedicated to
Reading through README_CRYPT.TXT today (my hard drive is making funny noises on my laptop so I just ordered a new hard drive - thought I'd take the opportunity to try out encryption) I noticed two things:
1. "avery" should be "every".
2. This one might be more controversial : "can not" should be "cannot". Some people consider this more a style issue, but at least "cannot" is used consistently in the other README*.TXT files over "can not". (See the description for the step package in PACKAGES.TXT for a scenario where "can" and "not" should remain as separate words.)
Thanks! Typos will be fixed with the next update batch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
: "can not" should be "cannot". Some people consider this more a style issue, but at least "cannot" is used consistently in the other README*.TXT files over "can not". (See the description for the step package in PACKAGES.TXT for a scenario where "can" and "not" should remain as separate words.)
