<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=6751&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / log2ram with sysv]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=6751</link>
		<description><![CDATA[The most recent posts in log2ram with sysv.]]></description>
		<lastBuildDate>Sat, 02 Aug 2025 22:49:50 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=57033#p57033</link>
			<description><![CDATA[<p>Hi, for those who must tinker, I have used a script to convert systemd to sysvinit programs, look for </p><div class="codebox"><pre><code>sysd2v.sh</code></pre></div><p> search on this forum and others.<br /><a href="https://dev1galaxy.org/viewtopic.php?id=4865" rel="nofollow">https://dev1galaxy.org/viewtopic.php?id=4865</a></p><p>It does not fix package dependencies, only start|stop services...</p><p>I hope this helps.</p>]]></description>
			<author><![CDATA[dummy@example.com (GlennW)]]></author>
			<pubDate>Sat, 02 Aug 2025 22:49:50 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=57033#p57033</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=57022#p57022</link>
			<description><![CDATA[<p>I&#039;ve reworked the Debian package for log2ram to work with sysvinit on Devuan. Please take a look and let me know if there is anything that I should change.<br /><a href="https://git.devuan.org/SteveM/log2ram" rel="nofollow">https://git.devuan.org/SteveM/log2ram</a></p>]]></description>
			<author><![CDATA[dummy@example.com (SteveM)]]></author>
			<pubDate>Sat, 02 Aug 2025 05:46:32 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=57022#p57022</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=53664#p53664</link>
			<description><![CDATA[<p>@cake, re git stores... nowadays I&#039;d suggest codeberg.org<br />and you&#039;re of course also welcome at git.devuan.org</p>]]></description>
			<author><![CDATA[dummy@example.com (ralph.ronnquist)]]></author>
			<pubDate>Fri, 27 Dec 2024 12:08:11 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=53664#p53664</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=53647#p53647</link>
			<description><![CDATA[<div class="quotebox"><blockquote><div><p>Edit#3: sleuthing around the internet today, I guess I should have used su - to get the correct path.</p></div></blockquote></div><p>From my install notes when I seen this come through.</p><div class="codebox"><pre><code>SU changes not noticed here but may be in future so may as well set it up.

Changes in su
- The behavior of su has changed. Use &#039;su -&#039; to get root&#039;s path or use
   the full path to commands if you use only &#039;su&#039;.
    - There are several ways to get the old behavior. The easiest is to
   edit /etc/default/su to add the line:

    ALWAYS_SET_PATH yes

root@9600k:~# cat /etc/default/su
cat: /etc/default/su: No such file or directory
root@9600k:~# nano /etc/default/su
root@9600k:~# cat /etc/default/su
# Added to always have the PATH set for su.

ALWAYS_SET_PATH yes</code></pre></div><p>You might want to create that file on your installs and install the lovely little program apt-listchanges which tells you thing like this when updating your packages..</p>]]></description>
			<author><![CDATA[dummy@example.com (RedGreen925)]]></author>
			<pubDate>Fri, 27 Dec 2024 04:44:30 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=53647#p53647</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=53645#p53645</link>
			<description><![CDATA[<p>Thanks Ralph, I am very much anti microsoft, google etc myself. Please suggest me a new place anyone?</p>]]></description>
			<author><![CDATA[dummy@example.com (cake)]]></author>
			<pubDate>Fri, 27 Dec 2024 04:37:21 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=53645#p53645</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=53644#p53644</link>
			<description><![CDATA[<p>Just a friendly reminer that It&#039;s Never Too Early to stop using Microsoft&#039;s github</p>]]></description>
			<author><![CDATA[dummy@example.com (ralph.ronnquist)]]></author>
			<pubDate>Fri, 27 Dec 2024 03:32:53 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=53644#p53644</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=53638#p53638</link>
			<description><![CDATA[<p>I figured it out, need to to wait until file system in read write mode. Simple fix to add # Required-Start: $local_fs to file inside init.d</p><p>I posted a very quick tutorial of the tutorial I found at ...*edited: I put it on codeberg.org<br />running short on time today</p><p><a href="https://codeberg.org/cake1/log2ram_SysV_Init" rel="nofollow">https://codeberg.org/cake1/log2ram_SysV_Init</a></p>]]></description>
			<author><![CDATA[dummy@example.com (cake)]]></author>
			<pubDate>Fri, 27 Dec 2024 01:00:31 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=53638#p53638</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=52939#p52939</link>
			<description><![CDATA[<p>Hi, thanks Jonny, I tried transientlog and had to modify the install script I believe (removed <span class="bbc">systemctl daemon-reload</span> from install.sh, Anyway I got it to work, but it was unreliable after I installed fail2ban and ufw. It would work if I stopped, deleted the permanentlog file and started it again. So I went searching for someone who has got ram2log working for sysv and I found this &gt; <a href="https://energytalk.co.za/t/gx-device-logging-to-ram-tmpfs-log2ram/2130" rel="nofollow">https://energytalk.co.za/t/gx-device-lo … g2ram/2130</a></p><p>I have 3 Arm sbc devices, one is a old bananapi pro. All are headless and have new fresh devuan installs on them. I followed the tutorial for log2ram above, it all went smooth, seems to work.<br />The other 2 smb&#039;s are located remotely and both running devuan daedalus as well. As I installed to the next one via ssh I did this too I thought this would work but it never came back after I rebooted (end of the install tutorial), so :-(</p><p>Maybe somebody here could look and suggest change(s) to that tutorial. I am not sure if I typed something wrong on my second device or not.<br />The only complaint during install was when entering this (both devices)- <span class="bbc">sudo update-rc.d log2ram-init.sh start 06 S . stop 80 0 6 .</span> I got this: <span class="bbc">update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults</span> otherwise no errors.</p><p>So maybe the tutorial works and maybe its doesn&#039;t. cheers</p><p>Edit: I just thought of this, On the bannanapro install, for root command I do not have to enter sudo first. Such as <span class="bbc">#findmnt</span> on the other 2 I have to enter sudo first <span class="bbc">#sudo findmnt</span> I wonder if this is my problem. The tutorial in link , he did say &quot;IMPORTANT: Install findmnt - needed to log2ram core tool:&quot;<br />hmmmmm</p><p>Edit#2: Actually after more digging around I can use findmnt (/sbin), but not anything located in /bin unless I type sudo first.<br />I bet that could be my problem</p><p>Edit#3: sleuthing around the internet today, I guess I should have used su - to get the correct path. I logged in as a normal user, then &quot;su root&quot; but I guess that is not enough, still need to su - first. Got the remote sbc rebooted and the root file system mounted.&#160; Its just busybox inititramfs and dropbear right now. Log file doesn&#039;t have much of a clue. I&#039;ll get this eventually sorted out and post a reply here, so if it works then there is alternative beside transientlog.</p>]]></description>
			<author><![CDATA[dummy@example.com (cake)]]></author>
			<pubDate>Wed, 13 Nov 2024 07:53:00 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=52939#p52939</guid>
		</item>
		<item>
			<title><![CDATA[Re: log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=51385#p51385</link>
			<description><![CDATA[<p>Okay after researching for another hour or so I found that log2ram is the successor of a project called <span class="bbc"><a href="https://github.com/hi5ato/transientlog" rel="nofollow">transientlog</a></span> which in turn was born out of an article from debian-administration.org called <em><a href="http://web.archive.org/web/20200709233124/https://debian-administration.org/article/661/A_transient_/var/log" rel="nofollow">A transient /var/log</a></em> - back in 2010 when systemd wasn&#039;t yet relevant. </p><p>Therefore I was able to apply <span class="bbc">transientlog</span> almost without modification to my Devuan 5 install and for now it seems to work. It creates a RAM drive on startup and copies all log files into it. On shutdown/reboot it does the opposite. It copies all log files from the RAM drive to the eMMC card. The only thing I modified was the size of the RAM drive - from 25M to 90M because my log folder was already 38M in size.</p><p>I will keep monitoring the script to see if it is stable and report my findings.</p>]]></description>
			<author><![CDATA[dummy@example.com (jonny101)]]></author>
			<pubDate>Sun, 28 Jul 2024 09:28:30 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=51385#p51385</guid>
		</item>
		<item>
			<title><![CDATA[log2ram with sysv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=51381#p51381</link>
			<description><![CDATA[<p>Hi everybody,</p><p>i just got Devuan working on my Odroid N2+ using the <a href="https://oph.mdrjr.net/meveric/images/Bullseye/" rel="nofollow">maveric image</a> as starting point (works flawlessly 🥰).</p><p>Now in order to spare the eMMC I used to run <a href="https://github.com/azlux/log2ram" rel="nofollow">log2ram</a> on it but log2ram is dependent on systemd.<br />According to the developer it should also <a href="https://github.com/azlux/log2ram/issues/16" rel="nofollow">work with init.d</a> only the init script is needed.</p><p>My question is, does anyone use log2ram with sysvinit or knows another simple tool I could use to write logs to ram? I have no experience with sysv so far and thought I&#039;d ask before starting to tinker myself.</p><p>Thank you.</p>]]></description>
			<author><![CDATA[dummy@example.com (jonny101)]]></author>
			<pubDate>Sun, 28 Jul 2024 05:18:25 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=51381#p51381</guid>
		</item>
	</channel>
</rss>
