From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Turritopsis Dohrnii Teo En Ming <teo.en.ming@protonmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: ceo@teo-en-ming-corp.com
Subject: Re: Teo En Ming has just discovered that the latest Sophos Firewall SFOS version 20.0.0 GA-Build222 is running on Linux kernel 4.14.302
Date: Fri, 17 Nov 2023 16:39:25 +0700 [thread overview]
Message-ID: <ZVc0zQHbfdBOQAZ0@archie.me> (raw)
In-Reply-To: <rjsYjj5lRT_rd91lLJ0DutYwgag5By6ghI92s1AFP5asT4IDtTlKhkt56KrcNBGKEKMWQYn430H-bs3-IS4GjEFQjKd79ZHv9iRDd1EVQiU=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
On Thu, Nov 16, 2023 at 02:19:47PM +0000, Turritopsis Dohrnii Teo En Ming wrote:
> Subject: Teo En Ming has just discovered that the latest Sophos Firewall SFOS version 20.0.0 GA-Build222 is running on Linux kernel 4.14.302
>
> Good day from Singapore,
>
> I have just discovered that the latest Sophos Firewall SFOS version 20.0.0 GA-Build222 is running on Linux kernel 4.14.302.
>
> # uname -a
> Linux localhost 4.14.302 #2 SMP Wed Nov 1 07:16:58 UTC 2023 x86_64 GNU/Linux
>
> However, I do not know which Linux distro Sophos Firewall is based on. When I run the Linux command "cat /etc/lsb-release", the output is
> DISTRIB_ID=Sophos Firewall
>
> Hence I do not know which Linux distro the Sophos Firewall is based on.
Most likely your vendor build their own custom distro (maybe Yocto
Project-based or anything between). Hence, if you have any problems with
it, please contact the support channel provided by your vendor (in your
case, [1]).
Bye!
[1]: https://support.sophos.com/support
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-11-17 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 14:19 Turritopsis Dohrnii Teo En Ming
2023-11-17 9:39 ` Bagas Sanjaya [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZVc0zQHbfdBOQAZ0@archie.me \
--to=bagasdotme@gmail.com \
--cc=ceo@teo-en-ming-corp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=teo.en.ming@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®