On Wed, Jul 15, 2020 at 4:06 AM Neil Bothwick wrote:
>
> As Andreas mentioned, the LICENSE setting is probably a more reliable way
> of excluding such packages. By only allowing open source licences you
> prevent the installation of proprietary binary packages. You can still
> install the *-bin
On Fri, Jul 10, 2020 at 7:37 PM Jack wrote:
>
> On 2020.07.10 19:08, Walter Dnes wrote:
> > I've done the preliminary setup on my laptop install, and copied the
> > package names I wanted into the world file. With dependancies thrown
> > in, the laptop is now compiling 268 ebuilds of various
On Thu, Jul 9, 2020 at 9:35 AM John Blinka wrote:
>
> app-text/pdftk
>
> pdftk page-1.pdf page-2.pdf cat output both.pdf
>
> Lots of other useful tricks it can do with pdf files.
>
+1 for pdftk if you can stand java. I'm sure there are some GUI-based
options that you might prefer, but pdftk is
On Mon, Jul 6, 2020 at 5:05 AM William Kenworthy wrote:
>
> It also makes the point that any adminstrator will have access to the sticks
> data - not just the user (same as root under Linux).
This is just a fundamental issue about how computers work. If you
attach your storage media to a
On Thu, Jun 25, 2020 at 2:55 AM Robin Atwood wrote:
>
> On Wed, 24 Jun 2020 13:31:30 -0400
> tedheadster wrote:
>
> > Robin,
> > are you comfortable just going with a bare-bones console and build a
> > new kernel where you _disable_ CONFIG_FB? That might do it.
> >
> > Alternately, you can hook
On Fri, Jun 26, 2020 at 10:18 PM james wrote:
>
> On 6/26/20 4:40 PM, Rich Freeman wrote:
> > Removing the group doesn't actually make things more secure, because
> > processes can use a gid even if it doesn't exist in /etc/groups.
> > Effectively any POSIX system has ever
On Fri, Jun 26, 2020 at 4:03 PM james wrote:
>
> So can some of the smarter (gentoo) folks illuminate how to totally
> avoid groups and users, except for the minimum required, application
> specific? For example like serial line tools, or outline a set of
> tweaks/setting to avoid these
On Tue, Jun 23, 2020 at 3:37 PM Dale wrote:
>
> I'm sure there is many false positives out there but ignoring the real
> positives isn't a good solution either. By all means, if one wants to just
> wing it and hope for the best, disable SMART and take the risk. At some
> point, a drive will
On Tue, Jun 23, 2020 at 12:14 PM Sid Spry wrote:
>
> So if I'm understanding properly most drive firmware won't let you
> operate the device in an append-only mode?
So, there are several types of SMR drives.
There are host-managed, drive-managed, and then hybrid devices that
default to
On Fri, Jun 19, 2020 at 5:19 PM Hervé Guillemet wrote:
>
> Or do you have any suggestion for alternatives to this gentoo chroot ?
> (I'd prefer avoid installing some CentOS or Ubuntu as virtual guests).
You're of course free to do it any way you wish, but if I wanted to
create packages for
On Sat, Jun 20, 2020 at 10:04 PM William Kenworthy wrote:
>
> I cant see any
> advantage to having multiple ebuilds for a package instead of using a
> support framework to deal with it other than exposing multiple
> opportunities for things to go wrong and make it harder to fix. This not
> an
On Sun, Jun 21, 2020 at 5:53 AM Dr Rainer Woitok
wrote:
>
> is there any difference between running "emerge --jobs=1 ..." and runn-
> ing "MAKEOPTS=-j1 emerge ..."?
>
Yes.
--jobs=1 tells emerge to build one package at a time.
-j1 tells make to compile one file at a time when building a
On Sat, Jun 20, 2020 at 7:06 PM Daniel Frey wrote:
>
> You just pointed out the ambiguity.
>
> Emerging a package solely by its name worked 99.9% of the time before
> this change.
>
> Now new users get the fun of "Gee, which one is the one I actually
> want?" MythTV is a fairly clear one to
On Wed, Jun 17, 2020 at 1:34 AM Andreas Fink wrote:
>
> The bug report for passwdqc is here:
> https://bugs.gentoo.org/728528
>
Since this thread seems to still be a thing, I'll point out that this
bug was fixed not too long after this thread started. At this point
there is probably little
On Thu, Jun 18, 2020 at 3:35 PM james wrote:
>
> I use a 3.18.40 kernel, currently, on one of my AMD systems. It has
> thousands of source build packages, not only from portage but many others.
Keep in mind that you're running a non-longterm kernel, which means
that if there is a known
On Wed, Jun 17, 2020 at 8:32 AM Wols Lists wrote:
>
> On 17/06/20 05:47, Dale wrote:
> > From what I've read, all the drive makers were selling SMR without
> > telling anyone at first. It wasn't just WD but Seagate as well.
>
> Yes, but Seagate didn't start selling SMR drives advertised as
>
On Tue, Jun 16, 2020 at 7:38 PM antlists wrote:
>
> On 16/06/2020 13:25, Rich Freeman wrote:
> > And of course the problem with these latest hidden SMR drives is that
> > they generally don't support TRIM,
>
> This, I believe, is a problem with the ATA spec. I don't u
On Tue, Jun 16, 2020 at 7:36 AM Michael wrote:
>
> Just to add my 2c's before you throw that SMR away, the use case for these
> drives is to act as disk archives, rather than regular backups. You write
> data you want to keep, once.
If your write pattern is more like a tape SMR should be ok in
On Mon, Jun 15, 2020 at 3:54 PM Mark Knecht wrote:
>
> The SMART test, long version, will do a very reasonable job catching
> problems. Run it 2 or 3 times if it makes you feel better.
>
> Chris's suggestion about Spinrite is another option but it is slow, slow,
> slow. Might take you weeks? On
On Fri, Jun 12, 2020 at 10:48 AM n952162 wrote:
>
> On 2020-06-12 16:42, J. Roeleveld wrote:
> > On 12 June 2020 16:38:28 CEST, Michael wrote:
> >>
> >> Perhaps I misunderstand this, but isn't it as simple as booting off a
> >> LiveCD/
> >> USB, chrooting, changing profiles, cleaning up world
On Fri, Jun 12, 2020 at 10:38 AM Michael wrote:
>
> On Friday, 12 June 2020 15:00:25 BST Jack wrote:
> > On 6/12/20 9:49 AM, Rich Freeman wrote:
> > >
> > > Ultimately if there was enough interest in something like this the
> > > solution would probably
On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
>
> On 2020-06-12 08:40, n952162 wrote:
> >
> >>
> >> BTW, is it becoming clear why it is best to update Gentoo at least
> >> ever few months? :)
> >
> >
> > Well, yes, but it's really pretty onerous. If you have gentoo in
> > embedded systems,
On Fri, Jun 12, 2020 at 2:40 AM n952162 wrote:
>
> Presumably, 13.0, unless some process had already made the 13.0 -> 17.0
> jump without my knowledge.
Ok, you're in fairly uncharted waters. The impact is mainly to gcc so
if you haven't updated that then most likely nothing is broken yet,
and
On Thu, Jun 11, 2020 at 5:45 PM n952162 wrote:
>
>
> * portage-2.3.89-bug-718578.patch BLAKE2B SHA512 size ;-)
> ... [ ok ]
> * Please follow the instructions in the news item:
> * 2019-06-05-amd64-17-1-profiles-are-now-stable
> * or choose the 17.0 profile.
> * ERROR:
On Thu, Jun 11, 2020 at 4:43 PM n952162 wrote:
>
> On 2020-06-11 22:35, Rich Freeman wrote:
> > On Thu, Jun 11, 2020 at 4:28 PM n952162 wrote:
> >> On 2020-06-11 22:01, Rich Freeman wrote:
> >>> Try:
> >>> USE="python_targets_python3_6 -python_
On Thu, Jun 11, 2020 at 4:10 PM n952162 wrote:
>
> On 2020-06-11 22:01, Rich Freeman wrote:
> >>
> >> The current version of portage supports EAPI '6'. You must upgrade to a
> >> newer version of portage before EAPI masked packages can be installed.
> >&
On Thu, Jun 11, 2020 at 4:28 PM n952162 wrote:
>
> On 2020-06-11 22:01, Rich Freeman wrote:
> > Try:
> > USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
> > emerge -p1v =sys-apps/portage-2.3.99-r2
> >
>
> Sorry, try again.
>
On Thu, Jun 11, 2020 at 3:36 PM n952162 wrote:
>
> On 2020-06-11 14:47, Rich Freeman wrote:
> > On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick wrote:
> >
> > Most likely what you're probably going to end up wanting to try is:
> > USE="python_targets_python3_
On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick wrote:
>
> >
> > sudo emerge -vauU portage 2>&1 | tee -a portage.200611
> >
> > !!! The following update has been skipped due to unsatisfied
> > dependencies:
> >
> > sys-apps/portage:0
> >
> >selected:
On Tue, Jun 9, 2020 at 5:17 AM wrote:
>
> What is the difference between 100% CPU load and 100% CPU load to
> create such an difference in temperature?
> How is X% load calculated?
>
I think a lot more detail around what you're actually running would be
needed to provide more insight here. I
On Mon, Jun 8, 2020 at 11:06 AM Peter Humphrey wrote:
>
> Afternoon all,
>
> Is there something special for me to set in the kernel config to enable it to
> find the root partition? I copied the config from 5.4.38, ran oldconfig and
> followed most of the suggested answers; but it won't boot.
>
>
On Sun, Jun 7, 2020 at 5:07 PM Dale wrote:
>
>
> Unless you have a really good reason to do so, you shouldn't try to update
> system by itself. It limits emerge and can lead to issues.
He's just following my earlier advice. While what you say is true in
general, the problem is that he is
On Sun, Jun 7, 2020 at 3:38 PM n952162 wrote:
>
> I don't understand this - what can I add to @system to get @system to update?
>
> Ah, you mean that since readline is used by ~@system packages ... I'll try
> @world ... oh, that's not inclusive of @system, perhaps.
@world includes @system. It
On Sun, Jun 7, 2020 at 2:46 PM n952162 wrote:
>
>
> Regarding ~amd64 vs. amd64 - these are both just keywords, reflecting
> only a qualitative difference, not a special syntax understood by
> ebuild/emerge?
>
Honestly, I'm not actually sure whether portage has any logic that
gives these
On Sun, Jun 7, 2020 at 2:56 PM n952162 wrote:
>
>
> $ equery list \* | grep readline
> sys-libs/readline-7.0_p5-r1
>
> But, given your answer about exclusivity/inclusivity in the other thread, I
> guess this result is questionable...
This is just showing what version you have
On Sun, Jun 7, 2020 at 2:16 PM n952162 wrote:
>
> When I try to update @system after --sync-ing, I get a conflict on readline.
>
> Bash wants readline 8.0 but the profile specifies readline 7.0 and lots of
> other packages are linked against 7.0. Just rebuilding those packages
> probably won't
On Sun, Jun 7, 2020 at 1:31 PM n952162 wrote:
>
> When I do an emerge --sync, various ebuilds are loaded onto my system,
> co-existing with other ebuilds, possibly from the same package. What
> determines which package version is to be used?
>
> I assumed this was specified by the profile (e.g.
On Sun, Jun 7, 2020 at 4:08 AM Dale wrote:
>
> I still don't think I'm ready to try and do this on a hard drive. I'm
> certainly not going to do this with /home yet.
If you have a spare drive or just a USB stick lying around, set it up
on that. Then you can test that it mounts on boot and
On Sat, Jun 6, 2020 at 8:47 PM Victor Ivanov wrote:
>
> On 06/06/2020 21:12, Rich Freeman wrote:
> > Maybe we're miscommunicating, but it seems like you're moving the
> > goalposts here.
> > ...
> > Your original point was, "The problem here is that a
On Sat, Jun 6, 2020 at 3:38 PM Victor Ivanov wrote:
>
> On 06/06/2020 19:51, Rich Freeman wrote:
> > Sure, if the attacker has a copy of the header they can spend as much
> > time as they wish brute-forcing it. However, the same is true if they
> > have the entire dis
On Sat, Jun 6, 2020 at 10:07 AM Victor Ivanov wrote:
>
> The problem here is that a leaked header immediately means a compromised
> volume. An adversary who gets hold of the header can now spend as much
> time as they would like to brute force a password (depending on password
> strength) and
On Sat, Jun 6, 2020 at 9:57 AM antlists wrote:
>
> Oh - the other thing - if it's PMR and you're copying files onto it,
> expect a puke! That thing on WD Reds going PMR, I copied most of that on
> to the linux raid mailing list and the general feeling I get is "PMR is
> bad".
>
You're mixing up
On Sat, Jun 6, 2020 at 3:49 AM Dale wrote:
>
> Thanks for both replies. I found one other Gentoo one but it was encrypting
> the whole thing, /boot and all, plus they used efi. I didn't find the one
> you linked too.
The Gentoo guide that was linked uses an example of encrypting a partition.
On Fri, May 22, 2020 at 5:40 PM antlists wrote:
>
> On 22/05/2020 19:23, Rich Freeman wrote:
> > A big problem with drive-managed SMR is that it basically has to
> > assume the OS is dumb, which means most writes are in-place with no
> > trims, assuming the drive even su
On Fri, May 22, 2020 at 2:08 PM antlists wrote:
>
> So what you could do is allocate one zone of CMR to every four or five
> zones of SMR and just reshingle each SMR as the CMR filled up. The
> important point is that zones can switch from CMR cache to SMR filling
> up, to full SMR zones decaying
On Fri, May 22, 2020 at 12:47 PM antlists wrote:
>
> What puzzles me (or rather, it doesn't, it's just cost cutting), is why
> you need a *dedicated* cache zone anyway.
>
> Stick a left-shift register between the LBA track and the hard drive,
> and by switching this on you write to tracks
On Fri, May 22, 2020 at 12:15 PM Dale wrote:
>
> The thing about the one I have now in use by LVM for /home, one is SMR and
> one is PMR. Even if the OS is aware, does it even know which drive the data
> is going to end up being stored on? I'm pretty sure since the PMR drive was
> in use
On Fri, May 22, 2020 at 11:32 AM Michael wrote:
>
> An interesting article mentioning WD Red NAS drives which may actually be SMRs
> and how latency increases when cached writes need to be transferred into SMR
> blocks.
Yeah, there is a lot of background on this stuff.
You should view a
On Thu, May 21, 2020 at 3:18 PM n952162 wrote:
>
> My system:
>
> Linux txm2 4.14.65-gentoo #1 SMP Sun Oct 21 11:50:40 -00 2018 x86_64 Intel(R)
> Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux
>
> I'm not sure why the x86 is coming into play here and if sse2 is relevant at
> all.
> I
On Thu, May 21, 2020 at 4:46 AM Thomas Mueller wrote:
>
> > from n952162:
>
> > > And really unless you REALLY care about your CFLAGS you get 99% of the
> > > benefit just sticking with the original stage3 and just rebuilding
> > > anything you change USE flags for. Over time it will all get
On Wed, May 20, 2020 at 5:52 PM n952162 wrote:
>
> The beauty of gentoo is that it's source. But that's just a fantasy if
> I use the stage3 tarball.
> I think.
The stage3 tarball is what you get if you build everything using the
default options.
If you change the options, then an emerge -e
First, stop top-posting, and fix your quoting. This is a mess to try
to reply to, and your update woes are bad enough to stare at...
On Wed, May 20, 2020 at 4:51 PM n952162 wrote:
>
>
> Well, you're talking about openssl here. I'm trying to go a step at a time
> and looking at the first
On Wed, May 20, 2020 at 3:49 PM n952162 wrote:
>
> On 05/20/20 21:24, Daniel Frey wrote:
> > On 5/20/20 12:06 PM, n952162 wrote:
> >> The command was:
> >>
> >> emerge -vu dev-qt/qtgui dev-qt/qtx11extras dev-qt/qtopengl
> >> dev-qt/qtprintsupport dev-qt/qtwidgets dev-qt/qtxml
> >>
On Wed, May 20, 2020 at 3:51 PM Matt Connell (Gmail)
wrote:
>
> On 2020-05-20 14:46, n952162 wrote:
> > You're saying, if I don't recognize it, I can remove
> > it from the list?
>
> The world file should contain only *selected* packages, meaning packages
> you explicitly, purposefully chose and
On Sat, May 16, 2020 at 1:04 PM Jack wrote:
>
> The basic idea is to upgrade as few packages at a time as possible - but
> you can't do just one because of these conflicts.
If you get stuck in a really bad dependency mess that is sometimes necessary.
However, I'd first suggest just trying to
On Fri, May 15, 2020 at 11:27 AM Wols Lists wrote:
>
> The crucial point here is that dm-integrity protects against something
> *outside* your stack trashing part of the disk. If something came along
> and wrote randomly to /dev/sda, then when my filesystem tried to
> retrieve a file,
On Fri, May 15, 2020 at 9:18 AM antlists wrote:
>
> On 15/05/2020 12:30, Rich Freeman wrote:
> > The actual problem that this module solves is no-doubt long solved
> > upstream, but here is the blog post on dracut modules (which is fairly
> > well-documented in t
On Fri, May 15, 2020 at 7:16 AM antlists wrote:
>
> On 15/05/2020 11:20, Neil Bothwick wrote:
> >
> > Or you can create a custom module, they are just shell scripts. I recall
> > reading a blog post by Rich on how to do this a few years ago.
> >
> My custom module calls a shell script, so it
On Thu, May 14, 2020 at 5:10 PM n952162 wrote:
>
> On 05/14/20 22:46, Rich Freeman wrote:
> > On Thu, May 14, 2020 at 4:13 PM n952162 wrote:
> >> Action: sync for repo: gentoo, returned code = 0
> >>
> >>* An update to portage is available. It is
On Thu, May 14, 2020 at 4:13 PM n952162 wrote:
>
> Action: sync for repo: gentoo, returned code = 0
>
> * An update to portage is available. It is _highly_ recommended
> * that you update portage now, before any other packages are updated.
>
> * To update portage, run 'emerge --oneshot
On Thu, May 14, 2020 at 4:13 PM n952162 wrote:
>
> $ lf /var/db/pkg
This is NOT your package repository and you should not ever touch
anything in there unless you REALLY know what you're doing. You may
end up having to reinstall everything on your system at the very least
to fix the resulting
On Thu, May 14, 2020 at 3:10 PM n952162 wrote:
>
> I tried to emerge net-im/telegram-desktop
> but it said:
>
> emerge: there are no ebuilds to satisfy "net-im/telegram-desktop".
>
Are you sure there is nothing wrong with your local repository? I
assume you're running an amd64 system/profile
On Tue, May 12, 2020 at 3:24 PM Daniel Frey wrote:
>
> On 5/12/20 10:54 AM, Joachim Gwoke wrote:
> > Been having trouble with mainly calibre 4.9.1-r2 and have since kept it
> > out of any emerges. Otherwise everything is alright with python 3.7 on
> > my side
> >
> >
>
> I believe mine was
On Tue, May 12, 2020 at 3:25 PM Alan Mackenzie wrote:
>
> Might openrc-0.34.11 have been dependent on Python 2.7, and that's why
> it was swept away?
openrc does not depend on python. In any case, python-2.7 isn't going
anywhere right away anyway.
--
Rich
On Tue, May 12, 2020 at 3:01 PM Joachim Gwoke wrote:
>
> Each time I did a system update and re-emerging calibre was required it
> always failed so I leave it out of any system update and will keep it that
> way.
>
Sounds like a possible bug. There are some build/install issues
reported in
On Tue, May 12, 2020 at 1:54 PM Joachim Gwoke wrote:
>
> Been having trouble with mainly calibre 4.9.1-r2 and have since kept it out
> of any emerges. Otherwise everything is alright with python 3.7 on my side
>
As long as you're not doing anything too crazy you should be ok just
setting
On Tue, May 12, 2020 at 2:47 PM Alan Mackenzie wrote:
>
> Portage has just unmerged my openrc-0.34.11. I didn't ask it to.
Did you change any config files/etc recently? You may have asked it
to without realizing it or intending to (computers are of course very
literal).
Full outputs on
On Tue, May 12, 2020 at 10:02 AM Daniel Frey wrote:
>
> On 5/12/20 6:52 AM, Victor Ivanov wrote:
> > Python has indeed been a bit of a mess recently for me as well, but I
> > haven't had any major issues. Presumably, this could be attributed to
> > the fact that since python migrations started I
On Mon, May 11, 2020 at 10:02 PM Raphael MD wrote:
>
> now suffering with python 3.6/3.8 dependency mess.
>
On anything but a simple system it seems very difficult to deal with
the python update without overriding the python flags on at least some
packages.
I recommend maintaining these in a
On Sun, May 10, 2020 at 2:11 PM Dale wrote:
>
> I did find a WD Red 8TB drive. It costs a good bit more. It's a good
> deal but still costs more. I'm going to keep looking. Eventually I'll
> either spend the money on the drive or find a really good deal. My home
> directory is at 69% so I
On Wed, May 6, 2020 at 10:14 PM Caveman Al Toraboran
wrote:
>
> are you referring to python's dependence on expat
> and glibc?
>
More like bash's dependence. Well, and in the case of glibc just
about everything. When those break you're basically stuck recovering
from a rescue disk.
On Wed, May 6, 2020 at 9:13 PM Caveman Al Toraboran
wrote:
>
> just to say that some portagy thing (layman) can't
> work now as emerge was rebuilding packages to
> remove python3_6):
>
> running "layman -S"...
> Traceback (most recent call last):
> File
On Sun, May 3, 2020 at 6:50 PM hitachi303
wrote:
>
> The only person I know who is running a really huge raid ( I guess 2000+
> drives) is comfortable with some spare drives. His raid did fail an can
> fail. Data will be lost. Everything important has to be stored at a
> secondary location. But
On Sun, May 3, 2020 at 6:52 PM Mark Knecht wrote:
>
> On Sun, May 3, 2020 at 1:16 PM Rich Freeman wrote:
> >
> > Up until a few weeks ago I would have advised the same, but WD was
> > just caught shipping unadvertised SMR in WD Red disks. This is going
> > to
On Sun, May 3, 2020 at 5:32 PM antlists wrote:
>
> On 03/05/2020 21:07, Rich Freeman wrote:
> > I don't think you should focus so much on whether read=write in your
> > RAID. I'd focus more on whether read and write both meet your
> > requirements.
>
> If yo
On Sun, May 3, 2020 at 2:29 PM Mark Knecht wrote:
>
> I've used the WD Reds and WD Golds (no not sold) and never had any problem.
>
Up until a few weeks ago I would have advised the same, but WD was
just caught shipping unadvertised SMR in WD Red disks. This is going
to at the very least impact
On Sun, May 3, 2020 at 1:44 AM Caveman Al Toraboran
wrote:
>
> * RAID 1: fails to satisfy points (1) and (3)...
> this leaves me with RAID 10
Two things:
1. RAID 10 doesn't satisfy point 1 (read and write performance are
identical). No RAID implementation I'm aware of does.
2. Some
On Mon, Apr 27, 2020 at 3:07 PM antlists wrote:
>
> On 27/04/2020 17:59, Rich Freeman wrote:
> > Really though a better solution than any of this is for the filesystem
> > to be more SSD-aware and just only perform writes on entire erase
> > regions at one time. If th
On Mon, Apr 27, 2020 at 12:20 PM wrote:
>
> The kernel is keep track of all, which already has been fstrimmed and
> avoids to retrimm the same data.
> This knowledge gets lost, when the PC is powercycled or rebooted.
>
I imagine this is filesystem-specific. When I checked the ext4 source
I
On Sun, Apr 26, 2020 at 9:43 PM wrote:
>
> To implement a dry run with a printf() is new to me... ;)
>
That is all they fstrim authors could do, since there is no dry-run
option for the actual ioctl, and fstrim itself has no idea how the
filesystem will implement it (short of re-implementing
On Sun, Apr 26, 2020 at 12:15 PM wrote:
>
> On 04/26 11:20, Rich Freeman wrote:
> > On Sun, Apr 26, 2020 at 10:52 AM wrote:
> > >
> > > Fstrim reports about 200 GiB of trimmed data.
> > >
> >
> > My suggestion would be to run fstrim twice
On Sun, Apr 26, 2020 at 10:52 AM wrote:
>
> Fstrim reports about 200 GiB of trimmed data.
>
> From the gut this looks quite a lot -- the whole
> partition is 256 GB in size.
>
> Smartclt report for the drive:
> Data Units Written: 700,841 [358 GB]
>
> Each week 200 GiB fstrimmed
On Fri, Apr 24, 2020 at 8:35 AM Caveman Al Toraboran
wrote:
>
> On Wednesday, April 22, 2020 8:32 PM, Michael Jones
> wrote:
>
> > > No-no. C++ is a nightmare. A few people want to use it.
> >
> > C++ is an extremely widespread language with millions of lines of code
> > written daily world
On Fri, Apr 24, 2020 at 6:31 AM Neil Bothwick wrote:
>
> On Fri, 24 Apr 2020 10:41:24 +0200, Michele Alzetta wrote:
>
> > ... I just hope the remote system isn't running systemd, if so, you
> > have to do some additional tweaking before screen or tmux work. I know
> > someone who was bitten hard
On Tue, Apr 21, 2020 at 9:49 PM Dale wrote:
>
> Then they created moderators with people to enforce some rules. It got
> better. Actually, a lot better.
That is actually really good to hear. The whole CoC/Proctors thing
has been a bit of a mess and incredibly contentious. It has also been
On Tue, Apr 21, 2020 at 8:09 PM Dale wrote:
> Yea, -dev gets lively when someone steps on the toes of another dev but isn't
> that true about anywhere? Gentoo is somewhat of a niche distro.
I've commented on this elsewhere, but I think these two are related.
With more mainstream binary distros
On Tue, Apr 21, 2020 at 3:01 PM Consus wrote:
>
> On Tue, Apr 21, 2020 at 07:47:44PM +0100, Peter Humphrey wrote:
> > On Tuesday, 21 April 2020 17:58:03 BST Consus wrote:
> >
> > > ... and even distribution kernel is not an official thing, but a desperate
> > > attempt of someone to fix things.
>
On Tue, Apr 21, 2020 at 2:33 PM Consus wrote:
>
> On Tue, Apr 21, 2020 at 02:10:54PM -0400, Rich Freeman wrote:
> > On Tue, Apr 21, 2020 at 12:58 PM Consus wrote:
> > >
> > > even distribution kernel is not an
> > > official thing, but a des
On Tue, Apr 21, 2020 at 12:58 PM Consus wrote:
>
> even distribution kernel is not an
> official thing, but a desperate attempt of someone to fix things.
>
Huh? gentoo-sources is in at least as good a shape as I've ever seen
it. I'd argue it is in better shape than at a lot of times in the
On Mon, Apr 20, 2020 at 9:13 AM Ashley Dixon wrote:
>
> Following the recent conversation started by Meino, I have decided to convert
> my
> package.* files to directory structures. For all but one, this has
> proven
> tedious, but relatively painless. My package.use file is another
On Thu, Apr 16, 2020 at 11:19 AM Neil Bothwick wrote:
>
> On Thu, 16 Apr 2020 17:15:45 +0200, tu...@posteo.de wrote:
>
> > a loop like this
> >
> > for fn in asd* ; do
> > do_something $fn
> > done
> >
> > fails, when a file is named like this:
> >
> > List of OSses allowing spaces in
On Wed, Apr 15, 2020 at 2:31 PM james wrote:
>
> On 4/15/20 11:40 AM, Rich Freeman wrote:
>
> > I personally use the latest longterm, but not until it has been out
> > for a few months. Mainly this is because I use zfs and don't want to
> > deal with what version
On Wed, Apr 15, 2020 at 11:27 AM james wrote:
>
> It works fabulously, but it is time to upgrade, as most codes dependent
> on old software, have been migrated.
>
> So should I skip to a version 5 kernel?
> If so which one? I usually run hundreds of testing packages so maybe
> make the new system
On Tue, Apr 14, 2020 at 10:26 AM Wols Lists wrote:
>
> On 14/04/20 13:51, Rich Freeman wrote:
> > I believe they have
> > to be PCIv3+ and typically have 4 lanes, which is a lot of bandwidth.
>
> My new mobo - the manual says if I put an nvme drive in - I think
On Mon, Apr 13, 2020 at 11:32 PM wrote:
>
> Since I have a NVMe drive on a M.2 socket I would
> be interested at what level/stage (?word? ...sorry...)
> the data go a different path as with the classical sata
> SSDs.
>
> Is this just "protocol" or there is something different?
NVMe involves both
On Mon, Apr 13, 2020 at 4:34 PM antlists wrote:
>
> aiui, the spec says you can send a command "trim 1GB starting at block
> X". Snag is, the linux block size of 4KB means that it gets split into
> loads of trim commands, which then clogs up all the buffers ...
>
Hmm, found the ATA spec at:
On Mon, Apr 13, 2020 at 11:41 AM David Haller wrote:
>
> First of all: "physical write blocks" in the physical flash are 128kB
> or something in that size range, not 4kB or even 512B
Yup, though I never claimed otherwise. I just made the generic
statement that the erase blocks are much larger
On Mon, Apr 13, 2020 at 9:18 AM wrote:
>
> One quesion -- not to express any doubt of what you wrote Rich, but onlu
> to check, whether I understand that detail or not:
>
> Fstrim "allows" the drive to trim ittself. The actual "trimming" is
> done by the drive ittself without any interaction from
On Mon, Apr 13, 2020 at 7:55 AM Michael wrote:
>
> I have noticed when prolonged fstrim takes place on an old SSD drive of mine
> it becomes unresponsive. As Rich said this is not because data is being
> physically deleted, only a flag is switched from 1 to 0 to indicate its
> availability for
On Mon, Apr 13, 2020 at 1:32 AM wrote:
>
> fstrim clears blocks, which currently are not in use and which
> contents is != 0.
>...
> BUT: Clearing blocks is an action, which includes writes to the cells of
> the SSD.
I see a whole bunch of discussion, but it seems like many here don't
actually
301 - 400 of 1596 matches
Mail list logo
