Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
a51aaa98
Commit
a51aaa98
authored
5 years ago
by
Peter Palfrader
Browse files
Options
Downloads
Patches
Plain Diff
iterate on new-machine-hetzner-robot.mdwn
parent
a99ea3a6
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tsa/howto/new-machine-hetzner-robot.mdwn
+13
-11
13 additions, 11 deletions
tsa/howto/new-machine-hetzner-robot.mdwn
with
13 additions
and
11 deletions
tsa/howto/new-machine-hetzner-robot.mdwn
+
13
−
11
View file @
a51aaa98
...
...
@@ -112,6 +112,8 @@ which we'll use below.
--password "$ROOTPASSWORD" \
--remove-configs --defaultinterfaces
umount /target/run/udev /target/run
4. Once the bootstrapping is complete, you still need to make sure
the system can boot as, the above doesn't (unfortunately)
configure everything for you. First, make a reasonable etc/fstab:
...
...
@@ -129,25 +131,25 @@ which we'll use below.
repository.
cd /target && bash /root/tsa-misc/scripts/tor-install-luks-setup
5
. Review the crypto configuration:
6
. Review the crypto configuration:
cat /target/etc/crypttab
6
. mount the helper filesystems once more
7
. mount the helper filesystems once more
for fs in dev proc run sys ; do
mount -o bind /$fs "/target/$fs";
done
7
. Do the same with the RAID configuration, probably with something like:
8
. Do the same with the RAID configuration, probably with something like:
chroot /target sh -c "/usr/share/mdadm/mkconf > /etc/mdadm/mdadm.conf"
8
. install grub on any secondary disk, for instance
9
. install grub on any secondary disk, for instance
chroot /target grub-install /dev/nvme1n1
9
. Review the network configuration:
10
. Review the network configuration:
cat /target/etc/network/interfaces
...
...
@@ -158,19 +160,19 @@ which we'll use below.
allow-hotplug eth0
iface eth0 inet dhcp
1
0
. Copy paste your key into the root's authorized keys, just to make
1
1
. Copy paste your key into the root's authorized keys, just to make
sure you can login:
mkdir -p /target/root/.ssh/ &&
cp /root/.ssh/authorized_keys /target/root/.ssh/authorized_keys
1
1
. If any of those latter things changed, you need to regenerate the
1
2
. If any of those latter things changed, you need to regenerate the
initramfs:
chroot /target update-initramfs -u
chroot /target update-grub
1
2
. umount things
1
3
. umount things
umount /target/run/udev
for fs in dev proc run sys ; do
umount /target/$fs
...
...
@@ -178,15 +180,15 @@ which we'll use below.
umount /target/boot
cd / && umount /target
1
3
. close things
1
4
. close things
vgchange -a n
cryptsetup luksClose cpv_nvme
for i in /dev/md/*; do mdadm --stop $i; done
1
4
. Document the LUKS passphrase and root password in `tor-passwords`
1
5
. Document the LUKS passphrase and root password in `tor-passwords`
1
5
. Cross fingers and reboot:
1
6
. Cross fingers and reboot:
reboot
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment