Hi richiec
Welcome to the forum.
Just a few thoughts ...
... TinyCore Linux is well suited to this, but it is far from easy to get working beyond ls working at the command line. This isn’t a tutorial on TinyCore itself — there are many introductions out there ...
Speaking of which, there used to be 2 files (IMPORTANT and README) in
the releases section that never got carried forward after TC12:
http://tinycorelinux.net/12.x/armv6/releases/RPi/ ... but as we’ll see the partition resize process is destructive. ...
I was under the impression resizing could be done non-destructively
using the instructions in README at the above link:
... 2) Delete second partition with 'd' than recreate it with 'n' command.
Use the same starting sector as deleted had and provide end
sectore or size greater than deleted had having enough free space
for Mounted Mode. When finished, exit fdisk with 'w' command. Now
partition size increased but file system size is not yet changed.
3) Reboot piCore. It is necessary to make Kernel aware of changes.
4) After reboot expand file system to the new partition boundaries with
typing the following command as root:
resize2fs /dev/mmcblk0p2
Now you are ready to use the bigger partition. ...
... sudo reboot ...
That should be:
exitcheck.sh reboot
or if you want to shutdown (poweroff):
exitcheck.sh
exitcheck ensures an orderly shutdown/reboot sequence:
exitcheck.sh reboot -> /opt/shutdown.sh -> /sbin/reboot -> /etc/inittab -> /etc/init.d/rc.shutdown
Then /etc/init.d/rc.shutdown performs the following:
1. Sync filesystems
2. Disable swap space
3. Kill all processes
4. Unmount all extensions
5. Delete extensions being updated
6. Unmount tce directory
7. Unmount backup directory
8. Unmount everything else
If you are running command line only (no GUI) and want backups
run automatically when rebooting/shutting down, see here:
https://forum.tinycorelinux.net/index.php/topic,24013.msg151369.html#msg151369 ... There’s in fact no easy way of determining what the actual device is other than trying to mount it and seeing if your files show up. Here’s one way I narrowed it down a bit:
dmesg | grep sda ...
Run:
dmesg | tail
Then plug in your device and run:
dmesg | tail
Your device will be the new dmesg entries. If there are no new
dmesg entries, your device was not recognized.
... What you’re looking for is an sda number (which might be none — my USB stick got mounted just as sda ). ...
The last couple of lines should look something like this:
tc@E310:~$ dmesg | tail
----- Snip -----
[18036149.154763] sdg: sdg1 sdg2
[18036149.157639] sd 7:0:0:0: [sdg] Attached SCSI removable disk
tc@E310:~$
The device in this example is sdg and it has 2 partitions, sdg1 and sdg2.
... tce-load -i dhcpcd.tcz firmware-rpi-wifi.tcz net-usb-6.6.47-piCore-v7.tcz ...
You can also do it like this:
tce-load -i dhcpcd firmware-rpi-wifi net-usb-6.6.47-piCore-v7
tce-load will work with or without the .tcz extension specified.
Typo:
... Edit the /etc/resolv.conf file and add a DNS server, which for me is simply my router of 192.168.1.1:
nameserver 193.168.1.1 ...
Should read:
... Edit the /etc/resolv.conf file and add a DNS server, which for me is simply my router of 192.168.1.1:
nameserver 192.168.1.1 ...
... ifconfig up eth0 ...
You need root permissions to run that
sudo ifconfig up eth0