On Mon, Sep 3, 2012 at 9:56 PM, Steven D'Aprano <st...@pearwood.info> wrote:
> On 04/09/12 10:26, Dwight Hutto wrote: > > On *nix there is a cron daemon that runs in the background. >>> but one job running in the background controlling dozens(?) of >>> >>> others is way more efficient than dozens of programs all running idle in >>> the background and periodically springing into action. >>> >>> >> But each OS(BIOS handler) has a way of providing/accepting instructions to >> the processor, which is constantly procedural. This has to have a terminal >> at some point. >> >> What is meant by behind a console, and running without a console, just a >> window system, and a file set that deals with instructions/errors based on >> BIOS input/output? >> > > > On Mon, Sep 3, 2012 at 9:56 PM, Steven D'Apran > > Best regards, > o <st...@pearwood.info> wrote: > >> On 04/09/12 10:26, Dwight Hutto wrote: >> >> On *nix there is a cron daemon that runs in the background. >>>> but one job running in the background controlling dozens(?) of >>>> >>>> others is way more efficient than dozens of programs all running idle in >>>> the background and periodically springing into action. >>>> >>>> >>> But each OS(BIOS handler) has a way of providing/accepting instructions >>> to >>> the processor, which is constantly procedural. This has to have a >>> terminal >>> at some point. >>> >>> What is meant by behind a console, and running without a console, just a >>> window system, and a file set that deals with instructions/errors based >>> on >>> BIOS input/output? >>> >> >> I'm afraid these sentences sound like gobbledygook to me. No offense >> Dwight, >> but it sounds like you're randomly inserting "computer terms" into >> sentences >> with no meaning. >> >> Which one's. If yuou could, please reply on a line by line, because some of what you listed above isn't mine. What's wrong with: But each OS(BIOS handler) has a way of providing/accepting instructions to the processor, which is constantly procedural. This has to have a terminal at some point. What is meant by behind a console, and running without a console, just a window system, and a file set that deals with instructions/errors based on BIOS input/output? I'll add Intel/AMD to the instructions secton. The gobbledy gook, might be a little smeared on your face...Want a rag?...Steven By the way, you can call me David...buddy. The only part that actually makes sense to me is: >> >> >> "This has to have a terminal at some point." >> >> but that is not true. The fact that cron runs without a tty (a terminal) >> is >> proof of that. >> >> >> >> -- >> Steven >> >> _______________________________________________ >> Tutor maillist - Tutor@python.org >> To unsubscribe or change subscription options: >> http://mail.python.org/mailman/listinfo/tutor >> > > I'm afraid these sentences sound like gobbledygook to me. No offense > Dwight, > but it sounds like you're randomly inserting "computer terms" into > sentences > with no meaning. > > The only part that actually makes sense to me is: > > > "This has to have a terminal at some point." > > but that is not true. The fact that cron runs without a tty (a terminal) is > proof of that. > > > > -- > Steven > > ______________________________**_________________ > Tutor maillist - Tutor@python.org > To unsubscribe or change subscription options: > http://mail.python.org/**mailman/listinfo/tutor<http://mail.python.org/mailman/listinfo/tutor> > -- Best Regards, David Hutto *CEO:* *http://www.hitwebdevelopment.com*
_______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor