1*4882a593SmuzhiyunWarning! 2*4882a593Smuzhiyun======== 3*4882a593Smuzhiyun 4*4882a593SmuzhiyunThis directory does *not* contain the root filesystem that you can use 5*4882a593Smuzhiyunon your embedded system. Since Buildroot does not run as root, it 6*4882a593Smuzhiyuncannot create device files and set the permissions and ownership of 7*4882a593Smuzhiyunfiles correctly in this directory to make it usable as a root 8*4882a593Smuzhiyunfilesystem. 9*4882a593Smuzhiyun 10*4882a593SmuzhiyunFor that reason, do *not* use the contents of this directory to mount 11*4882a593Smuzhiyunyour root filesystem over NFS or copy the contents of this directory 12*4882a593Smuzhiyunto a SD card or USB key, thinking it will work as the root filesystem 13*4882a593Smuzhiyunfor your embedded system. It will simply *not* work. 14*4882a593Smuzhiyun 15*4882a593SmuzhiyunInstead, if you need a usable root filesystem, please select one of 16*4882a593Smuzhiyunthe filesystem image formats available in the Buildroot configuration 17*4882a593Smuzhiyuninterface (make menuconfig or others) in the "Filesystem images" 18*4882a593Smuzhiyunsub-menu. If you want to get a filesystem image that you can easily 19*4882a593Smuzhiyunextract to your SD card or to some directory exposed through NFS, 20*4882a593Smuzhiyunplease use the "tar the root filesystem" option. It will generate a 21*4882a593Smuzhiyunimages/rootfs.tar image in your Buildroot output directory, which you 22*4882a593Smuzhiyuncan extract as root: 23*4882a593Smuzhiyun 24*4882a593Smuzhiyun sudo tar -C /destination/of/extraction -xf images/rootfs.tar 25*4882a593Smuzhiyun 26*4882a593SmuzhiyunThose image files are created using the contents of the target/ 27*4882a593Smuzhiyundirectory, but there is a post-processing step to create device files 28*4882a593Smuzhiyunand set ownership/permissions properly even if Buildroot does not run 29*4882a593Smuzhiyunas root. 30