Find a nice book/primer on Unix commands. They mostly work on Linux as well. You need 'cd' to move between folders, 'ls to list files, type to display text files, 'whereis' to find the location of a file 'su' to switch to root access. most commands will list command line options if you add the --help option. Conversely, you can try 'man '+ command to get help on most commands.
When I was working a lot on Linux/Unix, I found a book called "Tricks of the Un ix Masters". It helped immenselywith file editing and bash scripts.
Good Luck and Dive In,
I'm building a linux-based bluetooth speaker that uses speech recognition to display captions for what is playing on the speaker and I'm trying to figure out where to start in terms of where to intercept the bluetooth audio. I understand that ALSA and PulseAudio could be used to intercept audio from applications before they get sent to the audio hardware, but I haven't had much luck figuring out how a bluetooth source can be intercepted. Any help understanding how bluetooth fits into the audio architecture would be appreciated. Here's what I'm trying to do:
Phone->bluetooth->my custom linux-based bluetooth speaker->run raw audio through speech AI->audio out to speakers and captions out to display.
am I looking for someone who specializes in hardware programming? I have a sound card which is at the same time control surface is the digi 003 console of digidesign. at the time this card was dedicated and only worked with a specific software, protools 7, but as the company was acquired they stopped the software updates and now the control part is unusable, we only have access to the card are and at 2out of 8. suddenly I was wondering if it was possible to reprogram it, it isin firewire. if it was possible to go into it somehow and unlock it?
suddenly on my 2008 macpro I installed the famous linux studio that you helped me to troubleshoot, thank you again but it's been a while since I wonder if I could not hack my card to be able to use it at 100 %
You might be able to use nmap to find out. You can use the -Pn option to tell nmap to skip the ping scan to determine if the host is up. Be aware that nmap will try to connect to a wide range of known ports, which might trigger watchdogs on the target network. In general, using nmap on networks that you are not a valid user of is considered bad manners, so discuss with the network owner before using.
Your success will depend on how the firewall is configured. If it is set up to block all access from WAN for that host (e.g. drop all inbound/outbound packets to/from the host you are interested in), you will never get any response from the host. Your only hope may be that you can access a different host on the target network and be able to try to ping or connect to the host from there.
My current OS gparted obviously does not see md device associated with the array, but it sees the USB /dev/sdx (and all the partitions) , and it does not exist in mdadm.conf file. Also mdadm --detail --scan --verbose cannot see it either - no surprise here.
Is there a SAFE way to recreate RAID5 md device in my current OS?
Can I use mdadm --create ..... to keep current data intact?
A search for "<your distro> RAID" should lead you to some useful documents.
There is one I can't quickly find that discusses rearranging RAID partitions, changing RAID levels and so on.
That would give you a starting point.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
So far I have found tools to recover Linux.
I am after restoring specific , already data containing RAID5 array.
Looks as I could used mdadm --assemble
I cannot find anything stating it will keep exciting data intact.
After RAID is created it has to be configured in fstab to auto-mount on boot.
I am not sure where to obtain the correct format and mounting data to fstab.
I got as far as "UUID= ...."
I am using "mount -a" to verify fstab.
Is there a way to add line to fstab so mount will report / echo it as a comment ?
I am currently hacking it by putting invalid text to fstab, the "mount" reports such entry as an error and gives me a line # .
You can use --fake or -f to get mount to test your fstab.
What you put in /etc/fstab depends on what your raid is like. If you're using a hardware raid controller, then the RAID cluster is probably presented to the OS as /dev/sdx, but if you're using software raid, the I think the cluster is presented as /dev/mdn.
After creating your RAID, you'll need to partition and format, just like a normal Hard drive. Once you've done that, you can use blkid to get the UUID of the partition for fstab.
Keep Calm and Carry On
Last Visit: 31-Dec-99 19:00 Last Update: 1-Feb-23 13:33