location of config.txt

[wysiwyg]

Good afternoon all!  I was playing around with the prior release (8.x) of the piCore and noticed that the files that should belong inside /boot (according to the rpi docs) are all in the root of the first partition.  Was this change for any particular reason?  How would I be able to move them back into /boot?

The files in question seem to be: config.txt, bcm27*, and possibly the bootcode.bin and start*.elf

The cmdline.txt* are just modifications to config.txt it looks like, not sure about fixup_*.dat files...

Any help would greatly be appreciated!

Thanks,
Dave

[wysiwyg]

In addition, I noticed the included kernels have a .img placed at the end.  Is there something specific about these kernels to give them that naming convention or are they just normal compiled kernels with that file extension?

[bmarkus]

piCore never had  /boot. It is not a derivate of Raspbian.

[wysiwyg]

Thanks for the reply bmarkus.  So what would need to be done in order to get it to go back into /boot?

[bmarkus]

Thanks for the reply bmarkus.  So what would need to be done in order to get it to go back into /boot?

As I told there are no /boot and there will be no /boot. Why do you need it? If you can't leave without it, do it yourself

Code: [Select]

ln -s /mnt/mmcblk0p1 /boot
It is LINUX.

[patrikg]

cmdline.txt is not the same as config.txt, config.txt refers to cmdline.txt so you could use different cmdline.txt files.

cmdline.txt is files, is for the arguments line to the kernel.

And one thing to...raspberry pi can't boot with Linux partition like ext4, so you must have first a fat partition to boot the Broadcom Soc firmware files. These files is not in some boot directory.

But you are welcome as Bela suggest just to make a static link from the ext4 partition directory boot to the fat partition root.

[wysiwyg]

Thanks for the reply bmarkus.  So what would need to be done in order to get it to go back into /boot?

As I told there are no /boot and there will be no /boot. Why do you need it? If you can't leave without it, do it yourself

Code: [Select]

ln -s /mnt/mmcblk0p1 /boot
It is LINUX.

I understand that your build does not have a /boot directory, but that does not mean that others do not want to stick with tradition.  The hack you suggest is not what I am looking for.  If you have advice on returning it to the standard location, I am all ears!

[wysiwyg]

Thanks for the reply patrikg!  I have already re-located some of the files into /boot (including cmdline.txt), but several of them will not relocate without additional steps.  As eluded to by bmarkus, the manufacturer of the RPi places things in the traditional /boot directory which is what I would like to return to.  And thanks for the tips on the fat32 partition - already knew that though.

[bmarkus]

If you want to follow tradition that's fine use Raspbian. But please stop trolling.

[wysiwyg]

I would but our distro is based on TC.

And can you please explain to me how I am trolling?  I have never seen a person asking for help being accused of trolling...

[Misalf]

I'm currently looking at the contends of a µSD card with Rasbpian installed, mounted from my netbook's SD card slot (sdb):

Code: [Select]

$ \ls -lA  /mnt/sdb1
total 20480
-rwxrwxrwx 1 root root   18693 Nov 20  2016 COPYING.linux
-rwxrwxrwx 1 root root    1494 Nov 20  2016 LICENCE.broadcom
-rwxrwxrwx 1 root root   18974 Sep 23  2016 LICENSE.oracle
drwxrwxrwx 2 root root    8192 Okt  9  2016 System Volume Information
-rwxrwxrwx 1 root root   14273 Nov 20  2016 bcm2708-rpi-b-plus.dtb
-rwxrwxrwx 1 root root   14010 Nov 20  2016 bcm2708-rpi-b.dtb
-rwxrwxrwx 1 root root   13964 Nov 20  2016 bcm2708-rpi-cm.dtb
-rwxrwxrwx 1 root root   15356 Nov 20  2016 bcm2709-rpi-2-b.dtb
-rwxrwxrwx 1 root root   15992 Nov 20  2016 bcm2710-rpi-3-b.dtb
-rwxrwxrwx 1 root root   15350 Nov 20  2016 bcm2710-rpi-cm3.dtb
-rwxrwxrwx 1 root root   17932 Nov 20  2016 bootcode.bin
-rwxrwxrwx 1 root root     136 Nov 20  2016 cmdline.txt
-rwxrwxrwx 1 root root    1701 Okt  7  2016 config.txt
-rwxrwxrwx 1 root root    6620 Nov 20  2016 fixup.dat
-rwxrwxrwx 1 root root    2527 Nov 20  2016 fixup_cd.dat
-rwxrwxrwx 1 root root    9751 Nov 20  2016 fixup_db.dat
-rwxrwxrwx 1 root root    9749 Nov 20  2016 fixup_x.dat
-rwxrwxrwx 1 root root     145 Sep 23  2016 issue.txt
-rwxrwxrwx 1 root root 4129840 Nov 20  2016 kernel.img
-rwxrwxrwx 1 root root 4231160 Nov 20  2016 kernel7.img
drwxrwxrwx 2 root root    8192 Nov 20  2016 overlays
-rwxrwxrwx 1 root root 2821604 Nov 20  2016 start.elf
-rwxrwxrwx 1 root root  633636 Nov 20  2016 start_cd.elf
-rwxrwxrwx 1 root root 4954756 Nov 20  2016 start_db.elf
-rwxrwxrwx 1 root root 3904260 Nov 20  2016 start_x.elf

$ \ls -lA  /mnt/sdb2
total 88
drwxr-xr-x   2 root root  4096 Sep 23  2016 bin
drwxr-xr-x   2 root root  4096 Sep 23  2016 boot
drwxr-xr-x   4 root root  4096 Sep 23  2016 dev
drwxr-xr-x 119 root root  4096 Nov 20  2016 etc
drwxr-xr-x   4 root root  4096 Okt  7  2016 home
drwxr-xr-x  19 root root  4096 Sep 23  2016 lib
drwx------   2 root root 16384 Sep 23  2016 lost+found
drwxr-xr-x   3 root root  4096 Sep 23  2016 media
drwxr-xr-x   2 root root  4096 Sep 23  2016 mnt
drwxr-xr-x   7 root root  4096 Okt  5  2016 opt
drwxr-xr-x   2 root root  4096 Jan  7  2015 proc
drwx------   4 root root  4096 Okt  4  2016 root
drwxr-xr-x   5 root root  4096 Sep 23  2016 run
drwxr-xr-x   2 root root  4096 Sep 23  2016 sbin
drwxr-xr-x   2 root root  4096 Sep 23  2016 srv
drwxr-xr-x   2 root root  4096 Apr 12  2015 sys
drwxrwxrwt   9 root root  4096 Nov 26  2016 tmp
drwxr-xr-x  11 root root  4096 Sep 23  2016 usr
drwxr-xr-x  11 root root  4096 Sep 23  2016 var

$ \ls -lA  /mnt/sdb2/boot/
total 0

I'm not an expert but the  /boot  directory doesn't seem to be used traditionally to me? It's empty; boot files are in root ("/") of the first partition.

[bmarkus]

I would but our distro is based on TC.

And can you please explain to me how I am trolling?  I have never seen a person asking for help being accused of trolling...

Forks are not supported. Don't ask a system to be changed because it doesn't fit to your fork. If it doesn't fit to your fork, chose another base for your fork, make a new fork, whatever you want. It is GPL, you are free to do whatever you want as long as you stick to GPl rules.

It is your problem, not our.

[wysiwyg]

@misalf That's interesting because their online documentation consistently mentions and uses /boot.  That being said, Linux in general does traditionally use /boot.  I wonder when they deviated from that.  Also, as stated to bmarkus, I can't use raspbian because our distro is based on TC.  Thanks for the tips though!

[wysiwyg]

I would but our distro is based on TC.

And can you please explain to me how I am trolling?  I have never seen a person asking for help being accused of trolling...

Forks are not supported. Don't ask a system to be changed because it doesn't fit to your fork. If it doesn't fit to your fork, chose another base for your fork, make a new fork, whatever you want. It is GPL, you are free to do whatever you want as long as you stick to GPl rules.

It is your problem, not our.

It seems you have topic creep as there was no mention of this in the OP or any of my replies.  Additionally, you are an intelligent person bmarkus, but clearly you do not know the definition of trolling so I am going to help you out:

http://lmgtfy.com/?q=definition+of+trolling

As you can see I do not fit that definition.  And as the saying goes "misery loves company", but you won't find it here.  So unless you have something beneficial to add to a conversation, I am just going to ignore you.