Re: [DNG] daedalus with chromiium
On Tue, 19 Apr 2022 00:41:53 +0200 Florian Zieboll via Dng wrote: > Dementia Sorry, I mean: just don't feed it! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] OT, once again: Samba and ClamAV
Dear greybeards, another (i hope interesting) off topic question I don't know where else to get answered constructively: Why doesn't ClamAV's 'clamonacc' react on samba cifs shares - and it needs a 'vfs_virusfilter' configuration in the smb.conf? I am (quite) sure, that I didn't have 'OnAccessExcludeRootUID' or such in my clamd.conf - and clamd did act on all other tested 'cat's and "dogs". NB: This thread is not meant to discuss why a cifs server might need a virus scanner ;-) libre Grüße, Florian ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
On Tue, 19 Apr 2022 07:48:59 +1000 Ralph Ronnquist wrote: > presuamably it now says daedalus with u rather than daedalas ? Dementia is a b1tch, as tr0lls are... onezero, f. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
presuamably it now says daedalus with u rather than daedalas ? Ralph. On Mon, Apr 18, 2022 at 04:22:54PM -0400, Haines Brown wrote: > I apologize for allowing Bob's message to get burried. > > On Sat, Apr 16, 2022 at 09:02:08PM -0600, Bob Proulx via Dng wrote: > > Haines Brown wrote: > > > I still get "Unable to locate package chromium". It seems that when I > > > did update/dist-upgrade after modifying sources.list to accommodate > > > daedulus I did not get the no InRelease file error. The chimaera > > > previously installed on this disk did not have chromium installed. > > > > What does this say for you? > > > > apt-cache policy chromium > > > > It should say something similar to this. > > > > root@clash:~# apt-cache policy chromium > > chromium: > > Installed: (none) > > Candidate: 100.0.4896.127-1 > > Version table: > > 100.0.4896.88-1 500 > > 500 http://deb.debian.org/debian daedalus/main amd64 Packages > > Yes it did > > I stumbled on the reason for my not getting a release file. The > line in my sources.list was > > deb http://deb.devuan.org/merged daedalas main non-free contrib > > I changed it to > > deb http://deb.devuan.org/merged daedalas main > > and the update/upgrade worked. I was then able restore the non-free > and contrib and install chromium. > > > > ___ > 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] daedalus with chromiium
I apologize for allowing Bob's message to get burried. On Sat, Apr 16, 2022 at 09:02:08PM -0600, Bob Proulx via Dng wrote: > Haines Brown wrote: > > I still get "Unable to locate package chromium". It seems that when I > > did update/dist-upgrade after modifying sources.list to accommodate > > daedulus I did not get the no InRelease file error. The chimaera > > previously installed on this disk did not have chromium installed. > > What does this say for you? > > apt-cache policy chromium > > It should say something similar to this. > > root@clash:~# apt-cache policy chromium > chromium: > Installed: (none) > Candidate: 100.0.4896.127-1 > Version table: > 100.0.4896.88-1 500 > 500 http://deb.debian.org/debian daedalus/main amd64 Packages Yes it did I stumbled on the reason for my not getting a release file. The line in my sources.list was deb http://deb.devuan.org/merged daedalas main non-free contrib I changed it to deb http://deb.devuan.org/merged daedalas main and the update/upgrade worked. I was then able restore the non-free and contrib and install chromium. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Chimaera installation issue (regulatory.db)
Hi, al3xu5 via Dng writes: > [[PGP Signed Part:Undecided]] > Hi > > This is to report an istallation issue with Chimaera (net install). > > The setup process halted at the beginning asking the "firmware"(???) > package for 'regulatory.db'. I've encountered this too, for Daedalus even. I had no problem installing via a wireless connection *without* this file. YMMV. > After some investigation I found it is related to a wireless-regdb package: > >> wireless regulatory database for Linux >> This package provides a machine-readable database of legal >> regulations on radio emissions that affect use of wireless networking. >> The Linux kernel and drivers use this to maintain compliance with >> those regulations. > > I (was in doubt and) provided (on a USB key) two packages: > > wireless-regdb_2020.04.29-2_all.deb > wireless-regdb-udeb_2020.04.29-2_all.udeb > > Then the setup process went ahead. > > Maybe this should be handled by the setup program. I agree. The installer should not prompt people to provide "firmware" files that are available from packages that are in main. I do seem to remember that the handling of the file changed a bit and that now the kernel loads it instead of whatever used happen before that. Hope this helps, -- Olaf MeeuwissenFSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
