Re: [DNG] New Sakura document
On Mon, 5 Feb 2018 09:33:07 +0100 Didier Kryn wrote: > Le 05/02/2018 à 02:46, Steve Litt a écrit : > > I just finished a document on how to configure/use Sakura. > > > > http://troubleshooters.com/linux/sakura.htm > > > > SteveT > Hey Steve. > > Just read your nice little Sakura tutorial. > > In the last paragraph you write "/.config/sakura/secura.conf" . > I bet there's a typo here (-: Oh Oh. Here's what my Chromium browser says the last paragraph of the document says: === Sakura is much more featureful than discussed in this document, and its features are easy to use. Perform command sakura --help for more details, peruse the ~/.config/sakura/secura.conf file for even more, and for the utmost info on this program's behavior, look at its source code. === My intent was to precede the leading slash with a tilde. I must have done something that renders wrong on some browsers. I tested with my handy dandy XML checker and the doc is well formed XML, which *usually* means it will play right with most browsers, but... On what browser did you observe the lack of the tilde? > > What the difference between hitting T and hitting > ? Ctrl+Shift+t adds a tab on top. Hitting the tab key queries the files in the directory and asks you to select (this is a function of bash/dash, not the terminal emulator). > > Sakura rewriting its config file on exit is > definitely a bad feature. I'd rather have two files: One for config, the other for persistent state. I'd prefer the former not be overwritten, and the latter overwritten and headed by a comment not to edit it directly. SteeT Steve Litt January 2018 featured book: Troubleshooting: Why Bother? http://www.troubleshooters.com/twb ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] grsecunoff retpoline patch, toolchain update needed
I changed the subject because it's the (still) hot freshly known spectre-meltdown security issue [1] that regards the entire Devuan OS's (as any other OSes) reliability (but my side of the interest/desire lies mostly in getting the necessary mitigations into the grsecunoff kernel) On 180204-00:05+, Miroslav Rovis wrote: > On 180203-23:35+, Miroslav Rovis wrote: > ... > > But I don't have the toolchain to support retpoline. Namely, the first > > thing at the onset of: > > > > fakeroot make deb-pkg > > > ... > > arch/x86/Makefile:191: CONFIG_RETPOLINE=y, but not supported by the > > compiler. Toolchain update recommended. > > > > Anybody already had this kind of issue, and has a few quick tips to tell on > > how to update the toolchain (or other necessary details)? > > I found: > https://gitlab.com/jimdigriz/linux/commit/b8b9ce4b5aec8de9e23cabb0a26b78641f9ab1d6 > and it appears that it's fine to compile it disregarding that warning. > > (And I'll offer retpoline-patched 4.9.74 on > https://www.croatiafidelis.hr/gnu/deb/linux-deb-grsec-current/ by tomorrow, I > hope.) which I did, and in the link I gave there there's more talk, and also can be seen how linux-image-4.14.0-0.bpo.3-amd64 and my 4.9.74-unofficial+grsec180204-21 compare: https://user-images.githubusercontent.com/7559858/35819129-bb65a63c-0a99-11e8-804a-caa9f6cc1719.png https://user-images.githubusercontent.com/7559858/35819137-c3195090-0a99-11e8-81de-d560c4723857.png all of which is in comment: Spectre mitigation (retpoline) #26 https://github.com/minipli/linux-unofficial_grsec/issues/26#issuecomment-363157180 Meltdown support for grsecunoff is being developed and is at an unknown stage, In comment of Jan 9 2018: KPTI backport conflicts #25 https://github.com/minipli/linux-unofficial_grsec/issues/25#issuecomment-355921197 minipli wrote: > Expect it to be weeks/months/never. It's a pretty invasive change > conflicting with a lot of PaX. I'm betting minipli *will* make it... He's currently the best hope for what remained of grsec. ( There's been, and still is, an attempt to develop the entire hardened-kernel, without the GNU/Linux kernel continuing to be under the whims of who regards security bugs like any other bugs, along with, after spender and PaX Team left --unable to tollerate any more the ripoff of their code by Google--, [along with] security being basically under total control of the already mentioned, and just repeated the name of, unofficial world's top spy firm. [There's been, and still is, an attempt to develop the entire hardened-kernel,] separately, organizationally ab ovo, at: https://github.com/copperhead/linux-hardened if I understand correctly, but as here stated: https://github.com/minipli/linux-unofficial_grsec/issues/25#issuecomment-358370154 > not enough people actually were interested ) Questions for anybody that can tell more on the issues are, on my part, primarily: How come I couldn't get the amd64-microcode for my machines, as I presented in the screencast of specter-meltdown-checker.sh and in comments of today in issue #26 linked above? Another question is: I tried, but couldn't get amd64-microcode in Devuan, by apt-get, version 3.20171205.1, and so I got it from Debian (where it is the current offer): https://packages.debian.org/sid/amd64-microcode Did I misconf'd something or is it not available in Devuan. Also, it didn't work for my machines (explained in that minipli issue above), any idea why, or where to look for reasons? And more there will/would be to ask, and maybe to test (as I'm not really a dev, but can follow and test, mostly), time and strength permitting. Regards! --- [1] but existing and extremely likely known to exploit- writers and users months before it was discovered by the Austrian guys mid-2017 (and taken credit of over by the world's top commercial unofficial spy agency the Schmoog, just like they took credit for the Heartbleed, as if they discovered both those vuln issues, and instead they had only, in both cases, spied on people who were discovering it, to be able to apportion half of the credit to themselves: I could almost bet on this hypothesis anything you want... it's so terribly very likely the truth of it! -- Miroslav Rovis Zagreb, Croatia https://www.CroatiaFidelis.hr signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Backup revisited - the rsync time machine
On Mon, Feb 05, 2018 at 09:08:59AM -1000, Joel Roth wrote: > On Mon, Feb 05, 2018 at 09:15:33AM -0500, Hendrik Boom wrote: > > On Fri, Feb 02, 2018 at 05:32:36PM -1000, Joel Roth wrote: > > > Dear list, > > > > > > For years I'd used a couple of rsync scripts for backup, > > > usually just full snapshots. > > > > > > I knew there is an option using hardlinks that behaves like > > > the Mac Time Machine app, giving cheap incremental backups. > > > > > > https://blog.interlinked.org/tutorials/rsync_time_machine.html > > > > () > > > probably someone has done it better... > > > > > > > There's rdiff-backup, which uses an efficient algorithm to identify what > > has changed and transmit the diffs over the network. It also keeps a > > history of old backups on the backup drive, so you can restore as of a > > previous date. > > I used rdiff-backup years ago. ISTR it litters the directory tree > with index files. It has index files on the backup, right? They are for storing things like reverse diffs so it can reconstruct old backups. I've never noticed it litterring the actual working file system -- just the backups. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Backup revisited - the rsync time machine
On Mon, Feb 05, 2018 at 09:15:33AM -0500, Hendrik Boom wrote: > On Fri, Feb 02, 2018 at 05:32:36PM -1000, Joel Roth wrote: > > Dear list, > > > > For years I'd used a couple of rsync scripts for backup, > > usually just full snapshots. > > > > I knew there is an option using hardlinks that behaves like > > the Mac Time Machine app, giving cheap incremental backups. > > > > https://blog.interlinked.org/tutorials/rsync_time_machine.html > > () > > probably someone has done it better... > > > > There's rdiff-backup, which uses an efficient algorithm to identify what > has changed and transmit the diffs over the network. It also keeps a > history of old backups on the backup drive, so you can restore as of a > previous date. I used rdiff-backup years ago. ISTR it litters the directory tree with index files. cheers, > And the files themselves are readable on the backup drive, as ng as you > don't have them compressed or encrypted. > > -- hendrik > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Backup revisited - the rsync time machine
On Fri, Feb 02, 2018 at 05:32:36PM -1000, Joel Roth wrote: > Dear list, > > For years I'd used a couple of rsync scripts for backup, > usually just full snapshots. > > I knew there is an option using hardlinks that behaves like > the Mac Time Machine app, giving cheap incremental backups. > > https://blog.interlinked.org/tutorials/rsync_time_machine.html > > And now I fool around with it myself. > > Since I have map UUIDs to mount points in /etc/fstab, > I can put the full paths in the backup script > and simply run it without parameters to get a > date-and-time-stamped directory containing a full backup. > > Probably you all have something much better, but for the > sake of discussion, and will post my humble offering. > > The clever part of the code is using a symlink > .../backups/current/ to provide rsync with the --link-dest > argument, the tree of files available for hardlinking during > next backup pass. > > Also, the one-file-system argument to rsync lets me backup > the root directory without pulling in other mounts. > > The current script doesn't support copying over a network, > but can be easily achieved by consulting online resources > (left as an exercise to the reader.) > > Obviously, you will need to configure it. Note that the directories > excluded from backup are created in the last step. > > probably someone has done it better... > There's rdiff-backup, which uses an efficient algorithm to identify what has changed and transmit the diffs over the network. It also keeps a history of old backups on the backup drive, so you can restore as of a previous date. And the files themselves are readable on the backup drive, as ng as you don't have them compressed or encrypted. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Backup revisited - the rsync time machine
il devuanizzato Joel Roth il 03-02-18 04:32:36 ha scritto: > Dear list, > > For years I'd used a couple of rsync scripts for backup, > usually just full snapshots. > > I knew there is an option using hardlinks that behaves like > the Mac Time Machine app, giving cheap incremental backups. You may try rsnapshot. It is based on rsync and use hard links whenever possible. -- viverna ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] deb.devuan.org, netboot, ascii
On Mon, Feb 05, 2018 at 12:41:50PM +0100, m_maass wrote: > Dear friends, > > i just play with > > http://deb.devuan.org/devuan/dists/ascii/main/installer-amd64/current/images/netboot/netboot.tar.gz > > There is an error, the mirror "deb.devuan.org" do not work well for ascii. > > I had success with packages.devuan.org as mirror, and > > /merged/ as Devuan archive mirror directory > > > Thank you, Hi Mike, the ascii installer is under heavy development atm. It works if you use "/merged" instead than "/merged/" with deb.devuan.org, meaning that it should allow you to install the system without too many issues. But still, there are other problems, and we are working to solve them, so please do not use those installers until the field is clear (or use them at your own risk, and don't blame us if they break something ;)) My2Cents KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- 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
[DNG] deb.devuan.org, netboot, ascii
Dear friends, i just play with http://deb.devuan.org/devuan/dists/ascii/main/installer-amd64/current/images/netboot/netboot.tar.gz There is an error, the mirror "deb.devuan.org" do not work well for ascii. I had success with packages.devuan.org as mirror, and /merged/ as Devuan archive mirror directory Thank you, Mike ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Refracta issues
On 02/03/2018 02:59 AM, ghostlands wrote: > Is Fsmithred on this list? I'm having problems updating my kernel while > running a Refracta'd Devuan in either live mode or copy to Ram mode. > > gl > I'm on the list, but I haven't been keeping up with it. What's the problem? (which iso, which kernel, what error message?) fsr ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] New Sakura document
Le 05/02/2018 à 02:46, Steve Litt a écrit : Hi all, A few weeks ago, somebody on this list mentioned Sakura as an excellent terminal emulator not beholden to any desktop environment. They were right. I just finished a document on how to configure/use Sakura. http://troubleshooters.com/linux/sakura.htm SteveT Steve Litt January 2018 featured book: Troubleshooting: Why Bother? http://www.troubleshooters.com/twb Hey Steve. Just read your nice little Sakura tutorial. In the last paragraph you write "/.config/sakura/secura.conf" . I bet there's a typo here (-: What the difference between hitting T and hitting ? Sakura rewriting its config file on exit is definitely a bad feature. Even if it is easy to work-around. Didier Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
