CN1821960A - Embedded system for automatic loading root file system automatic loading system and method - Google Patents
Embedded system for automatic loading root file system automatic loading system and method Download PDFInfo
- Publication number
- CN1821960A CN1821960A CN 200510008394 CN200510008394A CN1821960A CN 1821960 A CN1821960 A CN 1821960A CN 200510008394 CN200510008394 CN 200510008394 CN 200510008394 A CN200510008394 A CN 200510008394A CN 1821960 A CN1821960 A CN 1821960A
- Authority
- CN
- China
- Prior art keywords
- file system
- root file
- expanding device
- microprocessor
- embedded system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
This invention relates to an embedded system capable of loading root file system automatically, an automatic loading system and a method, in which, said method includes: turning on the power supply of said embedded system to execute a boot-strap program and executing a core using it and starting an automatic starting program of the root file system by this core so as to read a root file image file stored by an extension device outside of said embedded system and loading said root file system based on the image file of said system.
Description
Technical field
The present invention relates to a kind of system and method that loads root file system, but particularly relate to a kind of embedded system, auto-loading system and method for automatic loading root file system.
Background technology
Development along with embedded system (Embedded system), relevant application apparatus is also day by day popularized, for instance, information household appliances (information appliance, IA), intelligent mobile phone (smart phone), set-top box (set-top-box), the multimedia video player, printer, the device of application such as router and personal digital assistant Embedded System Structure all is products that present industry does one's utmost to develop, generally speaking, embedded system system is made of computer software (embedded OS) and computer hardware (system single chip), that is it is based on a certain specific use and develops, therefore, compared to general personal computer, it is high that embedded system often has stability, little and the low advantage of cost of volume.For embedded OS, at present the employed product of industry is a lot, for example Palm OS, Windows CE and Linux etc., and wherein (SuSE) Linux OS is owing to have the characteristic of free mandate, so is applied in the embedded system in large quantities at present.
Existing embedded system is that the pairing root file system of its embedded OS (root file system) burning is seen also Fig. 1 in nonvolatile memories such as flash memory at present, and Fig. 1 is the function block schematic diagram of known embedded system 10.Embedded system 10 includes a microprocessor 12, a nonvolatile memory 14 and a volatile memory 16, wherein microprocessor 12 is used for controlling the running of embedded system 10, nonvolatile memory 14 (for example flash memory or ROM (read-only memory)) is used for noting down a boot program Boot_Code, a core Kernel and a root file system image file (root file system image file) RFS, and volatile memory 16 (for example dynamic RAM) required program code and operational data when being used for temporary embedded system 10 runnings.Boot program Boot_Code is used for controlling the loading of core Kernel, for instance, boot program Boot_Code is a power-on management program (boot loader), it can support the function of multi-boot, so the boot program of may command embedded system 10 loads suitable core Kernel so that control the running of hardware in the embedded system 10 via core Kernel with foundation user demand.
See also Fig. 2, Fig. 2 is the process flow diagram that embedded system 10 shown in Figure 1 loads root file system.The operation that embedded system 10 loads root file system includes the following step:
Step 100: the power supply of opening embedded system 10;
Step 105: microprocessor 12 is loaded into volatile memory 16 with boot program Boot_Code stored in the nonvolatile memory 14 automatically;
Step 110: microprocessor 12 reads the boot program Boot_Code that volatile memory 16 kept in and to carry out boot program Boot_Code further nonvolatile memory 14 stored core Kernel is loaded in the volatile memory 16;
Step 120: microprocessor 12 reads core Kernel that volatile memory 16 kept in and disposes hardware in (configure) embedded system 10 to carry out core Kernel further;
Step 130: after core Kernel had finished the hardware that disposes in the embedded system 10, microprocessor 12 was carried out core Kernel nonvolatile memory 14 stored root file system image file RFS is loaded in the volatile memory 16; And
Step 140: microprocessor 12 decompression root file system image file RFS produce embedded system 10 desired root file systems.
As mentioned above, embedded system 10 is come storage application all data in the root file system image file RFS of embedded system 10 by nonvolatile memory 14, yet, because the consideration of cost, the capacity of nonvolatile memory 14 is often limited, so significantly, the mechanism of known loading root file system has following three main shortcomings:
(1) limited size of root file system image file RFS is in the capacity of nonvolatile memory 14, and therefore, the application software that root file system image file RFS is comprised can be because storage volume restriction and can't optimization;
(2) because of the capacity limit of nonvolatile memory 14, embedded system 10 only can be used single root file system image file RFS; And
(3) embedded system 10 only can be used the root file system image file RFS that stores in the nonvolatile memory 14 and can't load other suitable root file system image file according to user's demand, so the function of embedded system 10 expands difficult.
Summary of the invention
Therefore but the present invention system provides a kind of embedded system, auto-loading system and method for automatic loading root file system, to solve the above problems.
According to embodiments of the invention, it has disclosed a kind of method of automatic loading one root file system to an embedded system, and this method includes: the power supply of opening this embedded system is to load and to carry out a boot program (boot code); Use this boot program to load and carry out a core (kernel); And use this core to start the automatic initial orders of a root file system (root file system autoinitial program, RootFS AIP), and loads this root file system to this embedded system according to this root file system image file reading the stored root file system image file (root file system image file) of the outside expanding device of this embedded system.
According to embodiments of the invention, it has also disclosed a kind of embedded system.This embedded system includes: a microprocessor (microcontroller) is used for controlling the running of this embedded system; One first storage device is coupled to this microprocessor; And one second storage device, be coupled to this microprocessor, be used for storing a boot program (boot code), a core (kernel), and the automatic initial orders of a root file system (root file system auto initial program).This microprocessor can load and carry out this boot program from this second memory in regular turn, this core and the automatic initial orders of this root file system, and this microprocessor is to use this core to start the automatic initial orders of this root file system reading the stored root file system image file of expanding device that is external in this embedded system, and loads a root file system to this first storage device according to this root file system image file.
According to embodiments of the invention, it has also disclosed the auto-loading system of a kind of root file system (root file system), and it includes: an embedded system and an expanding device.This embedded system includes: a microprocessor (microcontroller) is used for controlling the running of this embedded system; One first storage device is coupled to this microprocessor; And one second storage device, be coupled to this microprocessor, be used for storing a boot program (boot code), a core (kernel), and the automatic initial orders of a root file system (root file system auto initial program, RootFS AIP).This expanding device is external in this embedded system, is used for storing a root file system image file (root file system image file); Wherein this microprocessor can load and carry out this boot program from this second memory in regular turn, this core and the automatic initial orders of this root file system, and this microprocessor uses this core to start the automatic initial orders of this root file system reading this stored root file system image file of this expanding device, and loads this root file system to this first storage device according to this root file system image file.
The present invention utilizes external expanding device to provide bigger capacity to store root file system image file, therefore, as long as the capacity of volatile memory is large enough to hold and normally carries out root file system image file, the capacity of root file system image file just no longer is subject to the memory capacity of nonvolatile memory, therefore, but root file system image file just optimization to comprise more applications software so that embedded system can possess more diversified function.
Description of drawings
Fig. 1 is the function block schematic diagram of known embedded system.
Fig. 2 is the process flow diagram that embedded system shown in Figure 1 loads root file system.
Fig. 3 is applied to the functional block diagram of the auto-loading system of root file system for the present invention.
Fig. 4 is the process flow diagram that auto-loading system shown in Figure 3 loads root file system.
The reference numeral explanation
10,152 embedded systems
12,156 microprocessors
14,158 nonvolatile memories
16,160 volatile memory
150 auto-loading systems
154a, 154b, expanding device
154c
162 connecting interfaces
164 network interfaces
166 LAN
168 the Internets
Embodiment
See also Fig. 3, Fig. 3 is applied to the functional block diagram of the auto-loading system 150 of root file system for the present invention.Auto-loading system 150 includes an embedded system 152 and a plurality of expanding device 154a, 154b, 154c, in the present embodiment, embedded system 152 includes a microprocessor 156, a nonvolatile memory 158, a volatile memory 160, a connecting interface 162 and a network interface 164.In addition, nonvolatile memory 158 (for example flash memory or ROM (read-only memory)) records a plurality of default expanding device enactment document S of a boot program Boot_Code, a core Kernel, the automatic initial orders of a root file system (rootfile system auto initial program) RFS_AIP and the corresponding expanding device 154a of difference, 154b, 154c
1, S
2, S
3As shown in Figure 3, expanding device 154a directly is coupled to embedded system 152 via the connecting interface 162 (for example USB interface) of embedded system 152, then (localnetwork LAN) 166 is coupled to the network interface (for example network card) of embedded system 152 with the Internet (Internet) 168 via LAN respectively for expanding device 154b, 154c.In addition, expanding device 154a, 154b, 154c (for example data storing media such as Winchester disk drive, floppy drive or CD-ROM drive) store root file system image file (root filesystem image file) RFS respectively
a, RFS
b, RFS
cNote that embedded system shown in Figure 3 152 and assembly of the same name in the embedded system 10 shown in Figure 1 have identical functions and running, no longer repeat to give unnecessary details at this.
Please consult Fig. 3 and Fig. 4 simultaneously, Fig. 4 is the process flow diagram that auto-loading system 150 shown in Figure 3 loads root file system.Auto-loading system 150 loadings one root file system to the running of embedded system 152 is described as follows:
Step 200: the power supply of opening embedded system 152;
Step 205: microprocessor 156 is loaded into volatile memory 160 with boot program Boot_Code stored in the nonvolatile memory 158 automatically;
Step 210: microprocessor 156 reads the boot program Boot_Code that volatile memory 160 kept in and to carry out boot program Boot_Code further nonvolatile memory 158 stored core Kernel is loaded in the volatile memory 160;
Step 215: microprocessor 156 reads core Kernel that volatile memory 160 kept in and disposes hardware in (configure) embedded system 152 to carry out core Kernel further; And
Step 220: after core Kernel had finished the hardware that disposes in the embedded system 152, microprocessor 156 was to carry out core Kernel the nonvolatile memory 158 stored automatic initial orders RFS_AIP of root file system are loaded in the volatile memory 160;
Step 225: microprocessor 156 reads the automatic initial orders RFS_AIP of root file system that volatile memory 160 kept in and reads a default expanding device enactment document S to carry out the automatic initial orders RFS_AIP of root file system further
1, S
2, S
3
Need step 230: embedded system 152 use ICP/IP protocol to come access should preset the pairing expanding device of expanding device enactment document? if then execution in step 235; Otherwise, execution in step 245;
Need step 235: embedded system 152 use LAN 166 to come access should preset the pairing expanding device of expanding device enactment document? if then execution in step 240; Otherwise, execution in step 245;
Step 240: the automatic initial orders RFS_AIP of microprocessor 156 execution root file systems is next, and (dynamic host configuration protocol DHCP) is connected to the Internet 168 with embedded system 152 via DynamicHost configuration agreement;
Step 245: microprocessor 156 is carried out the automatic initial orders RFS_AIP of root file system and is enabled appropriate protocol to set up embedded system 152 and to be somebody's turn to do the binding of presetting between the pairing expanding device of expanding device enactment document (connection);
Step 250: microprocessor 156 is carried out the automatic initial orders RFS_AIP of root file system according to presetting the expanding device enactment document root file system image file that corresponding expanding device was write down was loaded in the volatile memory 160; And
Step 255: the above-mentioned root file system image file that is loaded on volatile memory 160 of microprocessor 156 decompressions produces embedded system 152 desired root file systems.
The running of step 200～215 is identical with the running of abovementioned steps 100～120, so do not give unnecessary details in this in addition.In the present embodiment, be that with the main difference of the load mechanism of well-known root file system embedded system 152 has the automatic initial orders RFS_AIP of a root file system, be used for controlling the load operation of root file system, the automatic initial orders RFS_AIP of the root file system application software that is not root file system wherein, therefore, it is after core Kernel has finished the hardware that disposes in the embedded system 152, carrying out core Kernel by microprocessor 156 is loaded on the automatic initial orders RFS_AIP of root file system in the volatile memory 160 (step 220), then, microprocessor 156 just can begin to carry out the follow-up flow process that the automatic initial orders RFS_AIP of root file system comes the control loaded root file system, in the present embodiment, the user can assign parameter in the automatic initial orders RFS_AIP of root file system, reads a default expanding device enactment document S so that control the automatic initial orders RFS_AIP of root file system according to its demand
1, S
2, S
3(step 225).
For instance, suppose root file system image file RFS
a, RFS
b, RFS
cThe family of languages of corresponding respectively Chinese, English and Japanese.If user's desire is used the embedded system 152 of supporting the Chinese family of languages, then the user can assign parameter and give the automatic initial orders RFS_AIP of root file system, reads default expanding device enactment document S with the automatic initial orders RFS_AIP of control root file system
1For default expanding device enactment document S
1, default expanding device enactment document S
1Include a pathname, its corresponding root file system image file RFS
aThe storage address, an and annotation data (Metadata), it is used for setting expanding device 154
aAccess mode (as previously mentioned, expanding device 154
aBe directly connected in embedded system 152), so, default expanding device enactment document S
1The annotation data that is had is a directly expansion instruction, and being used to refer to embedded system 152 does not need to come access expanding device 154 via network (LAN 166 and the Internet 168)
aStored root file system image file RFS
aSo,, microprocessor 156 is just carried out the automatic initial orders RFS_AIP of root file system and is enabled appropriate protocol (for example USB host-host protocol) to set up embedded system 152 and expanding device 154
aBetween binding (step 245).Then, the automatic initial orders RFS_AIP of root file system is just according to default expanding device enactment document S
1The pathname of being noted down is with desired root file system image file RFS
aBe loaded in the volatile memory 160 (step 250), last, microprocessor 156 decompresses and is loaded on the root file system image file RFS of volatile memory 160
aProduce embedded system 152 desired root file systems (supporting the Chinese family of languages).
In addition, if user's desire is used the embedded system 152 of supporting the English family of languages, then the user can assign parameter in the automatic initial orders RFS_AIP of root file system, and automatic initial orders RFS_AIP reads another default expanding device enactment document S with the control root file system
2For default expanding device enactment document S
2, default expanding device enactment document S
2Include a pathname, it is corresponding root file system image file RFS
bThe storage address, an and annotation data, it is used for setting expanding device 154
bAccess mode (as previously mentioned, expanding device 154
bBe connected in embedded system 152 indirectly via LAN 166), so, default expanding device enactment document S
2The annotation data that is had is a TCP/IP online-order, and being used to refer to embedded system 152 needs to come access expanding device 154 via LAN 166
aStored root file system image file RFS
b(step 230,235), so, microprocessor 156 is just carried out the automatic initial orders RFS_AIP of root file system and is enabled appropriate protocol, TFTP (Trivial File Transfer Protocol for example, tftp), file transfer protocol (FTP) (File Transfer Protocol, ftp), Hypertext Transport Protocol (HypertextTransmission Protocol, HTTP), network file system(NFS) (Network File System, NFS) or server message frame (Server Message Block, SMB) agreement is to set up embedded system 152 and expanding device 154
bBetween binding (step 245).Then, the automatic initial orders RFS_AIP of root file system is just according to default expanding device enactment document S
2The pathname of being noted down is with desired root file system image file RFS
bBe loaded in the volatile memory 160 (step 250), last, microprocessor 156 decompresses and is loaded on the root file system image file RFS of volatile memory 160
bProduce embedded system 152 desired root file systems (supporting the English family of languages).
On the other hand, if user's desire is used the embedded system 152 of supporting the Japanese family of languages, then the user can assign parameter and give the automatic initial orders RFS_AIP of root file system, and automatic initial orders RFS_AIP reads another default expanding device enactment document S with the control root file system
3For default expanding device enactment document S
3, default expanding device enactment document S
3Include a pathname, its corresponding root file system image file RFS
cThe storage address, an and annotation data, it is used for setting expanding device 154
cAccess mode (as previously mentioned, expanding device 154
bBe connected in embedded system 152 indirectly via the Internet 168), so, default expanding device enactment document S
3The annotation data that is had is a TCP/IP online-order, and being used to refer to embedded system 152 needs to come access expanding device 154 via the Internet 168
cStored root file system image file RFS
c(step 230), so, in order to make embedded system 152 be linked to the Internet 168, microprocessor 156 is carried out the automatic initial orders RFS_AIP of root file system and is come via DynamicHost configuration agreement (dynamic host configurationprotocol, DHCP) the network on-line information of setting embedded system 152, network address etc. (step 240) for example, then, microprocessor 156 is carried out the automatic initial orders RFS_AIP of root file system and is enabled appropriate protocol, TFTP (Trivial File TransferProtocol for example, tftp), file transfer protocol (FTP) (File Transfer Protocol, ftp), Hypertext Transport Protocol (Hypertext Transmission Protocol, HTTP), network file system(NFS) (Network File System, NFS) or server message frame (Server Message Block, SMB) agreement is to set up embedded system 152 and expanding device 154
cBetween binding (step 245).Then, the pathname noted down according to default expanding device enactment document 32 of the automatic initial orders RFS_AIP of root file system is with desired root file system image file RFS
cBe loaded in the volatile memory 160 (step 250), last, the root file system image file RFS that microprocessor 156 just decompresses and is loaded on volatile memory 160
cProduce embedded system 152 desired root file systems (supporting the Japanese family of languages).
Note that Fig. 3 only demonstrates three expanding devices 154
a, 154
b, 154
cYet, in fact the present invention does not limit the number of expanding device, in addition, because default expanding device enactment document includes pathname to be used to refer to the storage address of root file system image file, so, the present invention does not in fact also limit only can store a root file system image file in each expanding device, in other words, suppose to record in the same specific expanding device a plurality of different root file system image files, the present invention also can be via the particular path title that is write down in the default expanding device enactment document, read a root file system image file of wanting in a plurality of root file system image files of noting down from this specific expanding device, above-mentioned variation all belongs to category of the present invention.
Compared to known technology, the present invention utilizes external expanding device to provide bigger capacity to store root file system image file, therefore, as long as the capacity of volatile memory is large enough to hold and normally carries out root file system image file, the capacity of root file system image file just no longer is subject to the memory capacity of nonvolatile memory, therefore, but root file system image file optimization to comprise more applications software so that embedded system can have more diversified function.In addition, the present invention can make embedded system carry out required root file system according to demand via the mechanism of external load root file system image file, therefore can promote the use elasticity of embedded system further.Moreover, the present invention starts the automatic initial orders of root file system to control boot program before the application software load and execution, therefore, the mechanism that the present invention loads root file system image file can be applied to numerous embedded system at present easily, that is the mechanism that the present invention loads root file system image file is easy to real work.
The above only is preferred embodiment of the present invention, and all equalizations of doing according to claim of the present invention change and modify, and all should belong to covering scope of the present invention.
Claims (16)
1. method that automatically loads root file system to an embedded system, it includes:
(a) power supply of opening this embedded system is carried out a boot program;
(b) use this boot program to carry out a core;
(c) use this core to start the automatic initial orders of a root file system to read the stored root file system image file of the outside expanding device of this embedded system; And
(d) load this root file system to this embedded system according to this root file system image file.
2. the method for claim 1, wherein step (c) also includes:
Use the automatic initial orders of this root file system to read a default expanding device enactment document and how to judge this stored root file system image file of this expanding device of access.
3. method as claimed in claim 2 wherein should include by default expanding device enactment document:
One pathname, it is to storage address that should root file system image file; And
One annotation data, it is used for setting the access mode of this expanding device.
4. method as claimed in claim 3, wherein this annotation data is one directly to expand instruction, and step (c) this stored root file system image file of this expanding device of direct access via a network not.
5. method as claimed in claim 3, wherein this annotation data is a TCP/IP online-order, and step (c) is come this stored root file system image file of this expanding device of access via a network.
6. method as claimed in claim 5, wherein step (c) uses TFTP, file transfer protocol (FTP), Hypertext Transport Protocol, network file system(NFS) or server message frame agreement to come via this stored root file system image file of this expanding device of this network access.
7. method as claimed in claim 5, wherein this network is a Internet, and step (c) also includes and uses DynamicHost configuration agreement that this embedded system is online to this Internet.
8. embedded system, it includes:
One microprocessor is used for controlling the running of this embedded system;
One first storage device is coupled to this microprocessor; And
One second storage device is coupled to this microprocessor, is used for storing a boot program, a core, and the automatic initial orders of a root file system;
Wherein this microprocessor can load and carry out this boot program from this second memory in regular turn, this core and the automatic initial orders of this root file system, and this microprocessor uses this core to start the automatic initial orders of this root file system reading the stored root file system image file of expanding device that is external in this embedded system, and loads a root file system to this first storage device according to this root file system image file.
9. embedded system as claimed in claim 8, wherein this second storage device also stores a default expanding device enactment document, and this microprocessor is carried out the automatic initial orders of this root file system and read this default expanding device enactment document and how to judge this stored root file system image file of this expanding device of access.
10. embedded system as claimed in claim 8 wherein should include by default expanding device enactment document:
One pathname, it is to storing the address by root file system image file; And
One annotation data, it is used for setting the access mode of this expanding device.
11. embedded system as claimed in claim 10, wherein this annotation data is a directly expansion instruction, this embedded system also includes a connecting interface and is coupled to this expanding device, and this microprocessor is carried out the automatic initial orders of this root file system with via this connecting interface but not a network comes this stored root file system image file of this expanding device of direct access.
12. embedded system as claimed in claim 10, wherein this annotation data is a TCP/IP online-order, this embedded system also includes a network interface and is coupled to this expanding device, and then this microprocessor is carried out the automatic initial orders of this root file system to come this stored root file system image file of this expanding device of access via this network interface and a network.
13. embedded system as claimed in claim 12, wherein this microprocessor is carried out the automatic initial orders of this root file system to use TFTP, file transfer protocol (FTP), Hypertext Transport Protocol, network file system(NFS) or server message frame agreement next via this stored root file system image file of this expanding device of this network access.
14. embedded system as claimed in claim 12, wherein this network is a Internet, and this microprocessor is carried out the automatic initial orders of this root file system and to use DynamicHost configuration agreement this embedded system is online to this Internet.
15. embedded system as claimed in claim 8, wherein this first storage device is a volatile memory, and this second storage device is a nonvolatile memory.
16. the auto-loading system of a root file system, it includes:
One embedded system, it includes:
One microprocessor is used for controlling the running of this embedded system;
One first storage device is coupled to this microprocessor; And
One second storage device is coupled to this microprocessor, is used for storing a boot program, a core, and the automatic initial orders of a root file system; And
One expanding device is external in this embedded system, is used for storing a root file system image file;
Wherein this microprocessor can load and carry out this boot program from this second memory in regular turn, this core and the automatic initial orders of this root file system, and this microprocessor uses this core to start the automatic initial orders of this root file system reading this stored root file system image file of this expanding device, and loads this root file system to this first storage device according to this root file system image file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510008394 CN1821960A (en) | 2005-02-18 | 2005-02-18 | Embedded system for automatic loading root file system automatic loading system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510008394 CN1821960A (en) | 2005-02-18 | 2005-02-18 | Embedded system for automatic loading root file system automatic loading system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1821960A true CN1821960A (en) | 2006-08-23 |
Family
ID=36923348
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200510008394 Pending CN1821960A (en) | 2005-02-18 | 2005-02-18 | Embedded system for automatic loading root file system automatic loading system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1821960A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103106091A (en) * | 2013-01-31 | 2013-05-15 | 深圳市开立科技有限公司 | Start-up system and method of operating system based on removable storage media |
| CN103577210A (en) * | 2012-08-06 | 2014-02-12 | 广州三星通信技术研究有限公司 | System and method for mounting between mobile terminals |
| CN106502961A (en) * | 2016-10-26 | 2017-03-15 | 合肥润客软件科技有限公司 | A kind of operational approach for dsp software development system |
-
2005
- 2005-02-18 CN CN 200510008394 patent/CN1821960A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103577210A (en) * | 2012-08-06 | 2014-02-12 | 广州三星通信技术研究有限公司 | System and method for mounting between mobile terminals |
| CN103106091A (en) * | 2013-01-31 | 2013-05-15 | 深圳市开立科技有限公司 | Start-up system and method of operating system based on removable storage media |
| CN106502961A (en) * | 2016-10-26 | 2017-03-15 | 合肥润客软件科技有限公司 | A kind of operational approach for dsp software development system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1313941C (en) | Method for data exchange between data handling equipment and operating system | |
| US7523140B2 (en) | File system that manages files according to content | |
| CN1277213C (en) | A flash memory file system management method | |
| US7725700B2 (en) | Embedded system, automatic loading system, and method capable of automatically loading a root file system | |
| TWI465936B (en) | File system and methods for managing files according to application | |
| CN1261868C (en) | Method of rapid computer start-up | |
| CN101038551A (en) | Method for implementing the start of Linux operation system in mobile hard disk | |
| CN101030146A (en) | Method and system for updating fastener | |
| CN101650660A (en) | Booting a computer system from central storage | |
| CN1848087A (en) | Using usb memory device to recover operating system | |
| CN1825283A (en) | Method for implementing hardware image starting optimizing of embedded operating system | |
| CN1864138A (en) | Memory management with defragmentation in a computing device | |
| CN101042703A (en) | Method for managing metadata of file system using dbms | |
| CN105824678A (en) | Method and device for installing operating system | |
| EP2557497A1 (en) | Method for improving booting of a computing device | |
| CN1821960A (en) | Embedded system for automatic loading root file system automatic loading system and method | |
| CN108647034B (en) | Method for installing multiple operating systems on single mobile hard disk | |
| US20050257218A1 (en) | Method for automatically downloading and installing driver of peripheral | |
| CN1892597A (en) | Method for renewing hand-held device operation function through insert-and-use storage device | |
| CN1338682A (en) | Electronic device, apparatus therewith and data reading-out method according to relevant application file | |
| JP4816740B2 (en) | Information processing apparatus, information processing method, and program | |
| CN1447258A (en) | Networked computers with no local operation system | |
| CN1534473A (en) | Starting system for diskless operating station and its method | |
| CN101036121A (en) | Incremental provisioning of software | |
| CN1904828A (en) | Dynamic starting up system and method, and method for structuring mapping document of operation system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |