This is the command line I used to run cdrecord. Afterwards, I ran 'cdrecord -media-info' on the same disc and, as a result, I got the messages contained in the file I am adjoining. There, two consecutive warnings can be seen, which I quote:
Quote:
The disk, after recording, however, is both readable by GNU/linux and another O.S. What is the meaning of those warnings and what are its possible implications? I would like to know.
I am just now doing the 'final' few tweeks on my new x86_64 Laptop running multilib-enabled Slackware Current and as part of the process, I installed compat32pkg and ran:
Code:
Next, to test compat32pkg, I ran:
Code:
The compat32pkg script seemed to do the 'right thing', placing the three Slackware Packages in the /var/cache/compat32pkg/compat-32/ directory as it was configured to do:
Code:
Note the warnings about 'etc/gtk-2.0/i486-slackware-linux/im-multipress.conf.new' ...
I realize the information found here is potentially biased, but it made me curious where Fedora stands. Now that even Debian has agreed to distribute the original fork of Cdrtools, is Fedora considering that option? Several other distros are distributing the original fork now, and it's where active development is ongoing.
Still getting the "cdrecord has no permission to open the device" error when trying to burn an iso image to a DVD-RW.
I did yet another clean install of openSUSE 11.2 64 on my desktop computer, did updates, added Nvidia and Packman repos (it's not a repo problem as I tried it several times on a totally clean install), added codecs and stuff as advised by caf.
I updated the DVD drive firmware earlier today.
My user is a member of ALL groups.
Drive is an LG GH22NSS50 (sata)
It all works (with the same DVD-RW) under winxp on the same machine.
Is it HAL or something else that blocks permission to devices?
I'm really getting sick to death of this problem, and would be happy just to get rid of anything blocking permissions to the DVD drive.
I am using Oracle Enterprise Linux version 4 update 7. I would like to create and burn iso images via the terminal. Assume I have a folder called movies in directory /root/Desktop.I would like to create a movie.iso image ans burn it using mkisofs and cdrecord.
I was trying to burn an .iso with K3b a little while ago, and had some problems. First of all, even though I chose 8x to burn my (16x) DVD, it switched to 11x or 12x around halfway through the burning process. There were also some ticking noises that I'm pretty sure were coming from the DVD writer, not terribly loud, but noticeable. This had never happened before. Finally, it got stuck at about 98% (but not frozen, as the time elapsed kept going), and did not finish burning--got an error message (and a bad disc): "cdrecord has no permission to open the device"
I inspected the disc and there was one dark spot (on the dye) about halfway through the disc, very thin and couple of millimeters long. (This was present only after burning). I'm using Ubuntu 10.04, K3b version 1.91.0, Lite-On DVDRW SHW-160P6S
I tried to burn with k3b but after a while the fateful message "cdrecord has no permission to write to the device. " Then I launched k3bsetup and I selected the burning group. Did not exist. I created it and now i'm included in it. Then I checked all the boxes for the write permissions of the programs used by k3b and the writer. Now it works. But after reboot, the box of the burner device is not checked. So I have to select it each time. Boring. DO you know how to save the setting permanently
I've been trying to understand issues that occur during a uClinux distribution build (so I can include such issues in a module I'm writing for students). My process has been to work through errors that occur due to missing packages, then remove the distribution and build it again to uncover what happens.One thing I notice is different sets of warnings within each iteration of making a new build. From the document here (URl...it states, "A typical warning involves a variable being used before its value has been set."
So my question: is there a way to verify that the issue throwing the warning has been resolved by the end of the make build?And, is running make build again an option or could this cause problems within the build directories or image?
You should be running a firewall. I would also periodically check for rootkits with rkhunter and chkrootkit. Antivirus is usually optional, but it depends on your network ... if you have Window$ machines, do use clamav or something.Hope I'm not distorting the thread but just ran rkhunter and got a lot of red warnings, especially worrying seems:
Im currently installing debian on my old server, its a 64bit computer, so i've downloaded the amd64 for this project. But under the Basis Installation, of this cd image, im getting a debootstrap warning every time i want to continue the installation, the last warning i remember was something coreutils_6.10-6_amd64.deb (Something like that, not totaly sure), and im lost, can't find anything closely related to the subject.
When I start up my computer I always get the Akonadi message window with some errors. If I just close it, launch "akonadi configuration" and ask for a test, some of the errors have already disappeared. It looks like the first test is made too soon, before everything is running. It's not a big issue but I would like to get rid of the akonadi warnings window. Does anybody know how?
Every time I run "apt-get" or "apt-get autoremove" terminal-commands lately, I see this:
Code:
Do you want to continue [Y/n]? y (Reading database ... dpkg: warning: files list file for package `mythtv-theme-metallurgy' missing, assuming package has no files currently installed. (Reading database ... 10%
I've made a CentOS 5 x86_64 setup last year, around november/december.This system is supposed to operate as a home router/gateway, firewall, nas, small intranet/extranet server and media center.I've previously built a system using older parts (Pentium III 866MHz), and had on it CentOS 5 x86.It successfully served the same purpose (except nas and media center) for quite some time, about 1-2years, until i felt i needed better hardware (more memory, speed and disk space mainly) and 64-bit support.
Part of this intended setup isn't finished (router/gateway, firewall, media center), partially because i'm still lacking a good 1000mbps switch and a supported wireless n 3-antenna card in AP/server mode.In the previous setup, i had router/gateway, firewall and small intranet/extranet server working, with a crappy 100mbps switch (the switch is broken now).the new setup has run pretty well, it had been upgraded 2 times, etc...But since it has been installed, even before any updates, upgrades or repo additions, there has been always warnings/errors during kernel boot.I'm listing my specs, configs, versions and logs bellow. all the partitions, RAID and LVM were created during CentOS initial setup.
I'm trying to install uzbl and was following the step by step guide on this page http://xanderboy.esdebian.org/36949/uzb ... orts-flash When i run make i get a lot of errors and warnings. Can anybody point out what I'm doing wrong?
I've just bought a Linksys WRT610N router and I ran through various problems during the configuration, that brought some questions.Here is what I did to configure it (following the short manual that I got with the router)1. plugged the router in my modem and in my computer via ethernet cables2. entered its IP address (given on the manual) on my browser and logged in with the factory login3. changed the login passwordAfter this the problems that I have encountered are that:I set up the administration of the router to be disabled via wireless and enabled locally via https, but when saving those settings I either lost the connection (the browser telling me the server was not accessible) or asked confirm a security certificate after being (logically) redirected to the https version of the administration pageafter trying to loggin again, I wasn't able to login via https but only via http even if after logging those parameters were still as I set them (wireless administrative login disabled and local administrative login enabled only via https)
via https when getting something else than "the server is not responding or could be too busy", I was prompted the untrusted connection site, saying that"192.168.1.1 uses an invalid security certificate.The certificate is not trusted because it is self-signed.The certificate is only valid for Linksys.The certificate expired on 01/01/71 01:21. The current time is 19/04/11 22:56.(Error code:sec_error_expired_issuer_certificate)"I noticed that after loosing the connection and not being able to reach the router either with http or https, the only way I was then able to reconnect to it was to go into (I am using firefox 4 on squeeze) edit > preferences > advanced > encryption > view certificates > servers and delete the linksys certificate
I had Ubuntu 10.04 installed entirely on my 750 gig SATA drive. Yesterday I backed up my /home and installed a 200 gig drive and reinstalled using the 200 gig drive as / and swap. The 750 gig drive was all /home. Now, whenever I reboot it comes up saying it had serious errors mounting /home and I have to reboot again to get it to boot up. I never had this issue when the 750 gig drive was running the entire show. Has anyone else run into this? S.M.A.R.T. hasn't been throwing any warnings or errors so I am at a loss as to what "serious" errors Ubuntu could be running into.
I'm new to CMake, and I got a few warnings after running a 'configure' file, which I don't really understand.I was hoping someone could tell me if they are real problems of if I can just ignore them. Here is the output I got:
Code: [root@linux khtml2png-2.7.6]# ./configure rm: cannot remove `cmake_install.cmake': No such file or directory
Finally got around to updating from 2.6.31.8 and was surprised at the slew of warnings issued during the install. Rather than post them here, see: pastebin - Someone - post number 1792805 I would have bet money that the machine wouldn't boot after this, but it in fact did (whew). Since the kmp modules were not updated with this new kernel, I have merely suspicions....any one have the real reason for these warnings? Same type of warnings occured (thou I didn't copy the output) when I installed the ATI prop driver rpm. everything seems to work as normal so far, but it was so very different than many previous updates that I'm a bit leery.
Though my upgrade from 11.3 to 11.4 went pretty well (X and apparmor/samba config to renew), I have a bunch of warnings at boot time. Sample: "* wil be removed in a future UDEV version..." On another box, I get some "/etc/*/ipv6" should have a .conf file. Should I worry / fix up something before next upgrade?
After upgrading to Lucid I get the following warnings which I did not have before:
Warning: Cannot convert string "-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct Warning: Cannot convert string "-*-helvetica-medium-r-*--*-120-*-*-*-*-iso8859-1" to type FontStruct
These occur when I start emacs and xpdf. On searching I see people are adding font paths to their xorg.conf file but on looking at mine there is no longer a font section. Also I have few directories fonts/X11/usr/share/fonts/X11$ ls misc/util/. I'm assuming the above folders and xorg.conf file are correct.
We're syncing users from Active Directory over to our linux LDAP server (Red Hat Directory Server). The user names on the AD side are all written in uppcase letters, which is the company policy.The uppername usernames causes problems when setting up /etc/sudoers, since uppercase words are interpreted as aliases. For example, if I add user KENNETH to a User_Alias (i.e. something like "User_Alias ADMINS = KENNETH"), I will get a warning from visudo which expects KENNETH to be an alias and thus not a username. Despite the warning, sudo does seem to work correctly. But is there a way to tell visudo or sudo that usernames are uppercase, and should not trigger a warning? Or are there other ways to go about this sort of thing?
I put a few Itunes songs into my music folder and tried to play them. It didn't. Then, I got to reading in the forums and noticed that there was a "one click" configuration for Gnome users. After doing some more reading, I saw a lot of references to restricted codecs and things of that nature. After beginning the one-click process and then aborting midway through installation, three questions come to mind:
1) Why all the warnings about legalities of downloading the codecs/files? If I bought the music and I use the codecs to listen to it, where does legalities come into play?
2) While installing some of the different files, etc in the one-click process, I received a few warnings that a particular file was not from a trusted source (I don't remember the info verbatim) and then it gave me an email address, presumably from the developer, and asked if I wanted to install it anyway.
3) If I do go through the one-click process, will I be able to listen to I-tunes or am I pretty much screwed on I-tunes on linux?
