[13:37] <saiarcot895> When building a program using the hardening-wrapper, does the executable get changed into a library object and therefore cannot be launched through Nautilus?
[14:18] <Raazeer> since I'm being ignored over in #ubuntu, allow me the liberty to ask here too: is there a way to get /dev/dsp et al back in 13.04? several packages still use it
[14:18] <Raazeer> I'd very much like to use some of those
[14:22] <penguin42> Raazeer: There aren't many left that still only use /dev/dsp - but you might try libpulsedsp which is a fudge that persuades them to use pulse audio
[14:24] <Raazeer> penguin42, maybe not /dev/dsp specific but the whole group of nodes, including /dev/mixer or /dev/audio/mixer, /dev/audio in general, etc...
[14:24] <Raazeer> aumix uses them for example
[14:26] <Raazeer> imo, if the backing nodes were taken out of the sytem, those packages that needed it should either have been blacklisted or gotten a dependency on something that puts the nodes in, but that's just omo of course
[14:27] <penguin42> Raazeer: Yeh that sounds fair - if they're still dependent on OSS then they need either fixing or removing; alsamixer is what I'd use instead of aumix these days
[14:28] <Raazeer> penguin42, the problem is, aumix is very useful in scripts due to it's comparably simple, parser-friendly output.
[14:28] <Raazeer> among others, the mute utility depends on it, meaning it's broken in current 13.04
[14:29] <Raazeer> I guess I'll just try installing every component of oss I can find and see if I can somehow get at least the mixer and dsp node back
[14:30] <Raazeer> in principle, I've got oss installed according to my package output. If I had to guess, I'd say something must have seriously dropped in the crapper here. gotta look into osspd, maybe that can be a solution
[14:33] <Raazeer> Ah lookie here: linux-sound-base apparently contains a modprobe config file that blacklists oss completely
[14:33] <Raazeer> let's take that out and see what happens
[14:42] <Raazeer> Ok, taking that blacklist out did not bring the device nodes back, so I have to flag both siggen and aumix-common as broken at this time, how do I go about that?
[14:45] <Raazeer> does anyone happen to know what part of OSS is supposed to create the device nodes?
[19:23] <chowder> hey I tried asking this question in the main support channel but I didn't really get a reply. I was wondering if someone here could be of some assistance
[19:23] <chowder> Looking to install Ubuntu 13.04 as a Dom0 with Xen but I want LVM taking care of the hard drives as well as encryption. I know there's documentation on Ubuntu+Xen but how and at what phase would I set up the encryption?
[19:24] <chowder> *correction. I'm aware that LVM doesn't do encryption. That came out wrong. What I'm saying is that I don't know whether to encrypt the drives before setting up LVM or after.
[19:25] <chowder> I figure that it would have to be after setting up LVM but I wanted to be sure. Also wanted to know how exactly I'd go about doing it.
[19:26] <penguin42> chowder: Normal way is luks encryption with lvm on top
[19:30] <chowder> penguin42: so luks before LVM?
[19:30] <chowder> how would booting work in that case?
[19:34] <chowder> I'm wondering if I would need a password to decrypt everything before the system finishes booting up and then use my normal login password
[19:34] <penguin42> chowder: The way I'm used to is having an unencrypted boot partititon, then one more DOS partition that contains the luks crypt, and that luks contains an LVM set
[19:35] <penguin42> chowder: Ubuntu sets up the initrd to ask for the password and open the luks and everything just works
[19:36] <penguin42> chowder: Recent installers will do it all for you if you ask to encrypt the whole disk (when I say recent I think 13.04 does it, not sure about 12.04.2)
[19:36] <chowder> I see. It just seemed so complex and intimidating to me
[19:37] <penguin42> it's fine until it breaks - it's a little hairier to find your filesystem again, but it's not too bad
[19:37] <chowder> Its a security measure because my apartment has crappy locks on the doors and the landlord is a cheapskate. She won't replace them. If my lappy gets stolen I at least want to know that a criminal can't access my data
[19:38] <chowder> until it breaks? can luks cause filesystem corruption or something?
[19:41] <penguin42> no, it's just more complex
[19:42] <penguin42> chowder: luks is a good safe way of doing it - set a bios password as well
[19:43] <chowder> penguin42: how about using a hardened kernel? I know there's a "ubuntu-hardened" channel but I think I'd be ok with encryption
[19:45] <penguin42> chowder: Shrug that depends on what you're defending against
[19:45] <chowder> mainly wanna prepare in the event my lappie gets stolen
[19:45] <penguin42> chowder: Ideally you should set a hard drive password in the bios so that even if someone popped the drive into another machine they couldn't trojan the /boot part to record your password to rescue it later
[19:46] <chowder> penguin42: would encrypted swap be a good idea?
[19:46] <penguin42> chowder: Yes
[19:47] <penguin42> chowder: But if you just do the luks-lvm route then the swap is just one more lvm logical volume - so you get that with no extra effort
[19:47] <chowder> that's true...I kind of forgot about that
[19:47] <chowder> I need to run Windows in a DomU for school...ugh. I go to university online
[19:48] <penguin42> chowder: Now I don't know anything about Xen really - so don't know how this all interacts with Xen
[19:49] <chowder> penguin42: I figure it shouldn't be too bad seeing as how Ubuntu has a how-to article on running Ubuntu with Xen. I'm guessing it'll be fine.
[19:50] <penguin42> chowder: Probably but I think there is some magic about how Xen loads it's Dom0 and I don't know if that needs to be decrypted etc - but I use KVM and that just works with luks/lvm no hastle
[20:50] <Raazeer> hi guys, is there any way of getting the snd-*-oss modules in 13.04 (short of a custom kernel compile if at all possible)?
[20:54] <Raazeer> anyone?
[20:54] <Raazeer> the sources have to be somewhere
[20:55] <sladen> Raazeer: the ALSA OSS-emulation modules?
[20:59] <Laney> Can we do support elsewhere please? :-)
[20:59] <mlankhorst> Raazeer: use cuse + osspd
[21:01] <Raazeer> I assume you mean fuse instead of cuse
[21:01] <mlankhorst> cuse
[21:01] <mlankhorst> character device in userspace
[21:02] <Laney> :|
[21:02] <Raazeer> Laney: I DID ask in #ubuntu earlier. nobody there even reacted to questions about oss
[21:03] <Raazeer> I assumed (correctly) that I would find some more in-depth knowledge here.
[21:03] <Raazeer> mlankhorst, found it, and thanks for the hint
[21:04] <Raazeer> and thanks guys, that helps
[21:04] <Raazeer> whom do I turn to to have some package dependencies updated?
[21:07] <mlankhorst> the package's maintainer
[21:09] <Raazeer> guys, cut me some slack here, I usually try to keep as
[21:09] <Raazeer> close to the reef as possible where maintaining and stuff is concerned
[21:10] <Raazeer> I think oss-compat needs osspd as a dependency. how do I go about finding the right guy to talk to?
[21:15] <Raazeer> ok, have it your way - I was trying to help, see if I will again
[22:39] <sladen> Laney: it might be the weekend, but there are politer ways of directing people elsewhere.  eg. stating a specific location, rather than just "somewhere else", may people that somebody receives assistance, rather than feeling simply deflected
[22:40] <Laney> I PMed him
[22:40] <sladen> Laney: there's certainly a case with keeping the signal-to-noise high when things are busily happening, but if it's the only activity on the channel all day, questions are unlikely to a major deteriment to productivity
[22:41] <Laney> And my point isn't really the level of activity at the time of the question but creating inappropriate support backchannels
[22:55]  * ScottK agrees with Laney