search for: heirloom

<m.roth at 5-cent.us> wrote: > Ah. I don't remember if I was using csh, or ksh, and didn't realize about > bash. I *think* I vaguely remember that sh seemed to be more capable than > I remembered. If you like to check what the Bourne Shell did support in the late 1980s, I recommend you to fetch recent Schily tools from:

...; wrote: > On Apr 27, 2015, at 4:38 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > > > This is the SVr4 Bourne Shell, so you need to take into account what has been > > added with Svr4: > > Is there any difference between your osh and the Heirloom Bourne Shell? > > http://heirloom.sourceforge.net/sh.html Heirloom did make quick and dirty ports and then stopped working. Heirloom e.g. did make the same attempt to port to platforms that may cause problems with own malloc() implemenetaions: - add a private malloc for sh internal use...

Sorry for the extra email. It send to quickly. procmail: Assigning "SUBJECT= Tornado Monday, 03/27/2017 at 20:27:02. The Point BB.OBSURGRH is" jerry

On Apr 27, 2015, at 9:07 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > Heirloom added support for uname -S and for some linux ulimit extensions but > then stopped working on the code after a few months Ah. I had no idea it was in a state of disrepair. >> I see that you already wrote up the differences between osh and bosh in an earlier post. Is there a good reaso...

I am getting the following on my 'new box' for my DNS server: Date: Wed, 20 Feb 2013 13:58:04 -0500 From: To: Subject: [abrt] full crash report User-Agent: Heirloom mailx 12.4 7/29/08 abrt_version: 2.0.8 cmdline: ro root=/dev/mapper/vg_onlo3-root_01 rd_NO_LUKS rd_LVM_LV=vg_onlo3/root_01 LANG=en_US.UTF-8 +rd_NO_MD SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=128M rhgb quiet rd_NO_DM rhgb +quiet kernel: 2.6.32-279.22.1.e...

On Apr 27, 2015, at 4:38 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > This is the SVr4 Bourne Shell, so you need to take into account what has been > added with Svr4: Is there any difference between your osh and the Heirloom Bourne Shell? http://heirloom.sourceforge.net/sh.html I see that you already wrote up the differences between osh and bosh in an earlier post. Is there a good reason why these comparisons are not on the Schily Tools web page already? :)

...r-Encoding: base64' > > The version of mailx in Red Hat Enterprise Linux 5 is based off the old BSD mailx program (in Debian it looks like it is still available as bsd-mailx). That version was 'bit' rotting and having problems with newer mail servers. For an afternoon read http://heirloom.sourceforge.net/mailx_history.html and https://www.redhat.com/archives/rhl-devel-list/2008-June/msg00628.html [It looks like this was further forked into s-nail which Debian, Ubuntu, Arch, etc seem to ship as the default for mailx now.] Looking for why this change was done I found these: https://...

...13:28:10 ser dovecot: IMAP(juergen): Raw backtrace: imap [0x80cc01e] -> imap [0x80cc08a] -> imap [0x80cba78] -> imap [0x806642f] -> imap [0x80602c1] May 20 13:28:10 ser dovecot: child 23536 (imap) killed with signal 6 (core dumps disabled) it's almost always reproducible using the Heirloom mailx [1] mail client, with mutt I get a 'connection closed' message but no segfault: - login to the dovecot server via imap/imaps - move a message from INBOX to a another large mbox-file - quit Seems to be a new issue introduced with 1.1.15 because I don't see that with 1.1.14 or...

...t (Postfix, from userid 0) id 6F02E2A0078; Tue, 17 Jan 2012 08:11:56 -0500 (EST) Date: Tue, 17 Jan 2012 08:11:56 -0500 From: user at localhost.srv.net To: root at localhost.srv.net Subject: [abrt] full crash report Message-ID: <4f15739c.MHhrv8Xn0YkMj8Xp%user at localhost> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Duplicate check ===== Common information ===== architecture ----- x86_64 package ----- kernel kernel ----- 2.6.32-220.2.1.el6.x86_64 Additional information ===== kernel_tainted_lo...

Everyone, I have just upgraded a Centos 5 server to a Centos 7 server and am having difficulty with a change of behavior of mailx with the use of a command line of : mail -s 'This is the subject' user at domain.com < text_file.txt On Centos 5 when mailx was used by a program started by a cron job we were able to send a text file as an email message and the headers did not contain

