initial commit

This commit is contained in:
l_samenv 2024-01-24 10:04:43 +01:00
parent fafeca9e1a
commit e11dd89253
10 changed files with 71 additions and 90 deletions

View File

@ -1,93 +1,5 @@
# boot_tiny # boot_tiny
TinyCoreLinux system got a bootable USB stick for installing an APU from scratch
see aputools/README.md for details
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://gitlab.psi.ch/samenv/boot_tiny.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.psi.ch/samenv/boot_tiny/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

BIN
core.gz Normal file

Binary file not shown.

BIN
mbr.bin Normal file

Binary file not shown.

10
reg Normal file
View File

@ -0,0 +1,10 @@
echo -n "new hostname: "
read hostname
sudo hostname $hostname
echo "address of leftmost socket eth0 (for control box):"
ifconfig | grep eth0
echo " "
echo "address of rightmost socket (for bare apu):"
ifconfig | grep eth3
echo " "
echo "register $hostname to packet fence and connect LAN to corresponding socket"

27
ssh/id_rsa Normal file
View File

@ -0,0 +1,27 @@
-----BEGIN RSA PRIVATE KEY-----
MIIEowIBAAKCAQEA5tBw9eCW0caoCy+ugKmCIr/qYvAgCtvRqyEEdS9IMwCy7PwR
xHwEXLl86QAYroviRN6adMW6K9exFfTWovE8AvvqIU4RSX53DTSTMzJyz1DAJGGb
hILeWobw2+1YblCbyaxvbe9Lm3qlVyqxuuPC1xp/9+5OULgZZTTomHJl+ff/mS37
3Mo568dXEhou1zLHz9wfLhvVkubOB5bi4VRxPpk78WzKqSQBB2cgMKtIEzngbNcT
E/+ScGiAahfipphSe4dsQ91P7njsRe1vNHAnR30EKBX0sLRL6S4UpvC1NF0OJQc9
6LyrdiPgxM4OuuQbz4DJitPtFWDZMFL/52nO+wIDAQABAoIBABuGCaJYWMPFI67J
zc5L6FfKeOG5bqi808DLXCO5MqvaTnvSBzBd9Ys1Fz8VotvVlHLP9K0uEug9fUF4
A8xEZfqZHa9BBvCzovCxL0hwoJ42K+NqvEfN70PuSXSAVgY5mIoxBMygN2zf8C13
yt/VXxuVbmMbSL15ZpXZ/E6Jfb2T6iApWqKs62vn740BHdDO4iACu02aA1uFUilZ
f7xRYWmNZmKkx727+QYXqp2r1USrBCxSD5/dFavudexAgCYrg4+anSyUttHEWudU
MzNNeo02V3eGOewnok/Q3quW21TarROh1c7d5iObulWZM1lLyxKHGV27JSPyJiEQ
X5DDzKkCgYEA/gkMtvOl6WBWzCb9q6HMfSAVsWWaaLStU/furKh6DAlaCAQ8E/4G
nusAwurnkZ7JeMf/SmuiGldTrp7Fy5rRqvOcMgtepsuh2MGI9VXoPaA+/3CI1+MY
tze6kVQURbSBho7Jzz8po30uq1Dbi0RBbJROd9WglDGH+mKmkTIi5BUCgYEA6Jlq
2WZKRwSZFNy94cgyJNrr5KY7GKGJDiLMcFcE26DtT6NRELwXsP0oyi4hsi4RDYy5
x5ylv1hU7kUZaAiLRhsw4I6VzqCwVbr+8XNTeQKjpIuZxmi6pwXLvu1kzsSMwASa
WdagIkr8reykKMY7Sintf8U8Kcgf86FWECH0Ws8CgYEAqOH5SvOF3DXI3mYZhG3H
VXPsGAhU88ER7d3JFY3XvYLGEMhH7H6XhjTzR6IFGwE2LY7AQIh3tw1RO6igFHCz
bPQRZg+6+CYuTby0QW3APJ/44ba9stBuEPgClzUPWRvcdEkfDyGNm/vP9+KEYfyZ
hga+d9pUq9CV9rZ4x9RN79UCgYBJHLAxVa3TVOapYBlvdvYMD6RGYtoAjAYAo3+P
cErenl75wWQh1n277Fd99bIxx7kkgS+ERwDyfFl169JomQbuKm3ap/b+1BOZXwXz
70Q1rVayyg60BwdkqLW6dfRR6gYz9T5vLr93CAsUwGV5S5YnYbZ9iwm2OGmSswvS
VlnwkQKBgDfJw+nO0C4gMoBCRR+I78KDu6dVAgTdfaUupCiuFPuJUoAstndeKd1f
3hb1f2Y+mqfL+Y6O5jkHDz7oMCoZzbH78tpA0OdIgSlIiImtD9BW74wqkjsrGGSi
2NmhoS7oo0RDjWyNQsMG4Paj5bEiUJKIFA2koIi387Dxy9lqnRVD
-----END RSA PRIVATE KEY-----

1
ssh/known_hosts Normal file
View File

@ -0,0 +1 @@
samenv,129.129.138.218 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBPSxJ8gYfWa7Nt9BDl0B9dy6/flgafRZCAoFAtXsPufA39yHJMSb16quRefHZ0Jcvl06Xqm+DEoJ26ySCvQ8irg=

9
syslinux.cfg Normal file
View File

@ -0,0 +1,9 @@
SERIAL 0 115200
CONSOLE 0
default centos
ALLOWOPTIONS 0
TIMEOUT 600
label centos
kernel vmlinuz
append initrd=core.gz inst.stage2=hd:LABEL=BOOT_TINY quiet console=ttyS0,115200n8

12
tiny Normal file
View File

@ -0,0 +1,12 @@
tce-load -wi nano
tce-load -wi lz4
tce-load -wi openssh
sudo /usr/local/etc/init.d/openssh start
sudo chpasswd << EOF
tc:tc
root:root
EOF
cp -r ssh ~/.ssh
sudo chmod go-r ~/.ssh/id_rsa
ifconfig | grep 'inet addr'

BIN
vmlinuz Normal file

Binary file not shown.

10
write_to_ssd Normal file
View File

@ -0,0 +1,10 @@
sh tiny
BOXIMG=boxes/images
echo ""
echo "images from l_samenv@samenv:$BOXIMG:"
echo ""
ssh l_samenv@samenv "cd $BOXIMG; ls apumaster*.lz4"
echo ""
read -p "which image? " IMG
echo "write to stick"
ssh l_samenv@samenv "dd if=$BOXIMG/$IMG bs=512k" | lz4 -d | sudo dd of=/dev/sda bs=512k