Re: [DNG] Devuan on Raspberry Pi 3B+. Sound card driver installation.

[al3xu5 / dotcommon]

Il giorno giovedì 14/03/2019 23:23:52 +0100
Edward Bartolo  ha scritto:

> I have a raspberry Pi with a Pi DAC Pro sound for which there is no
> driver installed. Searching online takes me to readily prepared
> operating system images that I do not want to use as I am using
> Devuan. Does anyone know what I should do to be able to use the Pi DAC
> Pro sound card under Devuan? 

I think the 1st thing is the ALSA setup.

Configuration files are:
~/.asoundrc
/etc/modprobe.d/alsausb.conf


I have a barebone computer working as audio server, with an external Audiolab
DAC connected via USB:

~~~
$ cat /proc/asound/cards
 0 [MDAC ]: USB-Audio - Audiolab M-DAC
Lakewest Audio Audiolab M-DAC at usb-:00:1d.0-1.6, full
speed
 1 [HDMI ]: HDA-Intel - HDA Intel HDMI
HDA Intel HDMI at 0xf7d0 irq 43
$ lsusb
...
Bus 001 Device 004: ID 0451:adac Texas Instruments, Inc. 
...
~~~

As an example of what your setup might be, here is my ~/.asoundrc :

~~~
pcm.!default{
  type plug
  slave {
pcm "hw:0,0"
channels 2
  }
}
~~~

and, using a usb connection, my /etc/modprobe.d/alsausb.conf :

~~~
# ALSA portion
options snd cards_limit=2
alias snd-card-0 snd-usb-audio
alias snd-card-1 snd-hda_intel
options snd-usb-audio index=0
options snd-hda_intel index=1
# OSS/Free portion
alias sound-slot-0 snd-usb-audio
alias sound-slot-1 snd-hda-intel
~~~

There are also a lot of system optimization you can do if you want you machine
being a better bit-perfect real-time audio...


Anyway, other setup is required if you are using a software audio server.
I have mpd running, and here (as na example) is the content of my mpd
configuration file /ect/mpd.conf (the DAC setup is in the
`audio_output`section) :

~~~
# Files and directories ###
## music directory: local files
music_directory "/media/AUDIO/AudioHiFi"
## playlist directory
playlist_directory  "/home/mmusr/.mpd/playlists"
## other
db_file "/home/mmusr/.mpd/database"
log_file"/var/log/mpd/mpd.log"
sticker_file"/home/mmusr/.mpd/sticker.sql"
pid_file"/tmp/mpd.pid"
state_file  "/tmp/mpd.state"

# General music daemon options 
## user / group that MPD will run as
user"mpdusr"
## Network
bind_to_address "localhost"
port"6600"
## Other daemon settings
log_level   "default"
restore_paused  "yes"
auto_update "no"
state_file_interval "300"

# Symbolic link behavior ##
#
# following symbolic links outside of the configured music_directory
#follow_outside_symlinks"yes"
# following symbolic links inside of the configured music_directory
#follow_inside_symlinks "yes"

# Zeroconf / Avahi Service Discovery ##
zeroconf_enabled"no"

# Input ###
input {
plugin "curl"
}

# Audio Output 
## ALSA output 
audio_output {
type"alsa"
name"MDAC"
device  "hw:0,0"
mixer_type  "none"
replay_gain_handler "none"
dsd_usb "no"
auto_resample   "no"
auto_channels   "no"
auto_format "no"
}

# Character Encoding ##
filesystem_charset  "UTF-8"
id3v1_encoding  "UTF-8"

# Playlist plugins 
playlist_plugin {
name "cue"
enabled "yes"
}
playlist_plugin {
name "embcue"
enabled "yes"
}
playlist_plugin {
name "flac"
enabled "yes"
}
playlist_plugin {
name "m3u"
enabled "yes"
}
playlist_plugin {
name "extm3u"
enabled "yes"
}
playlist_plugin {
name "rss"
enabled "yes"
}
~~~

Obviously, you should refer to *your* specific hardware and software
configuration, having a closer look to the ALSA (and MPD if used) documentation.

Hope it helps.
Regards



-- 
al3xu5

Say NO to copyright, patents, trademarks and any industrial design restrictions.

Public GPG/PGP key block
ID:   4096 bit RSA key 69C5977BF94CFE23
Fingerprint:  59C6 9DC7 CD4B CF2F A190  E3DE 69C5 977B F94C FE23


pgplaiGIq5dNQ.pgp
Description: Firma digitale OpenPGP
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi 3B+. Sound card driver installation.

[Dimitris via Dng]

don't use any sound on rpi, but some searching online, pointed here :
http://www.iqaudio.com/downloads/IQaudIO.pdf
(check p.31. )


On 3/15/19 12:23 AM, Edward Bartolo via Dng wrote:
> I have a raspberry Pi with a Pi DAC Pro sound for which there is no
> driver installed. Searching online takes me to readily prepared
> operating system images that I do not want to use as I am using
> Devuan. Does anyone know what I should do to be able to use the Pi DAC
> Pro sound card under Devuan? VolumeIO, a strongly suggested OS, badly
> smells of a software lock-in, something I really want to avoid as I
> have already experienced it when I used Delphi under MS Windows.
> 
> Thanks.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Antony Stone]

On Wednesday 05 December 2018 at 17:41:22, Edward Bartolo wrote:

> Further Optimization:
> 
> Is it possible to configure Devuan on Raspberry Pi 3B+, so that,
> bash_history, settings pertaining to bash, and other user
> configuration files from being updated every time such an application
> is used?

Er, sorry, but what's the verb in that sentence?

Did you perhaps mean "... configuration files *are prevented* from being ..."?

If so, I believe you just need to set HISTFILESIZE to zero.

I'm not entirely sure what you mean by "settings pertaining to bash".

> If there is some other things I am not aware of, please inform me.

I'm not an expert on running read-only systems (although I'm certainly 
interested), so I'll let others chip in with expertise here :)


Antony.

-- 
The Royal Society for the Prevention of Cruelty to Animals was formed in 1824.
The National Society for the Prevention of Cruelty to Children was not formed 
until 1884.
That says something about the British.

   Please reply to the list;
 please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Bruce Ferrell]

On 12/3/18 3:24 AM, Steve Litt wrote:

On Sun, 2 Dec 2018 11:10:20 -0800
Bruce Ferrell  wrote:

  

Yeah, this IS one of the issues around flash/SSD storage... They run
fast and wear out faster.

The preceding sentence is true but it's not the whole truth. If one
uses SSD the way they would spinning rust, that being run it 80% to 90%
full, with lots of writes, and expects years of service, one will
likely be disappointed. But there are many situations in which SSD has
sufficient lifetime.

Let me start with my setup:

=
[root@mydesk mnt]# mount | grep sda
/dev/sda1 on / type ext4 (rw,noatime)
[root@mydesk mnt]# df -h /
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda1   220G   29G  181G  14% /
[root@mydesk mnt]# mount | grep "/dev/sd"
/dev/sda1 on / type ext4 (rw,noatime)
/dev/sdb1 on /boot type ext4 (rw,noatime)
/dev/sdb7 on /tmp type ext4 (rw,noatime)
/dev/sdb6 on /var type ext4 (rw,noatime)
/dev/sdb8 on /run type ext4 (rw,noatime)
/dev/sdc9 on /home type ext4 (rw,noatime)
/dev/sdc1 on /s type ext4 (rw,noatime)
/dev/sdc2 on /d type ext4 (rw,noatime)
/dev/sdc4 on /classic/a type ext4 (rw,noatime)
/dev/sdc5 on /classic/b type ext4 (rw,noatime)
/dev/sdc6 on /classic/c type ext4 (rw,noatime)
/dev/sdc7 on /home/slitt/mail/Maildir type ext4 (rw,noatime)
/dev/sdc8 on /scratch type ext4 (rw,noatime)
/dev/sdc3 on /inst type ext4 (rw,noatime)
[root@mydesk mnt]#
=

* Everything likely to have multitudes of writes under normal operating
conditions is mounted spinning rust.

* Only 1/5 of the SSD is used, so what few writes there are are
   distributed across lots of space.

* I delete unneeded stuff and fstrim / every few days, so the SSD
   doesn't fill up with erased stuff.

* I expect only 4 years life from any drive, spinning rust or SSD. At
   least half of my disks have blown up within 4 years: That's life. My
   SSD is currently 4 years old.

The OP's situation differs from mine in one major factor: He has no
spinning rust to offload writes to. So he'll use all the great
suggestions in the thread: noatime, put /tmp and logs in RAM
filesystems, fstrim early and often, and load it exclusively with files
it's meant to handle (I think the OP wanted an mp3 juke box).

Some people suggested using a USB thumb drive for temp and often
written files. This is a great idea because you can buy a 64GB thumb
drive for about $20.00 to $30.00 USD, and just throw it away when it
breaks. Keep the music on the SSD for speed and reliability, but if the
music player software happens to write to /tmp, that's on the thumb
drive that gets replaced every couple years.

An internal 1TB SSD can be had for under $150. External for less than
$200. If you buy 1TB and be sure to use only 100GB, follow all the tips
and fstrim every few days, this SSD should last for years. If we assume
that each song is 5MB, you can hold 20,000 songs in 100GB. If for some
reason you need to store more than 100GB, well, that's what spinning
rust is for: Add one.

So it's true, SSDs run fast and wear out faster, but the wear out
faster part is only if you use them the same way you use spinning rust.

  
SteveT


Steve Litt
December 2018 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Everything you say is true Steve... Except for one teeny tiny little thing.

In general people, even engineers, tend to expect storage to behave like storage and not 
require "special" handling.

At a job I was at a couple of years back, the decision was made to swap SSD for spinning rust in an appliance application that was sold to customers for it's high speed.  The use 
case was extreme high speed read/write. It worked REALLY well for that and we got a big boost in perfomance.  After a couple of years in the field, we started to see significantly 
disk higher failure rates than we had with spinning rust... And the customers noticed.  Yeah, Oops!


To contrast that, I have 10K rpm spinning rust that has been in use 
continuously for over a decade, and isn't unusual to see that kind of longevity.

Flash based storage CAN be made to behave, but even then, it will still wear out significantly faster than spinning rust. Generally the failure tends to be catastrophic unless  
utilities to monitor block sparing are used on a regular and on going basis to tell when the unit is approaching that failure point so it can be swapped out before failure.  Those 
utilities tend to be specific to the storage, so it's not like "just run smartmon".


Maybe someday there will be more generalized utilities for that type of 
thing... Not so now.

For now, I know running a Farrari in traffic is a bad idea.  They just don't like that.  
So I choose a vehicle best suited to the work load, not the 

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

Il 03/12/18 12:53, Alessandro Selli ha scritto:
> On 03/12/18 at 11:30, Edward Bartolo wrote:
>> Running "update-rc.d rsyslog disable 2" resulted in error messages
>> like the following:
>>
>> ERROR MESSAGE:
>> insserv: warning: current start runlevel(s) A of script 'rsyslog'
>> overrides LSB defaults B
>>
>> There were four lines with similar text but with A and B as follows:
>> a) A = (3 4 5); B = (2 3 4 5)
>> b) A = (0 1 2 6); B= (0 1 6)
>> c) A = (3 4 5); B = (2 3 4 5)
>> d) A = (0 1 2 6); B = (0 1 6)
>>
>> Is this Ok?
>
>   Yes, they're just warnings (I take the line "ERROR MESSAGE:" line is
> not from the output of update-rc.d).
>
>
>   On my system, for instance:
>
>
> [root@wkstn02 ~]# ls /etc/rc?.d/???atd
> /etc/rc0.d/K01atd  /etc/rc2.d/S03atd  /etc/rc4.d/S03atd  /etc/rc6.d/K01atd
> /etc/rc1.d/K01atd  /etc/rc3.d/S03atd  /etc/rc5.d/S03atd
> [root@wkstn02 ~]# update-rc.d atd disable 2 3
>  * service atd removed from runlevel default
> insserv: warning: current start runlevel(s) (4 5) of script `atd' overrides 
> LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 6) of script `atd' 
> overrides LSB defaults (0 1 6).
> insserv: warning: script 'savecache' missing LSB tags and overrides
> [root@wkstn02 ~]# ls /etc/rc?.d/???wdm
> /etc/rc0.d/K01wdm  /etc/rc2.d/S04wdm  /etc/rc4.d/S04wdm  /etc/rc6.d/K01wdm
> /etc/rc1.d/K01wdm  /etc/rc3.d/S04wdm  /etc/rc5.d/S04wdm
> [root@wkstn02 ~]# 
>
>
> Please note that the service atd was disabled on runlevels 2 and 3 only.


  Sorry, I issued the wrong command:


[root@wkstn02 ~]# ls /etc/rc?.d/???atd
[root@wkstn02 ~]# 
/etc/rc0.d/K01atd  /etc/rc2.d/K01atd  /etc/rc4.d/S03atd  /etc/rc6.d/K01atd
/etc/rc1.d/K01atd  /etc/rc3.d/K01atd  /etc/rc5.d/S03atd
[root@wkstn02 ~]# 


  To put everything like before:


[root@wkstn02 ~]# update-rc.d atd enable 2 3
 * service atd added to runlevel default
insserv: warning: script 'savecache' missing LSB tags and overrides
[root@wkstn02 ~]# ls /etc/rc?.d/???atd
/etc/rc0.d/K01atd  /etc/rc2.d/S03atd  /etc/rc4.d/S03atd  /etc/rc6.d/K01atd
/etc/rc1.d/K01atd  /etc/rc3.d/S03atd  /etc/rc5.d/S03atd
[root@wkstn02 ~]# 



  Bye,



-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

On 03/12/18 at 11:30, Edward Bartolo wrote:
> Running "update-rc.d rsyslog disable 2" resulted in error messages
> like the following:
>
> ERROR MESSAGE:
> insserv: warning: current start runlevel(s) A of script 'rsyslog'
> overrides LSB defaults B
>
> There were four lines with similar text but with A and B as follows:
> a) A = (3 4 5); B = (2 3 4 5)
> b) A = (0 1 2 6); B= (0 1 6)
> c) A = (3 4 5); B = (2 3 4 5)
> d) A = (0 1 2 6); B = (0 1 6)
>
> Is this Ok?


  Yes, they're just warnings (I take the line "ERROR MESSAGE:" line is
not from the output of update-rc.d).


  On my system, for instance:


[root@wkstn02 ~]# ls /etc/rc?.d/???atd
/etc/rc0.d/K01atd  /etc/rc2.d/S03atd  /etc/rc4.d/S03atd  /etc/rc6.d/K01atd
/etc/rc1.d/K01atd  /etc/rc3.d/S03atd  /etc/rc5.d/S03atd
[root@wkstn02 ~]# update-rc.d atd disable 2 3
 * service atd removed from runlevel default
insserv: warning: current start runlevel(s) (4 5) of script `atd' overrides LSB 
defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 6) of script `atd' 
overrides LSB defaults (0 1 6).
insserv: warning: script 'savecache' missing LSB tags and overrides
[root@wkstn02 ~]# ls /etc/rc?.d/???wdm
/etc/rc0.d/K01wdm  /etc/rc2.d/S04wdm  /etc/rc4.d/S04wdm  /etc/rc6.d/K01wdm
/etc/rc1.d/K01wdm  /etc/rc3.d/S04wdm  /etc/rc5.d/S04wdm
[root@wkstn02 ~]# 


Please note that the service atd was disabled on runlevels 2 and 3 only.


Running:

update-rc.d atd disable 


would disable atd on all runlevels.



-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Lars Noodén]

On 12/3/18 1:16 PM, Edward Bartolo wrote:
> Nevermind, I found that prepending a symlink with a 'K' in /etc/rcN.d
> is to disable that script.

See "man update-rc.d" for the official tool for that.

/Lars

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Steve Litt]

On Sun, 2 Dec 2018 11:10:20 -0800
Bruce Ferrell  wrote:

 
> Yeah, this IS one of the issues around flash/SSD storage... They run
> fast and wear out faster.

The preceding sentence is true but it's not the whole truth. If one
uses SSD the way they would spinning rust, that being run it 80% to 90%
full, with lots of writes, and expects years of service, one will
likely be disappointed. But there are many situations in which SSD has
sufficient lifetime.

Let me start with my setup:

=
[root@mydesk mnt]# mount | grep sda
/dev/sda1 on / type ext4 (rw,noatime)
[root@mydesk mnt]# df -h /
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda1   220G   29G  181G  14% /
[root@mydesk mnt]# mount | grep "/dev/sd"
/dev/sda1 on / type ext4 (rw,noatime)
/dev/sdb1 on /boot type ext4 (rw,noatime)
/dev/sdb7 on /tmp type ext4 (rw,noatime)
/dev/sdb6 on /var type ext4 (rw,noatime)
/dev/sdb8 on /run type ext4 (rw,noatime)
/dev/sdc9 on /home type ext4 (rw,noatime)
/dev/sdc1 on /s type ext4 (rw,noatime)
/dev/sdc2 on /d type ext4 (rw,noatime)
/dev/sdc4 on /classic/a type ext4 (rw,noatime)
/dev/sdc5 on /classic/b type ext4 (rw,noatime)
/dev/sdc6 on /classic/c type ext4 (rw,noatime)
/dev/sdc7 on /home/slitt/mail/Maildir type ext4 (rw,noatime)
/dev/sdc8 on /scratch type ext4 (rw,noatime)
/dev/sdc3 on /inst type ext4 (rw,noatime)
[root@mydesk mnt]#
=

* Everything likely to have multitudes of writes under normal operating
conditions is mounted spinning rust.

* Only 1/5 of the SSD is used, so what few writes there are are
  distributed across lots of space.

* I delete unneeded stuff and fstrim / every few days, so the SSD
  doesn't fill up with erased stuff.

* I expect only 4 years life from any drive, spinning rust or SSD. At
  least half of my disks have blown up within 4 years: That's life. My
  SSD is currently 4 years old.

The OP's situation differs from mine in one major factor: He has no
spinning rust to offload writes to. So he'll use all the great
suggestions in the thread: noatime, put /tmp and logs in RAM
filesystems, fstrim early and often, and load it exclusively with files
it's meant to handle (I think the OP wanted an mp3 juke box).

Some people suggested using a USB thumb drive for temp and often
written files. This is a great idea because you can buy a 64GB thumb
drive for about $20.00 to $30.00 USD, and just throw it away when it
breaks. Keep the music on the SSD for speed and reliability, but if the
music player software happens to write to /tmp, that's on the thumb
drive that gets replaced every couple years.

An internal 1TB SSD can be had for under $150. External for less than
$200. If you buy 1TB and be sure to use only 100GB, follow all the tips
and fstrim every few days, this SSD should last for years. If we assume
that each song is 5MB, you can hold 20,000 songs in 100GB. If for some
reason you need to store more than 100GB, well, that's what spinning
rust is for: Add one.

So it's true, SSDs run fast and wear out faster, but the wear out
faster part is only if you use them the same way you use spinning rust.

 
SteveT

Steve Litt 
December 2018 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Edward Bartolo]

Nevermind, I found that prepending a symlink with a 'K' in /etc/rcN.d
is to disable that script.

Thanks everyone, especially Dr Klepp.

-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
If you cannot make abstructions about details you do not understand
the concepts underlying them.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

On 03/12/18 at 10:50, Adam Borowski wrote:
> On Mon, Dec 03, 2018 at 10:33:44AM +0100, Alessandro Selli wrote:
>> On 03/12/18 at 10:05, Adam Borowski wrote:
>>> realtime greatly reduces atime writes, but it's still too much.
>>   I wouldn't say so.  Since relatime updates atime only relative to the
>> present ctime and mtime, it's only changed when one of those two is
>> changed.  That is, updating atime does not require a separate write
>> operation.
> That was the original design -- but alas, it was later changed so the atime
> is updated at least once a day.


  My experience is inconsistent with what you write:


[alessandro@wkstn02 ~]$ mount | grep ' on /home '
/dev/mapper/part6_crypt_home on /home type ext4 (rw,relatime,nobarrier)
[alessandro@wkstn02 ~]$ stat .xsession-errors.old
  File: .xsession-errors.old
  Size: 47036242Blocks: 91880  IO Block: 4096   regular file
Device: fd02h/64770dInode: 655383  Links: 1
Access: (0600/-rw---)  Uid: ( 1000/ alessandro)   Gid: ( 1000/ alessandro)
Access: 2018-07-06 13:22:22.312846358 +0200
Modify: 2018-07-06 13:08:36.392798307 +0200
Change: 2018-07-06 13:22:17.149512721 +0200
 Birth: -
[alessandro@wkstn02 ~]$ date
Mon Dec  3 11:18:47 CET 2018
[alessandro@wkstn02 ~]$ uname -r
4.19.5.wkstn02-0
[alessandro@wkstn02 ~]$ 
 

[...]

> Every inode has to be updated.


  Only when it has to be updated.  That is, only when attributes or data
must be.



-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Rick Moen]

Quoting Alessandro Selli (alessandrose...@linux.com):

>   Good idea.

Well, in the name of international amity

# touch NIENTE_E_MONTATO_QUI
# chattr +i NIENTE_E_MONTATO_QUI

;->

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Adam Borowski]

On Mon, Dec 03, 2018 at 10:33:44AM +0100, Alessandro Selli wrote:
> On 03/12/18 at 10:05, Adam Borowski wrote:
> > realtime greatly reduces atime writes, but it's still too much.
> 
>   I wouldn't say so.  Since relatime updates atime only relative to the
> present ctime and mtime, it's only changed when one of those two is
> changed.  That is, updating atime does not require a separate write
> operation.

That was the original design -- but alas, it was later changed so the atime
is updated at least once a day.

> >  Case in
> > point: it's the likely culprit for wasting the SD card that started this
> > thread (on a mostly-read load).
> 
> 
> if that filesystem was mounted with the relatime option (or with no
> option at all, since relatime is the default), then it's very unlikely
> it caused any more writes that if it was fully disabled.

You still rewrite every inode once per day.

> >  And, update frequency of 1/day happens to
> > match the typical backup schedule, making it ruin snapshots just the same
> > as strictatime would.
> 
>   Uh?  How can atime "ruin snapshots"?

Every inode has to be updated.  That causes a lot of metadata churn, and
even takes significant space.  Changing this single number tends to cost
far more than a page worth of space -- usual snapshot tools (btrfs, lvm,
etc) CoW more than just the inode.  Thus, for some common loads we're
looking at 5% wasted disk space just for atimes.

> > So it's time to kill the nasty thing.
> 
>   If only it was any nasty.


Some folks say systemd isn't nasty.



Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a worldly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

On 03/12/18 at 10:05, Adam Borowski wrote:
> realtime greatly reduces atime writes, but it's still too much.


  I wouldn't say so.  Since relatime updates atime only relative to the
present ctime and mtime, it's only changed when one of those two is
changed.  That is, updating atime does not require a separate write
operation.  For this reason:


>  Case in
> point: it's the likely culprit for wasting the SD card that started this
> thread (on a mostly-read load).


if that filesystem was mounted with the relatime option (or with no
option at all, since relatime is the default), then it's very unlikely
it caused any more writes that if it was fully disabled.


>  And, update frequency of 1/day happens to
> match the typical backup schedule, making it ruin snapshots just the same
> as strictatime would.


  Uh?  How can atime "ruin snapshots"?


> So it's time to kill the nasty thing.


  If only it was any nasty.



-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[g4sra]

http://hacks.slashdirt.org/sw/flashybrid/

Someone with non-systemd will have to suck it and see.
That someone will be me if no-one else has done it by Valentines Day.


On 02/12/2018 23:11, Alessandro Selli wrote:
> OnIl 02/12/18 at 22:58, g4sra wrote:
>> I have found flashybrid extremely beneficial in the past, on switching
>> from Debian to Devuan Ascii it appears not to be in the repository, is
>> it in Beowulf ?. I am not aware of any dependencies it has on 
>> systemd.
> 
> 
>   It was removed from Debian on January 2017:
> 
> https://tracker.debian.org/pkg/flashybrid
> 
> 
>   Looks like development upstream stopped 11 years ago:
> 
> https://github.com/elcuco/flashybrid
> 
> Latest commit 2a0d291
> 
> on 23 Sep 2007
> 
> 
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Adam Borowski]

On Mon, Dec 03, 2018 at 02:05:29PM +1100, Erik Christiansen wrote:
> On 03.12.18 00:47, Adam Borowski wrote:
> > On Sun, Dec 02, 2018 at 11:53:39PM +0100, Alessandro Selli wrote:
> > > On 02/12/18 at 17:23, Adam Borowski wrote:
> > > > You'd want to set noatime on every machine
> > > > you control.
> > > 
> > > 
> > >   Some mail servers and clients do use it to determine if a mail was
> > > read after it arrived.  In this case, it'd be better to have it set on 
> > > /var.
> 
> TL;DR: Use relatime there, as noatime will break mutt.

Hmm...
https://gitlab.com/muttmua/mutt/commit/489a1c394c29e4b12b705b62da413f322406326f
https://github.com/neomutt/neomutt/commit/816095bfdb72caafd8845e8fb28cbc8c6afc114f

> > That's no more.  And, let me clarify: atime was used for mail:
> > * only with mbox (Maildir never suffered from this issue)
> > * only on the local machine
> > * only by the shell to say "You have new mail." vs "You have mail."
> >   -- not even by the mail client
> 
> Not true, according to the on-line manual for my current mutt
> installation:
> 
> » Other possible causes of Mutt not detecting new mail in these folders
> are backup tools (updating access times) or filesystems mounted without
> access time update support (for Linux systems, see the relatime
> option).«

In the very post you're responding to, I started with "That's no more.".

> > So the whole effort gave you just a single word in a message, that many
> > people even didn't notice.
> > 
> > And, popular local mail clients are already patched to update atime
> > explicitly.
> > 
> > Ie, atime for mail is an ex-reason.
> 
> A fine assertion, but wiser is to check the facts.

And even wiser to actually change things you don't like. :)

> It would seem then, that noatime will break mutt, but relatime is OK,
> and is now the default. IIUC.

realtime greatly reduces atime writes, but it's still too much.  Case in
point: it's the likely culprit for wasting the SD card that started this
thread (on a mostly-read load).  And, update frequency of 1/day happens to
match the typical backup schedule, making it ruin snapshots just the same
as strictatime would.

So it's time to kill the nasty thing.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a wordly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Erik Christiansen]

On 03.12.18 00:47, Adam Borowski wrote:
> On Sun, Dec 02, 2018 at 11:53:39PM +0100, Alessandro Selli wrote:
> > On 02/12/18 at 17:23, Adam Borowski wrote:
> > > You'd want to set noatime on every machine
> > > you control.
> > 
> > 
> >   Some mail servers and clients do use it to determine if a mail was
> > read after it arrived.  In this case, it'd be better to have it set on /var.

TL;DR: Use relatime there, as noatime will break mutt.

> That's no more.  And, let me clarify: atime was used for mail:
> * only with mbox (Maildir never suffered from this issue)
> * only on the local machine
> * only by the shell to say "You have new mail." vs "You have mail."
>   -- not even by the mail client

Not true, according to the on-line manual for my current mutt
installation:

» Other possible causes of Mutt not detecting new mail in these folders
are backup tools (updating access times) or filesystems mounted without
access time update support (for Linux systems, see the relatime
option).«

> So the whole effort gave you just a single word in a message, that many
> people even didn't notice.
> 
> And, popular local mail clients are already patched to update atime
> explicitly.
> 
> Ie, atime for mail is an ex-reason.

A fine assertion, but wiser is to check the facts. A quick glance in "man
mount" shows:

»relatime
  Update inode access times relative to modify or change time.  Access
  time  is  only updated  if  the previous access time was earlier than
  the current modify or change time. (Similar to noatime, but doesn't
  break mutt or other applications  that  need to know if a file has
  been read since the last time it was modified.)

  Since  Linux  2.6.30,  the  kernel defaults to the behavior provided
  by this option (unless noatime was  specified), and the strictatime
  option is required  to  obtain traditional semantics. In addition,
  since Linux 2.6.30, the file's last access time is always  updated  if
  it  is more than 1 day old.
«

It would seem then, that noatime will break mutt, but relatime is OK,
and is now the default. IIUC.

Erik
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Adam Borowski]

On Sun, Dec 02, 2018 at 11:53:39PM +0100, Alessandro Selli wrote:
> On 02/12/18 at 17:23, Adam Borowski wrote:
> > You'd want to set noatime on every machine
> > you control.
> 
> 
>   Some mail servers and clients do use it to determine if a mail was
> read after it arrived.  In this case, it'd be better to have it set on /var.

That's no more.  And, let me clarify: atime was used for mail:
* only with mbox (Maildir never suffered from this issue)
* only on the local machine
* only by the shell to say "You have new mail." vs "You have mail."
  -- not even by the mail client

So the whole effort gave you just a single word in a message, that many
people even didn't notice.

And, popular local mail clients are already patched to update atime
explicitly.

Ie, atime for mail is an ex-reason.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a wordly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

OnIl 02/12/18 at 22:58, g4sra wrote:
> I have found flashybrid extremely beneficial in the past, on switching
> from Debian to Devuan Ascii it appears not to be in the repository, is
> it in Beowulf ?. I am not aware of any dependencies it has on 
> systemd.


  It was removed from Debian on January 2017:

https://tracker.debian.org/pkg/flashybrid


  Looks like development upstream stopped 11 years ago:

https://github.com/elcuco/flashybrid

Latest commit 2a0d291

on 23 Sep 2007


-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

On 02/12/18 at 21:04, Rick Moen wrote:
> I also recommend (while in single-user mode as the root user) doing this
> in each of your system's mountpoint directories:
>
> # touch NOTHING_IS_MOUNTED_HERE
> # chattr +i NOTHING_IS_MOUNTED_HERE
>
> That's saved me confusion quite a few times when I'm puzzled about one
> of those directories unexpectedly lacking the expected files.


  Good idea.  To address the same problem I often set the unmounted
mountpoint chmod 0.  However, I noticed this setting causes sshfs to
fail with the message:

fuse: failed to open mountpoint for reading: Permission denied


Your method does make sense.  It even works for root!  ☺



-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

On 02/12/18 at 17:23, Adam Borowski wrote:
> You'd want to set noatime on every machine
> you control.


  Some mail servers and clients do use it to determine if a mail was
read after it arrived.  In this case, it'd be better to have it set on /var.



-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

On 02/12/18 at 21:07, Dr. Nikolaus Klepp wrote:
> Am Sonntag, 2. Dezember 2018 schrieb Edward Bartolo:
>> On 02/12/2018, Dr. Nikolaus Klepp  wrote:
>> [...]
>>> Do not use swap.
>>> Use ramfs for /tmp and /var/tmp.
>>> Turn off logging.
>>> Mount / readonly.
>>> Use "noatime" mountoption.
>>>
>> How can I use ramfs for /tmp and /var/tmp?
> In your /etc/fstab:
> tmpfs   /tmptmpfs   relatime0   1
> tmpfs   /var/tmptmpfs   relatime0   1


  You'd better specify the mode=1777 mount option, to make sure the tmp
directory is going to have the Deletion Restriction Bit set.


>> And, also turn off logging?
> If you like a logfile that's available till shutdown:
> tmpfs   /var/logtmpfs   relatime0   1
>
> Or disable rsyslogd .. I think it was this sequence:
> # update-rc.d rsyslog disable 2
> # update-rc.d rsyslog disable 3
> # update-rc.d rsyslog disable 4
> # update-rc.d rsyslog disable 5

update-rc.d rsyslog disable

will work for all runlevels.


-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[golinux]

It appears not:

https://pkginfo.devuan.org/cgi-bin/d1pkgweb-query?search=flashybrid=any


On 2018-12-02 15:58, g4sra wrote:

I have found flashybrid extremely beneficial in the past, on switching
from Debian to Devuan Ascii it appears not to be in the repository, is
it in Beowulf ?. I am not aware of any dependencies it has on 
systemd.

On 02/12/2018 10:41, Edward Bartolo wrote:

Hi everyone.

Recently I have been using a Raspberry Pi 3B, obviously powered with
Devuan, to run as music player. Restarting it yesterday, I was
dismayed to discover it would not boot properly anymore, with long
lists of errors complaining about not being able to write to the SD
CARD. The latter is not full. Examining it I found it is now
permanently marked as read-only. Searching online for an explanatory
cause, I learnt this occurs when the maximum number of write cycles is
reached. So, the SD CARD, although brand new is now to be thrown away.

The purpose of this email is to ask how to radically minimized write
cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
how-to which uses /tmp fs for frequently modified system files, but
the user uses systemd and I do not want to have that.

Can any good soul help, please?
Thanks.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[g4sra]

I have found flashybrid extremely beneficial in the past, on switching
from Debian to Devuan Ascii it appears not to be in the repository, is
it in Beowulf ?. I am not aware of any dependencies it has on 
systemd.

On 02/12/2018 10:41, Edward Bartolo wrote:
> Hi everyone.
> 
> Recently I have been using a Raspberry Pi 3B, obviously powered with
> Devuan, to run as music player. Restarting it yesterday, I was
> dismayed to discover it would not boot properly anymore, with long
> lists of errors complaining about not being able to write to the SD
> CARD. The latter is not full. Examining it I found it is now
> permanently marked as read-only. Searching online for an explanatory
> cause, I learnt this occurs when the maximum number of write cycles is
> reached. So, the SD CARD, although brand new is now to be thrown away.
> 
> The purpose of this email is to ask how to radically minimized write
> cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
> how-to which uses /tmp fs for frequently modified system files, but
> the user uses systemd and I do not want to have that.
> 
> Can any good soul help, please?
> Thanks.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Gregory Nowak]

On Sun, Dec 02, 2018 at 11:41:48AM +0100, Edward Bartolo wrote:
> The purpose of this email is to ask how to radically minimized write
> cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
> how-to which uses /tmp fs for frequently modified system files, but
> the user uses systemd and I do not want to have that.
> 

I have an rpi2 which I've been running for almost three years now, and
which stays up 24/7. I run fstrim once a week from a cron job, and the
sd card is still doing fine as far as I can tell. While this doesn't
minimize write cycles, it does reduce wear on the card by distributing
writes to different sectors. The other suggestions in this thread are
also good ones.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Dr. Nikolaus Klepp]

Am Sonntag, 2. Dezember 2018 schrieb Edward Bartolo:
> On 02/12/2018, Dr. Nikolaus Klepp  wrote:
> [...]
> >
> > Do not use swap.
> > Use ramfs for /tmp and /var/tmp.
> > Turn off logging.
> > Mount / readonly.
> > Use "noatime" mountoption.
> >
> 
> How can I use ramfs for /tmp and /var/tmp?

In your /etc/fstab:
tmpfs   /tmptmpfs   relatime0   1
tmpfs   /var/tmptmpfs   relatime0   1



> And, also turn off logging?
If you like a logfile that's available till shutdown:
tmpfs   /var/logtmpfs   relatime0   1

Or disable rsyslogd .. I think it was this sequence:
# update-rc.d rsyslog disable 2
# update-rc.d rsyslog disable 3
# update-rc.d rsyslog disable 4
# update-rc.d rsyslog disable 5



> 
> Can anyone post a sample /etc/fstab as a hint as to what should it look like?
> 
> Thanks.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 



-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Rick Moen]

Quoting Alessandro Selli (alessandrose...@linux.com):

> All you need to do is putting this line in /etc/fstab:
> 
> tmpfs   /tmp    tmpfs   defaults,mode=1777  0 0

Seriously, yes, everyone running a system _just_ on flash media ought to 
be doing this and similar measures to reduce wear on the mass storage.

>   Then you go into runlevel 1, erase everything in /tmp, mount it and go
> back to runlevel 2 (or what you use on your RP3B).

I also recommend (while in single-user mode as the root user) doing this
in each of your system's mountpoint directories:

# touch NOTHING_IS_MOUNTED_HERE
# chattr +i NOTHING_IS_MOUNTED_HERE

That's saved me confusion quite a few times when I'm puzzled about one
of those directories unexpectedly lacking the expected files.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Rod Rodolico]

There is an old article at

http://wiki.linuxservertech.com/index.php?action=artikel=9=173

which may help you. I wrote it when I was booting servers from USB
Thumbdrives. Again, it is an older article so use some caution when you
review it. But, I have servers using thumbdrives that have been running
for 5+ years.

Rod

On 12/02/2018 04:41 AM, Edward Bartolo wrote:
> Hi everyone.
> 
> Recently I have been using a Raspberry Pi 3B, obviously powered with
> Devuan, to run as music player. Restarting it yesterday, I was
> dismayed to discover it would not boot properly anymore, with long
> lists of errors complaining about not being able to write to the SD
> CARD. The latter is not full. Examining it I found it is now
> permanently marked as read-only. Searching online for an explanatory
> cause, I learnt this occurs when the maximum number of write cycles is
> reached. So, the SD CARD, although brand new is now to be thrown away.
> 
> The purpose of this email is to ask how to radically minimized write
> cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
> how-to which uses /tmp fs for frequently modified system files, but
> the user uses systemd and I do not want to have that.
> 
> Can any good soul help, please?
> Thanks.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 

-- 
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465 US
http://dailydata.net
214.827.2170
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Bruce Ferrell]

On 12/2/18 2:41 AM, Edward Bartolo wrote:

Hi everyone.

Recently I have been using a Raspberry Pi 3B, obviously powered with
Devuan, to run as music player. Restarting it yesterday, I was
dismayed to discover it would not boot properly anymore, with long
lists of errors complaining about not being able to write to the SD
CARD. The latter is not full. Examining it I found it is now
permanently marked as read-only. Searching online for an explanatory
cause, I learnt this occurs when the maximum number of write cycles is
reached. So, the SD CARD, although brand new is now to be thrown away.

The purpose of this email is to ask how to radically minimized write
cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
how-to which uses /tmp fs for frequently modified system files, but
the user uses systemd and I do not want to have that.

Can any good soul help, please?
Thanks.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Yeah, this IS one of the issues around flash/SSD storage... They run fast and 
wear out faster.

My suggestion for a Raspberry PI is to use a USB disk and use the info at this 
link:

https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md

That will allow you to run Devuan from a USB drive attached to the PI and 
completely avoid the whole flash memory issue.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Adam Borowski]

On Sun, Dec 02, 2018 at 12:06:03PM +0100, info at smallinnovations dot nl wrote:
> On 02-12-18 11:41, Edward Bartolo wrote:
> > The purpose of this email is to ask how to radically minimized write
> > cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
> > how-to which uses /tmp fs for frequently modified system files, but
> > the user uses systemd and I do not want to have that.

> One dramatically sdcard saving option is to use noatime when mounting
> your sdcard in /etc/fstab like
> 
> /dev/mmcblk0p2  / ext4 defaults,noatime 0 0

Keeping the very concept of atime is _sabotage_.  It was one of the ideas
made when the world was young and when I/O was cheap compared to other
performance-related components.  You'd want to set noatime on every machine
you control.

Especially on:
* media with limited write cycles (<- you are here)
* thin storage
* CoW disk images
* filesystems with snapshots
* read caching

> It disables writing a timestamp when a file or directory has been
> accessed. Other options i know of are using JFFS2 made for flash kind of
> storage.

These days, I'd recommend f2fs -- much newer, faster, and doesn't differ
from a regular filesystem from a naive user's point of view.  And staying
naive saves your time.

> Using aufs or unionfs which in fact create a readonly fs with
> changes in RAM which can be write back to disk when your system shutdown
> in a orderly fashion.

Pretty risky, and requires non-negligible human effort.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a wordly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Arnt Karlsen]

On Sun, 2 Dec 2018 12:16:34 +0100, Dr. wrote in message 
<201812021216.34883.dr.kl...@gmx.at>:

> Am Sonntag, 2. Dezember 2018 schrieb Edward Bartolo:
> > Hi everyone.
> > 
> > Recently I have been using a Raspberry Pi 3B, obviously powered with
> > Devuan, to run as music player. Restarting it yesterday, I was
> > dismayed to discover it would not boot properly anymore, with long
> > lists of errors complaining about not being able to write to the SD
> > CARD. The latter is not full. Examining it I found it is now
> > permanently marked as read-only. Searching online for an explanatory
> > cause, I learnt this occurs when the maximum number of write cycles
> > is reached. So, the SD CARD, although brand new is now to be thrown
> > away.
> > 
> > The purpose of this email is to ask how to radically minimized write
> > cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found
> > a how-to which uses /tmp fs for frequently modified system files,
> > but the user uses systemd and I do not want to have that.
> > 
> > Can any good soul help, please?
> > Thanks.  
> 
> Do not use swap. 
> Use ramfs for /tmp and /var/tmp. 
> Turn off logging. 

...or log to a log server.

> Mount / readonly. 
> Use "noatime" mountoption.


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

On 02/12/18 on 13:08, info at smallinnovations dot nl wrote:
>
> If you disable journalling on ext4 you can just as well mount it with
> ext2 afaik.
>
> Grtz
>
> Nick
>

  No, ext2 is significantly slower than a journal-less ext4 filesystem.

  This must be due mainly to the fact that ext4 uses an improved
block-allocator algorithm, one that merges the allocation of a series of
blocks to the same file in one run instead of $FILE_SIZE/$BLOCK_SIZE
runs.  I recently run a comparison test on an old 1GB USB pendrive
connected to a USB-2 port, here you are with the log:


[alessandro@wkstn02 ~]$ cat bin/bomb_filesystem.sh
#!/bin/dash

TESTROOT=/mnt/loop
MAXDIRS=100
MAXFILES=10

if mountpoint --quiet "$TESTROOT"
then I=0
 while test "$I" -lt "$MAXDIRS"
 do mkdir "$TESTROOT/Dir_$I" || break
    I=$((I+1))
 done
 I=0
 while test $I -lt "$MAXDIRS"
 do J=0
    while test $J -lt "$MAXFILES"
    do dd count=$((1024+16*J)) if=/dev/zero
of="$TESTROOT/Dir_$I/file_$J"
   J=$((J+1))
    done
    I=$((I+1))
 done
else echo "ERROR: \"$TESTROOT\" does not exist or is not a mountpoint" >&2
 exit 1
fi


[root@wkstn02 ~]# mkfs.ext2 /dev/sdb
[root@wkstn02 ~]# mount /dev/sdb /mnt/loop
[root@wkstn02 ~]# chown alessandro /mnt/loop


[alessandro@wkstn02 ~]$ time (bomb_filesystem.sh ; sync)

real    10m35,149s
user    0m1,042s
sys 0m1,921s

[alessandro@wkstn02 ~]$ df /mnt/loop
File system Size Used Avail Use% Mounted on
/dev/sdb    953M  541M    364M  60% /mnt/loop


[alessandro@wkstn02 ~]$ time (\rm -r /mnt/loop/Dir_* ; sync)

real    0m2,133s
user    0m0,009s
sys 0m0,076s

[alessandro@wkstn02 ~]$ time (bomb_filesystem.sh ; sync)

real    11m10,261s
user    0m0,961s
sys 0m2,109s


[root@wkstn02 ~]# umount /dev/sdb
[root@wkstn02 ~]# mkfs.ext4 -O ^has_journal /dev/sdb
[root@wkstn02 ~]# mount /dev/sdb /mnt/loop
[root@wkstn02 ~]# chown alessandro /mnt/loop


[alessandro@wkstn02 ~]$ time (bomb_filesystem.sh ; sync)

real    3m39,434s
user    0m1,024s
sys 0m1,950s

[alessandro@wkstn02 ~]$ time (\rm -r /mnt/loop/Dir_* ; sync)

real    0m2,486s
user    0m0,002s
sys 0m0,082s


 

-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[info at smallinnovations dot nl]

On 02-12-18 13:01, Alessandro Selli wrote:
>
>
> Il 02/12/18 11:41, Edward Bartolo ha scritto:
>> Hi everyone.
>>
>> Recently I have been using a Raspberry Pi 3B, obviously powered with
>> Devuan, to run as music player. Restarting it yesterday, I was
>> dismayed to discover it would not boot properly anymore, with long
>> lists of errors complaining about not being able to write to the SD
>> CARD. The latter is not full. Examining it I found it is now
>> permanently marked as read-only. Searching online for an explanatory
>> cause, I learnt this occurs when the maximum number of write cycles is
>> reached. So, the SD CARD, although brand new is now to be thrown away.
>>
>> The purpose of this email is to ask how to radically minimized write
>> cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
>> how-to which uses /tmp fs for frequently modified system files, but
>> the user uses systemd and I do not want to have that.
>>
>> Can any good soul help, please?
>> Thanks.
>
>
>   All you need to do is putting this line in /etc/fstab:
>
> tmpfs   /tmp    tmpfs   defaults,mode=1777  0 0
>
>
>   Then you go into runlevel 1, erase everything in /tmp, mount it and
> go back to runlevel 2 (or what you use on your RP3B).
>
>   Others have already suggested more ways you can reduce writes to
> your filesystems.  I would add, if your device's power source is
> backed by a battery and you use an ext4 filesystem, to format or mount
> it with:
>
>  1. journal disabled (nointegrity);
>  2. barriers disabled (nobarrier or barrier=0).
>
>
>   These mount options will increase the chance of data loss and
> filesystem corruption in the case of an abnormal filesystem close
> (system crash or sudden power loss), but significantly decrease the
> number of write operations on the ext4 filesystem during regular
> operation.
>
>
>
> Alessandro
>
>
>
> -- 
> Alessandro Selli 
> VOIP SIP: dhatarat...@ekiga.net
> Chiave firma e cifratura PGP/GPG signing and encoding key:
>   BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE

If you disable journalling on ext4 you can just as well mount it with
ext2 afaik.

Grtz

Nick




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Lars Noodén]

On 12/2/18 12:41 PM, Edward Bartolo wrote:
> [snip]
> So, the SD CARD, although brand new is now to be thrown away.
> [snip]

Is it still under warranty?  If so you can get a replacement.

In addition to the tips already mentioned, under-provisioning helps a
bit too.

/Lars
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Alessandro Selli]

Il 02/12/18 11:41, Edward Bartolo ha scritto:
> Hi everyone.
>
> Recently I have been using a Raspberry Pi 3B, obviously powered with
> Devuan, to run as music player. Restarting it yesterday, I was
> dismayed to discover it would not boot properly anymore, with long
> lists of errors complaining about not being able to write to the SD
> CARD. The latter is not full. Examining it I found it is now
> permanently marked as read-only. Searching online for an explanatory
> cause, I learnt this occurs when the maximum number of write cycles is
> reached. So, the SD CARD, although brand new is now to be thrown away.
>
> The purpose of this email is to ask how to radically minimized write
> cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
> how-to which uses /tmp fs for frequently modified system files, but
> the user uses systemd and I do not want to have that.
>
> Can any good soul help, please?
> Thanks.


  All you need to do is putting this line in /etc/fstab:

tmpfs   /tmp    tmpfs   defaults,mode=1777  0 0


  Then you go into runlevel 1, erase everything in /tmp, mount it and go
back to runlevel 2 (or what you use on your RP3B).

  Others have already suggested more ways you can reduce writes to your
filesystems.  I would add, if your device's power source is backed by a
battery and you use an ext4 filesystem, to format or mount it with:

 1. journal disabled (nointegrity);
 2. barriers disabled (nobarrier or barrier=0).


  These mount options will increase the chance of data loss and
filesystem corruption in the case of an abnormal filesystem close
(system crash or sudden power loss), but significantly decrease the
number of write operations on the ext4 filesystem during regular operation.



Alessandro



-- 
Alessandro Selli 
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[ael]

On Sun, Dec 02, 2018 at 11:41:48AM +0100, Edward Bartolo wrote:
> 
> Recently I have been using a Raspberry Pi 3B, obviously powered with
> Devuan, to run as music player. Restarting it yesterday, I was
> dismayed to discover it would not boot properly anymore, with long
> lists of errors complaining about not being able to write to the SD
> CARD. The latter is not full. Examining it I found it is now

Just in case you are not aware of this, there is a huge market in fake
and substandard SD cards, often with the firmware modified to
fraudulently claim a larger capacity than the chips actually present.
That said, I don't think that they often fail into a read only mode.
The only time that I encountered that problem, the supplier replaced the
card.

sdtool (https://github.com/BertoldVdb/sdtool) may be useful if you don't
know about it.


I always check incoming cards with f3 (http://oss.digirati.com.br/f3/)
which should detect fraudulent cards. Of course it uses up one
write/erase cycle, but that can't be helped.

So do you know that you have a genuine card purcahsed from a reliable
source?

Again, apologies if this is all old news.

ael

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[Dr. Nikolaus Klepp]

Am Sonntag, 2. Dezember 2018 schrieb Edward Bartolo:
> Hi everyone.
> 
> Recently I have been using a Raspberry Pi 3B, obviously powered with
> Devuan, to run as music player. Restarting it yesterday, I was
> dismayed to discover it would not boot properly anymore, with long
> lists of errors complaining about not being able to write to the SD
> CARD. The latter is not full. Examining it I found it is now
> permanently marked as read-only. Searching online for an explanatory
> cause, I learnt this occurs when the maximum number of write cycles is
> reached. So, the SD CARD, although brand new is now to be thrown away.
> 
> The purpose of this email is to ask how to radically minimized write
> cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
> how-to which uses /tmp fs for frequently modified system files, but
> the user uses systemd and I do not want to have that.
> 
> Can any good soul help, please?
> Thanks.

Do not use swap. 
Use ramfs for /tmp and /var/tmp. 
Turn off logging. 
Mount / readonly. 
Use "noatime" mountoption.



-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry Pi fried SD CARD.

[info at smallinnovations dot nl]

On 02-12-18 11:41, Edward Bartolo wrote:
> Hi everyone.
>
> Recently I have been using a Raspberry Pi 3B, obviously powered with
> Devuan, to run as music player. Restarting it yesterday, I was
> dismayed to discover it would not boot properly anymore, with long
> lists of errors complaining about not being able to write to the SD
> CARD. The latter is not full. Examining it I found it is now
> permanently marked as read-only. Searching online for an explanatory
> cause, I learnt this occurs when the maximum number of write cycles is
> reached. So, the SD CARD, although brand new is now to be thrown away.
>
> The purpose of this email is to ask how to radically minimized write
> cycles to the SD CARD when I run Devuan for Raspberry Pi 3. I found a
> how-to which uses /tmp fs for frequently modified system files, but
> the user uses systemd and I do not want to have that.
>
> Can any good soul help, please?
> Thanks.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

One dramatically sdcard saving option is to use noatime when mounting
your sdcard in /etc/fstab like

/dev/mmcblk0p2  / ext4 defaults,noatime 0 0

It disables writing a timestamp when a file or directory has been
accessed. Other options i know of are using JFFS2 made for flash kind of
storage. Using aufs or unionfs which in fact create a readonly fs with
changes in RAM which can be write back to disk when your system shutdown
in a orderly fashion.

Grtz

Nick




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi 2

[J. Fahrner]

I found a way that seems ok:
I installed Raspbian Stretch and migrated it to Devuan Ascii.
The package raspberrypi-kernel is in 
"http://archive.raspberrypi.org/debian/ stretch main", so i left this in 
my sources list, but pinned it with priority 200, so no other packages 
are installed by accident.


Another way to update bootloader and kernel is through rpi-update.

At the moment all is working ok.

Am 2018-09-16 15:52, schrieb J. Fahrner:

Hi,
I dd'ed devuan_ascii_2.0.0_armhf_raspi2.img on sd card for my
Raspberry Pi 2 model B, but it does not boot. No action, black screen.
Are here any experiences with that model?

In the past I installed Raspbian Jessie and migrated that to Devuan,
but this no longer works because they changed installation of kernel
with Stretch. In Jessie bootloader and kernel were in a separate
section of repository (rpi) and could also be upgraded in parallel to
Devuan repositories. But in Stretch it appears kernel and bootlader
are in the main section, so they no longer get updates when switching
to Devuan repositories.

Are there packages for the Raspberry Pi kernel and bootloader also in
Devuan repositories? If yes, what are the correct package names?

Jochen
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry-Pi ?

[KatolaZ]

On Mon, Mar 27, 2017 at 10:21:27AM -0400, Renaud OLGIATI wrote:
> On Mon, 27 Mar 2017 14:21:58 +0100
> KatolaZ  wrote:
> 
> >  
> > https://files.devuan.org/devuan_jessie_beta/embedded/devuan_jessie_1.0.0-beta2_arm64_raspi3.img.xz
> 
> Would it run on the RP-2 ?
>  

Nope, since that one is an arm64 image. For the rpi2 you should use:

  devuan_jessie_1.0.0-beta2_armhf_raspi2.img.xz

which is an armhf image. Otherwise, the armel image for rpi1:

  devuan_jessie_1.0.0-beta2_armel_raspi1.img.xz

should work on all of them, but with soft FP.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry-Pi ?

[Ron]

On Mon, 27 Mar 2017 14:21:58 +0100
KatolaZ  wrote:

>  
> https://files.devuan.org/devuan_jessie_beta/embedded/devuan_jessie_1.0.0-beta2_arm64_raspi3.img.xz

Would it run on the RP-2 ?
 
Cheers,
 
Ron.
-- 
  Physics is like sex: 
  sure, it may give some practical results,
  but that's not why we do it. 
 -- Richard Feynman

   -- http://www.olgiati-in-paraguay.org --
 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry-Pi ?

[Stefan Mark]

On Mon, 27 Mar 2017 14:21:58 +0100
KatolaZ  wrote:

> On Mon, Mar 27, 2017 at 09:12:11AM -0400, Renaud OLGIATI wrote:
> > ISTR having seen a mention of this go past, I now have a Raspberry
> > Pi, and cannot find where to download it  ;-3(
> > 
> > Does it still exist ?  
> 
> Hi Renaud, 
> 
> It should still be there:
> 
>  
> https://files.devuan.org/devuan_jessie_beta/embedded/devuan_jessie_1.0.0-beta2_arm64_raspi3.img.xz
> 
It was there yesterday, although it seems that the device tree overlay
stuff does not work. At least, i did not get it to work.


pgp3xKq1_gnPO.pgp
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan for Raspberry-Pi ?

[KatolaZ]

On Mon, Mar 27, 2017 at 09:12:11AM -0400, Renaud OLGIATI wrote:
> ISTR having seen a mention of this go past, I now have a Raspberry Pi, and 
> cannot find where to download it  ;-3(
> 
> Does it still exist ?

Hi Renaud, 

It should still be there:

 
https://files.devuan.org/devuan_jessie_beta/embedded/devuan_jessie_1.0.0-beta2_arm64_raspi3.img.xz

HH

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[Jochen Fahrner]

Am 06.02.2017 um 12:11 schrieb Jaromil:
> The main reasons why Devuan acts like Debian in this case is that in
> Jessie we only operate to remove systemd, nothing else changes, while
> we still rely heavily on Debian for the bulk of binary builds.
>

Ok, I see it's Debians fault for the improper architecture
classification. VFP exists since ARMv5, but Debian decided to use VFP on
ARMv7 and above.
https://www.arm.com/products/processors/technologies/vector-floating-point.php

Are there any experiences what the impact on performance is, using
softfloat on a headless internet server box serving mainly files (smb,
http, ftp), doing no mathematic computations? Is FP used in encryption
technologies (ssl)?

-- 
Mit besten Grüßen
Jochen Fahrner

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[Jaromil]

dear Jochen,

tl;dr - just like Debian does, we do recommend using Raspian on rpi1
boards version 1 to take full advantage of their rather strange
architecture.

> On Mon, Feb 06, 2017 at 11:18:41AM +0100, Jochen Fahrner wrote:
> 
> [cut]
> 
> > 
> > The only option I have: install from scratch with Devuans "armel" Image.
> > But this is not really an option,  I will loose hardfloat, making my PI
> > even more slower than it already is. So I stay with Raspbian Jessie.
> > 

On Mon, 06 Feb 2017, KatolaZ wrote:
> I agree that we might decide to have an armv6+VFP2 Devuan image for
> rpi, but please do not call it armhf, since the price would be
> increasing the amount of confusion already made by Raspbian.

I was indeed surprised to read an rpi1 is 'armhf' platform.  Thanks
Katolaz and others for clarifying, did recall some discussion about
this in the past but lacked the details.

The main reasons why Devuan acts like Debian in this case is that in
Jessie we only operate to remove systemd, nothing else changes, while
we still rely heavily on Debian for the bulk of binary builds.

the Devuan installers for embedded architectures are all here
https://files.devuan.org/devuan_jessie_beta/embedded/

ciao

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[KatolaZ]

On Mon, Feb 06, 2017 at 11:18:41AM +0100, Jochen Fahrner wrote:

[cut]

> 
> The only option I have: install from scratch with Devuans "armel" Image.
> But this is not really an option,  I will loose hardfloat, making my PI
> even more slower than it already is. So I stay with Raspbian Jessie.
> 

I agree that we might decide to have an armv6+VFP2 Devuan image for
rpi, but please do not call it armhf, since the price would be
increasing the amount of confusion already made by Raspbian.

My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[KatolaZ]

On Mon, Feb 06, 2017 at 11:18:41AM +0100, Jochen Fahrner wrote:
> Am 06.02.2017 um 09:22 schrieb KatolaZ:
> > Like, for the same reason why you use packages compiled for amd64 with
> > your shiny Intel i5, despite you could have used packages compiled for
> > an i486 back in 1994? :)
> >
> 
> That's exactly the point. Nobody comes up with the idea to compile
> packages for the Intel platform only for the newest shiny Corie i7. So
> why do Devuan compile for ARMv7?
> 
> Raspbian made the decision to divide into architecture "armel" (PI 1A) 
> and "armhf" (PI 1B and later). So Devuan should do the same. If not, it
> comes to problems like mine: migrating from Raspbian Jessie with
> architecture "armhf" ends in segmentation faults on many PIs.

According to your reasoning then , since Raspbian decided to go for
systemd, Devuan should also do the same, right? :) And what happens if
Arch decides to move to a BSD kernel? Shall Devuan move there as well?

The real problem is that the "armhf" used in Raspbian is not a proper
armhf, but an armv6+VFP2. And it is *not* armhf since by armhf we (in
the De??an world) normally indicate armv7:

  https://www.debian.org/ports/arm/

And you will notice it immediately if you start using the vanilla
Debian armhf release on your rpi, since Debian's armhf is a proper
armv7 build. You will get in fact the same segfaults you get with the
Devuan repos.

The mistake was done by Raspbian, when they used "armhf" to indicate a
port that is different from what "armhf" really means in Debian. The
fact that they made a mistake does not mean that it should be
perpetrated down for generations, IMHO.

My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[Jochen Fahrner]

Am 06.02.2017 um 09:22 schrieb KatolaZ:
> Like, for the same reason why you use packages compiled for amd64 with
> your shiny Intel i5, despite you could have used packages compiled for
> an i486 back in 1994? :)
>

That's exactly the point. Nobody comes up with the idea to compile
packages for the Intel platform only for the newest shiny Corie i7. So
why do Devuan compile for ARMv7?

Raspbian made the decision to divide into architecture "armel" (PI 1A) 
and "armhf" (PI 1B and later). So Devuan should do the same. If not, it
comes to problems like mine: migrating from Raspbian Jessie with
architecture "armhf" ends in segmentation faults on many PIs.

The only option I have: install from scratch with Devuans "armel" Image.
But this is not really an option,  I will loose hardfloat, making my PI
even more slower than it already is. So I stay with Raspbian Jessie.

-- 
Mit besten Grüßen
Jochen Fahrner

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[KatolaZ]

On Mon, Feb 06, 2017 at 06:32:54AM +0100, J. Fahrner wrote:
> Am 05.02.2017 um 22:34 schrieb KatolaZ:
> > Because that image is an armv6 + hard float, so it works
> > everywhere. 
> >
> >
> 
> So why are the Devuan Images not compiled the same way?
> 

Like, for the same reason why you use packages compiled for amd64 with
your shiny Intel i5, despite you could have used packages compiled for
an i486 back in 1994? :)

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[J. Fahrner]

Am 05.02.2017 um 22:34 schrieb KatolaZ:
> Because that image is an armv6 + hard float, so it works
> everywhere. 
>
>

So why are the Devuan Images not compiled the same way?

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[KatolaZ]

On Sun, Feb 05, 2017 at 10:02:21PM +0100, J. Fahrner wrote:

[cut]

> 
> But thats without hardfloat. What I need is ARMv6 with hardfloat. I'm
> wondering why Raspbian has only one Image that works with all. How do
> they do that?
> https://www.raspberrypi.org/downloads/
> 

Because that image is an armv6 + hard float, so it works
everywhere. 

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[Florian Zieboll]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


On Sun, 5 Feb 2017 22:02:21 +0100
"J. Fahrner"  wrote:

> But thats without hardfloat. What I need is ARMv6 with hardfloat. I'm
> wondering why Raspbian has only one Image that works with all. How do
> they do that?
> https://www.raspberrypi.org/downloads/


The images contain both, the ARMv6 and the ARMv7 kernel... regarding
the userspace software, I just had a look at the Raspbian FAQ, where is
written that 

  "The packages are being compiled for the ARMv6+VFP CPU. If the
  hardware supports that CPU feature set then Raspbian should function
  well on that hardware." [1]

Libre Grüße,

Florian


[1] 
http://raspbian.org/RaspbianFAQ#Will_Raspbian_work_with_non-Raspberry_Pi_systems.3F

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYl5pUAAoJEO5FSXn+RB/Wwe0QAKwdyClqR8bFk+L/sRn+0Bnr
XrjQEWF4dwBukK/QYtT486dnSyt/It+6q+G/8fGejegIRKP0pAchh8EXIQsIINmV
xvYy09K9WMI6sj+qJXULvNQ6rbJYCou/Ysv0tfrjgtmoG2Ij8rlmKm4A8se3ulCI
N+bGBZcZ9Zi9KXPhF/6xeOLi6xi7ekIIya01OzZM3yaDhUX9lBzQn5z/vbf/ie3H
XuhYcX80xp/5E/maUbFre0rH3AEwARpk3byFrOvpgamdZlV4e3DQH6ry72c2v3pn
cp9BLR0s9QSe/2ETetp2zDFaUo7GHM0aTl26BEBrxqHa4P5Ut/jZGJISWmHLBx0h
shKVPNMMtkUcaVcC9QbHncEY7YO5CUXCHoXJNeShkHcitLgsqD+Dywn2SCaX20ld
da6Vra0a1pDVAtmzcXCg0BWl2jfEw7WWEmhtHzUPz5HfViFmijoaN91W5S3I3h0H
nlVWjwez1Ivd+nz1Sv80M3DnmkuPRsPWLbgyVw4TuynoItvzJE660w+nJWcqdCzl
1elN6J7V3kDcj/UQ9eOrxE5QBBbFLg8q7WhsdfyKsYBku+3CuJwAlCRZlh3lBB2o
JlvH8tkYzzB31Ij1lYYAQaW+YnPT2EYInazu05+tw1RpJPDRPx7kJmV9b+9NV+dg
efYCSs1T62YcXMs8AJ32
=w7sc
-END PGP SIGNATURE-
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[J. Fahrner]

