From nobody Mon Jul 24 02:06:39 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4R8Nnp5z8sz4p67x for ; Mon, 24 Jul 2023 02:06:54 +0000 (UTC) (envelope-from ksrdhrbsd@gmail.com) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R8Nnn5Vl4z3hmf for ; Mon, 24 Jul 2023 02:06:53 +0000 (UTC) (envelope-from ksrdhrbsd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-4f95bf5c493so5516416e87.3 for ; Sun, 23 Jul 2023 19:06:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690164411; x=1690769211; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oBUBrrwZfCPZfQuvq2LlaCi/ZiK6n/eXQWulhhhZQ2E=; b=gmXGhpaJxJ27yqwQYacAYS3m7W0IJlE4pk+ew3416Wjn5Gv6WAxm3no9v+8ksaxKxh yDd8fSGprI9fcI9985daHfldNI7lOYvYUqnQJkGT9VkUwdVZP/GMPLpCPcm0TlLLan91 RIk5239X1YlW9PwEQ5BViJsbJdNO878LaDfT2oKIvvbk7flUolB3LXhaZFjf9POkxMJ2 8e9Hfm8JibzFecam9taLn0YAugU6Kk9H6QNmQ3mLVv/R62PVjn8KFuPITCBk+smIhZ4A GJzU0ylLm6vjiZusBuc1mI3Awni9Rm8PeYS3QdH+NDHKJclYwI9/kY3mYEmMBd30nHER cIbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690164411; x=1690769211; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oBUBrrwZfCPZfQuvq2LlaCi/ZiK6n/eXQWulhhhZQ2E=; b=LeVHgbYDJECOBtcP66e6e8EzqeLYFsI9mmj46PvTS99gTM93zpW6avD76MuFJB4fwu 1vttU5QiBveDnbztq8ixJV/l2v1dG4THkejgIlaIqBxCZXWCPeUoKTHT6AtTbqpuT3NU mtBkKmkSMxXsz2xgYCf1RmI4lqNJ9Tm+Gf+f1KWjkdJBWbe4z0FjK+p1wuGDDTxOP3Mc K34ilLoHhIMCPxvhwYP4dsqwbQqiFVUb4wCTLZSrjR/GfXcqgE9iXdtVMXXoYBXCRv3W 00VMQpjiNnmVj8WKOZsoVrFRVXVaIVej0wi9OmvQE8QrjI0okNZ7z+1FwjwbFjORaRQK f0/A== X-Gm-Message-State: ABy/qLaQDe1EG8NA0CamFTV0k4Ytjn7Zcj91vOtHaZEClo/0Fcc0QRjR wQNpLCyxJ0mpGR+z1vmKDHlAwaN0NVepP4VCHtfsoHQY2Q== X-Google-Smtp-Source: APBJJlHdhyT2CgE1IawqGL7FifWWTjQ2b5OREWOV3sxyJjs543iEgODSSKcvdxWe1rN9LZWR9kLTzbooC8mAy4teX4I= X-Received: by 2002:a05:6512:3b27:b0:4fd:d016:c2e8 with SMTP id f39-20020a0565123b2700b004fdd016c2e8mr2077130lfv.43.1690164411170; Sun, 23 Jul 2023 19:06:51 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: k sridhar Date: Sun, 23 Jul 2023 22:06:39 -0400 Message-ID: Subject: Re: Contributing to one of the projects in the Ideas page To: imp@bsdimp.com Cc: FreeBSD Hackers Content-Type: multipart/alternative; boundary="00000000000057027506013211dc" X-Rspamd-Queue-Id: 4R8Nnn5Vl4z3hmf X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated --00000000000057027506013211dc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sure, I will start by reviewing what OpenBSD and NetBSD have done. Thanks a lot. On Sun, Jul 23, 2023 at 10:04=E2=80=AFPM Warner Losh wrote= : > > > On Sun, Jul 23, 2023, 7:59 PM k sridhar wrote: > >> >> Hello, >> >> I was browsing the Ideas page for ways to contribute to BSD. >> I came across this (which does not have any contact, I think). >> >> If it is still open, I wanted to check if I could try to do this. >> >> Briefly - I am in IT, and have been using UNIX since grad school in the >> early 90s (Solaris, briefly Ultrix/Aix and then different Linuxes >> and MacOS). C/C++/Java programming, scripting, installs, etc... and vari= ous >> other stuff. >> >> I want to give it a shot if you all think that is ok. >> > > Nobody is working on this. Might be best to see what openbsd and netbsd > have done first and start from there. It will be the first question peopl= e > ask when you start the review process. I think yhey have some fixes and = a > newer vixie cron import, but I'm not sure. > > Happy coding > > Warner > > Thanks a lot >> k.sridhar (U.S resident in Virginia) >> *Improve cron(8) and atrun(8)* >> >> *Currently, cron(8) and atrun(8) are outdated in their implementation. >> Here are some directions for improvement:* >> >> - *Update cron(8) to ISC cron with security fixes from OpenBSD.* >> - *Integrate the atrun(8) functionality into cron(8), as it was done >> in NetBSD.* >> >> *Requirements* >> >> - *Strong knowledge of the C language and Unix API.* >> >> --00000000000057027506013211dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sure, I will start by reviewing what OpenBSD and NetBSD ha= ve done.

Thanks a lot.

On Sun, Jul 23, 2023 at 10:0= 4=E2=80=AFPM Warner Losh <imp@bsdimp.c= om> wrote:


On Sun, Jul 23, 2023, 7:59 PM k sridhar <ksrdhrbsd@gmail.com&g= t; wrote:

Hello,

I was brow= sing the Ideas page for ways to contribute to BSD.
I came across = this (which does not have any contact, I think).

I= f it is still open, I wanted to check if I could try to do this.
<= div>
Briefly - I am in IT, and have been using UNIX since gra= d school in the early 90s (Solaris, briefly Ultrix/Aix and then different L= inuxes and=C2=A0MacOS). C/C++/Java programming, scripting, installs, etc...= and various other stuff.=C2=A0

I want to give it a = shot if you all think that is ok.

Nobody is = working on this. Might be best to see what openbsd and=C2=A0 netbsd have do= ne first and start from there. It will be the first question people ask whe= n you start the review=C2=A0process.=C2=A0 I think yhey have some fixes and= a newer vixie cron import, but I'm=C2=A0not sure.=C2=A0

Happy coding
<= br>
Warner

Thanks a lot
k.sridhar (U.S resident in = Virginia)

Improve cron(8) and atrun(8)

<= /span>

Currently, cron(8) and atrun(8) are outdated in t= heir implementation. Here are some directions for improvement:<= /span>

  • Update cron(8) to I= SC cron with security fixes from OpenBSD.
  • Integrate the atrun(8)= functionality into cron(8), as it was done in NetBSD.

Requirements
  • Strong knowledge of the C language and Unix API.
--00000000000057027506013211dc--