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.
I did read it before posting. It is one of the reasons I made my post. Back in the day is not today.
wow, ok I'll post on irc Chrisretusn expects all of us who have been running it for about 2 decades to stop, change our configurations, because thats what is decided for todays use.
you should apply for a job as a writer on the comedy channel.
pssst not even RedHat overwrites existing files
and go d/l the source and install postfix,, look at where it puts the alias file oh lookie there it is in /etc/postfix ;P
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 454
Rep:
One of the Japanese mirrors (ftp.kddilabs.jp) in /etc/slackpkg/mirrors hasn't updated -current (32 or 64 bit) since last October. 14.2 patches since that time are also missing. Maybe it should be taken off the list.
I still don't see where the postfix package does this. I mean, if you're *deleting* the /etc/postfix/aliases symlink and creating a same-named file, do you really expect that a package upgrade shouldn't overwrite that?
I've still not heard a good reason why you can't just use the /etc/aliases file.
Quote:
and go d/l the source and install postfix,, look at where it puts the alias file oh lookie there it is in /etc/postfix ;P
I did that. Then this happens:
Code:
# newaliases
postalias: fatal: open /etc/aliases: No such file or directory
Note that the postfix INSTALL documentation doesn't mention anything about being able to *use* the aliases file while leaving it in /etc/postfix:
Code:
10.8 - Create the aliases database
Postfix uses a Sendmail-compatible aliases(5) table to redirect mail for local
(8) recipients. Typically, this information is kept in two files: in a text
file /etc/aliases and in an indexed file /etc/aliases.db. The command "postconf
alias_maps" will tell you the exact location of the text file.
First, be sure to update the text file with aliases for root, postmaster and
"postfix" that forward mail to a real person. Postfix has a sample aliases file
/etc/postfix/aliases that you can adapt to local conditions.
/etc/aliases:
root: you
postmaster: root
postfix: root
bin: root
etcetera...
Note: there should be no whitespace before the ":".
Finally, build the indexed aliases file with one of the following commands:
# newaliases
# sendmail -bi
In short, what you're demanding runs contrary to the documentation and doesn't even work. I suspect if the sample file were to be left alone in /etc/postfix, people would try to edit it there and wonder why it doesn't work. Plus it would get overwritten. I'm not about to .new protect something that's not a functional config file (the /etc/aliases file *is* currently .new protected).
All Postfix parameters are listed and described in the various *sample configuration* files. The *sample files* are located in the directory specified by the sample_directory parameter, which is usually the same directory as your main.cf file.
/etc/postfix/aliases is a there as a *sample file*.
Last edited by franzen; 04-27-2021 at 01:23 AM.
Reason: seems pat posted the previous while i was writing
Your aliases won't get overriden if you would stop replacing the symlink /etc/postfix/aliases from the system package.
Assuming Nobby's root filesystem supports file attributes, perhaps he could try "chattr +i /etc/postfix/aliases" to stop his replaced file from getting clobbered by a symlink whenever the postfix package is updated. I haven't tried it myself so I'm not sure if upgradepkg would freak out.
Comparing to the hibernation with swap partition, hibernation into swap
file requires both 'resume' and 'resume_offset'. In addition, the
'resume' parameter should point to the unlocked or mapped device that
contains the filesystem with swap file when using LVM or dm-crypt and
the 'resume_offset' parameter contains the offset of the swap header.
Hi, it seems /sbin/mkinitrd also uses non-POSIX compliant commands (brace expansion, echo flags, and some more) while still having #!/bin/sh as the shebang line.
wow, ok I'll post on irc Chrisretusn expects all of us who have been running it for about 2 decades to stop, change our configurations, because thats what is decided for todays use.
you should apply for a job as a writer on the comedy channel.
pssst not even RedHat overwrites existing files
and go d/l the source and install postfix,, look at where it puts the alias file oh lookie there it is in /etc/postfix ;P
From the aliases file:
Code:
#
# Sample aliases file. Install in the location as specified by the
# output from the command "postconf alias_maps". Typical path names
# are /etc/aliases or /etc/mail/aliases.
postfix was added to Slackware on Fri Nov 17 00:56:25 UTC 2017; 3 years 5 months 11 days ago from date of this post. Last I checked a decade was 10 years.
I retired 18 years ago, not looking for a job. Now it's all work, no pay.
OK - I will bite after mulling on this for some hours and checking that the date is well past 1 April.
Why would I want this, apart from the fact that all other kde distros include?
I have read the documentation, the default is off. If allowed, supposedly the data only goes to KDE servers, but history teaches that such databases are prone to being breached. Any data collected provides information that could be used for fingerprinting.
Given KDE's history of being prepared to break users to force hardware manufacturers to comply with standards, I do not expect that this is in users best interests, but rather the interest of KDE.
OK - I will bite after mulling on this for some hours and checking that the date is well past 1 April.
Why would I want this, apart from the fact that all other kde distros include?
I have read the documentation, the default is off. If allowed, supposedly the data only goes to KDE servers, but history teaches that such databases are prone to being breached. Any data collected provides information that could be used for fingerprinting.
Given KDE's history of being prepared to break users to force hardware manufacturers to comply with standards, I do not expect that this is in users best interests, but rather the interest of KDE.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.