Sure, see the second part of this post

1 members found this post helpful.

Anyone knows the url to etc-15.0 or can tell me how to find it?

I am currently failing at googling there ... :/

upnort --

As volkerdi said postfix does all the same stuff that sendmail can do but the configs are completely different.

There is a lot of online documentation and books on postfix configuration.

Most use cases are very ( very ) simple.

This is a link to the Postfix Standard Configuration Examples which takes a little getting used to but once you do, it's much simpler than sendmail ( IMO ... of course, YMMV )

And when you've got a complicated use-case for sendmail, it's usually not too hard to find a postfix 'recipe' to do the same via google.

-- kjh( a happy postfix user for well over 10 years now )

In my LAN I am using sendmail only to shuffle system mails. I haven't touched my sendmail files in, oh, since I started using Slackware about 15 years ago. OK, probably I have added a nominal tweak or two.

I don't mind the change. I have a tip of the iceberg familiarity with postfix because of work. But just the tip.

Would be nice with a major change in a package like this if a simple migration shell script existed. Or a simple check list. Not complaining, just saying.

The nvidia-driver is extremely picky over which kernel it supports. Unfortunately, this is nothing new, so you're going to be stuck using nouveau or modesetting with egl enabled for the time being. That being said, you probably shouldn't be using the nvidia-driver on -Current in the first place.

Note that when you upgrade your slackware-current with a "slackpkg install-new" to get the new packages, you will get the postfix package and retain the sendmail package. Also, the rc.M script gives preference to rc.sendmail - if that script is executable, then Slackware will not attempt to start Postfix through its rc.postfix script even if that too is executable.

Unfortunately there is one snag (easy to fix though): the postfix package overwrites the main sendmail binary /usr/sbin/sendmail with a postfix wrapper. You think you start Sendmail while in fact it is Postfix which gets started.
You can fix this by re-installing sendmail package from the /extra directory, which will again overwrite the Postfix version of /usr/sbin/sendmail with a proper Sendmail binary.

2 members found this post helpful.

The CHANGES_AND_HINTS.TXT file lists the replacement, but does not contain your caveat warnng. Perhaps that could get added? I'll guess that one will catch more than a few folks off guard.

I see that mlocate will replace slocate. Just a small tip for new mlocate users.

For several years I have had to use both packages. I long have had the following in my /etc/bashrc:

Unlike slocate, mlocate does not automatically ignore files that are missing from the database, which is the normal behavior with slocate. The -e parameter makes mlocate function the same as the slocate default.

3 members found this post helpful.

Big update alright. I managed to break pretty much everything.

Had no kernel problems, booting was fine, but ended up being put into runlevel 3, so I startx and find I have no network and my VPN connection had disappeared altogether. KDE was playing up and wouldn't launch any programs after attempting to get into networkmanager config. I know I caused the issues by holding back some rc's and overwriting others (I admit it, I was looking through the diff to begin with but ended up just hitting 'o' because there were so many and I was short of time - I figured should any probs arise I'll deal with em later).

Edit to add: Just noticed my CPU is stuck on 3800MHz, it used to sit as low as 800 with powersaving option but jump to 4200 when needed. Now it's 3800 no matter what.

1 members found this post helpful.

Why not? I'm using it this way for longer than I can remember. Ocassionally, it won't work with the latest kernel, but Nvidia is always very quick in releasing updates in alike situations. At the moment, I'm with 387.22 version of driver, and it seems working fine through yesterday kernel update.

1 members found this post helpful.

Because -Current is always changing, various libraries and the kernel can change and disrupt the driver, as well as other packages dependent on it and Mesa as well which is used for the FOSS driver.

1 members found this post helpful.

This is rather broad statetment, one could say that for almost anything. Do you have a specific problem to point to, regarding using Nvidia driver with -current? Again: in my experience, and considering that it's not part of the FOSS ecosystem, Nvidia is doing pretty good job with keeping their drivers updated to kernel changes. One just have to remember to reinstall the driver after each kernel and Mesa update in -current, and there should be no problems.

1 members found this post helpful.

It is a broad statement because the topic has surfaced from time to time and not just Nvidia but other kernel driver or alternative drivers that depend on various libraries and kernels.

Generally, the OEM drivers are always aimed at stabilized releases to minimize issues like mismatched kernels, lack of patches, wrong libraries, or dependency related issues, or any other issues that could break something.

Again, these are broad statements. Are you personally using Nvidia driver, and which are specific issues that you encountered previously in using it with -current?

2 members found this post helpful.