How to back track ones steps to figure out what one did to get something working?

userxbw

userxbw

well I actually got bluetooth & firefox with videos to play into the BT headphones, but I have no idea how I did that from reading through so many how to's picking this and that out and hacking away trying different things some how I have /dev/dsp showing up in pavucontrol for pulseaudio I just need to figure out how to back track to know for sure how I did this to reproduce it.

anyone know what and how to check everything pertaing to connecting sound (whatever they are called) together to make a complete connection?
 
Last edited:
sh offers a history of previously entered commands....

But, if backtracking is important (and not an afterthought), you first list out the steps, and go through them like a sequential checklist that you actually stick to. I make a list of steps 1...n on a piece of paper, and actually check stuff off and write down what the output was. That way, I can backtrack to a specific step.
 
I've always undone all my changes and tried different methods until I find the one solution that works.

Edit: sorry, this is what I've done in the past. I didn't clarify very well.
 
You must log in or register to reply here.
Back
Top