Re: jigdo error

2020-02-16 Thread john doe
On 2/16/2020 5:37 PM, john doe wrote: > On 2/15/2020 10:37 PM, Steve McIntyre wrote: >> Hi John, >> >> kaufm...@nb.net wrote: >>> When my last Thinkpad died, I lost my Mint/Xfce. My new Thinkpad, of >>> course, comes with >>> Windows 10, and I want to move on to Debian. As a Debian newbie, I'm als

Re: help with gitlab on buster

2020-02-16 Thread john doe
On 2/16/2020 11:45 PM, Graham Seaman wrote: > > On 14/02/2020 17:39, john doe wrote: >> On 2/14/2020 5:42 PM, Graham Seaman wrote: >>> I run a debian house server for firewall, routing etc. The last few >>> years I've also run gitlab on it, which I use to manage text files I >>> work on from an ass

Re: need syntax for /etc/fstab to mount space on an ssd over /tmp

2020-02-16 Thread Andrei POPESCU
On Lu, 17 feb 20, 00:10:52, Gene Heskett wrote: > Greetings all; > > I am trying to remove as much write activity as possible from the u-sd > that a raspi boots from. To that end I'll create a partition on an ssd, > of 5000 megs, then copy the existing /tmp's contents to it it, then > mount th

need syntax for /etc/fstab to mount space on an ssd over /tmp

2020-02-16 Thread Gene Heskett
Greetings all; I am trying to remove as much write activity as possible from the u-sd that a raspi boots from. To that end I'll create a partition on an ssd, of 5000 megs, then copy the existing /tmp's contents to it it, then mount the ssd partition of that name on top of it where it is in the

Re: *nix

2020-02-16 Thread David Wright
On Sun 16 Feb 2020 at 13:03:05 (-0800), Charlie Gibbs wrote: > On Sun, 16 Feb 2020 21:10:01 +0100 Andrei POPESCU > wrote: > > On Du, 16 feb 20, 09:36:16, Charlie Gibbs wrote: > >> On Sun, 16 Feb 2020 14:20:01 +0100 Andrei POPESCU > >> wrote: > >> > >>> Just use whatever works for you. > >> > >>

Re: *nix

2020-02-16 Thread Doug McGarrett
On 2/16/20 4:30 PM, Charles Curley wrote: On Sun, 16 Feb 2020 13:03:05 -0800 Charlie Gibbs wrote: > With touchscreen technology becoming the standard even for laptops > and desktop monitors the demand for keyboard oriented interaction > decreases so the developers must create interfac

Re: help with gitlab on buster

2020-02-16 Thread Graham Seaman
On 14/02/2020 17:39, john doe wrote: On 2/14/2020 5:42 PM, Graham Seaman wrote: I run a debian house server for firewall, routing etc. The last few years I've also run gitlab on it, which I use to manage text files I work on from an assortment of laptops/PCs; I have a lot of these files (curre

Re: *nix

2020-02-16 Thread Felmon Davis
On Sun, 16 Feb 2020, Curt wrote: On 2020-02-15, John Kaufmann wrote: Just so. At what point does a small and natural generalization of "one thing" become more complex than a new thing? Simplicity is the friend, complexity the enemy; order the friend, entropy the enemy. It takes a lifetime of

Re: *nix

2020-02-16 Thread Charles Curley
On Sun, 16 Feb 2020 13:03:05 -0800 Charlie Gibbs wrote: > > With touchscreen technology becoming the standard even for laptops > > and desktop monitors the demand for keyboard oriented interaction > > decreases so the developers must create interfaces that are better > > suited for tap / swip

Re: *nix

2020-02-16 Thread Charlie Gibbs
On Sun, 16 Feb 2020 21:10:01 +0100 Andrei POPESCU wrote: > On Du, 16 feb 20, 09:36:16, Charlie Gibbs wrote: > >> On Sun, 16 Feb 2020 14:20:01 +0100 Andrei POPESCU >> wrote: >> >>> Just use whatever works for you. >> >> If you can. I really resent the increasing amount of coercion >> toward us

Re: jigdo error

2020-02-16 Thread Thomas Schmitt
Hi, john doe wrote: > http://cdimage.debian.org/debian-cd/current/amd64/jigdo-cd/debian-10.3.0-amd 64-netinst.jigdo > "OK: MD5 Checksums match, image is good! > WARNING: MD5 is not considered a secure hash! > WARNING: It is recommended to verify your image in other ways too!" > What are those othe

Re: *nix

2020-02-16 Thread Andrei POPESCU
On Du, 16 feb 20, 09:36:16, Charlie Gibbs wrote: > On Sun, 16 Feb 2020 14:20:01 +0100 Andrei POPESCU > wrote: > > > > Just use whatever works for you. > > If you can. I really resent the increasing amount of coercion > toward using GUIs (no keyboard equivalents for menus, etc.) that > I'm seeing

Re: LVM Boot fail

2020-02-16 Thread Tom Dial
On 2/16/20 05:36, Reco wrote: > Hi. > > On Sat, Feb 15, 2020 at 10:57:36PM -0700, Tom Dial wrote: >> Neither the host nor the guest VM is rebooted often, and it is not a >> particularly serious problem now that it's known, but it would be better >> gone. I'm not averse to doing work to so

Re: *nix

2020-02-16 Thread Charlie Gibbs
On Sun, 16 Feb 2020 14:20:01 +0100 Andrei POPESCU wrote: > On Du, 16 feb 20, 03:36:44, ghe wrote: > >> Complexity of the software is for us programmers to deal with. >> Making the programs useful for a user can be one of the problems >> in our writing and design. That, I think, is what they mea

Re: *nix

2020-02-16 Thread Charles Curley
On Sun, 16 Feb 2020 12:31:30 - (UTC) Curt wrote: > That members of the most generalist species on earth should extol the > merits of the most extreme form of specialisation is something of an > ironic puzzlement here in the balcony seats. "Specialization is for insects." -- Robert Heinlein

Re: jigdo error

2020-02-16 Thread john doe
On 2/15/2020 10:37 PM, Steve McIntyre wrote: > Hi John, > > kaufm...@nb.net wrote: >> When my last Thinkpad died, I lost my Mint/Xfce. My new Thinkpad, of course, >> comes with >> Windows 10, and I want to move on to Debian. As a Debian newbie, I'm also >> new to jigdo, >> but want to use it beca

Re: LVM Boot fail

2020-02-16 Thread Stefan Monnier
> Boot faults to an (initrd) prompt with a complaint that the /usr LV, > correctly identified by its UUID, does not exist. It does, but is not > activated. In fact, lvscan shows that only the root and swap LVs > are active, and the others are not. Why does the initrd want to check activation of so

Re: *nix

2020-02-16 Thread Stefan Monnier
> That members of the most generalist species on earth should extol the > merits of the most extreme form of specialisation is something of an > ironic puzzlement here in the balcony seats. If you want to stay on top, you have to impose on others different rules than those you impose on yourself.

Re: *nix

2020-02-16 Thread Andrei POPESCU
On Du, 16 feb 20, 03:36:44, ghe wrote: > > Complexity of the software is for us programmers to deal with. Making > the programs useful for a user can be one of the problems in our > writing and design. That, I think, is what they meant by "One program > doing the job well" -- users have a colle

Re: LVM Boot fail

2020-02-16 Thread Reco
Hi. On Sat, Feb 15, 2020 at 10:57:36PM -0700, Tom Dial wrote: > Neither the host nor the guest VM is rebooted often, and it is not a > particularly serious problem now that it's known, but it would be better > gone. I'm not averse to doing work to sort this out, but would be > grateful for

Re: *nix

2020-02-16 Thread Curt
On 2020-02-15, John Kaufmann wrote: > > Just so. At what point does a small and natural generalization of "one > thing" become more complex than a new thing? Simplicity is the friend, > complexity the enemy; order the friend, entropy the enemy. It takes a > lifetime of design to see where to draw

*nix

2020-02-16 Thread ghe
‐‐‐ Original Message ‐‐‐ On Sunday, February 16, 2020 1:52 AM, Andrei POPESCU wrote: > On Sb, 15 feb 20, 20:17:07, Charles Curley wrote: > > > On Sat, 15 Feb 2020 14:03:02 -0700 > > ghe g...@slsware.net wrote: > > > > > Until recently, the *nix communities have stuck pretty well to

Re: *nix

2020-02-16 Thread Eduardo M KALINOWSKI
On 16/02/2020 05:52, Andrei POPESCU wrote: > On Sb, 15 feb 20, 20:17:07, Charles Curley wrote: >> On Sat, 15 Feb 2020 14:03:02 -0700 >> ghe wrote: >> >>> Until recently, the *nix communities have stuck pretty well to these >>> recommendations -- they're just descriptions of competent programming,

Re: *nix

2020-02-16 Thread Andrei POPESCU
On Sb, 15 feb 20, 20:17:07, Charles Curley wrote: > On Sat, 15 Feb 2020 14:03:02 -0700 > ghe wrote: > > > Until recently, the *nix communities have stuck pretty well to these > > recommendations -- they're just descriptions of competent programming, > > after all. There may be some discussion ove