That didn't work either. I just got mad and wiped the drive and reinstalled the OS and it works now.
Thanks for the help anyway.
I use morituri http://thomas.apestaart.org/morituri/trac/I desperately need a CD ripper to rip music from an external USB drive but I can't find any at all... Here's what I've tried:
Sound Juicer: works well for FLAC, no paranoia mode for accurate rips (especially important for scratched CDs), can only rip straight to MP3 at 32kbps which can't be changed.
Asunder: doesn't recognize external drive.
RipperX: doesn't recognize external drive.
Rhythmbox: very unstable, crashes all the time when trying to rip a CD.
ABCDE: only works in Terminal, no idea how to use it, let alone get it configured to work with my external CD drive.
I mean seriously, I'm starting to think I'll have to buy Windows just so I can rip CDs....
Sound Juicer works perfectly for me. IIRC correctly it uses paranoia mode by default and proper MP3 support should be a matter of having the relevant packages installed. What distribution are you running?
I use morituri http://thomas.apestaart.org/morituri/trac/
Recognizes my external drive. It checks musicbrainz for metadata and looks at the accurip database for accuracy.
edit: just installed it but I can't find it anywhere???
Only rips to FLAC. So if you want MP3, you'd need something to convert from FLAC to MP3, which should be easy enough.
Only rips to FLAC. So if you want MP3, you'd need something to convert from FLAC to MP3, which should be easy enough.
The command is just 'rip'edit: just installed it but I can't find it anywhere???
rip cd rip
rip offset find
The command is just 'rip'
rip cds using
Code:rip cd rip
But for the first thing you want to do is have it record the offset of your drive using:
Code:rip offset find
you can look at the manpage for rip for more info.
Using fallback read offset 0
Checking device /dev/sr0
eject: CD-ROM tray close command failed: Input/output error
rip: error: cannot read CD from drive.
cdrdao says:
Unable to open SCSI device /dev/sr0: Device or resource busy.
Please use option '--device {[proto:]bus,id,lun}|device', e.g. --device 0,6,0, --device ATA:0,0,0 or --device /dev/cdrom
Cannot setup device /dev/sr0.
How do I select my external drive? I suppose I'd have to find out what the drive is called first, how do I do that?
This is what I get after typing rip cd rip:
Looks like you use --device. Usually with my external drive, it's put in dev/sr0 (which is what this looks for by default).
But if you CD is somewhere else, you can put the path like it's shown onthe last line of the error message
Okay so I just found out the external drive is sr1. What's the command line I have to use to set Morituri to sr1?
i think it's the commands above with --device /dev/sr1
Usage: rip cd rip
rip: error: no such option: --device
I type "rip cd rip --device /dev/sr1" and I get:
I'm completely terminal illiterate so no clue what to do now.
I think it might need to be rip cd --device /dev/sr1 rip
then
It works, thanks! Recorded the offset as well which is 6.
Now while ripping I get "Warning: pycdio not installed, cannot identify drive". Can I just ignore this?
It works without that?
I think that is python bindings for for libcdio:
https://www.gnu.org/software/libcdio/
Which does some important stuff. Maybe it's only a soft dependency for morituri or something...
The Linux Mint website was cracked, and on Saturday was made to offer for download modified versions of Linux Mint that have a backdoor (the checksum listings were also changed). The backdoor is Tsunami, which is used to make a botnet.
Personally identifiable information from users from the Linux Mint forum was also taken, and the passwords used PHPass which is crackable (some of these passwords have already been). The entirety of this information has been made available for purchase on the dark web.
http://www.zdnet.com/article/hacker-hundreds-were-tricked-into-installing-linux-mint-backdoor/
Well, that's quite ugly. What a nasty business. I hope the affected end users can avoid all, or most, damage to their systems and reputations.
What was the means of attack to get in?
http://www.csoonline.com/article/30...ata-up-for-sale-iso-downloads-backdoored.htmlResearchers who have examined the compromised ISO file say that the backdoor an IRC bot named Kaiten - doesn't work.
Kaiten has been open source since about 2001, so the code isn't something new or unique. Early reports on the hack said the IRC bot was Tsunami, which is technically correct, as that's one of the names used to identify the bot's core code (AV companies use this name too), but the code itself is Kaiten.c.
Another article just says that the individual targeted "vulnerabilities in WordPress".
But also:
What did they ship that they shouldn't have? I am completely ignorant of Mint in general.That's the problem with hosting WordPress and your download pages on the same server. Even if you do a pretty good job in admin you should always assume WP may be cracked one day.
Linux Mint has always annoyed me with how poorly they do things, both on the technical side as well as their insistence on illegally shipping software (i.e. shipping stuff they're not allowed to) but this must be pretty bad days for the people working on the project, feel kind of bad for them.
What did they ship that they shouldn't have? I am completely ignorant of Mint in general.
It was confirmed that the forums database was compromised during the attack led against us yesterday and that the attackers acquired a copy of it. If you have an account on forums.linuxmint.com, please change your password on all sensitive websites as soon as possible.
The database contains the following sensitive information:
Your forums username
An encrypted copy of your forums password
Your email address
Any personal information you might have put in your signature/profile/etc…
Any personal information you might written on the forums (including private topics and private messages)
People primarily at risk are people whose forums password is the same as their email password or as the password they use on popular or sensitive websites. Although the passwords cannot be decrypted, they can be brute-forced (found by trial) if they are simple enough or guessed if they relate to personal information.
Out of precaution we recommend all forums users change their passwords.
While changing your passwords, please start with your email password and do not use the same password on different websites.
What happened?
Hackers made a modified Linux Mint ISO, with a backdoor in it, and managed to hack our website to point to it.
Does this affect you?
As far as we know, the only compromised edition was Linux Mint 17.3 Cinnamon edition.
If you downloaded another release or another edition, this does not affect you. If you downloaded via torrents or via a direct HTTP link, this doesn’t affect you either.
Finally, the situation happened today, so it should only impact people who downloaded this edition on February 20th.
How to check if your ISO is compromised?
If you still have the ISO file, check its MD5 signature with the command “md5sum yourfile.iso” (where yourfile.iso is the name of the ISO).
The valid signatures are below:
6e7f7e03500747c6c3bfece2c9c8394f linuxmint-17.3-cinnamon-32bit.iso
e71a2aad8b58605e906dbea444dc4983 linuxmint-17.3-cinnamon-64bit.iso
30fef1aa1134c5f3778c77c4417f7238 linuxmint-17.3-cinnamon-nocodecs-32bit.iso
3406350a87c201cdca0927b1bc7c2ccd linuxmint-17.3-cinnamon-nocodecs-64bit.iso
df38af96e99726bb0a1ef3e5cd47563d linuxmint-17.3-cinnamon-oem-64bit.iso
If you still have the burnt DVD or USB stick, boot a computer or a virtual machine offline (turn off your router if in doubt) with it and let it load the live session.
Once in the live session, if there is a file in /var/lib/man.cy, then this is an infected ISO.
What to do if you are affected?
Delete the ISO. If you burnt it to DVD, trash the disc. If you burnt it to USB, format the stick.
If you installed this ISO on a computer:
Put the computer offline.
Backup your personal data, if any.
Reinstall the OS or format the partition.
Change your passwords for sensitive websites (for your email in particular).
Is everything back to normal now?
Not yet. We took the server down while we’re fixing the issue.
Who did that?
The hacked ISOs are hosted on 5.104.175.212 and the backdoor connects to absentvodka.com.
Both lead to Sofia, Bulgaria, and the name of 3 people over there. We don’t know their roles in this, but if we ask for an investigation, this is where it will start.
What we don’t know is the motivation behind this attack. If more efforts are made to attack our project and if the goal is to hurt us, we’ll get in touch with authorities and security firms to confront the people behind this.
If you’ve been affected by this, please do let us know.
bcdedit /set "{bootmgr}" path \EFI\elementary\grubx64.efi
Is this the one that brings AMDGPU PRO?Ubuntu + XUbuntu 16.04 are here.
Is this the one that brings AMDGPU PRO?
I installed Ubuntu Gnome 16.04 (64-bit) two days ago.
Steam isn't wanting to install, either from the deb from the website or from the multiverse repository. I am not on my computer now so I can't write the exact error at the moment but is anyone else having the issue? I tried the usual 32-bit additions but had no success.
I installed XUbuntu which uses Kernel 4.4.0-21 at the moment when the current release is 4.4.8.
Something's not right.
I think Kernel 4.5 will be used in 16.10, which will see full AMD optimization, so the answer to your question is sort of. 4.4 is the start. Only exciting since this release is a LTS (long term support for updates). The releases in between LTS are usually supported at most 9 months.
I've been looking at the kernel changelog over the months, and it's been updating consistently. I'm guessing with what XUbuntu is using what Ubuntu uses, and that's why things are wonky. Read my post above.
The 'upstream' kernel (what you see in kernel.org) changes too rapidly, meaning bugs may be introduced. Ubuntu takes a version a few months before they ship and use that, only bringing in specific, hand-picked fixes from the newer versions.
Thank you for replying. Yes it is a fresh install and I know it was a daily, but it was updated and upgraded. I just tried installing it by command line again today and this time it worked. It is a bit weird that it was cut this close, only being able to be installed from the day of the distribution version's official release.Today is the official release day. Prior to that, there were dailies.
I've been looking at the kernel changelog over the months, and it's been updating consistently. I'm guessing with what XUbuntu is using what Ubuntu uses, and that's why things are wonky. Read my post above.
Did you install from a clean partition?
I installed XUbuntu which uses Kernel 4.4.0-21 at the moment when the current release is 4.4.8.
Something's not right.
I think Kernel 4.5 will be used in 16.10, which will see full AMD optimization, so the answer to your question is sort of. 4.4 is the start. Only exciting since this release is a LTS (long term support for updates). The releases in between LTS are usually supported at most 9 months.
Today is the official release day. Prior to that, there were dailies.
I've been looking at the kernel changelog over the months, and it's been updating consistently. I'm guessing with what XUbuntu is using what Ubuntu uses, and that's why things are wonky. Read my post above.
Did you install from a clean partition?
Hey GAF, quick question: what do you guys recommend as a gamepad for playing steam games in Ubuntu? I assume either Dualshock 4 or Xbox One gamepad depending on personal preference? Is there something better out there?
Hey GAF, quick question: what do you guys recommend as a gamepad for playing steam games in Ubuntu? I assume either Dualshock 4 or Xbox One gamepad depending on personal preference? Is there something better out there?
Ok so I am downloading Ubuntu 16.04 I want to install it on my second drive. The 2nd drive does have files and things on it. Can I partition it to have space where I can install Ubuntu too while keeping my other files on it for windows?