POV-Ray : Newsgroups : povray.off-topic : Not again, Bill! Server Time
11 Oct 2024 01:24:23 EDT (-0400)
  Not again, Bill! (Message 21 to 24 of 24)  
<<< Previous 10 Messages Goto Initial 10 Messages
From: Darren New
Subject: Re: Not again, Bill!
Date: 23 Feb 2008 19:52:06
Message: <47c0bfb6@news.povray.org>
Warp wrote:
> in the case of Linux it's really part of the OS because device drivers
> are compiled into the kernel,

Is that still true, tho? I thought the "modules" stuff took care of 
that? Like loading the encryption loopback device makes something new in 
/dev (/dev/loop0) yes?

Or am I just confused?

>   Also, is a firewall an integral part of the OS, or is it just a app
> in the distro?

Clearly the ability to examine connections has to be part of the OS if 
the TCP stack is part of the OS. How you decide to permit or refuse a 
connection is probably in user-space if you can afford the inefficiency.

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."


Post a reply to this message

From: Warp
Subject: Re: Not again, Bill!
Date: 24 Feb 2008 04:02:17
Message: <47c13299@news.povray.org>
Darren New <dne### [at] sanrrcom> wrote:
> Warp wrote:
> > in the case of Linux it's really part of the OS because device drivers
> > are compiled into the kernel,

> Is that still true, tho? I thought the "modules" stuff took care of 
> that? Like loading the encryption loopback device makes something new in 
> /dev (/dev/loop0) yes?

> Or am I just confused?

  Driver modules can be dynamically linked to the kernel at runtime.
They are still part of the kernel, though. Once linked they are part
of the kernel code, have all the same rights and all the same access.
Moreover, there's no standard stable binary interface between the modules
and the rest of the kernel. A module compiled for one version of the
kernel may well not work with the next version. In other words, all the
device driver modules must always be provided with each new version of
the kernel. Closed source binary-only driver modules are not feasible
(because they would only work for a very limited range of kernels).

-- 
                                                          - Warp


Post a reply to this message

From: Darren New
Subject: Re: Not again, Bill!
Date: 24 Feb 2008 22:21:16
Message: <47c2342c$1@news.povray.org>
Warp wrote:
>> Or am I just confused?
>   Driver modules can be dynamically linked to the kernel at runtime.

Thanks for the explanation!

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."


Post a reply to this message

From: Tom Austin
Subject: Re: Not again, Bill!
Date: 25 Feb 2008 09:05:06
Message: <47c2cb12@news.povray.org>
somebody wrote:
> "Tim Cook" <z99### [at] gmailcom> wrote in message
> news:47bf2aeb$1@news.povray.org...
> 
>> Which means that, in theory, they fixed security holes that AV and
>> firewalls use to do low-level system calls, thereby also blocking off a
>> lot of viruses/malware in the process.
> 
> Antivirus, anti-malware and firewall should be an integral and irreplacable
> part of the OS, for any modern OS.
> 
> 


It is - you can use the ultra useful and secure MS security programs.


Post a reply to this message

<<< Previous 10 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.