Just in time to celebrate me fixing up three lighting dimmer packs for sale on ebay, the new thread...YAY...and a tuxonice sources version I seemed to have missed somehow, I have just uploaded the .configs for 2.6.32-tuxonice-r8 in both x86 and x86_64 flavors. Enjoy!

Cool...three threads. I never thought it would happen. Thank you to all those who use these threads.

I'm setting up a vanilla-sources-2.6.34 kernel and using your settings write-up and my current 2.6.33.4 kernel as my guides. Helps in seeing what's changed from .33.X to .34.

On page 8 of the guide in the following section:

Code:

[*] Legacy (BSD) PTY support
(64) Maximum number of legacy PTY in use
These settings are another group of silencers. Without these settings, starting a terminal session will result in the non-fatal error: "Out of pty devices." Set up in this fashion, you can open 64 terminal sessions without seeing the error. The number is adjustable. These settings have defaults as shown above.

This is dated information. Terminal sessions now use:

Code:

-*- Unix98 PTY support

The legacy BSD pty support is only for things like 3rd party serial cards and modems such as 16 serial port Digicom cards.

I originally raised this question in the gentoo forums last year. I subsequently did a bit more research on it. Current versions of xterm, konsole and friends all make use of POSIX standard Unix98 PTY support now.

Today, anyone getting an "Out of pty devices" error should probably check what version of xterm and friends they are running and/or what specialist serial port hardware they may have.

All my kernels now have Legacy (BSD) PTY support turned off.

Under "Unix98 PTY support", nearly everyone wants to leave "Support multiple instances of devpts" off. If I remember correctly, this is (optionally) for people running LNX containers (a type of virtual PC).

This is what ps shows for two instances of 'konsole', each with 4 terminal tabs open:

I will have to look at this a bit deeper, but you are most likely correct in this. I'm getting close to finishing things...only a few more pages left for the site. Once I get there, there are a lot of settings getting reset. For now, I'll add this to my list of notes to check for the next iteration of settings.

It's a source-fest yet again, and this time, even hardened sources are represented in the list of the new. I kid you not!

I have just uploaded .configs for 2.6.27.47, 2.6.32.14, 2.6.32-hardened-r7, 2.6.32-zen7-r1, 2.6.33.5, and 2.6.33-zen2-r1 in both x86 and x86_64 flavors. I also added this discussion thread to the main site page. Enjoy!

Cheers,
Pappy

PS, thanks to tomk for sticky-ing this message. I meant to say that earlier._________________This space left intentionally blank, except for these ASCII symbols.

No prob. It's not like it's something critical! Heck, I was happy to help actually. The kernel changes so fast that keeping up with what gets "dated" is darned difficult! In fact, this time around, it was the only thing I noticed from your settings descriptions which needs attention.

Of course, it helps I both encountered the problem before and that I've worked at places that still use Digicom serial controllers ..._________________People whom think M$ is mediocre, don't know the half of it.

I was thinking about your issue as I watched that kernel version come up. Frankly, I figured that hardened sources was gone, nevermore to be seen. And there it was, after months and months, another version of hardened sources. Will wonders ever cease?

well after forgetting to build in BTRFS this time, I panicked, thought "oh no, you mean this release can't mount it either?" (NOTE: I'm positive I included it for the original failures, as I was being more careful, and checked!)

facepalm

anyway, all sorted, rebuilt it, and as per usual it ZOOMS. Strangely it has half the memory of the guest functioning as my web server, seems a hell of a lot snappier (web and mail are both the same - headless kvm guests, 2.6.29, no btrfs). If it weren't for fear of BKL, I'd upgrade the other boxes to this build. Long time coming, but I'm very pleased with the work the hardened folks did on this.

I too was interested in using BTRFS for both VM filesystems, and also for backup storage. It would be fairly easy to try if for backup on my laptop -- just grab another laptop-sized SATA-2 drive of rather large size and run my existing backup scripts on it for a while. Of course, I would still have to run the old scripts, just in case BTRFS flops.

Let me know how it works for you, and after a couple of weeks, I will try it if you find not grief.

I am currently 500 miles from home on a consulting gig, or I might even try it on my network backup server, which is where I really need it._________________The MyWord KJV Bible tool is at http://www.elilabs.com/~myword

I'm still trying to get my head around an issue on this .32-hardened build. Far as I can tell it's leaking kernel memory? Having trouble telling. I just look up and am swapping like crazy, yet, looking at top I see virtually nothing consuming memory. Always surfaces during a significant `emerge`.

If I don't merge anything, however, it performs just dandy! Not sure what's going on - oh well.

I'm not ready to go to zen on my laptop, as it is my road warrior machine, and I need it to earn my living. I am currently still running Linux gehazi 2.6.31-gentoo-r6 #44 SMP PREEMPT Sun Feb 28 20:35:58 EST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz GenuineIntel GNU/Linux as per my Pappy's Seeds laptop tread from the earlier part of this year. It has been as solid as a rock, so I don't want to rock the boat.

I only want a dedup filesystem for backups, but if it works well at that, I am ready to try it as a vmware virtual disk store aslo, as it sure would save space with multiple vm's._________________The MyWord KJV Bible tool is at http://www.elilabs.com/~myword

I've got a weird thing happening. On an AMD quad-core, with a 5-bay SATA backplane, I am running the boot drive (a 1TB), a spare drive (also 1TB), and 3 new 2TB drives. Since the drives are new, I am running badblocks on them, as is my usual practice. One of the drives seems to be getting most of the attention, as the top display shows:

Note the 3 badblocks tasks at the top. the very topmost one is getting 8% of the CPU, and the other 2 are only getting 1% each. Other than this assymetrical cpu usage, the top drive is also way ahead of the other 2 drives in its progress with the surface test.

Why should this be? Is this maybe a crummy hardware implementation of SATA? A scheduling problem in the kernel, or what? There is plenty of free cpu time, after all, it is a quad core._________________The MyWord KJV Bible tool is at http://www.elilabs.com/~myword

Note the 3 badblocks tasks at the top. the very topmost one is getting 8% of the CPU, and the other 2 are only getting 1% each. Other than this assymetrical cpu usage, the top drive is also way ahead of the other 2 drives in its progress with the surface test.

It seems you started two of those jobs on the same drive (sdb), so they would compete for drive access. Did you maybe want to start one on sdd instead?

I was hoping that the badblocks would be finished by tomorow night, but now I'm not so sure it will make it. I need to put these drives in service before 1:30 AM EDT Wednesday morning, or I'll miss a day of backups. _________________The MyWord KJV Bible tool is at http://www.elilabs.com/~myword

Another day, lots more tuxonice source releases. I've just uploaded the .configs for 2.6.30-tuxonice-r11, 2.6.31-tuxonice-r11, 2.6.32-gentoo-r10, and 2.6.32-tuxonice-r9 in both x86 and x86_64 flavors. Enjoy!

Not really. The big claim to fame of tuxonice is that it's fully set up to handle hibernation. Along with tuxonice sources, you also get some scripts to make this happen as well. If the ability to hibernate is important, then by all means, use tuxonice sources. If it isn't, then stay where you are.

Other than the ability to hibernate, tuxonice sources are vanilla. For that reason, I can say that you really won't gain much if you switch sources unless hibernation isn't working for you under Gentoo sources.