Les Mikesell <lesmikesell at gmail.com> wrote: > On Mon, Apr 27, 2015 at 10:07 AM, Joerg Schilling > <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > > > > I would be interested to understand why Heirloom seems to so well known and my > > portability attempts seem to be widely unknown. > > > > Not sure why it matters with a standalone application like sh, but I > think a lot of people have been put off by the GPL incompatibility > with your tools. If you want popularity - a...

...--------------------------------------------------------------------- However, using mail, i can read the emails : ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- $ mail Heirloom mailx version 12.5 6/20/10. Type ? for help. "/var/mail/desktop": 20 messages 9 new 18 unread U 1 Desktop User Sun Sep 27 13:01 19/621 ceci est le sujet <snip /> N 20 Yvon Thoraval Tue Sep 29 18:02 25/1042 another mail with Maildir... ? ----------------...

Hi, I'm trying to get the so-called "single instance store" (I think cyrus has got the name for the first time) with dovecot --version = 2.0.19 binary package installed from ubuntu 12.04 lts official repo. I have checked that "maildir_copy_with_hardlinks" is enabled ("dovecot -a|grep hard" shows "yes") then I have installed and enabled the lmtp

...t the contents of the package without explaining why one would want to download it. I thought I don't need to make advertizing for well known software. I manage the only actively maintained portable Bourne Shell and I do so as well for SCCS. > > I would be interested to understand why Heirloom seems to so well known and my > > portability attempts seem to be widely unknown. > > I can think of several explanations: > > 1. The Heirloom pages explain what features each download provides, rather than just give a list of program names. The problem is that the developes pag...

On Mon, Apr 27, 2015 at 10:07 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > > I would be interested to understand why Heirloom seems to so well known and my > portability attempts seem to be widely unknown. > Not sure why it matters with a standalone application like sh, but I think a lot of people have been put off by the GPL incompatibility with your tools. If you want popularity - and usability, a dual-license...

...500) id 98C33606BE; Wed, 12 Apr 2017 12:40:20 -0700 (PDT) Date: Wed, 12 Apr 2017 12:40:20 -0700 To: pierce at hogranch.com Subject: Tornado Monday, 03/27/2017 at 20:27:02. The Point BB.OBSURGRH is in Alarm at PRI3 with a value of 63.4 %.Informational Text:OB SURGERY HUMIDITY ALARM User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20170412194020.98C33606BE at new.XXX.com> From: pierce at XXX.com (John R Pierce) -- john r pierce, recycling bits in santa cruz

...rbird INBOX, nor using openssl : > [..] > However, using mail, i can read the emails : > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > $ mail > > Heirloom mailx version 12.5 6/20/10. Type ? for help. > > "/var/mail/desktop": 20 messages 9 new 18 unread > [..] > my dovecot setup uses vhosts : > ------------------------------------------------------------------------------------------------------------------------------------...

...users = @"domain users" locking = yes public = yes writeable = yes browseable= yes printable = no create mask = 0660 force create mode = 0660 directory mask = 0771 -----Original Message----- Date: Mon, 20 Nov 2017 15:21:40 -0500 To: samba at lists.samba.org User-Agent: Heirloom mailx 12.5 7/5/10 Subject: [Samba] How to use AD authentication for normal Samba file sharing From: Mark Foley via samba <samba at lists.samba.org> I have a Linux host used for file sharing. Although I have a Samba4 AD/DC configured in the LAN, this file-sharing host is not currently a domai...

I've been using Dovecot 2.2.15 as the IMAP server for Outlook (2010/2013) on Windows workstations for over 6 months with no problems. Dovecot is hosted on the office Samba4 AC/DC server. I have been using auth_mechanisms plain login, and passdb driver = shadow. What I'd like to do now is use the "Windows Authenticated" login so I don't have to have separate passwords for

About a year-and-a-half ago I wrote in a thread having this same subject about a problem my sendmail server was having on my Samba4 AD/DC. To solve that problem at the time, I maintained domain user entries in both the sam.ldb and in /etc/passwd, and did not have winbind specified in /etc/nsswitch.conf. I am now trying to remove all users from /etc/passwd and use winbind. Unfortunately, I'm