Re: [gentoo-user] Re: Re: [Gentoo-User] emerge --sync likely to kill SSD?
On Sat, Jun 21, 2014 at 3:24 PM, Kai Krakow wrote: > And while we are at it, I'd also like to mention bcache. Tho, conversion is > not straight forward. However, I'm going to try that soon for my spinning > rust btrfs. I contemplated that, but I'd really like to see btrfs support something more native. Bcache is way too low-level for me and strikes me as inefficient as a result. Plus, since it sits UNDER btrfs you'd probably lose all the fancy volume management features. ZFS has ssd caching as part of the actual filesystem, and that seems MUCH cleaner. Rich
[gentoo-user] apache-2.2.27 disable SSLCipherSuite LOW 40 56 bit
Before upgrading to apache 2.2.27 I had this line in httpd.conf SSLProtocol -ALL +SSLv3 +TLSv1 +TLSv1.2 SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:!LOW:!SSLv2:!EXPORT and I was getting "A-" rating from: www.ssllabs.com Now after upgrading to apache-2.2.27 I'm getting "C" because of weak Cipher Strength inclusion: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x3) WEAK 40 TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x6) WEAK 40 TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x8) WEAK 40 TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x14) DH 512 bits (p: 64, g: 1, Ys: 64) FS WEAK 40 TLS_RSA_WITH_DES_CBC_SHA (0x9) WEAK 56 TLS_DHE_RSA_WITH_DES_CBC_SHA (0x15) DH 1024 bits (p: 128, g: 1, Ys: 128) FS WEAK 56 How to get rid of it? I've tired setting in 00_default_ssl_vhost.conf SSLProtocol all -SSLv2 -SSLv3 SSLCompression Off SSLCipherSuite "EECDH+AESGCM EDH+AESGCM EECDH -RC4 EDH -CAMELLIA -SEED !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS !RC4" or SSLProtocol -ALL +SSLv3 +TLSv1 +TLSv1.2 SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:!LOW:!SSLv2:!EXPORT nothing helps, I'm still getting "C" because of weak Cipher Strength inclusion. -- Joseph
[gentoo-user] Re: Re: [Gentoo-User] emerge --sync likely to kill SSD?
Peter Humphrey schrieb: > On Friday 20 June 2014 19:48:14 Kai Krakow wrote: >> microcai schrieb: >> > rsync is doing bunch of 4k ramdon IO when updateing portage tree, >> > that will kill SSDs with much higher Write Amplification Factror. >> > >> > I have a 2year old SSDs that have reported Write Amplification Factor >> > of 26. I think the only reason is that I put portage tree on this SSD >> > to speed it up. >> >> Use a file system that turns random writes into sequential writes, like >> the pretty newcomer f2fs. You could try using it for your rootfs but >> currently I suggest just creating a separate partition for it and either >> mount it as /usr/portage or symlink that dir into this directory (that >> way you could use it for other purposes, too, that generate random short >> writes, like log files). > > Well, there's a surprise! Thanks for mentioning f2fs. I've just converted > my Atom box's seven partitions to it, recompiled the kernel to include it, > changed the fstab entries and rebooted. It just worked. It's said to be twice as fast with some workloads (especially write workloads). Can you confirm that? I didn't try it that much yet - usually I use it for pendrives only. I have no experience using it for rootfs. And while we are at it, I'd also like to mention bcache. Tho, conversion is not straight forward. However, I'm going to try that soon for my spinning rust btrfs. -- Replies to list only preferred.
[gentoo-user] Re: Re: [Gentoo-User] emerge --sync likely to kill SSD?
Rich Freeman schrieb: > On Sat, Jun 21, 2014 at 10:27 AM, Peter Humphrey > wrote: >> >> I found that fstrim can't work on f2fs file systems. I don't know whether >> discard works yet. > > Fstrim is to be preferred over discard in general. However, I suspect > neither is needed for something like f2fs. Being log-based it doesn't > really overwrite data in place. I suspect that it waits until an > entire region of the disk is unused and then it TRIMs the whole > region. F2fs prefers to fill an entire erase block before touching the next. It also tries to coalese small writes into 16k blocks before submitting them to disk. And according to the docs it supports trim/discard internally. > However, I haven't actually used it and only know the little I've read > about it. That is the principle of a log-based filesystem. There's an article at LWN [1] and in the comments you can find a few important information about the technical details. Posted Oct 11, 2012 21:11 UTC (Thu) by arnd: | * Wear leveling usually works by having a pool of available erase blocks | in the drive. When you write to a new location, the drive takes on block | out of that pool and writes the data there. When the drive thinks you | are done writing to one block, it cleans up any partially written data | and puts a different block back into the pool. | * f2fs tries to group writes into larger operations of at least page size | (16KB or more) to be efficient, current FTLs are horribly bad at 4KB | page size writes. It also tries to fill erase blocks (multiples of 2MB) | in the order that the devices can handle. | * logfs actually works on block devices but hasn't been actively worked on | over the last few years. f2fs also promises better performance by using | only 6 erase blocks concurrently rather than 12 in the case of logfs. A | lot of the underlying principles are the same though. | * The "industry" is moving away from raw flash interfaces towards eMMC and | related technologies (UFS, SD, ...). We are not going back to raw flash | any time soon, which is unfortunate for a number of reasons but also has | a few significant advantages. Having the FTL take care of bad block | management and wear leveling is one such advantage, at least if they get | it right. According to wikipedia [2], some more interesting features are on the way, like compression and data deduplication to lower the impact of writes. [1]: http://lwn.net/Articles/518988/ [2]: http://en.wikipedia.org/wiki/F2FS -- Replies to list only preferred.
Re: [gentoo-user] Re: [Gentoo-User] emerge --sync likely to kill SSD?
On Sat, Jun 21, 2014 at 10:27 AM, Peter Humphrey wrote: > > I found that fstrim can't work on f2fs file systems. I don't know whether > discard works yet. Fstrim is to be preferred over discard in general. However, I suspect neither is needed for something like f2fs. Being log-based it doesn't really overwrite data in place. I suspect that it waits until an entire region of the disk is unused and then it TRIMs the whole region. However, I haven't actually used it and only know the little I've read about it. That is the principle of a log-based filesystem. I'm running btrfs on my SSD root, which is supposed to be decent for flash, but the SMART attributes of my drive aren't well-documented so I couldn't tell you what the erase count is up to. Rich
Re: [gentoo-user] Re: [Gentoo-User] emerge --sync likely to kill SSD?
On Friday 20 June 2014 19:48:14 Kai Krakow wrote: > microcai schrieb: > > rsync is doing bunch of 4k ramdon IO when updateing portage tree, > > that will kill SSDs with much higher Write Amplification Factror. > > > > I have a 2year old SSDs that have reported Write Amplification Factor > > of 26. I think the only reason is that I put portage tree on this SSD > > to speed it up. > > Use a file system that turns random writes into sequential writes, like the > pretty newcomer f2fs. You could try using it for your rootfs but currently I > suggest just creating a separate partition for it and either mount it as > /usr/portage or symlink that dir into this directory (that way you could > use it for other purposes, too, that generate random short writes, like log > files). Well, there's a surprise! Thanks for mentioning f2fs. I've just converted my Atom box's seven partitions to it, recompiled the kernel to include it, changed the fstab entries and rebooted. It just worked. --->8 > I'd also suggest not to use the discard mount options and instead create a > cronjob that runs fstrim on the SSD devices. But YMMV. I found that fstrim can't work on f2fs file systems. I don't know whether discard works yet. Thanks again. -- Regards Peter
Re: [gentoo-user] Video & audio out of sync mkv mplayer
On 06/21/2014 04:16 PM, Alan McKinnon wrote: > On 21/06/2014 15:01, Alexander Kapshuk wrote: >> What could be amiss there? >> Thanks. >> > > dodgy source files? > > use the mplayer hotkeys that gets them back in sync > > > That sounds about right. Tried playing some other video files. They seemed to work all right. Thanks.
Re: [gentoo-user] Video & audio out of sync mkv mplayer
On 21/06/2014 15:01, Alexander Kapshuk wrote: > What could be amiss there? > Thanks. > dodgy source files? use the mplayer hotkeys that gets them back in sync -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Video & audio out of sync mkv mplayer
What could be amiss there? Thanks.
[gentoo-user] Re: Checking the reason for (-useflags) in brackets
"man emerge" would have been even faster ;-) meino.cra...@gmx.de wrote: > Alan McKinnon [14-06-21 12:36]: >> On 21/06/2014 11:19, meino.cra...@gmx.de wrote: >> > Hi, >> > >> > for some applications I want to activate some USE flags, which are >> > disabled by default. >> > >> > Some of those USE flags are set in () brackets. From searching the >> > internet I learned, that this may be due to unresolveable dependencies >> > or settings in the make.profile or >> > >> > Is there a way to exactly pin point the reason why a certain USE flags >> > gets "(diabled)" and whether it is possible to resolve the problem? >> > >> > How can I figure out that? >> >> >> From the emerge man page: >> >> >> () circumfix forced, masked, or removed >> >> >> So the answer is usually one of >> >> - flag not in ebuild anymore. Look in the ebuild >> - masked in profile. For these I usually search the profile directory >> recursively for the flag and figure it out that way >> >> >> What is it that you are trying to find out? A disabled flag is disabled >> and can't work, what further detail do you need? >> >> >> >> -- >> Alan McKinnon >> alan.mckin...@gmail.com >> >> > > Thanks for your help. In the internet I have already found the answer > in the meanwhile. > > > Best regards, > mcc
Re: [gentoo-user] Checking the reason for (-useflags) in brackets
Alan McKinnon [14-06-21 12:36]: > On 21/06/2014 11:19, meino.cra...@gmx.de wrote: > > Hi, > > > > for some applications I want to activate some USE flags, which are > > disabled by default. > > > > Some of those USE flags are set in () brackets. From searching the > > internet I learned, that this may be due to unresolveable dependencies > > or settings in the make.profile or > > > > Is there a way to exactly pin point the reason why a certain USE flags > > gets "(diabled)" and whether it is possible to resolve the problem? > > > > How can I figure out that? > > > From the emerge man page: > > > () circumfix forced, masked, or removed > > > So the answer is usually one of > > - flag not in ebuild anymore. Look in the ebuild > - masked in profile. For these I usually search the profile directory > recursively for the flag and figure it out that way > > > What is it that you are trying to find out? A disabled flag is disabled > and can't work, what further detail do you need? > > > > -- > Alan McKinnon > alan.mckin...@gmail.com > > Thanks for your help. In the internet I have already found the answer in the meanwhile. Best regards, mcc
Re: [gentoo-user] Checking the reason for (-useflags) in brackets
On 21/06/2014 11:19, meino.cra...@gmx.de wrote: > Hi, > > for some applications I want to activate some USE flags, which are > disabled by default. > > Some of those USE flags are set in () brackets. From searching the > internet I learned, that this may be due to unresolveable dependencies > or settings in the make.profile or > > Is there a way to exactly pin point the reason why a certain USE flags > gets "(diabled)" and whether it is possible to resolve the problem? > > How can I figure out that? >From the emerge man page: () circumfix forced, masked, or removed So the answer is usually one of - flag not in ebuild anymore. Look in the ebuild - masked in profile. For these I usually search the profile directory recursively for the flag and figure it out that way What is it that you are trying to find out? A disabled flag is disabled and can't work, what further detail do you need? -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Checking the reason for (-useflags) in brackets
Hi, for some applications I want to activate some USE flags, which are disabled by default. Some of those USE flags are set in () brackets. From searching the internet I learned, that this may be due to unresolveable dependencies or settings in the make.profile or Is there a way to exactly pin point the reason why a certain USE flags gets "(diabled)" and whether it is possible to resolve the problem? How can I figure out that? Thank you very much in advance for any help! Best regards, mcc
Re: [gentoo-user] problem with nvidia card -- could it be hardware?
Daniel Frey wrote: > On 06/20/2014 12:31 PM, Alexander Kapshuk wrote: > > On 06/20/2014 11:58 AM, cov...@ccs.covici.com wrote: > >> Hi. I am using the nvidia GeForce GT 430 for years and suddenly within > >> the last few days, if I start gdm, it gives me an error, no screens > >> found and dumpss core and if I let it go it will keep dumping core and > >> filling up my root partition. It works with my frame buffer, but no > >> longer with gdm or even startx. So is this some kind of strange > >> hardware glitch? I did downgrade the nvidia driver, but no joy. > >> > >> Thanks in advance for any suggestions. > >> > > You may want to take a look at this, > > http://forums.gentoo.org/viewtopic-t-858782-start-0.html, see if that helps. > > > > What is the version of your nvidia driver? > > > > Did the problem you're experiencing come about as a result of a recent > > nvidia driver, and/or xorg server update? > > > > As already suggested, having a look at your /var/log/Xorg.0.log may > > through some more light on what could be amiss. > > > > > > Also, if it started out of the blue, check your other hardware. When my > power supply started to go, X would randomly crap out with "No screens > found." > > I'd let it sit for a few minutes and restart X and it would be fine. OK, thanks to everyone who has responded. I am going to try another card and see if that fixes the problem as there are other things going on in my systemwhich may relate i.e. v86d is using a lot more cpu that it used to do, so we shall see. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
