| DistroWatch Weekly
|Linux Foundation Training
|Reader Comments • Jump to last comment
1 • Limit CPU usage (by Mike on 2018-08-20 00:53:52 GMT from Australia) |
I use 'nice' because it was set up automatically by 'Back in Time' and I wasn't sure what it did. This was a great article,thanks.
2 • "without backup" = "begging for disaster" (by OS2_user on 2018-08-20 01:12:10 GMT from United States)
Re the Fedora "fstransform": I wouldn't advise anyone try to convert a file system on the fly. Vastly safer way is make a backup FIRST. Then you have a backup. You can swap the 2nd drive in physically and use it, or reformat the existing and copy to it. -- With the last 3T WD I bought new at $50, there's NO reason to risk loss. Whether pro or home.
I'd say Fedora is actually making these assumptions: 1) the data IS backed up elsewhere, would be only lose a little of recent 2) the system is highly reliable 3) and powered by UPS / EPS so losing power in middle of this foolishness won't happen: otherwise, you'd have TWO file systems! -- sure: the program MIGHT have crash recovery. -- Risk it if you want! You know you want to. Won't bother ME. -- I just do things the obvious way, rather than try fancy stunts. (By the way, I've never actually lost a byte with OS/2 except for hardware failures -- and even then I'd a full backup except for what was working on.)
3 • Mint Debian (by Jon Wright on 2018-08-20 01:29:17 GMT from Hong Kong)
I've been running Mint Debian for a week now. I mentioned last week how the resource usage was very high, but running MATE desktop brings it down significantly. Install a few Caja packages and fix gksu to get the file manager working in a familiar way, then install a few (more) MATE packages to get the Control Center and panel filled out ... then you have a solid desktop. I've gone through my usual post-install songsheet and everything goes smoothly. Using 723MB with a few services already installed. This 'beta' could be the best release of 2018.
BTW Jesse, you omitted hardware used in review.
4 • Yunohost (by tuxUser on 2018-08-20 01:41:34 GMT from Canada)
I have also tested this promising system. I am a regular server user. Cpanel, Webmin etc ... Yunohost saves us a lot of time. On the forum there is a lot of problem with the DNS. The tutorial on the website is not bad but it gets lost in explanation.
If you have your own domain name with a registrar. The problems begin my friend. We can not give an ip address like this: 22.214.171.124 (dns target) at our registrar domain name.
You must specify a server name like this:
Yunohost is easy to use but they have to work Wiki with clear explanations with screenshoot or small video by function type. Not one
45 minutes video. But 1 minutes. Clear, Simple, Direct how to on screen.
I tested all the server distributions. Although they all want to be Lambba user oriented, I can tell you that none succeed. You must have the knowledge to install, use and especially maintain a security server at home.
In conclusion: Great Work!
5 • Hardware (by Jesse on 2018-08-20 01:53:03 GMT from Canada)
@3: I didn't run YunoHost on any physical hardware for this review, it was done entirely in VirtualBox as I wasn't testing compatibility, just features. Though YunoHost should run on any hardware Debian works with, including some single-board computers.
6 • limiting a process (by MikeOh Shark on 2018-08-20 02:21:00 GMT from Turkey)
In Mint 13 I noticed that when the updater ran my system would become nonresponsive for a minute or two. It was annoying. I added
taskset -cp 2,3 $(pgrep mintUpdate)
renice -n 19 $(pgrep mintUpdate)
to my startup and the problem went away. In Mint 19 I tried the same BUT now mintUpdate starts checkAPT.py. How do I make sure a process started by another uses the same niceness?
7 • Family of nice (by Jesse on 2018-08-20 02:38:58 GMT from Canada)
@6: "How do I make sure a process started by another uses the same niceness?"
This happens automatically, you won't need to do anything. Child processes inherit niceness values from their parents. If you assign a program, like your shell, a nice value, it automatically gets passed onto its children.
8 • Linux Kernel 4.19 GPS/GNSS subsystem - Limiting process resources. (by Larry Limitter on 2018-08-20 03:06:37 GMT from Canada)
If new released linux kernel 4.19 supports GPS/GNSS subsystem on low level system bus, some users would like to Limit process resource usage by different means.
9 • Limiting CPU Useage (by penguinx64 on 2018-08-20 03:14:40 GMT from Bahrain)
I don't limit CPU useage. I'm running Mint on a laptop with an AMD quad core A8 processor, 16gb of RAM and an SSD. Most of the time there are plenty of resources available. But sometimes the system bogs down when I run Virtualbox guests. Thanks for these tips. I'll give them a try.
10 • Nice? (by edcoolio on 2018-08-20 04:18:26 GMT from United States)
I do not use the nice command.
I do, however, tend to minimize background processes, stripping my system(s) to the minimum I need for the task at hand.
One thing that I do not like are processes running in the background that will never be used or that are used so little that I prefer to run them as necessary.
Cutting out the bloat in the 'buntu seems like a full time job these days...
11 • Cutting out the bloat in the 'buntu seems like a full time job these days... (by Larry Limitter on 2018-08-20 04:56:07 GMT from Canada)
@ # 10
"Cutting out the bloat in the 'buntu seems like a full time job these days..."
Many lone linux distro brewers might stop brewing and only those who are funded might continue. Many users might walk-away from linux, and many users might dump all tech-tools in the garbage. Seems like end-phase has already begun.
Do not get surprised if you can not find many incl. myself very frequent here.
12 • Resources limiting (by zykoda on 2018-08-20 07:05:08 GMT from United Kingdom)
With 8GB RAM, 4 CPU cores, SSDs, Gigabit LAN and 350 Megabit WAN systems are faster today. Limiting resource usage is a rare necessity. GRUB2 os_prober is a slowdown with multi-boot. I see core under-use (<30%) most of the time. Competing processes from several users is where resource limiting is useful.
13 • Debian and offshoots (by OstroL on 2018-08-20 09:28:04 GMT from Poland)
Well, at least a review of Debian based distro is here today at DW,, even though it is quite an unknown one. It would've been much nicer, if there had been a feature story on Debian and its footprint our new history for last 25 years. The review of this unknown distro shows how embedded Debia is in our environment.
14 • unnecessary background processes (by cykodrone on 2018-08-20 13:28:03 GMT from Canada)
Never used 'nice', nice to know (pun intended), but do shut off useless processes via other methods, CL and otherwise (I am NOT a systemd user). A kajillion background processes reminds of a certain monopoly OS, where I got in the habit of hunting down and making sure things that don't need to be running won't start at boot. The great irony, that hand-holding OS (actually very buggy, complicated, and Swiss cheese security wise) turned me in to an uber geek, go figure, at least it was good for something. :)
Here is a good example, I don't own or use any bluetooth devices, but yet almost every OS I have tested or used insists on enabling it at boot. I get the 'just in case' mentality, just sayin'.
15 • Happy Belated Birthday Debian (by cykodrone on 2018-08-20 13:34:59 GMT from Canada)
Sir Ian Murdock is one of my many FOSS heroes, second only to Linus, but I can assure you, he is spinning in his grave because Debian is now infested with and beholden to buggy bloat written by a corporation. Blasphemy. Democratic distro my rear.
16 • @18, Time traveling (by Angel on 2018-08-20 13:40:45 GMT from Philippines)
There are several degrees of paranoia among internet users. Some don't wish to be followed or located at all. It's a bit of extra bother, but to each his own. For example: I was on Distrowatch two weeks ago, and someone posted a link to an SSD card holder from China. I clicked on the link. Next day, as I was reading Yahoo news, an ad for those very same card holders appeared. Some people may be spooked by that. Me, I don't mind. Makes my Google searches more tailored and productive, among other things. Not that the spooky followers are as good as some think. Some Chinese company keeps trying to sell me giant rock crushers, earth movers and cranes. How they got the idea I need them or would have a use for them, I don't know. In any case, when I want to go private, I con do it as well as anyone else.
17 • @20 (by OstroL on 2018-08-20 14:43:21 GMT from Poland)
"Some Chinese company keeps trying to sell me giant rock crushers, earth movers and cranes."
Well, they've already sold you a laptop, don't they? Even if your mobile is an iPhone, it is also made in China, even if they say, it had been designed in the US. The Chinese are very hard working, effective people. I've been there. What a country!
18 • Linux on a usb stick. (by willi-amp. on 2018-08-20 15:12:38 GMT from United Kingdom)
Two weeks ago 'Comments' item 4, by Bob. He wrote, ‘MX linux is amazing on a USB. I put it on a USB and installed it to a 16G USB’. I’m just a linux user, not that clever, but by following Bobs simple instructions I successfully made a stand-alone USB stick installation. If only all instructions were as succinct and that easy to follow. Thanks Bob,.and thanks MX.
19 • Nice reminder (by Norm on 2018-08-20 15:40:33 GMT from United States)
Thanks for the nice writeup and notes on CPU limit functions.
Last time I used nice was in 1991 on a Unix machine. I wounder if that means I am old and mean?
In any case; it is a great function, if you are running FE models, and want to do something else while it churns in the background.
Thanks again for the nice reminder!
20 • used cpulimit for ffmpeg on vps (by dmacleo on 2018-08-20 17:12:11 GMT from United States)
was playing around running clipbucket on vps with all vid conversions (1080,720,etc) working using ffmpeg.
so had to limit process somehow, set up bash cmd that ran cpulimit (set process ffmpeg to 60%) by cron every minute.
seemed to work better than nice did for this issue, vps host said never crossed any TOS/usage limits.
21 • Limiting resource usage (by AboTaha on 2018-08-20 20:11:25 GMT from Saudi Arabia)
Many thanks for the very informative article about Limiting resource usage.
22 • Cpulimit (by Tim on 2018-08-20 21:57:21 GMT from United States)
This was a really good article on limited resource usage, I thank you for it.
I used to use cpulimit quite a bit when encoding video. I had an old 32 bit Compaq laptop and if you just let it go while doing that it ran so hot you could smell it. I always found it useful to use with the Top command and the PID. I haven’t needed it on any of my machines in the last 3 or 4 years.
23 • OS/2 reliability (by qweo on 2018-08-21 02:09:04 GMT from Russia)
OS2_user, did you use HPFS then, JFS or, perchance, FAT?
24 • About limiting resources (by SA on 2018-08-21 08:30:45 GMT from France)
A tool that is useful in some cases: cpufrequtils
It has two commands: cpufreq-set (to run with sudo) and cpufreq-info (as normal user)
With this you can set up either a fixed frequency, either a range of frequency for your processors.
(and each core can have a different frequency "setting")
I have put it in the crontab (with "@reboot") for a laptop that did have too much 'heat'. (in summer)
25 • Deepin 15.7 (by OstroL on 2018-08-21 22:00:14 GMT from Poland)
The newly released Deepin 15.7 has brought down the idle memory usage to around 830MB from 1.1 GB of Deepin 15.6, a massive jump for a point release. I have found that Ubuntu based on Deepin DE would idle at 660MB! Both screenshots are available in another website writing about Ubuntu, one screenshot today, and the other with Ubuntu base 2 months ago.
Deepin was originally based on Ubuntu, but moved to Debian Sid, which was a smart move by Deepin. Ubuntu too is based on Debian Sid, somewhat cranked to not to suit the normal Debian Sid.
I've been using both, standard Deepin and Deepin DE on Ubuntu base for quite a while, both working without a hitch. While Cannonical doesn't appear to have developers, Deepin seems to have a lot of dedicated developers, and it shows; by comparing the default releases of both. Most probably, Ubuntu Kylin must be more popular than Ubuntu default with Gnome shell. Ubuntu default with Gnome shell is quite bug ridden.
Don't have to believe me, just try out the new Deepin 15.7 for a check. It can be downloaded from a fast server in most European countries and the US and SA.
26 • k3b, brasero, xfburn, etc. (by Stone on 2018-08-21 22:17:57 GMT from United States)
I have tested all 3 mention dvd burners and none of them works.
It seems counterproductive to limit accidentally or otherwise the ways to record isos.
example: Sudo dd, unetbootin, etc do not work for all the Linux distros,the only sure way there was before was burning to a disk, now we are scrambling trying to record an iso for installation.
Please somebody correct the problems with dvd burners otherwise Linux will be used by only the ones that make the different distros.
27 • Burning dvds (by Tim on 2018-08-22 01:56:15 GMT from United States)
On what distro are you having trouble? Brasero works great for me on Ubuntu Mate 18.04.1.
Occasionally on certain distros I’ve had trouble with it, but in those cases K3b always worked.
28 • @26 DVD burning in Linux (by cykodrone on 2018-08-22 10:35:21 GMT from Canada)
I prefer Xfburn, I reduce the burning speed on purpose (half of the drive's max burn speed is my basic rule of thumb, 16x burner=8x burn setting), not only does that make for a better bug free burn, it makes less 'coasters'. There must be something wrong with your burner or setup, possibly very proprietary hardware, because I have been building generic PCs for years and rarely had a problem burning anything. K3b is good, but it drags in the rest of the KDE DE if you try to install it, I dumped KDE years ago because of over-engineering bloat, no thanks. Brasero was always the most flaky, worked OK but would try to burn at the most insane fastest speed possible, doesn't allow burn speed throttling. Slower burning is a must for OS ISOs, you don't want even the tiniest of errors.
I have also used various tools, methods and means of 'installing' or copying live or installer distros to USB sticks, don't remember ever having a problem with that either, granted formatting and permission issues could be tricky for some people, live and learn.
You definitely sound frustrated, but FUD is never the answer, I find research and trial and error works for me. :)
29 • @26 (by kc1di on 2018-08-22 10:50:11 GMT from United States)
I also use xfburn from most of my dvd burning, it's fairly light weight and has always burned everything I've thrown at it. Never like Baerso or K3b that much.
for usb burning try Etcher found at https://etcher.io works well and is appimage so no need to install it.
good luck in your search.
30 • Late answer (by frisbee on 2018-08-22 11:20:55 GMT from Switzerland)
From: DistroWatch Weekly, Issue 776, 13 August 2018
37 • Linux file system (by Carney3 on 2018-08-13 19:15:54 GMT from United States)
"... I'm much more interested in Linux finally getting what Windows and MacOS have had for decades: information about date/time CREATED as well as date/time modified. ... It's IRRELEVANT if YOU don't see the need to find or sort by date created ..."
Linux offers three timestamps for files: time of last access of contents (atime), time of last modification of contents (mtime), and time of last modification of the inode (metadata, ctime).
date/time modified you get as an output of stat command.
Executing stat command shows us that date/time created is supported but, on ext4 fs it is empty. Noticed the empty field "Birth time"?
This missing timestamp you can find out by executing a couple of commands.
First, you need to find the mountpoint for the file or directory, which you need to find out the inode number of the file:
df --output=source /path/to/file/example.txt
Next, you lookup for the inode number:
stat -c %i /path/to/file/example.txt
(This is some example number and yours will be different.)
At the end, command debugfs will give you date/time CREATED.
Syntax of debugfs is:
debugfs -R 'stat ' DEVICE
So, to get the creation time for our file, you simply execute:
debugfs -R 'stat ' /dev/sda1
debugfs 1.42.13 (17-May-2015)
One could also make a script to automate it and combine it together with sort to output a sorted list in a file.
31 • @30 (by edcoolio on 2018-08-22 12:36:53 GMT from United States)
Although your effort is greatly appreciated, and in a pinch it will be very useful, it seems a bit complicated compared to just clicking on "Date Created" in Windows 10.
32 • @31 (by frisbee on 2018-08-22 14:14:22 GMT from Switzerland)
Don't mind your "Just sayin'" but ...
This is where the discussions about sense and nonsense starts.
Timestamps are very complex topic and a very unreliable thing.
Timestamps are depending on file systems, on protocols and on applications (== metadata).
Imagine a file "example.pdf" creadted on January, 1st 2015 modified on January, 1st 2016 and last accessed on on January, 1st 2017 and imagine a folder A and folder B.
When your document was created? On January, 1st 2015, right?
Now, copy that file from folder A into the folder B. How old is it now? August, 22nd 2018.
If you go and check properties in Adobe Acrobat reader, it will still say January, 1st 2015. ;)
Can one file have two "Birthdays"? Was it created when it was actually created or was it created in a moment when it was written to your HD? If first, timestamps would have to stay preserved but, same time, they would be wrong because the file was actually created later, when you copied it. So, it would have to have two date/time created's -- the time first ever created and the one when it got localy created.
Usually, in practice you would download a file from Internet. To help forensics (== spying), Microsoft for example writes hidden datastreams, so you can reliably say when and from where one file was downloaded, even if you later copy it and the creation date changes or if it has completely different creation time.
The way I showed you is the most reliable way and how you do it if you are into forensics and you do it that way under Mac, Windows and Unix, incl. Linux. All other ways (right click/properties) are not reliable.
Please have a look at the following example here: https://ibb.co/eHr6ce
Birth (Erstellt): May, 16th 2016
Change/Modify (Geändert): December, 7th 2015
Access (Letzter Zugriff): May, 26 2016
Here we have two problems:
1. The file was changed/modified half a year BEFORE it was created. ;)
2. Last accessed time was August, 22nd 2018, NOT 2016.
Edge Browser under Windows 10 "forgot" to write a new timestamp when it accessed the file.
So, it's more something like: "It's IRRELEVANT if YOU don't see the need to find or sort by date created; what's relevant is that Windows and Mac users CAN'T have taken for granted for decades the ability to do so if they chose BECAUSE THEY'LL GET MISINFORMED."
33 • Response to @26 about dvd burners. (by Stone on 2018-08-22 23:21:23 GMT from United States)
Mr @26 I read your post and at the same read a lot of comments of people having the same problems with dvd burning in linux; My computer is less than 3 years old, with lots (8g) memory, I started with Ubuntu in 2004 but Ubuntu did some radical changes around 2010 and i did not work for me. Switched to L. mint, then L. LITE, etc, that is to tell you I am not an expert neither a beginner.
I have tried dvd burners in different computers, newer laptops and desktops with the same results, did that before posting my problems.
I tried ETCHER for about 3 months and I like it.
The problem started about 4 months ago and gotten worse with an update to k3b, xfburn, brasero.
Apparently you are one of the lucky ones "congrats" but I am not as a lot of users like me.
34 • Distros (by Tim on 2018-08-22 23:59:57 GMT from United States)
I am sorry you’re having trouble, but you haven’t answered my question. What distro are you having this trouble on?
35 • Response to @33 about Linux distro being used. (by Stone on 2018-08-23 00:17:19 GMT from United States)
Mr @33 I am sorry initially missed your post.
I am using mainly two distros now: L. Mint and L. lite but during last 4 months several others.
This is the best answer I can give you.
If there is a way to send you the debugging from k3b and brasero let me know and gladly will.
36 • Sorry (by Tim on 2018-08-23 01:25:04 GMT from United States)
This was the only thing I could find that seemed like it could be helpful. Seems to be a wodim problem affecting multiple burners.
I hope it helps! If not I think if you ask a question on the Mint or Ubuntu forums they might be a better place and can get you more help (and make it easier for everyone having the issue to find it.) Good luck!
If you get too fed up Ubuntu Mate 18.04 is a great distro and I’ve had good luck burning with it.
37 • @32 (by edcoolio on 2018-08-23 01:41:29 GMT from United States)
You are, of course, correct.
I suppose I was just lamenting the fact that, forensics aside, it would be nice to have a simple and quick function when working with straightforward documents. I believe that from the standpoint of usability for an end-user, it would be a huge plus to ease linux adoption.
Is anyone up for writing an kernel API to simplify things?
I suppose we could really throw a monkey-wrench in things and begin to discuss the use and possible abuse of the 'touch' command...
Either way, I enjoyed your take on the issue(s) and the information.
38 • Respomse to @36 (Tim) about dvd Burners. (by Stone on 2018-08-23 01:42:00 GMT from United States)
Mr @ 36 (Tim)
I appreciate your advice about ubuntu mate 18.04 and will follow your advise, will download it and try it, it is a shame to have to abandon a good distro because of dvd burning.
I do hope somebody payed attention to this and correct the problem.
We at Linux use and love it, ussualy is very well designed and capable,
Updates do not require hours to install during which no one can use the computer. Nowadays Linux has improved a lot from the almost begining
I remember in 2004 one had to go looking for players and how to install them, codecs also.
Mr @36 thank you for your time and advise and will do.
39 • Response to @32 by edcoolio (by frisbee on 2018-08-23 05:23:03 GMT from Switzerland)
"... it would be nice to have a simple and quick function when working with straightforward documents. ... Is anyone up for writing an kernel API to simplify things?"
No need for writing anything new, its all there just not implemented.
Today, my answer shall be a couple of citations.
"For a long time, Linux hasn't bothered with file creation dates because none of the file systems it commonly used supported them."
Today we have couple, ext4 among them. Anybody can install xstat without much hassle. Or simply use ZFS.
"That birth time is rarely useful. It's not the age of the data in the file (data is written to files after they have been created), nor necessarily the time the file appeared by that name in a directory (it could have been created as a different name and renamed or linked there and the content or attributes been changed several times in between)."
"The struct xstat structure resembles struct stat, but with some differences. It includes fields for file metadata like the creation time, the inode "generation number," and the "data version number" for filesystems which support this information, and it has a version number to provide for changes in the system call API in the future."
"This worries me, the updated version returns different data depending on the underlying filesytem. This will surely lead to breakage when someone gets that one wrong. The result should include the filesystem where the file lives somehow."
You noticed "metadata" and "for filesystems which support this information" ... this is allready the first problem. Linux would have to limit itself by not supporting some file systems any more. Not to forget, applications would also have to be able to handle it and of course the protocols.
Depending on your DE, metadata can be kept or ignored (== destroyed) when working with smb for example.
So yeah, quiet complex topic.
If you are interested in it, here some more discussions/information/sources:
40 • @Stone #s 26, 33, 35, 38: (by dragonmouth on 2018-08-23 13:05:25 GMT from United States)
I have been using k3b regularly and Brasero intermittently on various Linux distros to burn ISOs for over 10 years with very few problems. Both Brasero and k3b have performed flawlessly. I may not like some of their features and look-and-feel but that is an another discussion. Any problems that I have had burning ISOs were caused by bad file downloads, cheaply made DVD disks or DVD drive failures. The DVD drive failures are understandable since I use drives pulled from discarded PCs so some may be in questionable condition.
Since none of k3b, Brasero, xfburn or dd work for you, I would suggest that your problems are be due to the hardware you use and/or the way you have it set up.
BTW - even though Ubuntu, Mint and Lite are considered to be separate distros, they are all Ubuntu-based and therefore basically the same distro. Have you tried any distros based on Fedora, Slackware, Arch or Mageia?
41 • @28 • Brasero DVD burning in Linux (by cykodrone) (by Ted H in Minnesota on 2018-08-23 14:56:00 GMT from United States)
"Brasero...doesn't allow burn speed throttling."
Yes it does, click on the button box "Properties" and you can choose your burn speed.
I also burn at about half of the possible burn speed for the same reason you do.
42 • @Stone regarding Optical Drive Burning (by Rev_Don on 2018-08-23 16:47:35 GMT from United States)
I tend to agree with dragonmouth in comment 40. Hardware issues including the use of cheap blank disks and corrupted files tend to cause a lot more bad burns than the software used to do the burning. Why don't you post what your hardware specs are (in as much detail as possible) and what blank disks you are using. That will give us some sort of starting point to attempt diagnosing your problem. And don't tell us it's a dual core processor as that tells us absolutely nothing useful. You need to be as specific as possible such as Intel i5-2500 and the brand name and model of the drive and how old it is.
And if you are burning on a laptop make sure it is running on the charger. I've seen a lot of laptops that had problems burning while running on battery power, especially older laptops.
As for burning speed, the speed of the drive is less important than the speed of the disk. One person recommended burning at half of the drives rated speed, but if you try to burn a n 8x rated disk on a 24x rated drive his method would result in burning the disk at 12x, probably below it's reliability factor. Try half of the rated speed of the lowest of the drive and the disk. But for the record I have had much better luck burning at the rated speed of the disk and I burn several hundred disk per year with maybe 2 or 3 failures using that method. At most I will burn at one speed lower than the rated speed of the disk.
43 • Response to Dragonmouth, cykodrone and Rev_Don. (by Stone on 2018-08-23 20:26:41 GMT from United States)
Thank you for the interest in my problem.
The disks am presently using are :
Verbatim dvd+r 16x single layer
Optimum dvd+r 16x single...
Also used Memorex +r 4x single layer
verbatim rw 4x single layer
and none of them ever failed before.
1- Dell Inspiron 15 series 3000, intel i3 (1.9) with 4 gigs mem.
2-Dell inspiron 15 series 3000, intel i3 7 gen with 8 g mem.
3-Desktop proyect in progres and being improved 2 dvd burners
one is a Lite-on.
Op. Sys for # 1:
Kernel Linux 4.4.o-134 generic (x86-64)
Comp #160-Ubuntu smp.
Linux Lite 3.8
Desk env. Xfce-4 The brand name of burner unknown (Dell)
Last night I got a couple of updates and after k3b managed to burn
L Mint mate 19 64b.iso but failed on Ubuntu mate 18.04 desk-amd 64;tried with Brasero and it did. YES i know xfburn is the one that comes with the distribition but when ist started failing I changed to k3b and brasero.
But disregarding specs the fact the problem with dvd burning software started about 4 mo. ago (For me that is) is very strange and that all three computers started failing to burn at the same time.
Supposing I changed a parameter that would be only in one, the other 2 have not been changed. (I do all the dumb stuff in one computer only).
44 • @Stone re: burning (by Rev_Don on 2018-08-24 02:54:25 GMT from United States)
Did all of the problems coincide with the use of 18.04 or a distro based on it? I found 18.04, 18.04.1, Mint 19, and every other distro based on 18.04 to be buggy as all get out. One of the worst releases in the past several years as far as I'm concerned. Just out of curiosity try booting to a recent Knoppix Live USB or anything based on Ubuntu 16.04.x and see if your burning problems go away.
45 • Response to Rev_Don about burner sotw... (by Stone on 2018-08-24 03:21:21 GMT from United States)
You may have hit the problem on the nail head, in one of my computers I had to shop for a distro that worked; tried Solus, Manjaro,etc; ended up for using L. Mint xfce but had to replace kernels until finding one that worked.
I will try to avoid the ubuntu derivatives for a while until corrections are made, I also tried slackware but could not get sudo dd to work on it, my computer kept flaging a major problem and refused to reboot.
Now I think may have to suffer until a new Ubuntu version and derivatives come out.
I will try knoppix and let you know.
Thank you Rev_Don.
46 • Mr Rev_Don about knoppix. (by Stone on 2018-08-24 03:29:21 GMT from United States)
Sorry but knoppix is not a go, my internet is not too fast and knoppix is 4.4G.
Apreciate the thought.
47 • Old dvds (by Tim on 2018-08-24 12:42:15 GMT from United States)
Do you have any old DVDs lying around from a distro based on 14.04 or 16.04?
If you go back to an old OS that worked for you and it still works, you know it’s Ubuntu 18.04 and your hardware not being compatible. You could try openSuse or Manjaro.
If not, then you know it’s the hardware going bad
48 • @Stone re: burning (by Rev_Don on 2018-08-24 14:34:21 GMT from United States)
Yeah, Knoppix can be a lot to download if you have a slower connection or data cap. I'm lucky to have a 50 meg download connection with no data cap.
49 • Live USB/DVD burner (by Gary on 2018-08-25 00:59:45 GMT from United States)
Am running PeachOS on an old generic desktop. (dual 3.06 64 bit intell processor) Enjoy checking out new distos and installing them on either my or others computer. Usually since I right click on the ISO image, open with, disk image writer, and specify the disc to write to. Haven't had any problems.
50 • @41 Re Brasero burn speed, etc (by cykodrone on 2018-08-25 02:14:02 GMT from Canada)
You are right, you can 'attempt' to throttle the speed in Brasero, but it always ignored the throttling for ME.
Re half burn speed, I meant half the disk's rated max speed, I have a 16x burner and use 16x disks, everybody has to do their own math. After years of burning and experimenting, it's MY fail-safe setting, makes a perfect burn, every time, movies, tv shows, OS ISOs, etc.
Re Verbatim disks, I used to love them but started noticing problems with them (especially their DVD+Rs), I also switched back to DVD-Rs, far more compatible with my home DVD player, etc. Even discount DVD-Rs burn problem free for me. The feature difference between DVD-Rs and +Rs is negligible.
Are your BIOSes UEFI? Have you poked around the settings? Sounds like the optical drives are no longer communicating with the kernel and the machine properly. Don't UEFI BIOSes require all that 'signed' nonsense? I have mine set to legacy (non UEFI), I'm old school like that.
Everybody's setup/situation is different, you have to find what works for you. Like one person suggested, try an older distro/kernel version and see what happens, try a live copy-to-ram distro like PCLOS Xfce, eject the live disk and try a burn. My machine hated the 4.4 kernel series, loves the versions below and above, I tend to run the highest LTS available, was glad to see the back of the 4.4 series.
51 • response ro Rev_Don (by Stone on 2018-08-25 03:15:26 GMT from United States)
I am already looking for a faster speed but it makes me itch just to think of the prices isp are asking.
Nice talking to you Mr Rev_Don I got Absolute64-15ob.iso which is supposed to be based on Slackware and as soon as I find out how to put it in usb stick will try.
52 • @50 re: Verbatum disks (by Rev_Don on 2018-08-25 04:01:37 GMT from United States)
The old Mitsubishi manufactured Verbatum with AZO dye disks were some of the best ever produced. When Mitsubishi outsourced the manufacture of them to outside sources the quality slipped dramatically with some being worse than Memorex, house brands, and other junk disks.
Right now the good brands are CMC Pro Powered by TY (CMC purchased the rights and technology to ajvc/Taiyo Yuden in 2015 when they decided to get out of the business) and Falcon Media. Everything else manufactured today is junk at best. If you have or can find the older (and now out of production) AZO Dye Verbatums they perform on par with the CMC Pro TY's and Falcons, but they are getting harder and harder to find.
As far as DVD +R vs -R that depends more on the specific drive as to which works best. Some of mine prefer +R and some -R. I keep a supply of each and use whichever one the specific drive prefers.
53 • Mr Rev_Don /about disks. (by Stone on 2018-08-25 09:16:53 GMT from United States)
It seems that about dvd disks I am a lot out of the loop, will get some cmc's and try them.
54 • Burning / Media etc. (by Winchester on 2018-08-25 12:57:48 GMT from United States)
First,I use PClinuxOS for most of my multimedia tasks,including disc burning with K3B.
Just yesterday,I burned (successfully) a Voyager Linux Debian Version .iso to a DVD+R using PClinuxOS and K3B. I actually can't remember it ever failing.
Sometimes,I use "xfburn" through Void Linux XFCE or "pBurn" from the Puppy Linux family. pBurn is also available in Gentoo.
As far as blank media discs go, CMC is good but,archival grade discs from MAM-A or JVC are even better. Here's the link : * http://www.mam-a.com/ *
For burning Slackware-based .iso's to USB,I have found that I actually need to use the "Rufus" software under Windows. That's one of the extremely rare tasks (probably can count them on one hand) when I find that I need to use Windows. Fire-up a secondary computer with a Windows installation on a partition and start-up "Rufus" ...... only for Slackware-based .iso's. Alternatively,they could be burned to a blank Optical Disc under Linux.
There are a few USB .iso burning tools for Linux which work great for everything EXCEPT the Slackware family. SUSE Studio Image Writer. Fedora Media Writer (also lets you select non-Fedora .iso's). Etcher. ROSA Media Writer. The Gnome "Disks" Utility >>>> "Restore Image".
55 • L1 Terminal Fault attack (Foreshadow) (by cykodrone on 2018-08-25 18:55:28 GMT from Canada)
I ran (as root) [code]cat /sys/devices/system/cpu/vulnerabilities/l1tf[/code] and got "Not affected", thank you AMD. :)
56 • @54 Re: Blank Disks (by Rev_Don on 2018-08-25 21:07:22 GMT from United States)
JVC hasn't made disks since 2008 when they sold their Media Division to Taiyo Yuden which then sold it to CMC in 2015. Any JVC disks available now would be at least 10 years old. See the linked article for more information on this.
57 • Writing images to USB (by Barnabyh on 2018-08-26 02:32:48 GMT from United States)
Why don't you just use the dd command in the terminal to transfer images to USB key? Works every time, even for Slackware ;) .
58 • @26 • k3b, brasero, xfburn, etc. (by Stone) (by frisbee on 2018-08-26 11:11:17 GMT from Switzerland)
„I have tested all 3 mentiond dvd burners and none of them works.“
I have tested all 3 mentiond dvd burners and ALL of them work.
Sudo dd also works.
You could install Jorg Schilling's cdrecord from Brandon Snider's PPA. This has often solved odd burning problems for many.
First add the repository:
sudo add-apt-repository ppa:brandonsnider/cdrtools
Then find the appropriate device address for your DVD drive by running:
Finally run a commandline like the following (your own device address will be different):
cdrecord -v dev=0,0,0 -speed 8 driveropts=burnfree fs=32m -eject my_distro.iso
A modern cdrecord has no issues with either CD or DVD burning, or Bluray for that matter...
However, before burning a DVD or write USB, I would strongly suggest you to red How-To on distribusions Website.
The burning/writing problems usualy are not a problem of your SW or HW but have more to do with how the.iso was prepared.
59 • Response to Winchester, barnabyh and frisbee. (by Stone on 2018-08-26 17:37:37 GMT from United States)
It seems i got a goldmine of info with all of you.
As for using Windows and Rufus I got rid of Windows completely, any new computer first thing is to erase Windows and the stupid uefi so Legacy is the word. (you must have seen how many partitions uefi creates in the hard drive and some are really hard to erase)
As to disks brands, I live in California and first time I heard about them.
Regarding Slackware and derivatives you are right I get a lot of trouble putting it to disk, the software flags "this is not an iso".
Mr Winchester in 15 years or so of using different Linux versions this the first time I got this kind of trouble, I have tried redownloading, rebooting,
changing speeds, dedicating more memory to burning software, friends computers, etc and still the problem persists.
I think will stop thinking about this for a while and then hit it again;f it does not work I will do the sensible (coward) thing and leave Ubuntu derivatives for a while.
60 • LINUX : CD and DVD BURNING (by C D McBURN on 2018-08-26 20:45:32 GMT from Canada)
For myself, k3b (PCLOS) just works fine all the times. but, last cd/dvd was burnt a long long ago.
Brasero and Xfburn also worked for me, but, also produced tea-coaster once in a while.
As already said in # 58 by frisbee
You could install Jorg Schilling's cdrecord.
Then find the appropriate device address for your DVD drive by running:
Finally run a commandline like the following (your own device address will be different):
cdrecord -v dev=0,0,0 -speed 8 driveropts=burnfree fs=32m -eject my_distro.iso
A modern cdrecord has no issues with either CD or DVD burning, or Bluray for that matter...
Once in a while, I use cdrecord as under:
linuxmint@user#> cdrecord -v -dao speed=4 dev=/dev/dvd /path/to/linuxmint-19-cinnamon-64bit-v2.iso
-v - turns on verbose mode.
-dao - puts us in Disc At Once mode and finalise the disc.
speed=4 - I keep the burning speed down as it is more likely to burn properly and not fail. You can experiment with higher speeds if you want,
dev=/dev/dvd - this is the device node for your DVD drive. It's usually safe to put /dev/dvd here, but if that doesn't work, you may need to use /dev/cdrom or something else.
according to cdrecord --scanbus --> my burner located at dev=0,0,0
Finally, I specify the path to the ISO image I want to burn.
in my case, /usr/home/downloads/linuxmint-19-cinnamon-64bit-v2.iso
ArchWiki and GentooWiki has very useful information for Linux New Bees.
61 • 16.04 (by Tim on 2018-08-26 22:42:44 GMT from United States)
Keep in mind too that if a 16.04 derivative worked for you (I loved Mint Mate Serena 17.1) you can go back to it through 2021.
Number of Comments: 61
Display mode: DWW Only • Comments Only • Both DWW and Comments
|• Issue 832 (2019-09-16): BlackWeb 1.2, checking for Wayland session and applications, Fedora to use nftables in firewalld, OpenBSD disables DoH in Firefox|
|• Issue 831 (2019-09-09): Adélie Linux 1.0 beta, using ffmpeg, awk and renice, Mint and elementary improvements, PureOS and Manjaro updates|
|• Issue 930 (2019-09-02): deepin 15.11, working with AppArmor profiles, elementary OS gets new greeter, exFAT support coming to Linux kernel|
|• Issue 829 (2019-08-26): EndeavourOS 2019.07.15, Drauger OS 7.4.1, finding the licenses of kernel modules, NetBSD gets Wayland application, GhostBSD changes base repo|
|• Issue 828 (2019-08-19): AcademiX 2.2, concerns with non-free firmware, UBports working on Unity8, Fedora unveils new EPEL channel, FreeBSD phasing out GCC|
|• Issue 827 (2019-08-12): Q4OS, finding files on the disk, Ubuntu works on ZFS, Haiku improves performance, OSDisc shutting down|
|• Issue 826 (2019-08-05): Quick looks at Resilient, PrimeOS, and BlueLight, flagship distros for desktops,Manjaro introduces new package manager|
|• Issue 825 (2019-07-29): Endless OS 3.6, UBports 16.04, gNewSense maintainer stepping down, Fedora developrs discuss optimizations, Project Trident launches stable branch|
|• Issue 824 (2019-07-22): Hexagon OS 1.0, Mageia publishes updated media, Fedora unveils Fedora CoreOS, managing disk usage with quotas|
|• Issue 823 (2019-07-15): Debian 10, finding 32-bit packages on a 64-bit system, Will Cooke discusses Ubuntu's desktop, IBM finalizes purchase of Red Hat|
|• Issue 822 (2019-07-08): Mageia 7, running development branches of distros, Mint team considers Snap, UBports to address Google account access|
|• Issue 821 (2019-07-01): OpenMandriva 4.0, Ubuntu's plan for 32-bit packages, Fedora Workstation improvements, DragonFly BSD's smaller kernel memory|
|• Issue 820 (2019-06-24): Clear Linux and Guix System 1.0.1, running Android applications using Anbox, Zorin partners with Star Labs, Red Hat explains networking bug, Ubuntu considers no longer updating 32-bit packages|
|• Issue 819 (2019-06-17): OS108 and Venom, renaming multiple files, checking live USB integrity, working with Fedora's Modularity, Ubuntu replacing Chromium package with snap|
|• Issue 818 (2019-06-10): openSUSE 15.1, improving boot times, FreeBSD's status report, DragonFly BSD reduces install media size|
|• Issue 817 (2019-06-03): Manjaro 18.0.4, Ubuntu Security Podcast, new Linux laptops from Dell and System76, Entroware Apollo|
|• Issue 816 (2019-05-27): Red Hat Enterprise Linux 8.0, creating firewall rules, Antergos shuts down, Matthew Miller answers questions about Fedora|
|• Issue 815 (2019-05-20): Sabayon 19.03, Clear Linux's developer features, Red Hat explains MDS flaws, an overview of mobile distro options|
|• Issue 814 (2019-05-13): Fedora 30, distributions publish Firefox fixes, CentOS publishes roadmap to 8.0, Debian plans to use Wayland by default|
|• Issue 813 (2019-05-06): ROSA R11, MX seeks help with systemd-shim, FreeBSD tests unified package management, interview with Gael Duval|
|• Issue 812 (2019-04-29): Ubuntu MATE 19.04, setting up a SOCKS web proxy, Scientific Linux discontinued, Red Hat takes over Java LTS support|
|• Issue 811 (2019-04-22): Alpine 3.9.2, rsync examples, Ubuntu working on ZFS support, Debian elects new Project Leader, Obarun releases S6 tools|
|• Issue 810 (2019-04-15): SolydXK 201902, Bedrock Linux 0.7.2, Fedora phasing out Python 2, NetBSD gets virtual machine monitor|
|• Issue 809 (2019-04-08): PCLinuxOS 2019.02, installing Falkon and problems with portable packages, Mint offers daily build previews, Ubuntu speeds up Snap packages|
|• Issue 808 (2019-04-01): Solus 4.0, security benefits and drawbacks to using a live distro, Gentoo gets GNOME ports working without systemd, Redox OS update|
|• Issue 807 (2019-03-25): Pardus 17.5, finding out which user changed a file, new Budgie features, a tool for browsing FreeBSD's sysctl values|
|• Issue 806 (2019-03-18): Kubuntu vs KDE neon, Nitrux's znx, notes on Debian's election, SUSE becomes an independent entity|
|• Issue 805 (2019-03-11): EasyOS 1.0, managing background services, Devuan team debates machine ID file, Ubuntu Studio works to remain an Ubuntu Community Edition|
|• Issue 804 (2019-03-04): Condres OS 19.02, securely erasing hard drives, new UBports devices coming in 2019, Devuan to host first conference|
|• Issue 803 (2019-02-25): Septor 2019, preventing windows from stealing focus, NetBSD and Nitrux experiment with virtual machines, pfSense upgrading to FreeBSD 12 base|
|• Issue 802 (2019-02-18): Slontoo 18.07.1, NetBSD tests newer compiler, Fedora packaging Deepin desktop, changes in Ubuntu Studio|
|• Issue 801 (2019-02-11): Project Trident 18.12, the meaning of status symbols in top, FreeBSD Foundation lists ongoing projects, Plasma Mobile team answers questions|
|• Issue 800 (2019-02-04): FreeNAS 11.2, using Ubuntu Studio software as an add-on, Nitrux developing znx, matching operating systems to file systems|
|• Issue 799 (2019-01-28): KaOS 2018.12, Linux Basics For Hackers, Debian 10 enters freeze, Ubuntu publishes new version for IoT devices|
|• Issue 798 (2019-01-21): Sculpt OS 18.09, picking a location for swap space, Solus team plans ahead, Fedora trying to get a better user count|
|• Issue 797 (2019-01-14): Reborn OS 2018.11.28, TinyPaw-Linux 1.3, dealing with processes which make the desktop unresponsive, Debian testing Secure Boot support|
|• Issue 796 (2019-01-07): FreeBSD 12.0, Peppermint releases ISO update, picking the best distro of 2018, roundtable interview with Debian, Fedora and elementary developers|
|• Issue 795 (2018-12-24): Running a Pinebook, interview with Bedrock founder, Alpine being ported to RISC-V, Librem 5 dev-kits shipped|
|• Issue 794 (2018-12-17): Void 20181111, avoiding software bloat, improvements to HAMMER2, getting application overview in GNOME Shell|
|• Issue 793 (2018-12-10): openSUSE Tumbleweed, finding non-free packages, Debian migrates to usrmerge, Hyperbola gets FSF approval|
|• Issue 792 (2018-1203): GhostBSD 18.10, when to use swap space, DragonFly BSD's wireless support, Fedora planning to pause development schedule|
|• Issue 791 (2018-11-26): Haiku R1 Beta1, default passwords on live media, Slax and Kodachi update their media, dual booting DragonFly BSD on EFI|
|• Issue 790 (2018-11-19): NetBSD 8.0, Bash tips and short-cuts, Fedora's networking benchmarked with FreeBSD, Ubuntu 18.04 to get ten years of support|
|• Issue 789 (2018-11-12): Fedora 29 Workstation and Silverblue, Haiku recovering from server outage, Fedora turns 15, Debian publishes updated media|
|• Issue 788 (2018-11-05): Clu Linux Live 6.0, examining RAM consumpion, finding support for older CPUs, more Steam support for running Windows games on Linux, update from Solus team|
|• Issue 787 (2018-10-29): Lubuntu 18.10, limiting application access to specific users, Haiku hardware compatibility list, IBM purchasing Red Hat|
|• Issue 786 (2018-10-22): elementary OS 5.0, why init keeps running, DragonFly BSD enables virtual machine memory resizing, KDE neon plans to drop older base|
|• Issue 785 (2018-10-15): Reborn OS 2018.09, Nitrux 1.0.15, swapping hard drives between computers, feren OS tries KDE spin, power savings coming to Linux|
|• Issue 784 (2018-10-08): Hamara 2.1, improving manual pages, UBports gets VoIP app, Fedora testing power saving feature|
|• Issue 783 (2018-10-01): Quirky 8.6, setting up dual booting with Ubuntu and FreeBSD, Lubuntu switching to LXQt, Mint works on performance improvements|
|• Issue 782 (2018-09-24): Bodhi Linux 5.0.0, Elive 3.0.0, Solus publishes ISO refresh, UBports invites feedback, Linux Torvalds plans temporary vacation|
|• Issue 781 (2018-09-17): Linux Mint 3 "Debian Edition", file systems for SSDs, MX makes installing Flatpaks easier, Arch team answers questions, Mageia reaches EOL|
|• Issue 780 (2018-09-10): Netrunner 2018.08 Rolling, Fedora improves language support, how to customize Kali Linux, finding the right video drivers|
|• Full list of all issues|
Star Labs - Laptops built for Linux.
View our range including the Star Lite, Star LabTop and more. Available with a choice of Ubuntu, Linux Mint or Zorin OS pre-installed with many more distributions supported. Visit Star Labs for information, to buy and get support.
|Random Distribution |
Southern California Internet Linux
SCI.Linux was a Linux distribution based on system administration through Webmin, best-in-class desktop applications, Microsoft Office compatibility, VPN connections to Windows, remote desktop to Windows XP, easy dual-boot with Win2K/XP/NT, multimedia applications for CD/DVD plus authoring utilities, spam blocker, complete set of high performance development tools, high performance video, extensive printer and sound card support, LaTeX, cluster software, and more. This distro was aimed at the student/researcher who wants to replace Windows and still interface to the Windows world. Requires a Pentium MMX or better, 256MB or more of RAM, at least 2.5GB of free disk space.