英文字典中文字典


英文字典中文字典51ZiDian.com



中文字典辞典   英文字典 a   b   c   d   e   f   g   h   i   j   k   l   m   n   o   p   q   r   s   t   u   v   w   x   y   z       







请输入英文单字,中文词皆可:

GCOS    
/jee'kohs/ An {operating system} developed
by {General Electric} from 1962; originally called GECOS (the
General Electric Comprehensive Operating System).

The GECOS-II operating system was developed by {General
Electric} for the 36-bit {GE-635} in 1962-1964. Contrary to
rumour, GECOS was not cloned from {System/360} [{DOS/360}?] -
the GE-635 architecture was very different from the {IBM 360}
and GECOS was more ambitious than DOS/360.

GE Information Service Divsion developed a large special
multi-computer system that was not publicised because they did
not wish {time sharing} customers to challenge their bills.
Although GE ISD was marketing {DTSS} - the first commercial
time sharing system - GE Computer Division had no license from
Dartmouth and GE-ISD to market it to external customers, so
they designed a time-sharing system to sell as a standard part
of GECOS-III, which replaced GECOS-II in 1967. GECOS TSS was
more general purpose than DTSS, it was more a programmer's
tool (program editing, e-mail on a single system) than a BASIC
TSS.

The {GE-645}, a modified 635 built by the same people, was
selected by {MIT} and {Bell} for the {Multics} project.
Multics' infancy was as painful as any infancy. Bell pulled
out in 1969 and later produced {Unix}.

After the buy-out of GE's computer division by {Honeywell},
GECOS-III was renamed GCOS-3 (General Comprehensive Operating
System). Other OS groups at Honeywell began referring to it
as "God's Chosen Operating System", allegedly in reaction to
the GCOS crowd's uninformed and snotty attitude about the
superiority of their product. [Can anyone confirm this?]
GCOS won and this led in the orphaning and eventual death of
Honeywell {Multics}.

Honeywell also decided to launch a new product line called
Level64, and later DPS-7. It was decided to mainatin, at
least temporarily, the 36-bit machine as top of the line,
because GCOS-3 was so successfull in the 1970s. The plan in
1972-1973 was that GCOS-3 and Multics should converge. This
plan was killed by Honeywell management in 1973 for lack of
resources and the inability of Multics, lacking {databases}
and {transaction processing}, to act as a business operating
system without a substantial reinvestment.

The name "GCOS" was extended to all Honeywell-marketed product
lines and GCOS-64, a completely different 32-bit operating
system, significanctly inspired by Multics, was designed in
France and Boston. GCOS-62, another different 32-bit low-end
DOS level was designed in Italy. GCOS-61 represented a new
version of a small system made in France and the new {DPS-6}
16-bit {minicomputer} line got GCOS-6.

When the intended merge between GCOS-3 and Multics failed, the
Phoenix designers had in mind a big upgrade of the
architecture to introduce {segmentation} and {capabilities}.
GCOS-3 was renamed GCOS-8, well before it started to use the
new features which were introduced in next generation
hardware.

The GCOS licenses were sold to the Japanese companies {NEC}
and {Toshiba} who developed the Honeywell products, including
GCOS, much further, surpassing the {IBM 3090} and {IBM 390}.

When Honeywell decided in 1984 to get its top of the range
machines from NEC, they considered running Multics on them but
the Multics market was considered too small. Due to the
difficulty of porting the ancient Multics code they considered
modifying the NEC hardware to support the Multics compilers.

GCOS3 featured a good {Codasyl} {database} called IDS
(Integrated Data Store) that was the model for the more
successful {IDMS}.

Several versions of transaction processing were designed for
GCOS-3 and GCOS-8. An early attempt at TP for GCOS-3, not
taken up in Europe, assumed that, as in {Unix}, a new process
should be started to handle each transaction. IBM customers
required a more efficient model where multiplexed {threads}
wait for messages and can share resources. Those features
were implemented as subsystems.

GCOS-3 soon acquired a proper {TP monitor} called Transaction
Driven System (TDS). TDS was essentially a Honeywell
development. It later evolved into TP8 on GCOS-8. TDS and
its developments were commercially successful and predated IBM
{CICS}, which had a very similar architecture.

GCOS-6 and GCOS-4 (ex-GCOS-62) were superseded by {Motorola
68000}-based {minicomputers} running {Unix} and the product
lines were discontinued.

In the late 1980s Bull took over Honeywell and Bull's
management chose Unix, probably with the intent to move out of
hardware into {middleware}. Bull killed the Boston proposal
to port Multics to a platform derived from DPS-6. Very few
customers rushed to convert from GCOS to Unix and new machines
(of CMOS technology) were still to be introduced in 1997 with
GCOS-8. GCOS played a major role in keeping Honeywell a
dismal also-ran in the {mainframe} market.

