Oozie時bin/oozied.sh start或bin/oozied.sh run出現Bootstrap程序無法啟動，http://bigdatamaster:11000/oozie介面也無法開啟？E0103: Could not load servi
不多說，直接上乾貨！
問題詳情
[[email protected] oozie-4.1.0-cdh5.5.4]$ bin/oozied.sh start Setting OOZIE_HOME: /home/hadoop/app/oozie-4.1.0-cdh5.5.4 Setting OOZIE_CONFIG: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf Sourcing: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf/oozie-env.sh setting CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m" setting OOZIE_CONF=${OOZIE_HOME}/conf setting OOZIE_DATA=${OOZIE_HOME}/data setting OOZIE_LOG=${OOZIE_HOME}/logs setting CATALINA_BASE=${OOZIE_HOME}/oozie-server setting CATALINA_TMPDIR=${OOZIE_HOME}/oozie-server/temp setting CATALINA_OUT=${OOZIE_LOG}/catalina.outSetting OOZIE_CONFIG_FILE: oozie-site.xml Using OOZIE_DATA: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/data Using OOZIE_LOG: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs Setting OOZIE_LOG4J_FILE: oozie-log4j.properties Setting OOZIE_LOG4J_RELOAD: 10 Setting OOZIE_HTTP_HOSTNAME: bigdatamaster Setting OOZIE_HTTP_PORT:11000 Setting OOZIE_ADMIN_PORT: 11001 Setting OOZIE_HTTPS_PORT: 11443 Setting OOZIE_BASE_URL: http://bigdatamaster:11000/oozie Using CATALINA_BASE: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server Setting OOZIE_HTTPS_KEYSTORE_FILE: /home/hadoop/.keystore Setting OOZIE_HTTPS_KEYSTORE_PASS: password Setting OOZIE_INSTANCE_ID: bigdatamaster Using CATALINA_OUT: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs/catalina.out Setting CATALINA_PID: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp/oozie.pid Using CATALINA_OPTS: -Xmx1024m -Dderby.stream.error.file=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs/derby.log Adding to CATALINA_OPTS: -Doozie.home.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4 -Doozie.config.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf -Doozie.log.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs -Doozie.data.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/data -Doozie.instance.id=bigdatamaster -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10 -Doozie.http.hostname=bigdatamaster -Doozie.admin.port=11001 -Doozie.http.port=11000 -Doozie.https.port=11443 -Doozie.base.url=http://bigdatamaster:11000/oozie -Doozie.https .keystore.file=/home/hadoop/.keystore -Doozie.https.keystore.pass=password -Djava.library.path= Using CATALINA_BASE: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server Using CATALINA_HOME: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server Using CATALINA_TMPDIR: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp Using JRE_HOME: /home/hadoop/app/jdk Using CLASSPATH: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/bin/bootstrap.jar Using CATALINA_PID: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp/oozie.pid Existing PID file found during start. Removing/clearing stale PID file. [[email protected] oozie-4.1.0-cdh5.5.4]$
檢視日誌
2017-05-08 22:12:45,253 INFO XLogService:520 - SERVER[bigdatamaster] Log4j configuration file [oozie-log4j.properties] 2017-05-08 22:12:45,257 INFO XLogService:520 - SERVER[bigdatamaster] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 22:12:45,258 INFO XLogService:520 - SERVER[bigdatamaster] Log4j reload interval [10 sec] 2017-05-08 22:12:45,361 INFO ConfigurationService:520 - SERVER[bigdatamaster] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 22:12:45,367 INFO ConfigurationService:520 - SERVER[bigdatamaster] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 22:12:45,371 INFO ConfigurationService:520 - SERVER[bigdatamaster] Oozie conf file [oozie-site.xml] 2017-05-08 22:12:47,178 INFO ConfigurationService:520 - SERVER[bigdatamaster] Configuration change via System Property, [oozie.base.url]=[http://bigdatamaster:11000/oozie] 2017-05-08 22:12:47,179 INFO ConfigurationService:520 - SERVER[bigdatamaster] Configuration change via System Property, [oozie.http.hostname]=[bigdatamaster] 2017-05-08 22:12:47,180 INFO ConfigurationService:520 - SERVER[bigdatamaster] Configuration change via System Property, [oozie.http.port]=[11000] 2017-05-08 22:12:47,193 INFO ConfigurationService:520 - SERVER[bigdatamaster] Configuration change via System Property, [oozie.instance.id]=[bigdatamaster] 2017-05-08 22:12:47,196 WARN ConfigurationService:523 - SERVER[bigdatamaster] System property [oozie.https.keystore.pass] no defined in Oozie configuration, ignored 2017-05-08 22:12:47,196 WARN ConfigurationService:523 - SERVER[bigdatamaster] System property [oozie.admin.port] no defined in Oozie configuration, ignored 2017-05-08 22:12:47,197 WARN ConfigurationService:523 - SERVER[bigdatamaster] System property [oozie.https.port] no defined in Oozie configuration, ignored 2017-05-08 22:12:47,198 WARN ConfigurationService:523 - SERVER[bigdatamaster] System property [oozie.https.keystore.file] no defined in Oozie configuration, ignored 2017-05-08 22:12:47,204 INFO ConfigurationService:520 - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.hostname], Value [bigdatamaster] 2017-05-08 22:12:47,205 INFO ConfigurationService:520 - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.instance.id], Value [bigdatamaster] 2017-05-08 22:12:47,205 INFO ConfigurationService:520 - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.port], Value [11000] 2017-05-08 22:12:47,232 WARN ConfigurationService:523 - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.hosts] 2017-05-08 22:12:47,233 WARN ConfigurationService:523 - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.groups] 2017-05-08 22:12:47,246 WARN Services:523 - SERVER[bigdatamaster] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 22:12:47,248 INFO Services:520 - SERVER[bigdatamaster] Exiting null Entering NORMAL 2017-05-08 22:12:47,254 INFO Services:520 - SERVER[bigdatamaster] Initialized runtime directory [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp/oozie-hado4767423416871899036.dir] 2017-05-08 22:12:47,375 FATAL Services:514 - SERVER[bigdatamaster] Runtime Exception during Services Load. Check your list of 'oozie.services' or 'oozie.services.ext' 2017-05-08 22:12:47,387 FATAL Services:514 - SERVER[bigdatamaster] E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found org.apache.oozie.service.ServiceException: E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found at org.apache.oozie.service.Services.loadServices(Services.java:309) at org.apache.oozie.service.Services.init(Services.java:213) at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4709) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:802) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:676) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:602) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:503) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1068) at org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1060) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:759) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:2178) at org.apache.oozie.service.ConfigurationService$LogChangesConfiguration.getClasses(ConfigurationService.java:400) at org.apache.oozie.service.ConfigurationService.getClasses(ConfigurationService.java:561) at org.apache.oozie.service.Services.loadServices(Services.java:288) ... 26 more Caused by: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2105) at org.apache.oozie.util.XConfiguration.getClassByName(XConfiguration.java:194) at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:2174) ... 29 more [[email protected] logs]$
解決辦法
http://community.cloudera.com/t5/Cloudera-Manager-Installation/Oozie-startup-failure-ERROR-XSDB6/td-p/11584
檢視
[[email protected] oozie-4.1.0-cdh5.5.4]$ ps aux | grep oozie hadoop 18405 0.0 0.0 103256 844 pts/2 S+ 22:22 0:00 grep oozie [[email protected] oozie-4.1.0-cdh5.5.4]$[[email protected] oozie-4.1.0-cdh5.5.4]$ ps aux | grep oozie|grep -v grep
[[email protected] oozie-4.1.0-cdh5.5.4]$
說明oozie沒程序啟動
然後
Its likely that another instance of Oozie may be running on the machine already thats causing this. You can first check for such an instance via a "ps aux | grep oozie" command perhaps, and kill it if one is indeed running.
If there's no other instance, then its likely that the OOME caused crash/kill has left the DB lock under the derby directory, causing the further startups to fail as it now thinks the DB is in use (Derby DB supports only 1 max. current user, which is why we strongly discourage its use in your clusters - consider moving off of Derby when you get a chance).
To resolve that, run: rm /var/lib/oozie/data/*.lck
After this, start up the Oozie server again, and it should come up now.
Once again: Consider changing the default DB of Oozie to MySQL/etc. instead of Derby. You'll avoid a lot of other pains that will come later if you continue to use it.
[[email protected] oozie-4.1.0-cdh5.5.4]$ jps 3205 Bootstrap 2328 NameNode 2483 SecondaryNameNode 3215 Jps 2182 QuorumPeerMain 2654 ResourceManager [[email protected] oozie-4.1.0-cdh5.5.4]$
2017-05-09 09:20:47,007 WARN ConfigurationService:523 - SERVER[bigdatamaster] System property [oozie.https.keystore.file] no defined in Oozie configuration, ignored 2017-05-09 09:20:47,010 INFO ConfigurationService:520 - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.hostname], Value [bigdatamaster] 2017-05-09 09:20:47,010 INFO ConfigurationService:520 - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.instance.id], Value [bigdatamaster] 2017-05-09 09:20:47,011 INFO ConfigurationService:520 - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.port], Value [11000] 2017-05-09 09:20:47,036 WARN ConfigurationService:523 - SERVER[bigdatamaster] Invalid configuration defined, [oozie.use.system.libpath] 2017-05-09 09:20:47,038 WARN ConfigurationService:523 - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.hosts] 2017-05-09 09:20:47,039 WARN ConfigurationService:523 - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.groups] 2017-05-09 09:20:47,065 WARN Services:523 - SERVER[bigdatamaster] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-09 09:20:47,077 INFO Services:520 - SERVER[bigdatamaster] Exiting null Entering NORMAL 2017-05-09 09:20:47,083 INFO Services:520 - SERVER[bigdatamaster] Initialized runtime directory [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp/oozie-hado2668923471340073361.dir] 2017-05-09 09:20:47,258 FATAL Services:514 - SERVER[bigdatamaster] Runtime Exception during Services Load. Check your list of 'oozie.services' or 'oozie.services.ext' 2017-05-09 09:20:47,282 FATAL Services:514 - SERVER[bigdatamaster] E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found org.apache.oozie.service.ServiceException: E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found at org.apache.oozie.service.Services.loadServices(Services.java:309) at org.apache.oozie.service.Services.init(Services.java:213) at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4709) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:802) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:676) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:602) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:503) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:2178) at org.apache.oozie.service.ConfigurationService$LogChangesConfiguration.getClasses(ConfigurationService.java:400) at org.apache.oozie.service.ConfigurationService.getClasses(ConfigurationService.java:561) at org.apache.oozie.service.Services.loadServices(Services.java:288) ... 26 more Caused by: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2105) at org.apache.oozie.util.XConfiguration.getClassByName(XConfiguration.java:194) at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:2174) ... 29 more [[email protected] logs]$後來，我又在網上查了下，說，試試，是否oozie在啟動的時候，沒有許可權對oozie-server進行讀寫。
[[email protected] oozie-4.1.0-cdh5.5.4]$ chmod 777 oozie-server
然後，我又執行這條命令。
同時，還看到網上說，在$OOZIE_HOME/libext目錄下，解壓ext-2.2.zip。 [[email protected] libext]$ unzip ext-2.2.zip [[email protected] libext]$ chmod -R 777 ext-2.2
相關推薦
Oozie時bin/oozied.sh start或bin/oozied.sh run出現Bootstrap程序無法啟動，http://bigdatamaster:11000/oozie介面也無法開啟？E0103: Could not load servi
不多說，直接上乾貨！ 問題詳情 [[email protected] oozie-4.1.0-cdh5.5.4]$ bin/oozied.sh start Setting OOZIE_HOME: /home/hadoop/app/o
Oozie時bin/oozied.sh start或bin/oozied.sh run出現Bootstrap程序無法啟動，http://bigdatamaster:11000/oozie介面也無法開啟？
不多說，直接上乾貨！ 問題詳情 按照官網 http://archive.cloudera.com/cdh5/cdh/5/oozie-4.1.0-cdh5.5.4/DG_QuickStart.html Start Oozie as a daemon process r
Oozie時出現org.apache.oozie.service.ServiceException: E0103: Could not load service classes, Cannot load JDBC driver class 'com.mys
不多說，直接上乾貨！ 問題詳情 檢視你的$OOZIE_HOME/logs 我的是/home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs/oozie.log檔案 [[email protected] logs]$ c
PLSQL連Oracle資料庫Could not load "……\bin\oci.dll"
64位win7上裝PL/SQL，經常會遇見“Could not load "……\bin\oci.dll"”這個錯誤，我查了一下資料，原因是PL/SQL只對32位OS進行支援，解決方法是
Jmeter-無法啟動，'findstr'不是內部或外部命令，也不是可運行的程序
運行 root 內部 system32 重新 變量 es2017 外部命令 oot 今天有一個同事的jmeter無法安裝，於是幫他看了看，報以下錯誤： JAVA的環境變量沒有配置好，於是重新配置了下環境變量後，再啟動，發現還是不好，於是網上查了下， 發現要在電腦的環境變量
win7啟動盤或PE無法啟動，原因是U盤只支持FAT32不支持NTFS格式
win7啟動盤或PE無法啟動上周周末由於一些原因需要將本來的deepin系統換成windows系統，可是手裏沒有現成的啟動盤，於是上網買了個4G U盤，心想4G也就夠了。U盤到了之後就到網吧去下了個windows7的系統，用軟碟通寫入到了U盤，可是發現啟動時有問題，直接提示找不到winload.exe. 於是
cdh oozie 無法啟動問題Could not load service classes, Cannot create PoolableConnectionFactory
問題描述：在安裝cdh元資料myslq高可用時，使用的是myslq主主複製+keepalived實現。期間發現切換時，出現如下異常資訊！ 花了很長時間尋找問題的原因。因為切換的時候，使用本機命令列是可以連線的，但是誇伺服器就無法連線，沒有去這方面的嘗試，後來使用navicate無法連線後，就推測
記一次springcloud整合到專案中，無法啟動，Failed to start bean 'eurekaAutoServiceRegistration'
貼出錯誤資訊 org.springframework.context.ApplicationContextException: Failed to start bean 'eurekaAutoServiceRegistration'; nested exception is java
應用程式無法啟動，因為應用程式的並行配置不正確。有關詳細資訊，請參閱應用程式事件日誌，或使用命令列sxstrace.exe工具。解決方法
【原創】 轉載請註明出處 問題解決方法僅限於我的情況，就當給大家個提示。 我的電腦環境：Windows 7 64位 編譯器環境：VS2005 出現這個問題可能是因為引用了MFC的東西，並且工程設定為 在共享DLL中使用MFC 【解決方法一】：改為在靜態庫中使用MFC（
程式打包，"錯誤：應用程式無法啟動，因為應用程式的並行配置不正確。有關詳細資訊，請參閱應用程式事件日誌，或使用命令列sxstrace.exe"工具解決辦法
<span style="font-size:18px;">最近專案功能做完，基本測試也過了一下，程式打包，在自己的的電腦上面執行正常，但是當把程式拷貝到其他沒有安裝開發環境的電腦上面，程式報如下錯誤：</span> 一 在網上搜索資料
關於SQL Server 2005服務無法啟動，報3417錯誤。(附帶重灌SQL時解決COM+目錄問題）(轉帖)
那天很是鬱悶，由於長期沒有使用SQL Server 2005，那天用時候居然伺服器啟動不到，報3417錯誤。。。當時沒有找到解決方案，不得已，只有重灌了。那個痛苦哦。。。解除安裝就要花費二三十分鐘，安裝又要用掉一個小時。。。（這是SQL 2005，後來裝SQL 2008的時候
idea在執行時正常，但打包成一個jar執行檔案時出現Could not load JNR C Library問題
在通過java連線cassandra時，其中com.datastax.driver.core是通過maven加入的，通過Idea執行時是正常的，在匯出jar時如果不是將所有的jar打包成一個jar時也是正常的，但是如果將所有的第三方打包成jar，則會出現如下錯誤： 17:3
Qt程式無法啟動，debug時提示During startup program exited with code 0xc0000135
編譯好opencv後，用一個簡單的控制檯程式做測試，在pro檔案中加入了opencv的幾個libopencv_xxx.a的庫檔案，編譯沒有問題，但無法執行，main無法進入。即使沒有使用任務opencv的函式也是如此。 採用單步除錯模式，提示：During startup
使用powerdesigner連線資料庫時出現Non SQL Error : Could not load class com.mysql.jdbc.Drive
Non SQL Error : Could not load class com.mysql.jdbc.Driver 這是因為powerdesigner 無法找到驅動所產生的 解決辦法是：配置系統的classpath 路徑，指定jar 包路徑就好了。 貌似要重啟下powerdesigner，否則還
MDK生成bin檔案通過USB進行IAP升級時，無法啟動
BOOT 更新微控制器內的使用者程式，方式一般都是模擬器，串列埠，網路口，usb DFU，另類一點CAN也行，但是這些方式都有一個共同點，必須要有相應的上位機配合操作，這個比較麻煩。 另一種方式是把我們的裝置通過USB插入電腦，在電腦上映射出一個磁碟，把升級的.bin檔案拷貝到磁碟中，b
linux執行sh指令碼時提示“沒有那個檔案或目錄”
在linux上使用bash XXX.sh執行指令碼時，提示“for reading(No such file or directory)”。 問題原因： 因為作業系統是windows，在windows下編輯的指令碼，所以有可能有不可見字元。指令碼檔案是DOS格式的 即每一行
[uboot]MLO和uboot-spl.bin, uboot.img和uboot.bin
mpi pict bsp with end .com eterm rmi 啟動 前段時間使用TI的am4378芯片，發現系統在SD卡啟動的時候，啟動文件使用的是MLO和uboot.img；而Norflash和eMMC啟動的時候使用的是 uboot-spl.bin和uboo
linux 系統中的 /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin 目錄的區別
。。 process pre this 用戶 unix table mount sent 先來段英文的： /bin This directory contains executable programs which are needed in single user
當文字過長時裁剪（顯示省略號或只裁剪 用CSS方法，不用程序）
fire 省略號 fixed strong face con str 來源 type 原文發布時間為：2009-09-16 —— 來源於本人的百度文章 [由搬家工具導入]CSS中ellipsis()应用【转
idea使用Git提交代碼時忽略指定文件或文件夾
使用 生成 rest 版本控制器 mage 才會 tar 存在 名稱 簡述 使用idea編寫代碼並使用git作為版本控制器的時候，常常不需要提交配置文件以及一些其他不需要提交的文件，可以使用.ignore插件來在上傳的時候忽略一些文件或文件夾。 安裝