Well.... Bash scripting is pretty much no existant, at least for now. Radio shows are going fine but what I did was pre record my shows for the next 12 weeks because I am getting a bone marrow transplant around the end of October. This way my audience will still think I am doing my show live, at least until early next year. I just completed a 21K marathon today so I am really happy. It was fantastic!!
Now, getting back to this forum, it's nice to see that you are still involved with this VERY SPECIAL distro. You helped me out a great deal in the past and I learned a lot.
What I find this time around is that I have learned even more when it comes to Linux, AND I have been using Google more for answers to some of my questions.. There's just something about #! that's hard to pin down. The community for sure is a big part but it's the distro itself that I find so captivating especially on my old laptops.
I, like so many was very sad to hear about Crunchbang. I have always had this amazing distro on all my machines and although I tried and continue to try out other distros, I always came back to Crunchbang. I stumbled along the way learning linux through this great distro and if it wasn't for the excellent Crunchbang community, I might still be trying to figure out fstab is and what crontabs are for.
My hope is that something will come out of this and that some variant of Crunchbang will emerge.
In the meantime, can I still use Crunchbang? Will the security updates and regular debian updates still be available? Any recomended distro alternatives I can try out? I tried Manjaro Openbox. Very interesting distro but it at least for me lacks the speed and simplicity of Crunchbang. For the moment, I am using Xubuntu as my main distro.
Again, I want to thank the entire Crunchbang community and this EXCELLENT forum for helping me along the way over the past few years!!
I have Linuxlite 2.2 installed on a Dell 3000 desktop with 2GB of RAM. When I went to the terminal and typed crontab -e, I used nano to setup my cronjob:
*/10 * * * * /usr/bin/arecord -t wav -f cd -d 44 /home/randy/Music/test.wav
This works fine except that there is no audio. When I run this from the terminal, everything works fine.
/usr/bin/arecord -t wav -f cd -d 44 /home/randy/Music/test.wav
Any ideas why it is not working from Cron? What can I try out and post back? I have Crunchbang installed as well on this machine and I have no issues at all regarding the above. I had Zorin installed and also had no issues. It seems to be with Linux Lite. I have a post on their forum as well but thought that maybe someone in this forum might have me try something I missed.
I will manually run my regular rsync code in the terminal instead of a cronjob My sync issues that I had mentioned in my initial post were probably because I was running the code in a crontab. I just thought that automating the sync's would require less of me to get involved but I will do it manually from now on.
Thanks Luc. What I decided to do was run the rsync code I have been using, from the terminal instead of a crontab. So far it is working great and I am almost finished doing the initial syncing. Once this is done than I will run rsync from a crontab set to run every hour or something like that.
Thanks to everyone who submitted posts to this thread as it will greatly help me in the future.
I am running the rsync code verbose directly from a terminal window instead of using Cron. This way I can see if there are any hickups happening. I was successful syncing the letter K folder (2.1GB), in just under 3 minutes so that's good.
What I was seeing before when I had show hidden files on, were a few . files that were created and they were all dealing with the same file. Now I only see one . file at a time that corresponds to the FLAC file being processed if that makes any sense.
It took around two and a half minutes to copy 2.3GB of data (FLAC files) from drive A to drive B. When I used rsync, after over 35 minutes it was still syncing one file.
I think I will just copy the folders from Drive A to drive B and then implement rsync to keep both drives in sync unless there is another option. I can post the verbose output when trying to sync if that will be helpful.
Both external USB drives are 1TB in size and are plugged directly into the USB ports on the Dell 3000. I'm not going through a USB hub.
By a straight copy/paste, I mean selecting a few FLAC files (say 8), and just copying/pasting them to Drive B. That may take 10 minutes to do, if that.
By taking a long time, I mean days to sync the files on Drive a to Drive B. What I am going to do is, as a test, choose one of my folders that contain about 10 FLAC files and see how long it takes to sync them to drive B. My largest folders so far are A, B, C, D. I am now going through the letter E in my record LP collection.
I'll try the test I mentioned above and post back with the results. I agree that the first time can take a long time.
Thanks for the advice!!
I have two external USB drives Drive A and Drive B (ext4) hooked up to my computer. I want to copy the files from one drive to another. At the moment I am using this code and it seems to be taking a long time to copy the files over. Is there a better more efficient and speediy way to do this. I want USB drive B to be identical to USB drive A. The files are FLAC files of my digitized LP's. I want to make sure I have copies of them just in case. I am still in the process of digitizing LP's so I would need to continuously backup/sync to Drive B.
A straight copy/paste goes faster than what I am doing with rsync.
* * * * * /usr/bin/rsync -a --delete /media/masterlps/lps/H/ /media/lpsbackup/lps/H
I tried using this but it was really taking a long time (days) so I thought I would break it down and it's still taking a long time
* * * * * /usr/bin/rsync -a --delete /media/masterlps/lps/ /media/lpsbackup/lps
Yes. You're right. The sound should be the same. Sometimes when I recordvoff air I get some interference so it's nice to have the streaming option I can used. And like I said it's so easy to set up. I'll play around with the streamripper options to see what they offer.
I figured this out last night and I have to say that coming from the Mac side for so many years that the terminal, after so much trial and error on my part has to be one of the greatest things about using Linux. I took the code below and just copied it to all my computers in the crontab so that my shows were recorded on each computer and at specific times.
50 10 * * 7 streamripper http://icecast1.isiglobal.ca:80/chuo.mp3 -d /home/randy/ihtsbnov2314 -s -l 6200 50 11 * * 7 streamripper http://icecast1.isiglobal.ca:80/chuo.mp3 -d /home/randy/intransitionnov2314 -s -l 8200 50 9 * * 7 streamripper http://icecast1.isiglobal.ca:80/chuo.mp3 -d /home/randy/bosnianshownov2314 -s -l 6200
Super easy!! Now the only thing is that the files that resulted looked like this - .mp3.
I'm still figuring out how I can name each file by studying the Man page.
The sound of the streamed recordings is quite good so now I have to decide whether to use the off air recordings I make every week or the NEW streamed recordings. Tough decisions
At the moment, I use this code to record my radio show and it works great. I'm recording off air from a radio attached to my computer.
arecord -t wav -f cd -d 8800 /home/randy/Desktop/intransition.wav
I put this code in my crontab file and set the time I want it to record. Works like a charm.
What I want to try now as an added measure of protection so that I have extra backups of my show is to have the ability to record my show from the command line, and then put that in my crontab.
This is the link I will be using:
How can I do this? Streamripper seems to only work with Shoutcast. My show is tomorrow so if I can find a solution by tomorrow, that would be great!
So I changed it to this:
Selection Path Priority Status ------------------------------------------------------------ 0 /usr/bin/startxfce4 50 auto mode * 1 /usr/bin/openbox-session 40 manual mode 2 /usr/bin/startxfce4 50 manual mode 3 /usr/bin/xfce4-session 40 manual mode Press enter to keep the current choice[*], or type selection number: 1 randy@cb11dv6:~$ randy@cb11dv6:~$
Do I just restart my machine now? In the future if this happens again, is there a config file I can go into to change this or is this the proper way to do it?
randy@cb11dv6:~$ sudo update-alternatives --config x-session-manager [sudo] password for randy: There are 3 choices for the alternative x-session-manager (providing /usr/bin/x-session-manager). Selection Path Priority Status ------------------------------------------------------------ * 0 /usr/bin/startxfce4 50 auto mode 1 /usr/bin/openbox-session 40 manual mode 2 /usr/bin/startxfce4 50 manual mode 3 /usr/bin/xfce4-session 40 manual mode Press enter to keep the current choice[*], or type selection number
Is this the section you mean? I see the openbox session is not commented but I'm always booting into something else.
# Available sessions (first one is the default). # The current chosen session name is replaced in the login_cmd # above, so your login command can handle different sessions. # see the xinitrc.sample file shipped with slim sources #sessions default,startxfce4,openbox,ion3,icewm,wmaker,blackbox,awesome sessions openbox-session
I think recently I installed another desktop environment to boot into. Since then I deleted it. But now when I boot into #!, if I don't press F1 to boot into my proper Openbox enviroment, I boot into what looks like a broken DE I used to have installed. How can I get rid of this so that when I start up Crunchbang it loads properly?
Is it something in my autostart file I have to delete?
## Openbox autostart.sh ## ==================== ## When you login to your CrunchBang Openbox session, this autostart script ## will be executed to set-up your environment and launch any applications ## you want to run at startup. ## ## Note*: some programs, such as 'nm-applet' are run via XDG autostart. ## Run '/usr/lib/openbox/openbox-xdg-autostart --list' to list any ## XDG autostarted programs. ## ## More information about this can be found at: ## http://openbox.org/wiki/Help:Autostart ## ## If you do something cool with your autostart script and you think others ## could benefit from your hack, please consider sharing it at: ## http://crunchbang.org/forums/ ## ## Have fun & happy CrunchBangin'! :) ## GNOME PolicyKit and Keyring eval $(gnome-keyring-daemon -s --components=pkcs11,secrets,ssh,gpg) & ## Set root window colour hsetroot -solid "#2E3436" & ## Group start: ## 1. nitrogen - restores wallpaper ## 2. compositor - start ## 3. sleep - give compositor time to start ## 4. tint2 panel (\ nitrogen --restore && \ cb-compositor --start && \ sleep 2s && \ tint2 \ ) & ## Volume control for systray (sleep 2s && pnmixer) & ## Volume keys daemon xfce4-volumed & ## Enable power management xfce4-power-manager & ## Start Thunar Daemon thunar --daemon & ## Detect and configure touchpad. See 'man synclient' for more info. if egrep -iq 'touchpad' /proc/bus/input/devices; then synclient VertEdgeScroll=1 & synclient TapButton1=1 & fi ## Start xscreensaver xscreensaver -no-splash & ## Start Clipboard manager (sleep 3s && clipit) & ## Set keyboard settings - 250 ms delay and 25 cps (characters per second) repeat rate. ## Adjust the values according to your preferances. xset r rate 250 25 & ## Turn on/off system beep xset b off & ## The following command runs hacks and fixes for #! LiveCD sessions. ## Safe to delete after installation. cb-cowpowers & ## cb-welcome - post-installation script, will not run in a live session and ## only runs once. Safe to remove. (sleep 10s && cb-welcome --firstrun) & ## cb-fortune - have Waldorf say a little adage #(sleep 120s && cb-fortune) & ## Run the conky conky -q &