[email protected] wrote in <[email protected]>: | Quoth Herr Steffen Nurpmeso, 'We are at Slackware, too! Thank |you, this is really nice!! I did not even know that Slackware is |still truly alive, but i think: good that it is.' | Viva Slackware! | | Quoth Herr Johannes Sch�pfer, 'Maybe a missing user folder in |/var/spool/mail ?' | No. | | Quoth Herr Johannes Sch�pfer, 'Where does the string "mailx |v14.9.11, 2018-08-08 (build for linux)" come from? Is this a prebuilt |binary? Or from slackbuilds.org, or from slackware-current?' | I thought I got it from 'mail -V', but it is the the first |line of 'mailx -Xversion'. This is in slackware-current. I've been |using mail since the beginning, even as an MUA (!!!!!). Which means I |am soon headed for the grave, so maybe you don't have to address my |problems. | | Quoth Herr Johannes Sch�pfer, 'heirloom-mailx development is |now at s-nail, so why not go with it.' | That's the spirit! | | nytimes is a plain text file. I save e-mail into files named |after the sender (for example JohnSmith, SteffenNurpmeso, |JohannesSch�pfer, nytimes...). | I just noticed something: | | s2 NYTimes | |works; | | s2 nytimes | |returns the error. nytimes is a link to NYTimes.
Ah! Oh yes, i see, this is true. This is because we actively reject to follow symbolic links by setting O_NOFOLLOW when calling open(2), and our error number mapping table misses the ELOOP error that is generated if this is triggered! This i will fix for the next release, hopefully before the christian christmas -- thanks for reporting this bug, Russell! --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
