shadowguardian507-irl

Read-only FS on Raspberry Pi

Most embedded devices use a read-only root filesystem. This can make them more resilient to unexpected shutdowns that could otherwise cause data corruption. Depending on your application, you might consider your Pi to be an embedded system. This can also help with some issues that can come from SD card unreliability.

Full instructions and explanations are obtained from this link but you can run these commands directly. I modified some of the instructions for personal convenience.

Login with default username and password: (ArchLinux Arm: alarm, alarm, Raspbian: pi, raspberry)

Optionally enable root over SSH. The rest of these instructions assume you are in root.

nano /etc/ssh/sshd_config

shadowguardian507-irl

iptables
put following in /etc/rc.local

 iptables -I INPUT -p tcp --dport 22 --syn -j ACCEPT
 
 
 update safe files
 
 put following in /etc/sysupgrade.conf
 

shadowguardian507-irl

Taken from http://damsteen.nl/blog/how-to-use-a-serial-connection-to-your-netgear-readynas as it always seems to be down

How-to: Use a serial connection to your Netgear ReadyNAS

It is possible to connect to the command-line interface of your Netgear ReadyNAS using a serial connection. I have seen a very old blog post on the internet describing how to connect via serial to a Infrant ReadyNAS NV but it wasn't very clear how to connect to a Netgear ReadyNAS NVX Pioneer Edition, which I have. I guess I'm not the only one who wants to connect to their ReadyNAS, so I'm sharing my knowlegde here :)

The obvious advantages of a serial connection to your ReadyNAS is that you can experiment with network settings without the fear of rendering your NAS inaccessible. I believe it is also possible to recover the firmware in the event an update fails, although I haven't tried this myself.

Requirements

shadowguardian507-irl

serial pinout

on back of system from left to right (network ports to the left)

not connected , white wire:RXD , green wire:TXD , black:ground

note this is 3.3V logic level

shadowguardian507-irl

Ansible will hang at 'gathering facts' when
  NFS mounts are broken on target server

shadowguardian507-irl

pavucontrol
libcanberra-pulse lib32-libpulse lib32-alsa-lib lib32-alsa-plugins
lib32-jack lib32-libsamplerate lib32-speex

sudo pulseaudio -k
pulseaudio --start

ref https://bbs.archlinux.org/viewtopic.php?id=174946

shadowguardian507-irl

make new service def at /etc/systemd/system/synergy@.service
content 
-------------
[Unit]
Description=Synergy Service [multiuser fixed]
After=network.target

[Service]
Type=simple
Restart=always

shadowguardian507-irl

shift + f = update file being viewed
shift + g = go to end of file

shadowguardian507-irl

if NETLOGN and SYSVOL shares are missing, the DC won't beleve it is a DC, so create shares then from

https://support.microsoft.com/en-us/help/947022/the-netlogon-share-is-not-present-after-you-install-active-directory-domain-services-on-a-new-full-or-read-only-windows-server-2008-based-domain-controller

Cause
This problem occurs when the Netlogon service reads the SysvolReady Flag in the registry very quickly. Then, the Netlogon service tries to share out the \Windows\SYSVOL\domain\scripts folder before the NT File Replication Service (NTFRS) creates this folder.
Workaround
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this issue, set the SysvolReady Flag registry value to "0" and then back to "1" in the registry. To do this, follow these step

shadowguardian507-irl

Keybase proof

I hereby claim:

• I am shadowguardian507-irl on github.
• I am sg507irl (https://keybase.io/sg507irl) on keybase.
• I have a public key ASAWG3QmNaYZMG_wten4qMGXnX0UimsZcro-nYj9Rulh4Qo

To claim this, I am signing this object: