06:20 <asimovsh> can anyone say what are this process running in sh?

06:20 <asimovsh> sh -c while date +'%Y-%m-%d %l:%M:%S %p'; do sleep 1; done

10:14 <phoebos> asimovsh: maybe you can guess?

13:10 <sad_plan> hi

13:49 <asimovsh> phoebos: i really don't know too much about sh, i just want to find what is causing the terminal bug

14:43 <phoebos> what bug?

14:44 <phoebos> you're missing quotes around the argument to sh -c

14:45 <phoebos> or, remove the `sh -c`

14:50 <asimovsh> phoebos: everytime i exec a new term it appears with 3 lines instead of one

14:51 <asimovsh> I just don't know why kiss is running this sh -c command

14:52 <asimovsh> I think is some problem with sh because all terminal is the same

15:00 <sad_plan> asimovsh: no, all terminals will run a shell of thier own

15:01 <sad_plan> did you put this into your .profile or shellrc? making it spawn each time you start a new terminal

15:04 <asimovsh> No

15:05 <asimovsh> Is just export configs and some sway conditions to creat XDG_RUNTIME and auto start sway

15:07 <asimovsh> https://privatebin.net/?4c61272e0bf2f4a5#B4yqg87yamMf6fAq9Js1N9S2mb3XS4VXhRdWq4J2jruZ

15:12 <asimovsh> termbin.com/v9nq1

15:12 <asimovsh> Heres my .profile

15:13 <asimovsh> And ashrc is just one alias

15:34 <sad_plan> hm

15:43 <phoebos> maybe a sway configuration?

15:45 <sad_plan> yea, or perhaps his /etc/profile if root is running it?

16:54 <asimovsh> My SWAT config

16:54 <asimovsh> https://termbin.com/ikyv

16:54 <asimovsh> Sway config

16:58 <asimovsh> Seems pretty normal

17:27 <sad_plan> looks good to me. any bootonfigs perhaps?

17:47 <asimovsh> Just a sec

17:52 <asimovsh> termbin.com/bj5r

17:53 <asimovsh> Inittab

17:53 <asimovsh> termbin.com/xvvk

17:54 <asimovsh> rc.boot

17:55 <asimovsh> also like i said

17:56 <asimovsh> i don't know if your kiss is doing this sh process too

17:57 <kmf> hello, is there any up to date statically linked kisslinux repo? I dylin's is 2 years old and only the stuff in core is statically linked and sad_plan's is a year old (but supposedly everything in there builds which is super cool), how much is carbslinux statically linked?

17:57 <sad_plan> what about any configs in /etc/rc.d? those are boot hooks that you can appply pre/post-boot etc..

17:58 <sad_plan> kmf check my kiss-dumpsterfire. or oasis linux. i my repo, I try to be mostly statically linked, but some stuff is just a pain..

17:59 <sad_plan> you could also just reference kiss-somethingsomethingstatic aswell. that was probably the one you refered to though

18:01 <asimovsh> sad_plan: i dont have rc.d in /etc

18:01 <asimovsh> termbin.com/8iifx

18:01 <sad_plan> no? hm. I couldve sworn its added by default

18:01 <kmf> sad_plan how to use kiss-dumpsterfire, I tried building tinyx in there but couldn't because it required libX11 and such, should I just get them from the xorg repo? but then they wouldn't be statically linked (I wouldn't mind that too much, but I want to get a working Xorg, what other repos do I need?)

18:01 <asimovsh> This is the process running when i view with htop

18:02 <asimovsh> And i don't know what it do

18:02 <sad_plan> who runs it? is it root? or your user asimovsh ?

18:02 <asimovsh> user

18:03 <sad_plan> ok, that means its not global, so it must be something assosiated with your user. some config file or w/e. any scrpts you usually use?

18:03 <asimovsh> Nop

18:03 <asimovsh> i dont use any script

18:03 <sad_plan> kmf: I use kiss-xorg aswell, so I dont have to maintain everything myself. libX11 is one of those things.

18:03 <asimovsh> or a special config

18:03 <asimovsh> just use .profile and thats all

18:04 <sad_plan> kmf: kiss-xorg has added static libs into xlibs, so should still be able to statically link things just fine. however, the mere existence of shared libs often gives one issues, because it always defaults to them. which is rather anoying

18:04 <sad_plan> kmf: I also use the upstream repo, aswell as community

18:05 <sad_plan> asimovsh: hm. this ones a tough one..

18:11 <asimovsh> Yeah

18:12 <asimovsh> I dont now why is this happening

18:12 <asimovsh> But i think is something related to kernel or something

18:12 <asimovsh> I never haved this problem

18:13 <asimovsh> I just made one installation and know is everytime with the bugs

18:14 <sad_plan> never have I. does it have a PPID? a parent PID

18:17 <asimovsh> The sh process?

18:20 <sad_plan> yep

18:21 <sad_plan> and I assume it runs wether you reboot aswell?

18:22 <sad_plan> kmf: I cant respond to your messages if you quit. in any case; kiss-xorg after mine, then upstream core repo and community

19:31 <asimovsh> Yeah

19:31 <asimovsh> Even if i reboot it still running

19:33 <sad_plan> hm, ok

20:21 <ehawkvu> turns out that I'm not the first person to provide an emacs interface into kiss

20:21 <ehawkvu> https://github.com/dylanaraps/community/commit/e370a224520d07e6e42ba045845674b39dea03a4

21:39 <kmf> sad_plan: thanks, for some reason my mouse isn't working in tinyx even though it is working in Xorg (does libinput work even if you don't have the mouse driver in kernel?)

21:52 <vouivre> asimovsh: I also use ash as my shell and I have the same problem.

21:53 <vouivre> when I open a terminal, I have three lines.

21:53 <vouivre> I never solved this problem until now

21:54 <vouivre> I remember, if I downgrad busybox to 1.35, everything works fine. I don't have the problem anymore.

21:56 <midfavila> bleh

21:56 <midfavila> haven't had any time to do computer shit recently