Rocksolid Light

Welcome to Rocksolid Light

mail  files  register  newsreader  groups  login

Message-ID:  

We are MicroSoft. You will be assimilated. Resistance is futile. (Attributed to B.G., Gill Bates)


computers / alt.os.linux.slackware / reusing slacklive usb stick for install

SubjectAuthor
* reusing slacklive usb stick for installJohn Forkosh
`- reusing slacklive usb stick for installJohn Forkosh

1
reusing slacklive usb stick for install

<t8rkhk$mu3$1@reader1.panix.com>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2342&group=alt.os.linux.slackware#2342

  copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!panix!.POSTED.panix3.panix.com!not-for-mail
From: forkosh@panix.com (John Forkosh)
Newsgroups: alt.os.linux.slackware
Subject: reusing slacklive usb stick for install
Date: Tue, 21 Jun 2022 05:21:56 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <t8rkhk$mu3$1@reader1.panix.com>
Injection-Date: Tue, 21 Jun 2022 05:21:56 -0000 (UTC)
Injection-Info: reader1.panix.com; posting-host="panix3.panix.com:166.84.1.3";
logging-data="23491"; mail-complaints-to="abuse@panix.com"
User-Agent: tin/2.6.0-20210823 ("Coleburn") (NetBSD/9.2 (amd64))
 by: John Forkosh - Tue, 21 Jun 2022 05:21 UTC

Seems to fail trying to re-use the same slacklive usb stick
for several installs. Problem turns out to be that it fills
up the usb stick 100% with messages, then complains about
"memory" and hangs. If the usb stick is /dev/sdX and you
mount /dev/sdX3 /mnt/usb/ then cd /mnt/usb/persistence/var/log/
then the two files messages and syslog seem to be the culprits.
What I did was cat /dev/null > messages and cat /dev/null > syslog
but I haven't yet tried to use that stick again for an install.

Will the above procedure work, and let me reuse the stick for install?
And is there another way around the problem? I was thinking about
rm'ing those two files and just symlinking them to /dev/null.
Will that work "permanently", rather than having to empty them out
each time?
--
John Forkosh ( mailto: j@f.com where j=john and f=forkosh )

Re: reusing slacklive usb stick for install

<t9j8cc$kik$1@reader2.panix.com>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2364&group=alt.os.linux.slackware#2364

  copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!panix!.POSTED.panix3.panix.com!not-for-mail
From: forkosh@panix.com (John Forkosh)
Newsgroups: alt.os.linux.slackware
Subject: Re: reusing slacklive usb stick for install
Date: Thu, 30 Jun 2022 04:21:32 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <t9j8cc$kik$1@reader2.panix.com>
References: <t8rkhk$mu3$1@reader1.panix.com>
Injection-Date: Thu, 30 Jun 2022 04:21:32 -0000 (UTC)
Injection-Info: reader2.panix.com; posting-host="panix3.panix.com:166.84.1.3";
logging-data="21076"; mail-complaints-to="abuse@panix.com"
User-Agent: tin/2.6.0-20210823 ("Coleburn") (NetBSD/9.2 (amd64))
 by: John Forkosh - Thu, 30 Jun 2022 04:21 UTC

John Forkosh <forkosh@panix.com> wrote:
> Seems to fail trying to re-use the same slacklive usb stick
> for several installs. Problem turns out to be that it fills
> up the usb stick 100% with messages, then complains about
> "memory" and hangs. If the usb stick is /dev/sdX and you
> mount /dev/sdX3 /mnt/usb/ then cd /mnt/usb/persistence/var/log/
> then the two files messages and syslog seem to be the culprits.
> What I did was cat /dev/null > messages and cat /dev/null > syslog
> but I haven't yet tried to use that stick again for an install.
>
> Will the above procedure work, and let me reuse the stick for install?
> And is there another way around the problem? I was thinking about
> rm'ing those two files and just symlinking them to /dev/null.
> Will that work "permanently", rather than having to empty them out
> each time?

Solved: turns out /var/log/syslog and messages were filling up with
about 100MB/sec of error messages due to a relatively common hardware
"glitch", as soon as dhcpcd starts in my case. And I'm assuming it's
a relatively common glitch because I was able to google a solution:
append="...pci=nommconf..."
added to the kernel options. That completely and immediately cleared
everything up. No more error messages whatsoever.
--
John Forkosh ( mailto: j@f.com where j=john and f=forkosh )

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor