Re: Cheap NAS
On 17/10/22 9:32 am, Stefan Monnier wrote: pa...@quillandmouse.com [2022-10-16 14:22:16] wrote: Pi's don't have SATA. Depends on the flavor. Banana Pi and Orange Pi mini definitely do. [ But not a very good one, admittedly. And their power infrastructure tends to be overwhelmed when you connect a spinning rust drive (I've had to try various power adapters and power cables before the setup was reliable enough). ] I run a very competent NanoPi M4V2 based on Rockchip 3399 SOC. It supports 2 x NVME PCI-e drives and/or 4 x SATA drives, plus several USB-3 drives It's more than fast enough to saturate its Gigabit LAN with data in NAS configuration. It also has built in Wifi. The M4V2 at around $100 US is a lot cheaper than the chassis, power supply, and 4 x drives required to make up the rest of a conventional NAS. However NVME PCI-e is an option. For reference, a 1TB M4V2 server on a NVME PCI-e drive will be under $250 US - depending on the current price of drives. I run my M4V2 using a single NVME PCI-e drive and it acts as mail and web server and provides SAMBA services. It would be possible to go to the 4 x SATA drive configuration, but 1 TB of very reliable NVME PCI-e flash seems sufficient for my needs. The whole thing (1TB server) is about the size of a thick paperback book and sits on a shelf without air conditioning - even through my Australian summers. I use Armbian on it, but there are a variety of operating systems available (including Debian?) -- Jeremy OpenPGP_signature Description: OpenPGP digital signature
Re: Apt upgrade problem
On Sun 16 Oct 2022 at 23:44:00 (+0100), Mark Fletcher wrote: > > Tonight I am seeing a behaviour pattern in my Debian Bullseye system that I > have not seen before. > > After "sudo apt update", the system informs me there is 1 package that can > be upgraded. > > "sudo apt upgrade" reports nothing to do, 0 packages upgraded, 0 newly > installed, 0 to remove and 0 not upgraded... > > "apt list --upgradable" shows a new version of the Amazon Workspaces > client, version 4.3.0.1766. It also shows that there is one more version > available. > > "apt list -a --upgradable" shows: > > Listing... Done > workspacesclient/unknown 4.3.0.1766 amd64 [upgradable from: 4.2.0.1665] > workspacesclient/now 4.2.0.1665 amd64 [installed,upgradable to: 4.3.0.1766] > > "sudo apt install" reports: > > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > > System doesn't seem to want to install the new version of the Amazon > workspaces client. I'm assuming some dependency not known to the system is > needed for the new version. However I also note the /unknown after the > package name in the new version, which is /now in the current version. I am > not sure what that is, but presumably /unknown isn't good... Can anyone > suggest an approach to investigate why this upgrade won't happen? > > In case important, Amazon workspaces client is included in my package list > by "amazon-workspaces-clients.list" in /etc/apt/sources.list.d/ : > > deb [arch=amd64] https://d3nt0h4h6pmmc4.cloudfront.net/ubuntu bionic main > > That comes from the install instructions page of the Amazon Workspaces > client. It did occur to me that perhaps the new version needs some > additional repository, so I went back and checked but the installation > instructions have not changed, so it seems not. AFAIK the apt list command is only examining your lists that you updated, whereas apt install is looking for the package itself. So, apart from just trying again later, I would check if the package is actually in the archive mirror you're using (or any other). I don't think it would be the first time that a package's existence is glimpsed in the lists before it actually gets transferred into a particular mirror. (I don't know anything about the ubuntu archives and that reference.) Cheers, David.
Re: Cheap NAS
pa...@quillandmouse.com [2022-10-16 14:22:16] wrote: > Pi's don't have SATA. Depends on the flavor. Banana Pi and Orange Pi mini definitely do. [ But not a very good one, admittedly. And their power infrastructure tends to be overwhelmed when you connect a spinning rust drive (I've had to try various power adapters and power cables before the setup was reliable enough). ] > They can run SATA over USB. However, with 9 TB of storage of media > files, I'm afraid this would throttle my access to storage. It depends on many factors, most importantly how you communicate with that Pi box: in many cases the link between you and the Pi box will be the main bottleneck rather than the link between the Pi box and the drive. Stefan
Apt upgrade problem
Hi Tonight I am seeing a behaviour pattern in my Debian Bullseye system that I have not seen before. After "sudo apt update", the system informs me there is 1 package that can be upgraded. "sudo apt upgrade" reports nothing to do, 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded... "apt list --upgradable" shows a new version of the Amazon Workspaces client, version 4.3.0.1766. It also shows that there is one more version available. "apt list -a --upgradable" shows: Listing... Done workspacesclient/unknown 4.3.0.1766 amd64 [upgradable from: 4.2.0.1665] workspacesclient/now 4.2.0.1665 amd64 [installed,upgradable to: 4.3.0.1766] "sudo apt install" reports: Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. System doesn't seem to want to install the new version of the Amazon workspaces client. I'm assuming some dependency not known to the system is needed for the new version. However I also note the /unknown after the package name in the new version, which is /now in the current version. I am not sure what that is, but presumably /unknown isn't good... Can anyone suggest an approach to investigate why this upgrade won't happen? In case important, Amazon workspaces client is included in my package list by "amazon-workspaces-clients.list" in /etc/apt/sources.list.d/ : deb [arch=amd64] https://d3nt0h4h6pmmc4.cloudfront.net/ubuntu bionic main That comes from the install instructions page of the Amazon Workspaces client. It did occur to me that perhaps the new version needs some additional repository, so I went back and checked but the installation instructions have not changed, so it seems not. Thanks in advance Mark
Re: vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
On Sun, Oct 16, 2022 at 10:05:07PM +0200, Paul van der Vlis wrote: > Op 16-10-2022 om 12:52 schreef Gijs Hillenius: > > Hallo > > > > Acht jaar geleden installeerde ik deze raid1: > > > > lsblk --fs > > NAME FSTYPELABEL MOUNTPOINT > > sdb > > ├─sdb1 linux_raid_member harde-schijf:0 > > │ └─md0ext4/boot > > ├─sdb2 linux_raid_member harde-schijf:2 > > │ └─md2 > > │ └─md2_crypt (dm-1) swap[SWAP] > > └─sdb3 linux_raid_member harde-schijf:1 > >└─md1crypto_LUKS > > └─md1_crypt (dm-0) ext4/ > > sda > > ├─sda1 linux_raid_member harde-schijf:0 > > │ └─md0ext4/boot > > ├─sda2 linux_raid_member harde-schijf:2 > > │ └─md2 > > │ └─md2_crypt (dm-1) swap[SWAP] > > └─sda3 linux_raid_member harde-schijf:1 > >└─md1crypto_LUKS > > └─md1_crypt (dm-0) ext4/ > > > > > > En nu moet ik die herbouwen, met twee nieuwe en grotere schijven. > > > > Ik weet niet (meer) in welke stap ik de / /boot en swap partities > > definieer. > > > > Maak ik 1 raid partitie op beide schijven, en verdeel ik daarna met > > lvm+encryptie de schijf in 3 partities? > > > > Of moet ik elke harde schijf in 3 verdelen, en van elke 2 gelijke > > partities dan één raid1 partitie maken? > > Als ... > ... Ik zou hem maken > > ... zou ik dus ... naar ... > ... En verder testen ... > Ik zou tijd nemen om e-mail te beantwoorden. Groeten Geert Stappers -- Silence is hard to parse
Re: vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
Op 16-10-2022 om 12:52 schreef Gijs Hillenius: Hallo Acht jaar geleden installeerde ik deze raid1: lsblk --fs NAME FSTYPELABEL MOUNTPOINT sdb ├─sdb1 linux_raid_member harde-schijf:0 │ └─md0ext4/boot ├─sdb2 linux_raid_member harde-schijf:2 │ └─md2 │ └─md2_crypt (dm-1) swap[SWAP] └─sdb3 linux_raid_member harde-schijf:1 └─md1crypto_LUKS └─md1_crypt (dm-0) ext4/ sda ├─sda1 linux_raid_member harde-schijf:0 │ └─md0ext4/boot ├─sda2 linux_raid_member harde-schijf:2 │ └─md2 │ └─md2_crypt (dm-1) swap[SWAP] └─sda3 linux_raid_member harde-schijf:1 └─md1crypto_LUKS └─md1_crypt (dm-0) ext4/ En nu moet ik die herbouwen, met twee nieuwe en grotere schijven. Ik weet niet (meer) in welke stap ik de / /boot en swap partities definieer. Maak ik 1 raid partitie op beide schijven, en verdeel ik daarna met lvm+encryptie de schijf in 3 partities? Of moet ik elke harde schijf in 3 verdelen, en van elke 2 gelijke partities dan één raid1 partitie maken? Als je grotere schijven wilt kunnen gebruiken dan 2TB dan moet je UEFI gebruiken en dan heb je GPT en een "BIOS boot" partitie nodig. Vaak is die maar 1 MB groot. Ik zou hem maken op zowel sda1 als sdb1. Alleen die op sda1 zal worden gebruikt, maar ik zou later als de boel klaar is met dd de inhoud van sda1 kopieren naar sdb1, en op sdb ook grub installeren. De doelstelling is dat sdb sda kan vervangen als deze kapot mocht zijn. Eventueel door hem fysiek op de plek van sda te zetten of in het bios te kiezen voor de andere disk. Dit zou ik ook willen testen (maar later). Dan zou ik van de rest van de disks twee raids maken, eentje voor /boot (niet encrypted) en een andere die je encrypt met cryptsetup en LUKS. In dat encrypted volume maak je dan een LVM volume groep, waarin je weer logical volumes maakt. Een van die logical volumes is je swap, en uiteraard kun je meer volumes maken. Voordeel van LVM is, dan je maar 1 keer je paswoord hoeft in te geven voor meerdere volumes. En ook verder is LVM fijn. Laat altijd nog wat ruimte vrij, zodat je je volumes later nog kunt uitbreiden. Als je klaar bent zou ik dus sda1 kopieren naar sdb1, en grub ook installeren op sdb. En verder testen of het systeem ook wil booten terwijl sdb op de plaats van sda zit. Of evt zonder sda. Groet, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://vandervlis.nl/
Re: Cheap NAS
Am 16.10.22 um 20:19 schrieb pa...@quillandmouse.com: On Sun, 16 Oct 2022 10:11:50 -0400 Wayne Sallee wrote: What about just putting some drives in a desktop, and installing some free nas software like https://linuxhint.com/best-nas-software-linux It's possible, but it sort of violates the size and power requirements in my scenario. Paul What's about to use a (old) ThinClient with space for 1 or 2 2,5" drives? I use a old FSC Futro 920 as router and LAN storage server with soft raid. My setup: - FSC Futro 920 (with AMD GX-222GC 2x2,2Ghz) - mSATA to SATA adapter (ASM1062) to get more SATA ports - 4 Port NIC (not need for your setup I think) - The drives are stacked with https://www.ryang3d.com/shop/ssd-stackers/ power consumption is round about 15-20 W more than a Raspberry or similar hardware but not more than a (in Germany very popular) fritzbox.
Re: Cheap NAS
On Sun, 16 Oct 2022 23:04:03 +0500 Stanislav Vlasov wrote: > 2022-10-16 21:58 GMT+05:00, Andrew M.A. Cater : > >> > What about just putting some drives in a desktop, and installing > >> > some free > >> > nas software like > >> > https://linuxhint.com/best-nas-software-linux > >> > >> OpenMediaVault work fine even on Orange Pi 3 LTS with usb drives. > > > > USB connected drives work fine - until they don't ... I learned > > that the hard way 15 years ago [LVM done that way and you'd lose a > > drive ...]. > > I know. Mitigate it by installing all to wooden board and don't use > LVM on external drives. > Orange Pi 3 LTS does not have another interfaces for really big > non-network drives, only one usb3.0 (up to 100-110MB/s on my hdd > drives, does not test on ssd) and two usb2.0 (up to 30MB/s) > It's also worth noting: on my setup with a spinning rust laptop drive hooked via USB 3 to my RPi, the drive doesn't spin continuously (apparently). So on occasional use, I wait a couple of seconds for the drive to spin up before it can transfer at full speed. It's possible an SSD would solve this, but I had the laptop drive around already. Paul -- Paul M. Foster Personal Blog: http://noferblatz.com Company Site: http://quillandmouse.com Software Projects: https://gitlab.com/paulmfoster
Re: Cheap NAS
On Sun, 16 Oct 2022 19:21:05 +0500 Stanislav Vlasov wrote: > 2022-10-16 19:11 GMT+05:00, Wayne Sallee : > > What about just putting some drives in a desktop, and installing > > some free nas software like > > https://linuxhint.com/best-nas-software-linux > > OpenMediaVault work fine even on Orange Pi 3 LTS with usb drives. > Pi's don't have SATA. They can run SATA over USB. However, with 9 TB of storage of media files, I'm afraid this would throttle my access to storage. FWIW, I do use a Pi with a laptop drive to run my LAN web server. Paul -- Paul M. Foster Personal Blog: http://noferblatz.com Company Site: http://quillandmouse.com Software Projects: https://gitlab.com/paulmfoster
Re: Cheap NAS
On Sun, 16 Oct 2022 10:11:50 -0400 Wayne Sallee wrote: > What about just putting some drives in a desktop, and installing some > free nas software like https://linuxhint.com/best-nas-software-linux > It's possible, but it sort of violates the size and power requirements in my scenario. Paul -- Paul M. Foster Personal Blog: http://noferblatz.com Company Site: http://quillandmouse.com Software Projects: https://gitlab.com/paulmfoster
Re: Strange syslog behaviour [Solved]
On Sun 16 Oct 2022 at 09:09:36 (-0400), Wayne Sallee wrote: > I wrote: > > On Sat 15 Oct 2022 at 13:59:18 (-0400), Wayne Sallee obfuscated the > > following with HTML: > > > > > Jeremy Ardley, did you update your code from " invoke-rc.d rsyslog rotate > > > > /dev/null" to > > > "/usr/lib/rsyslog/rsyslog-rotate"? > > I've added a new post to that part of the thread. I think your > > problem concerns changing to systemd, whereas his concerns mixing > > inetdutils-* packages with the more usual equivalent ones. > > > > > So I got my servers straitened out, I think. I will know tomorrow. > > > For anyone else running into this problem, the problem was caused from > > > modifying > > > /etc/logrotate.d/rsyslog then upgrading to Buster. > > > The fix: > > > diff /etc/logrotate.d/rsyslog.dpkg-dist /etc/logrotate.d/rsyslog > > > edit /etc/logrotate.d/rsyslog > > > Change from > > > invoke-rc.d rsyslog rotate > /dev/null > > > to > > > /usr/lib/rsyslog/rsyslog-rotate > > > Then delete /etc/logrotate.d/rsyslog.dpkg-dist > > > I then rebooted my servers to get the syslog used. > > > Then > > > ls /var/log | grep syslog > > > To see that it was working. I will know tomorrow if it is still working. > > I think the point you've missed is that at some stage, you upgraded > > from SystemV to systemd. Whenever that happened, the upgrade to > > rsyslog would have supplied a new /etc/logrotate.d/rsyslog file > > containing "/usr/lib/rsyslog/rsyslog-rotate", which knows how to > > handle both SystemV and systemd systems. > > My situation is now solved. It's working as it should. I think Debian > 9 is systemd by default, so I don't think it was a change from systemv > to systemd. But it was definitely a change in programs used that > required the change to "rsyslog-rotate". That's right: AIUI buster is when rsyslog started using systemd to rotate the logs, rather than the compatibility script that's still present in /etc/init.d/ for non-systemd users. The decision is now made in /usr/lib/rsyslog/rsyslog-rotate. > > You rejected the new file, which is why it was instead written to > > /etc/logrotate.d/rsyslog.dpkg-dist (which you could have safely > > left or removed—it's harmless). > > Yes, I rejected the new file, causing the other file to be there. It > would be nice if updates told what needed to be updated in the old > file when updates are done. If you reject the file, it falls to you to look at what changes were made. All the system knows is that your file's message digest doesn't match what dpkg expects as the old Debian version. > > Effectively, your edit has merged the contents of both files, > > whatever changes you made earlier before the Buster upgrade, > > and the vital change that would have been made for you if > > you'd accepted the new version. > > But If I had accepted the new file, it would probably have discarded the > changes that I had made. Yes. It's a while since I did this, but I'm almost certain that your own version would be renamed as *.dpkg-old were you to accept the new version. > It would be nice if updates presented "old file", "new file", "combined > file"; choice: (1), (2), (3). (3) isn't really practicable, and you couldn't really set that as Policy unless it could be more or less guaranteed to work. To mis-quote Tolstoy, “Happy updates are all alike; every unhappy update is unhappy in its own way.” You could use patch to generate a .diff between your version and its original, then apply the patch to the new Debian version. Fine when it works, but there's no guarantee. It requires a certain discipline when making any changes. So it's safer to leave the choice of process to the system administrator. Cheers, David.
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
On Sun 16 Oct 2022 at 17:24:05 (+0200), Mario Marietto wrote: > Il giorno dom 16 ott 2022 alle ore 10:50 Thomas Schmitt ha scritto: > > On Sat 15 Oct 2022 at 23:03:41 (+0200), Mario Marietto wrote: > > > echo logo_debian_dark.png | cpio -H newc -o -A -F > > > initrd/usr/share/graphics > > > cpio: can't open initrd/usr/share/graphics: Is not a directory > > > > cpio option -F expects the path to the archive as argument. I.e. the path > > to the uncompressed initrd. > > > > > The images that I should edit are inside this archive / folders : > > > initrd/usr/share/graphics > > > > Are you sure about the first path component "initrd/" ? > > I see the path without it: > > > > $ gunzip < /mnt/iso/d-i/gtk/initrd.gz | cpio -t | fgrep > > logo_debian_dark.png > > 264529 blocks > > usr/share/graphics/logo_debian_dark.png > > > > > I should decompress it and I will have the file called "initrd",that's a > > > cpio file. The images that I should edit are inside this archive / > > > folders : > > > > > > initrd/usr/share/graphics > > > > > > and they are called : logo_debian.png and logo_debian_dark.png ; > > > > > > at this point this is what I did to add two new image files inside the > > > archive in the same position of the old ones : > > > > So i expect that you want to create a new copy of that file inside the > > initrd. No, that would be dishonest: they are no longer Debian logos. You should give names to your edited files that indicate what they are: /your/ images for /your/ derivative. Add them to the archive and change the symlinks there. You should end up with something like: drwxr-xr-x 2 root root 0 Mar 22 2022 usr/share/graphics -rw-r--r-- 1 root root 14649 Feb 15 2021 usr/share/graphics/logo_debian.png -rw-r--r-- 1 root root 14649 Feb 15 2021 usr/share/graphics/logo_debian_dark.png -rw-r--r-- 1 root root 12345 Oct 15 23:59 usr/share/graphics/logo_marietto.png -rw-r--r-- 1 root root 12345 Oct 15 23:59 usr/share/graphics/logo_marietto_dark.png lrwxrwxrwx 1 root root15 Feb 15 2021 usr/share/graphics/logo_installer.png -> logo_marietto.png lrwxrwxrwx 1 root root20 Feb 15 2021 usr/share/graphics/logo_installer_dark.png -> logo_marietto_dark.png > > If so, then you have to write its desired path into stdin of cpio > > > > echo usr/share/graphics/logo_debian_dark.png | cpio -H newc -o -A -F \ > > > > /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/d-i/gtk/initrd > > > > Since cpio seems to offer no opportunities for grafting files to arbitrary > > paths, you have to cd to some playground directory, create the directories > > of the path usr/share/graphics/, and put your .png into the "graphics" > > directory. Then run above echo|cpio pipe. > > Thanks very much. It worked : https://ibb.co/GHHDQ3H ; I'm at a good point > by creating this derivative debian distro. Cheers, David.
Re: Cheap NAS
2022-10-16 21:58 GMT+05:00, Andrew M.A. Cater : >> > What about just putting some drives in a desktop, and installing some >> > free >> > nas software like >> > https://linuxhint.com/best-nas-software-linux >> >> OpenMediaVault work fine even on Orange Pi 3 LTS with usb drives. > > USB connected drives work fine - until they don't ... I learned that the > hard way 15 years ago [LVM done that way and you'd lose a drive ...]. I know. Mitigate it by installing all to wooden board and don't use LVM on external drives. Orange Pi 3 LTS does not have another interfaces for really big non-network drives, only one usb3.0 (up to 100-110MB/s on my hdd drives, does not test on ssd) and two usb2.0 (up to 30MB/s) > Also, most of the USB connected solutions rapidly become very, very slow > with > throughput - USB is not the best I/O solution for drives. [Very expensive > USB3 drives perhaps - Corsair flash voyager GTX] Yes, but for home use one hdd in usb3.0 is enough. I have no cables to my notebooks, only single wifi point, so 1Gbit of storage connection and 100MB/s of primary hdd does not main speed limiting factor. It was very budget solution and will work until replaced to more reliable but more expensive one. Or not replaced -- it's work and data somtimes duplicates to another place. All is ok, but you miss some info: "even on Orange Pi". Even. It's worst case for OpenMediaVault. On normal PC with intel/amd processor it work better. I does not recommend to do office storage on this board (in office server must be softraid on mdadm or hardware raid and normal backup with checks for restoration), but for home it work and most time work fine (but create backup of microsd). -- Stanislav
Re: Cheap NAS
On Sun, Oct 16, 2022 at 07:21:05PM +0500, Stanislav Vlasov wrote: > 2022-10-16 19:11 GMT+05:00, Wayne Sallee : > > What about just putting some drives in a desktop, and installing some free > > nas software like > > https://linuxhint.com/best-nas-software-linux > > OpenMediaVault work fine even on Orange Pi 3 LTS with usb drives. > > -- > Stanislav > USB connected drives work fine - until they don't ... I learned that the hard way 15 years ago [LVM done that way and you'd lose a drive ...]. Also, most of the USB connected solutions rapidly become very, very slow with throughput - USB is not the best I/O solution for drives. [Very expensive USB3 drives perhaps - Corsair flash voyager GTX] All the very best, as ever, Andy Cater
Re: Strange syslog behaviour [Solved]
On Sun, 2022-10-16 at 09:09 -0400, Wayne Sallee wrote: > It would be nice if updates presented "old file", "new file", "combined > file"; choice: (1), (2), (3). It does offer several choices, one of them is to show a 'diff' of the old and new files. Only you can know what changes you made and want to keep, and just automatically merging files is very likely just to produce a broken config. Personally, I do a diff first, which usually acts of a reminder of what I've changed, then I accept the new file and in another terminal edit that to reapply my changes. -- Tixy
Re: debian-user-digest Digest V2022 #816
no On Sun, 16 Oct 2022, 11:35 pm , wrote: > Content-Type: text/plain > > debian-user-digest Digest Volume 2022 : > Issue 816 > > Today's Topics: > Re: Some of the parameters used in m [ Mario Marietto >Re: Strange syslog behaviour [Solved [ David Wright < > deb...@lionunicorn.co ] > Re: Strange syslog behaviour [Solved [ David Wright < > deb...@lionunicorn.co ] > Re: Some of the parameters used in m [ "Thomas Schmitt" < > scdbac...@gmx.net ] > Re: Strange syslog behaviour [Solved [ Wayne Sallee >Re: MUD [ Wayne Sallee >Re: Cheap NAS [ Wayne Sallee >Re: Cheap NAS [ Stanislav Vlasov >Re: Some of the parameters used in m [ Mario Marietto > Date: Sat, 15 Oct 2022 23:03:41 +0200 > From: Mario Marietto > To: Thomas Schmitt , debian-user@lists.debian.org > Subject: Re: Some of the parameters used in my genisoimage command don't > produce a bootable ISO image > Message-ID: < > ca+1fsiihzsepsv0xm6kpq4gpkatqknh_nobbccyybn4jdhu...@mail.gmail.com> > Content-Type: multipart/alternative; > boundary="ec4dc505eb1915eb" > > --ec4dc505eb1915eb > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Hello. > > I have understood that the graphic files I need to change are inside the > file called "initrd.gz" that's inside this folder : > > /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/d-i/gtk/ > > I should decompress it and I will have the file called "initrd",that's a > cpio file. The images that I should edit are inside this archive / folders > = > : > > initrd/usr/share/graphics > > and they are called : logo_debian.png and logo_debian_dark.png ; > > at this point this is what I did to add two new image files inside the > archive in the same position of the old ones : > > chmod +w -R > /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/d-i/gtk/ > echo logo_debian_dark.png | cpio -H newc -o -A -F initrd/usr/share/graphics > > but unfortunately this is not the proper command to issue : > > cpio: can't open initrd/usr/share/graphics: Is not a directory > > how to fix that ? > > > > Il giorno sab 15 ott 2022 alle ore 20:48 Mario Marietto < > marietto2...@gmail.com> ha scritto: > > > Hello to everyone. > > > > I'm trying to customize the debian 11 and I'm creating a derivative > distr= > o > > for debian 11. I've changed a lot of logos,images and pictures,but not > > everything. For example I'm not able to understand which file belongs to > > the image and the logo that you see in this picture : > > https://ibb.co/SvbvsyR ; thanks. > > > > Il giorno gio 13 ott 2022 alle ore 22:58 Mario Marietto < > > marietto2...@gmail.com> ha scritto: > > > >> =F0=9F=98=82 > >> > >> Il giorno gio 13 ott 2022 alle ore 22:35 Thomas Schmitt < > >> scdbac...@gmx.net> ha scritto: > >> > >>> Hi, > >>> > >>> Mario Marietto wrote: > >>> > anyway,using another append shouldn't be wrong because the debian > >>> developers > >>> > used,not me,in this way > >>> > >>> Oh. In this case we should not bet against their wisdom. > >>> > >>> If it is by mistake, then it is harmless and heavily tested during the > >>> last years. > >>> (Regrettably i have not many old Live ISOs and half of them are > >>> "standard", > >>> i.e. without GUI. I see the line with the unexplained "append" in > >>> debian-live-9.2.0-amd64-cinnamon.iso . > >>> Maybe one of the subscribed DDs has nostalgic memories from the time > >>> when > >>> the graphic installer was introduced ?) > >>> > >>> > >>> Have a nice day :) > >>> > >>> Thomas > >>> > >>> > >> > >> -- > >> Mario. > >> > > > > > > -- > > Mario. > > > > > --=20 > Mario. > > --ec4dc505eb1915eb > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Hello.I have understood > tha= > t the graphic files I need to change are inside the file called > initr= > d.gz thats inside this folder > :/home/z= > > iomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/d-i/gtk/ >I should decompress it and I will have the file called > in= > itrd,thats a cpio file. The images that I should edit are > inside= > this archive / folders > :initrd/usr/share/graphic= > sand they are called : logo_debian.png and > logo_d= > ebian_dark.png ;=C2=A0at this point this is what > = > I did to add two new image files inside the archive in the same position > of= > the old ones : style=3D"font-family:monospa= > ce"> style=3D"color:rgb(0,0,0);background-color:rgb(255,255,255)">chmo= > d +w -R > /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custo= > m-disk/d-i/gtk/ style= > =3D"color:rgb(0,0,0);background-color:rgb(255,255,255)">echo > logo_debian_da= > rk.png | cpio -H newc -o -A -F initrd/usr/share/graphics > style=3D"font-family:monospace"> an>but unfortunately this > = > is not the proper command to issue : style=3D"fo= > nt-family:monospace"> style=3D"font-family:monos= >
Re: Strange syslog behaviour [Solved]
On Sun, 16 Oct 2022 09:09:36 -0400 Wayne Sallee wrote: > > You rejected the new file, which is why it was instead written to > > /etc/logrotate.d/rsyslog.dpkg-dist (which you could have safely > > left or removed—it's harmless). > > Yes, I rejected the new file, causing the other file to be there. It > would be nice if updates told what needed to be updated in the old > file when updates are done. You can get that by accepting or rejecting the new file, then diffing the resulting file with the one dpkg writes. > > Effectively, your edit has merged the contents of both files, > > whatever changes you made earlier before the Buster upgrade, > > and the vital change that would have been made for you if > > you'd accepted the new version. > > But If I had accepted the new file, it would probably have discarded > the changes that I had made. It would have. But it preserves the old file, and you can then copy from the old file to the new as appropriate. Again, diff is your friend. I use Emacs' ediff mode to do this. > > It would be nice if updates presented "old file", "new file", > "combined file"; choice: (1), (2), (3). There is no way the updates could figure out what the appropriate combined file would be. It would have no idea what your changes to the old file do, or which changes are appropriate to the new situation. You have to make that decision. When I do an upgrade I run the upgrade in one terminal, and have Emacs running in another. As these differences pop up, I accept one of the options, then edit away as necessary. It takes a while to do an upgrade, but I usually get what I want and don't have to go back and make more edits. And I also make sure I have recent backups of /etc and a few other places so I can restore my original files if need be. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Thanks very much. It worked : https://ibb.co/GHHDQ3H ; I'm at a good point by creating this derivative debian distro. Il giorno dom 16 ott 2022 alle ore 10:50 Thomas Schmitt ha scritto: > Hi, > > Mario Marietto wrote: > > echo logo_debian_dark.png | cpio -H newc -o -A -F > initrd/usr/share/graphics > > cpio: can't open initrd/usr/share/graphics: Is not a directory > > cpio option -F expects the path to the archive as argument. I.e. the path > to the uncompressed initrd. > > > > The images that I should edit are inside this archive / folders : > > initrd/usr/share/graphics > > Are you sure about the first path component "initrd/" ? > I see the path without it: > > $ gunzip < /mnt/iso/d-i/gtk/initrd.gz | cpio -t | fgrep > logo_debian_dark.png > 264529 blocks > usr/share/graphics/logo_debian_dark.png > > So i expect that you want to create a new copy of that file inside the > initrd. If so, then you have to write its desired path into stdin of cpio > > echo usr/share/graphics/logo_debian_dark.png | cpio -H newc -o -A -F \ > > /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/d-i/gtk/initrd > > Since cpio seems to offer no opportunities for grafting files to arbitrary > paths, you have to cd to some playground directory, create the directories > of the path usr/share/graphics/, and put your .png into the "graphics" > directory. Then run above echo|cpio pipe. > > > Have a nice day :) > > Thomas > > -- Mario.
Ya hay decisión (era: [OT] Debian decide sobre su política de paquetes firmware «non-free»)
El 2022-08-28 a las 10:11 +0200, Camaleón escribió: > Hola, > > A través de Phoronix¹ leo que en Debian² se está llevando a cabo una > consulta sobre la política a seguir con los paquetes de firmware > non-free, que actualmente se tienen que instalar por separado y de > manera plenamente consciente, con el consiguiente perjuicio que causa > en las instalaciones, principalmente a los nuevos usuarios. (...) > ¹https://www.phoronix.com/news/Debian-Non-Free-Firmware-GR > ²https://www.debian.org/vote/2022/vote_003 Bueno, pues ya hay ganador para esta cuestión¹. En resumen: 1. Se cambia el Contrato Social (un párrafo pequeño) para adecuarlo a la nueva realidad, que es que el medio de instalación oficial de Debian podrá contener paquetes privativos. 2. Sólo habrá un medio de instalación oficial de Debian, con paquetes libres y no libres mezclados, pero en teoría el usuario podrá desactivar la instalación de paquetes propietarios antes de iniciar el proceso de instalación (queda por ver cómo de efectivo resultará la pretensión y cómo lo expondrá el instalador sencillo dirigido a usuarios noveles). 3. El instalador informará de los paquetes propietarios que se van a instalar (en tiempo rela) y una vez instalado el sistema, se podrá consultar posteriormente alguna especie de archivo de registro o similar con los paquetes que se hayan instalado desde «non-free». Si al menos la opción predeterminada hubiera sido que el instalador no instalara paquetes propietarios SALVO que el usuario lo seleccionara a conciencia, ESPECÍFICAMENTE, pues hubiera sido una transición un poco más entendible. Pero no, ahora de manera predeterminada si el kernel necesita algún binario propietario se instalará, salvo que el usuario diga EXPRESAMENTE que no. En fin... qué se le va a hacer. Ceder a estar alturas no me complace lo más mínimo. :-( ¹https://www.debian.org/vote/2022/vote_003#outcome Saludos, -- Camaleón
Re: Cheap NAS
2022-10-16 19:11 GMT+05:00, Wayne Sallee : > What about just putting some drives in a desktop, and installing some free > nas software like > https://linuxhint.com/best-nas-software-linux OpenMediaVault work fine even on Orange Pi 3 LTS with usb drives. -- Stanislav
Re: Cheap NAS
What about just putting some drives in a desktop, and installing some free nas software like https://linuxhint.com/best-nas-software-linux Wayne Sallee wa...@waynesallee.com http://www.WayneSallee.com
Re: MUD
Original Message *Subject: * Re: MUD *From: * Maude Summerside *To: * Debian-user *CC: * *Date: * 2022-10-13 11:13 AM I'm talking mostly about the server software needed. To make it more acceptable by a larger group of people, you could make it so that on the client side, a simple terminal window could be used. I have not used MUD for about 25 years, back in my Windows days. I used to use a MUD room for holding meetings. It made the meetings a bit more interesting. :-) Wayne Sallee wa...@waynesallee.com http://www.WayneSallee.com
Re: Strange syslog behaviour [Solved]
Original Message *Subject: * Re: Strange syslog behaviour [Solved] *From: * David Wright *To: * Debian-user *CC: * *Date: * 2022-10-16 01:27 AM On Sat 15 Oct 2022 at 13:59:18 (-0400), Wayne Sallee obfuscated the following with HTML: Jeremy Ardley, did you update your code from " invoke-rc.d rsyslog rotate > /dev/null" to "/usr/lib/rsyslog/rsyslog-rotate"? I've added a new post to that part of the thread. I think your problem concerns changing to systemd, whereas his concerns mixing inetdutils-* packages with the more usual equivalent ones. So I got my servers straitened out, I think. I will know tomorrow. For anyone else running into this problem, the problem was caused from modifying /etc/logrotate.d/rsyslog then upgrading to Buster. The fix: diff /etc/logrotate.d/rsyslog.dpkg-dist /etc/logrotate.d/rsyslog edit /etc/logrotate.d/rsyslog Change from invoke-rc.d rsyslog rotate > /dev/null to /usr/lib/rsyslog/rsyslog-rotate Then delete /etc/logrotate.d/rsyslog.dpkg-dist I then rebooted my servers to get the syslog used. Then ls /var/log | grep syslog To see that it was working. I will know tomorrow if it is still working. I think the point you've missed is that at some stage, you upgraded from SystemV to systemd. Whenever that happened, the upgrade to rsyslog would have supplied a new /etc/logrotate.d/rsyslog file containing "/usr/lib/rsyslog/rsyslog-rotate", which knows how to handle both SystemV and systemd systems. My situation is now solved. It's working as it should. I think Debian 9 is systemd by default, so I don't think it was a change from systemv to systemd. But it was definitely a change in programs used that required the change to "rsyslog-rotate". You rejected the new file, which is why it was instead written to /etc/logrotate.d/rsyslog.dpkg-dist (which you could have safely left or removed—it's harmless). Yes, I rejected the new file, causing the other file to be there. It would be nice if updates told what needed to be updated in the old file when updates are done. Effectively, your edit has merged the contents of both files, whatever changes you made earlier before the Buster upgrade, and the vital change that would have been made for you if you'd accepted the new version. But If I had accepted the new file, it would probably have discarded the changes that I had made. It would be nice if updates presented "old file", "new file", "combined file"; choice: (1), (2), (3). Wayne Sallee wa...@waynesallee.com http://www.WayneSallee.com Cheers, David.
vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
Hallo Acht jaar geleden installeerde ik deze raid1: lsblk --fs NAME FSTYPELABEL MOUNTPOINT sdb ├─sdb1 linux_raid_member harde-schijf:0 │ └─md0ext4/boot ├─sdb2 linux_raid_member harde-schijf:2 │ └─md2 │ └─md2_crypt (dm-1) swap[SWAP] └─sdb3 linux_raid_member harde-schijf:1 └─md1crypto_LUKS └─md1_crypt (dm-0) ext4/ sda ├─sda1 linux_raid_member harde-schijf:0 │ └─md0ext4/boot ├─sda2 linux_raid_member harde-schijf:2 │ └─md2 │ └─md2_crypt (dm-1) swap[SWAP] └─sda3 linux_raid_member harde-schijf:1 └─md1crypto_LUKS └─md1_crypt (dm-0) ext4/ En nu moet ik die herbouwen, met twee nieuwe en grotere schijven. Ik weet niet (meer) in welke stap ik de / /boot en swap partities definieer. Maak ik 1 raid partitie op beide schijven, en verdeel ik daarna met lvm+encryptie de schijf in 3 partities? Of moet ik elke harde schijf in 3 verdelen, en van elke 2 gelijke partities dan één raid1 partitie maken?
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Hi, Mario Marietto wrote: > echo logo_debian_dark.png | cpio -H newc -o -A -F initrd/usr/share/graphics > cpio: can't open initrd/usr/share/graphics: Is not a directory cpio option -F expects the path to the archive as argument. I.e. the path to the uncompressed initrd. > The images that I should edit are inside this archive / folders : > initrd/usr/share/graphics Are you sure about the first path component "initrd/" ? I see the path without it: $ gunzip < /mnt/iso/d-i/gtk/initrd.gz | cpio -t | fgrep logo_debian_dark.png 264529 blocks usr/share/graphics/logo_debian_dark.png So i expect that you want to create a new copy of that file inside the initrd. If so, then you have to write its desired path into stdin of cpio echo usr/share/graphics/logo_debian_dark.png | cpio -H newc -o -A -F \ /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/d-i/gtk/initrd Since cpio seems to offer no opportunities for grafting files to arbitrary paths, you have to cd to some playground directory, create the directories of the path usr/share/graphics/, and put your .png into the "graphics" directory. Then run above echo|cpio pipe. Have a nice day :) Thomas