Some early Unix systems at {Bell Labs} used GCOS machines for
print spooling and various other services. The field added to
"/etc/passwd" to carry GCOS ID information was called the
"{GECOS field}" and survives today as the "pw_gecos" member
used for the user's full name and other human-ID information.

[{Jargon File}]

(1998-04-23)

General Comprehensive Operating System (Honeywell, OS, Honeywell Series 60, Honeywell Series 6000)

GCOS: /jee´kohs/, n. A quick-and-dirty
clone of System/360 DOS that emerged from GE around
1970; originally called GECOS (the General Electric Comprehensive Operating
System). Later kluged to support primitive timesharing and transaction
processing. After the buyout of GE's computer division by Honeywell, the
name was changed to General Comprehensive Operating System (GCOS). Other
OS groups at Honeywell began referring to it asGod's Chosen
Operating System’, allegedly in reaction to the GCOS crowd's
uninformed and snotty attitude about the superiority of their product. All
this might be of zero interest, except for two facts: (1) The GCOS people
won the political war, and this led in the orphaning and eventual death of
Honeywell Multics, and (2) GECOS/GCOS left one
permanent mark on Unix. Some early Unix systems at Bell Labs used GCOS
machines for print spooling and various other services; the field added to
/etc/passwd to carry GCOS ID information was called
the GECOS field and survives today as
the pw_gecos member used for the user's
full name and other human-ID information. GCOS later played a major role
in keeping Honeywell a dismal also-ran in the mainframe market, and was
itself mostly ditched for Unix in the late 1980s when Honeywell began to
retire its aging big iron designs.


请选择你想看的字典辞典:
单词字典翻译
GCOS查看 GCOS 在百度字典中的解释百度英翻中〔查看〕
GCOS查看 GCOS 在Google字典中的解释Google英翻中〔查看〕
GCOS查看 GCOS 在Yahoo字典中的解释Yahoo英翻中〔查看〕





安装中文字典英文字典查询工具!


中文字典英文字典工具:
选择颜色:
输入中英文单字

































































英文字典中文字典相关资料:


  • What is the fundamental difference between CNN and RNN?
    A CNN will learn to recognize patterns across space while RNN is useful for solving temporal data problems CNNs have become the go-to method for solving any image data challenge while RNN is used for ideal for text and speech analysis
  • machine learning - What is a fully convolution network? - Artificial . . .
    Fully convolution networks A fully convolution network (FCN) is a neural network that only performs convolution (and subsampling or upsampling) operations Equivalently, an FCN is a CNN without fully connected layers Convolution neural networks The typical convolution neural network (CNN) is not fully convolutional because it often contains fully connected layers too (which do not perform the
  • Extract features with CNN and pass as sequence to RNN
    But if you have separate CNN to extract features, you can extract features for last 5 frames and then pass these features to RNN And then you do CNN part for 6th frame and you pass the features from 2,3,4,5,6 frames to RNN which is better The task I want to do is autonomous driving using sequences of images
  • What is the difference between CNN-LSTM and RNN?
    Why would "CNN-LSTM" be another name for RNN, when it doesn't even have RNN in it? Can you clarify this? What is your knowledge of RNNs and CNNs? Do you know what an LSTM is?
  • convolutional neural networks - When to use Multi-class CNN vs. one . . .
    0 I'm building an object detection model with convolutional neural networks (CNN) and I started to wonder when should one use either multi-class CNN or a single-class CNN
  • machine learning - What is the concept of channels in CNNs . . .
    The concept of CNN itself is that you want to learn features from the spatial domain of the image which is XY dimension So, you cannot change dimensions like you mentioned
  • neural networks - Are fully connected layers necessary in a CNN . . .
    A convolutional neural network (CNN) that does not have fully connected layers is called a fully convolutional network (FCN) See this answer for more info An example of an FCN is the u-net, which does not use any fully connected layers, but only convolution, downsampling (i e pooling), upsampling (deconvolution), and copy and crop operations
  • In a CNN, does each new filter have different weights for each input . . .
    Typically for a CNN architecture, in a single filter as described by your number_of_filters parameter, there is one 2D kernel per input channel There are input_channels * number_of_filters sets of weights, each of which describe a convolution kernel So the diagrams showing one set of weights per input channel for each filter are correct
  • How to use CNN for making predictions on non-image data?
    You can use CNN on any data, but it's recommended to use CNN only on data that have spatial features (It might still work on data that doesn't have spatial features, see DuttaA's comment below) For example, in the image, the connection between pixels in some area gives you another feature (e g edge) instead of a feature from one pixel (e g color) So, as long as you can shaping your data





中文字典-英文字典  2005-2009