Am 05.02.2017 um 18:58 schrieb Florian Zieboll:
>
> "Raspbian armhf" is a special build for rpi1: ARMv6 with hardfloat
> support. This is the actual reason for Raspian's existence, as the
> common "armhf" builds are compiled for ARMv7.

ok, that explains the segmentation faults on my PI1 model B.

>
> If you don't want to use Raspbian, you'll need to go for the armel
> build:
>
> https://files.devuan.org/devuan_jessie_beta/embedded/devuan_jessie_1.0.0-beta2_armel_raspi1.img.xz

But thats without hardfloat. What I need is ARMv6 with hardfloat. I'm
wondering why Raspbian has only one Image that works with all. How do
they do that?
https://www.raspberrypi.org/downloads/


-- 
Mit besten Grüßen
Joachim Fahrner

PGP-Key: http://www.fahrner.name/JoachimFahrner.asc
---
Es gibt keine Cloud. Es ist nur der Computer eines Anderen.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[Florian Zieboll]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 5 Feb 2017 18:36:29 +0100
"J. Fahrner"  wrote:

> Strange. Mine is a PI 1 Model B. (armhf architecture). Maybe the
> current packages are not compatible with that? But original Raspbian
> Jessie (armhf) works fine. Only Devuan has segmentation faults.


"Raspbian armhf" is a special build for rpi1: ARMv6 with hardfloat
support. This is the actual reason for Raspian's existence, as the
common "armhf" builds are compiled for ARMv7.

If you don't want to use Raspbian, you'll need to go for the armel
build: 

https://files.devuan.org/devuan_jessie_beta/embedded/devuan_jessie_1.0.0-beta2_armel_raspi1.img.xz

Florian
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYl2fPAAoJEO5FSXn+RB/W2NwP/1Sm7k3nFaHPi8p6OQX/2fXg
ZvV5I1LMVY447r3yGoV2kcdAI6xXoOAPhWzLw2H15dRppFQcyZdKqUv0AU905LM2
zTcE38XPKGrt4tyiRXWqMNLAw1JVNetHKa47ypv7q3wMqvZE88LYrDu0kwxm2mO8
XU3WKl6MG6u89Apjj/2QZGDtVAjIUxn+Xy93aEJIwda9Jtdxh4MEMNwq+mtGY5vO
p1UWXr6TsDt7QMwY47ZEVGlyI8H89Wssh0kL9IWBimXphm6k1bX1E9RmWNcVs8zf
8fAXYkAAPbWrVPtyq+CoOax2ffTv2pT03BdEAjB1J+n2tFNR4Sda7EdaXFfKoPmr
jUUBbU9/MDNqzccBnbNIxJ60I78adc8IgvZJlXDtc7V9lRZuQDirkSO3s4QTC1yN
xVYDd69vKPbpV//iB4qRZj+m5+rXidcGTqiZI90bNDyEMUnaoabfNKdhuVbtf5Kr
EB/kB20YOTqMdXe2SyDuYrnWEk8pli4VF+NKf+dK6nvgJdjLxEkEufHepuffk+6m
Zpd0KH5DTIIWa/BojhRFfPI3h6koyyM5JgVQ/1z9x35AdUO0NFuP15o9wkny7HO+
utyMP7VlPXKOEmJUqFDc6xPRpg+eVBVHb3Y4GCXiuzIIZBtVcwNlNfEtg9XKo93o
oVvXQRPrbrtITOUH1WV6
=kjHy
-END PGP SIGNATURE-
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[KatolaZ]

On Sun, Feb 05, 2017 at 05:51:54PM +0100, J. Fahrner wrote:
> Hello,
> 
> has someone had success in installing Devuan on Raspberry Pi?
> 
> My first attempt was to upgrade from Raspbian Wheezy following this guide:
> 
> https://git.devuan.org/dev1fanboy/Upgrade-Install-Devuan/wikis/Upgrade-to-Devuan
> 
> Did not work, segmentation fault in some package installation script.
> 
> Next try: installed image from Devuan downloads to SD card. Did not
> boot. :-(

Hi,

I have been using the latest Devuan Beta 2 rpi images:

   https://files.devuan.org/devuan_jessie_beta/embedded/

on a rpi-zero (raspi1), a rpi-2 (raspi2), and a rpi-3 (raspi3) for
several weeks now, and all of them work seamlessly. You can have
problems when you try to upgrade a rpi from Raspbian, since Raspbian
has made a lot of confusion with architecture names. Go with the
genuine images, and select the correct ones for your pi model, since
the three available ones are different (raspi1 is armel, raspi2 is
armhf, and raspi3 is arm64).

My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[Hendrik Boom]

On Sun, Feb 05, 2017 at 06:36:29PM +0100, J. Fahrner wrote:
> 
> 
> Am 05.02.2017 um 18:23 schrieb Florian Zieboll:
> >
> >
> > Both ways it worked like a charm.
> >
> 
> Strange. Mine is a PI 1 Model B. (armhf architecture). Maybe the current
> packages are not compatible with that? But original Raspbian Jessie
> (armhf) works fine. Only Devuan has segmentation faults.

Interesting.  Just what are the differences between Raspian and Debian?
Does Debian also segfault?  If not, perhaps it's worth seeing if the 
changes from Debian to Raspian need to be applied to Devuan to produce 
Raspuan?

-- hendrik
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[J. Fahrner]

Am 05.02.2017 um 18:23 schrieb Florian Zieboll:
>
>
> Both ways it worked like a charm.
>

Strange. Mine is a PI 1 Model B. (armhf architecture). Maybe the current
packages are not compatible with that? But original Raspbian Jessie
(armhf) works fine. Only Devuan has segmentation faults.

-- 
Mit besten Grüßen
Joachim Fahrner

PGP-Key: http://www.fahrner.name/JoachimFahrner.asc
---
Es gibt keine Cloud. Es ist nur der Computer eines Anderen.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[Florian Zieboll]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


On Sun, 5 Feb 2017 17:51:54 +0100
"J. Fahrner"  wrote:

> has someone had success in installing Devuan on Raspberry Pi?

I have Devuan armhf running on a rpi2, installed from the first Beta image - 
here
the link to my li'l HOWTO [1].

Some time before, I had installed Devuan using the raspbian-ua-netinst
image for a minimal Raspian Wheezy installation, which I then upgraded to
Devuan Jessie, see link [2]. As of raspbian-ua-netinst v1.0.8.1, the
default release has changed to Jessie and thus the following line would have to 
be
added the the file config.txt in the root of the image: 

release=wheezy

Both ways it worked like a charm.

libre Grüße,

Florian


[1] https://cheatsheet.zwischenspeicher.info/2016/05/11-2016-05-05/  
[2] https://lists.dyne.org/lurker/message/20150805.163347.dcffacec.en.html


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYl1+FAAoJEO5FSXn+RB/Wdu8P/0pXt6HLGCk4e/Ffjlh7d+AE
fg+/hfwnxrmcsfY6Ov6mLAvNppU0zgw12C39YnRJckDeQSXQjxXLjGd9SGKzMy0p
6ofWWspykv/5O04qi1wcOk7j9H8EjmnGLMngAjCNCwQIYA7WUvRVoQAVL6CgqcU+
bjKhYEM/q6WTikwCicmRmjnG8QbyIlCcma+FMWoFtR6S9KLKMTPSGwI/qwp3nXcw
ed7Nm8pQZwnZBERdUXr0lcsLtT+kOG9SybeulnI2EhqtCQrfonwGAOXFLo80gNKm
Cpkzni+84aodDyxYA29o60uwc5VFd6PZDyAfe0TJoITRhbHM2/h47p3GhyR25Mp5
UDsK/tuJC58lGr9K5AZavqrvURGIpL7WcmoKjvWDpQTnGJEzFHuMLfmzeEf1RcEn
I88DNPkKGIbmBBGzfbAJReI8V9ZJhRp6XcbPIhZqg9nF+HcbssM1xwbo3gTCHTFr
O9+AcXEUIF/t7b4sI3cRW3c8k919DaN/TpYzM3PMdHfTnMykaGdbGyVm3CiaPGx5
v9/A7V/GLERMUp6Nf9hY4CREVjNqAV9KOuxoDyr6Ft/c7bui2nhplkJVLd7PB3Av
w0/u9uHxB6SmsZQJ428Z1gkKahsrhPokg5Fjc0knTVu6FeULX2WQkIqJhHj2W2q/
qxyh/GHcMqWp0oJZklt9
=7nOA
-END PGP SIGNATURE-
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan on Raspberry Pi

[etech3]

On 02/05/2017 11:51 AM, J. Fahrner wrote:
[snip]

has someone had success in installing Devuan on Raspberry Pi?
Havn't gotten around to Pi yet, But did have a Acer laptop with no 
cd/dvd. I installed from a external usb cd/dvd, and I copyies the beta2 
iso to usb and installed that way.


justmy2cents
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng