00:37:29 <Tekk> I'm pretty sure I'm missing something stupid, but I'm not sure where to look. When I open, say, a youtube page, the media will start playing for a few seconds and then pause. I have autoplay enabled in Settings/Media. in about:config media.autoplay.enabled is true, media.enabled.user-gestures-needed is false, and block-autoplay-until-in-foreground is false 00:37:34 <Tekk> Where else should I be looking? 10:41:52 <frg_Away> Tekk if you have NoScript you need to enable js for all domains which show blocked. 17:45:08 <nsITobin> hai 17:51:03 <Tekk> Hej 17:51:22 <Tekk> Apparently one of the autoplay things I did eventually fixed it, plus let me scroll on youtube videos again 17:51:24 <Tekk> Browsers are weird. 17:55:20 <nsITobin> i need to find a linux userspace that isn't terrible 18:13:08 <Tekk> nsITobin: Depending on your definition I think you can use alpine with musl an busybox :) 18:13:41 <nsITobin> it needs to be standard glibc and sysvinit 18:14:07 <nsITobin> really I'd just like something even simpler than sysvinit but i dunno yet 18:14:34 <nsITobin> i want to basically be able to assume control over startup of the userspace as if it was fuckin dos and i had an autoexec file 18:16:30 <nsITobin> Tekk: I need a sysroot in a tarball with x11 and devtools beyond that i can do everything else 18:17:01 <nsITobin> you see what I am getting at? 18:17:48 <nsITobin> i can do even that but damn its a slog and i'd need to learn to build x11 as well 18:18:00 <Tekk> That wouldn't be the worst thing to roll on your own, probably. 18:18:40 <nsITobin> well i don't understadn why no one provides such a base/starter distro 18:19:19 <Tekk> What you're describing is pretty similar to the alpine sysroot I think? 18:19:30 <nsITobin> yeah but what init system? 18:19:45 <Tekk> I think apk uses sysv or something simpler 18:19:54 <Tekk> I don't think it's a systemd distro at any rate 18:20:30 <nsITobin> openrc 18:23:19 <Tekk> That's not too ba 18:23:22 <Tekk> bad 18:24:24 <nsITobin> yeah the point is i don't actually want to learn another init system but be capable of BEING the init system.. and going from there 18:24:57 <nsITobin> after I do it THEN i will have a BETTER idea of what needs to be done to deal with it simply and efficiently for me 18:25:21 <Tekk> I mean if you're in a chroot there's not gonna be an init syste running 18:26:55 <nsITobin> yeah but i want to boot to a shell and type them in my self and then write a script that does it 18:27:05 <nsITobin> BASH should be the init system... 18:27:10 <nsITobin> ha 18:28:53 <nsITobin> but yeah Tekk taking control of startup.. that's the ticket 18:36:56 <Tekk> Oh! That's even easier 18:37:08 <Tekk> So all you need to do is either build your kernel with no modules 18:37:19 <Tekk> Or just replace /bin/init (or whatever your initrd calls for 'real' init with /bin/bash ) 18:37:20 <Tekk> :) 19:27:42 <nsITobin> Tekk: while my kernel has module support i typically build in everything.. 19:27:51 <nsITobin> need it for vmware 20:00:19 <Tekk> Well there you go then. You don't need an initrd 20:00:36 <Tekk> Just edit your bootloader config to pass init=/bin/bash and remove the initrd 20:00:41 <Tekk> Unless you have an encrypted disk or similra 20:06:16 <nsITobin> it is getting to the point any mainstream systemd distro is too compramised to run in that way to any useful degree and i don't use initramfs .. right now i can install any redhat based os with a basic chroot if i do it from a redhat based os it is simple but its all systemd based