feddit.org

2 points

1 month ago

Yes that is indeed what I seek, thank you!

Well so it seems it is on /dev/sr0, because I have found some help on burning the disk through CLI with cdrecord itself, and sox to convert the files to .cdr format. The disk is now “burning” (well, it sounds like it! We’ll see if it plays here shortly), but I would like to find out how to use brasero to do it.

For now though I can write a script to convert all the files in a given dir to .cdr and then auto burn them to the disk if this works though which ain’t too shabby.

report

[ - ]

2 points

1 month ago

It looks like Brasero would handle all of that kind of Media Management stuff for you, so try it out before you reinvent the wheel.

report

[ - ]

1 point

1 month ago

Well that’s the thing, I still haven’t figured out how to make brasero actually do anything, but I have already written and tested my first version of my script and it’s burning my second disk now. On this test I’ve figured out another line I need to add to improve it (and make it clean up the .cdr files after itself.) So, unless I can find someone with better instructions on brasero than “just do it” it seems I’m stuck with reinvention.

Incidentally, is it better for me to call sudo inside the script for cdrecord -v or should I not use it inside and instead run sudo myscript for the whole thing?

report

Kimjongtooill@sh.itjust.works

[ - ]

2 points

1 month ago

I think Ideally you should be able to run it as you instead of root or sudo. I’m assuming you are needing sudo since you don’t have access to the burner as your user.

Do an “ls -lah” on your cd burner. I think you said it was /dev/sr0 so “ls -lah /dev/sr0” and see if it is owned by root:root or hopefully root:disk or something like that. The format is “user:group” so I’m hoping it is owned by a group that you can simply add your user to.

If it is owned by another group, you can just run “sudo usermod -aG disk user” replace disk with the group that shows on the ls command and user with your user.

If that burner is owned by root:root, there is a way to change that. But that gets very complicated. And I’m not sure its worth the effort for you unless you are wanting to learn more. Point 4.3 here: https://wiki.archlinux.org/title/Udev

In which case to directly answer your question, I’d personally prefer to sudo the script instead of adding sudo in the script. But at the end of the day, I don’t think it matters too much for this specific use case.

report

[ - ]

1 point

1 month ago

Looks like root, I think. It says

brw-rw----+ 1 root cdrom 11, 0 Aug 18 14:13 /dev/sr0

no “:” though oddly, so maybe I can run

sudo usermod -aG cdrom $USER?

Edit: looks like it throws the same error as not sudoing, wodim no write mode specified blah blah. It did add me to the cdrom group though. Although now it won’t work with sudo, how do I remove myself from the cdrom group?

Edit again: Wait, I got it working with another disk, the one I was just trying may have been too big to fit on the disk but throwing the same error as when I didn’t use sudo. Burning this one with sudo, will test again without when it finishes. Thankfully I have a stack of these disks lol I can do this all day.

Ok, still need sudo. Without sudo it just exits without writing to the disk. I guess what I thought was warnings is just standard incomprehensible readout, but yeah without sudo (or if the files are too big for the disk) it just exits and finishes out my script removing the .cdr files.

report

Kimjongtooill@sh.itjust.works

[ - ]

2 points

1 month ago

My bad thought it was printed as “user:group” and not “user group”.

When you add yourself to a group you need to either log out and log back in or reboot in order for it to take effect. So maybe next time you log in try it without sudo again.

report

[ - ]

1 point

1 month ago

Oh cool thanks I’ll log out and try again. Ran into another issue in my script I’m trying to work around now though: I disconnected and reconnected the drive, now it’s /dev/sr1!

So, I guess I need to have my script run cdrecord -checkdrive, and then take that answer as a variable $CDROM and pump it back into cdrecord -v dev=/dev/$CDROM -audio yadda yadda.

This is getting a liiitle above my head lmao.

Edit: logged out and in, no dice, still sudo. Now to figure out this checkdrive issue…

report

Show more comments

[ - ]

1 point

1 month ago

hey, man. I’m sorry you felt like I was saying “just do it”. I’d be happy to help more, but I don’t have a CD ROM to test with. I just assumed the GUI would be more self explanatory. Like I said above, I’ve never had to burn a CD on Linux. Please remember that the Linux community is made of volunteers. Getting frustrated at them doesn’t really make them want to help, especially since I literally cannot help anymore than I have without a CD rom in my hands. If you want to ship one to me, I’d be happy to figure out Brasero and walk you through it. Since that is clearly unreasonable, remember that these forums are populated by well-intentioned people doing their best.

report

[ - ]

1 point

1 month ago

I mean it’s not your fault, that’s what the documentation for brasero says. It doesn’t tell me how to “select where to save it” or whatever their exact verbiage is however, and the hard part is even getting people to understand what my issue is. You may not have been able to answer my main question but you helped me work around it, sorta, and for that I am grateful. I just wish the documentation and every comment helping didn’t just say “download brasero” (which I clearly have already done as per my question) or “use this link which says ‘brasero: just do it.’”

Tbf I’m sure most people don’t bother to try and solve things themselves before posting, but I’ve already seen the brasero instructions that were linked because I did, and it still doesn’t tell me what I need to select to get the files on the disk, it just tells me that I need to select something. Again I think selecting /dev/sr0 will replace and overwrite sr0 as per the warning, so I do not think it is the correct answer, and so far nobody has given any alternatives as to what the answer might be, instead offering suggestions on how to download brasero or that darn link again.

And as to reinventing the wheel:

Now I’m trying to get my script to run cdrecord -checkdrive and pipe that answer into my script, the damn thing is now on /dev/sr1!

report

[ - ]

1 point

1 month ago

oh! I’m more of a debian guy than a fedora guy which is why this is a bit out of my depth, but /dev/sr1 is just the equivalent of the E:// drive (that is, for whatever reason, you OS mounted it as a new disk). Perhaps this means it burned successfully?

Unfortunately, yeah, not all documentation can cover the entirety of Linux design from the bottom up and back in this era, Linux was used almost exclusively by academics at universities. As such, the documentation was never written for a general user. It has come a very long way since then, but back when cd roms were common, it was a thousand times worse. Also, YouTube didnt work on Linux at all, so you had to be really committed to fuck around with it.

report

[ - ]

1 point

1 month ago

Yeah I was able to burn a few successfully but not with brasero, found a reddit post where someone was just using cdrecord and I’ve now wrote a script to just call cdburner (my script) and just burn all the files in the directory to a disk.

Now I just need to figure out how to take the output of cdrecord -checkdisk which gives

Detected CD-R drive: /dev/sr1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'Slimtype'
Identification : 'eNAU108   8     '
Revision       : 'XL0A'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R

And take the Detected CD-ROM Drive: /dev/sr1 part, or rather just the /dev/sr1 part of that in particular, and use that as a variable called $cdrom or something, and pipe that back into cdrecord -v speed=8 dev=$cdrom -audio -pad -nofix *.cdr that does the burning. At the moment I have to edit the /dev/sd[X] part of the script before I call it.

report

Show more comments

[ - ]

https://dev.to/softwaresennin/linux-directory-structure-simplified-a-comprehensive-guide-3012

2 points

1 month ago

Also, check out this article:

It goes over basic folder structure for Linux so that you have a rough idea where something like C://Users/User/Program Files lives in it’s equivalent form on Linux.

report

[ - ]

1 point

1 month ago

Thanks this is super helpful! I’ll be saving this one to pdf for future reference too!

report