Re: Need help with ffmpeg installation - strange behaviour of my system - am I correct here?
Am 09.07.21 um 22:47 schrieb Stefan Monnier: 2. repair my situation - I cannot go to Debian 10 right now (I posted the reason somewhere here - mouse ist awfully slow and jumpy)) You might want to try `aptitude` instead of `apt`: it will try to offer ways to fix the problem (by removing&upgrading&downgrading package). The solutions it offers can sometimes take a long time to come up (because it performs a search through a large search tree), and it may have effects you won't like, so carefully review the solutions proposed. Stefan I think I now know what went wrong - AND I do not know how to revert!!!: some days ago I did unadvertantly: root@primergy:/home/joerg# apt-get install \ > build-essential \ > cmake \ > git \ > libmbedtls-dev \ > libasound2-dev \ > libavcodec-dev \ #!!! > libavdevice-dev \ > libavfilter-dev \ > libavformat-dev \ > libavutil-dev \ > libcurl4-openssl-dev \ > libfdk-aac-dev \ > libfontconfig-dev \ > libfreetype6-dev \ > libglvnd-dev \ > libjack-jackd2-dev \ > libjansson-dev \ > libluajit-5.1-dev \ > libpulse-dev \ > libqt5x11extras5-dev \ > libspeexdsp-dev \ > libswresample-dev \ > libswscale-dev \ > libudev-dev \ > libv4l-dev \ > libvlc-dev \ > libwayland-dev \ > libx11-dev \ > libx264-dev \ > libxcb-shm0-dev \ > libxcb-xinerama0-dev \ > libxcomposite-dev \ > libxinerama-dev \ > pkg-config \ > python3-dev \ > qtbase5-dev \ > qtbase5-private-dev \ > libqt5svg5-dev \ > swig \ > libxcb-randr0-dev \ > libxcb-xfixes0-dev \ > libx11-xcb-dev \ > libxcb1-dev \ > libxss-dev \ > qtwayland5 \ > libgles2-mesa \ > libgles2-mesa-dev Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Hinweis: »libfontconfig1-dev« wird an Stelle von »libfontconfig-dev« gewählt. libgles2-mesa ist schon die neueste Version (13.0.6-1+b2). libgles2-mesa wurde als manuell installiert festgelegt. pkg-config ist schon die neueste Version (0.29-4+b1). pkg-config wurde als manuell installiert festgelegt. Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: libavcodec-dev : Hängt ab von: libavcodec58 (= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden libavdevice-dev : Hängt ab von: libavdevice58 (= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden Hängt ab von: libpostproc-dev (>= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden Hängt ab von: libavresample-dev (>= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden libavfilter-dev : Hängt ab von: libavfilter7 (= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden Hängt ab von: libpostproc-dev (>= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden Hängt ab von: libavresample-dev (>= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden libavformat-dev : Hängt ab von: libavformat58 (= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden libavutil-dev : Hängt ab von: libavutil56 (= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden libglvnd-dev : Hängt ab von: libegl-dev (>= 1.3.0-1) soll aber nicht installiert werden Hängt ab von: libgl-dev (>= 1.3.0-1) Hängt ab von: libgles-dev (>= 1.3.0-1) soll aber nicht installiert werden Hängt ab von: libglx-dev (>= 1.3.0-1) soll aber nicht installiert werden libswresample-dev : Hängt ab von: libswresample3 (= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden libswscale-dev : Hängt ab von: libswscale5 (= 10:4.1.6-dmo1+deb10u1) soll aber nicht installiert werden libvlc-dev : Hängt ab von: libvlc5 (= 1:3.0.12-dmo0+deb10u2) soll aber nicht installiert werden libx264-dev : Hängt ab von: libx264-157 (= 4:0.157.2980+git34c06d1-dmo1+deb10u2) soll aber nicht installiert werden E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.
Re: Bash: testing a variable
Am 09.07.21 um 21:54 schrieb Charles Curley:
I'd like to check two things:
* Whether a given path is not already in the $PATH variable
* Whether the given path already exists
If both are true, I'd like to add the given path to the $PATH variable.
I can add the given path, and test for the existence of the given path.
I can write expressions that work to detect the given path in $PATH.
What I don't seem able to do is combine all that in a script.
Here's what I have for the script:
#!/bin/bash
# A short script for testing some code.
# pelican seems to like local installations here.
SUBSTR="${HOME}"/\.local/bin/
echo Substr is "${SUBSTR}"
# if [[ ! ${PATH} =~ .*/home/charles/.local/bin.* ]] ; then
if [[ $( echo "$PATH" | grep -E -v "${SUBSTR}" ) ]] ; then
echo Substring NOT found.;
if [ -d "${HOME}/.local/bin/" ] ; then
echo Adding to \$PATH
PATH=${HOME}/.local/bin:$PATH
fi
else
echo Substring found!;
fi
I call the script with the . operator: ". test.sh"
this is the result:
root@primergy:~/software-env# . test.sh
Substr is /root/.local/bin/
Substring NOT found.
root@primergy:~/software-env#
Why do I always end up adding the given path, even if it is already in
$PATH?
Debian is Buster, bash is 5.0.3(1)-release (x86_64-pc-linux-gnu).
Re: Need help with ffmpeg installation - strange behaviour of my system - am I correct here?
Am 09.07.21 um 21:44 schrieb Greg Wooledge: On Fri, Jul 09, 2021 at 09:36:00PM +0200, Kampmann wrote: The following packages have unmet dependencies: libavcodec58 : Depends: libavutil56 (>= 10:4.1.6) but it is not going to be installed Depends: libc6 (>= 2.27) but 2.24-11+deb9u4 is to be installed This is a really powerful indicator that you've mixed sources which are either from, or for, different Debian releases. Or mixed Debian sources and non-Debian sources. The "libc6 (>= 2.27)" dependency is identical to the libc6 dependency on the *buster* (Debian 10) version of libavcodec58. (Which is a package that does not even exist in Debian 9.) So, it looks like you've either got a buster (Debian 10) source, or you've got some third-party source that was meant to be used with Debian 10. You can't use Debian 10 sources on Debian 9. this really seems to be the clue, however: how do I get 1. information on the installed packages? 2. repair my situation - I cannot go to Debian 10 right now (I posted the reason somewhere here - mouse ist awfully slow and jumpy))
Need help with ffmpeg installation - strange behaviour of my system - am I correct here?
Hello - I tried to install ffmpeg (a normal Debian package) and got some strange messages. the ffmpeg-group adviced me to go to a Debian group. I hope I am correct here in this group. I am running Debian 9 on a Fujitsu TX 100 S1 computer ... /base) joerg@primergy:~$ uname -a Linux primergy 4.9.0-16-amd64 #1 SMP Debian 4.9.272-1 (2021-06-21) x86_64 GNU/Linux (base) joerg@primergy:~$ / Here is the dialogue I had in the *ffmpeg*-group; Am 09.07.21 um 11:31 schrieb Kampmann/: Thanks - that is strange. Do you have any clues? /Am 09.07.21 um 11:16 schrieb Reindl Harald/: that's a problem with your distribution and not ffmpeg specific /Am 09.07.21 um 11:06 schrieb Joerg Kampmann: /Hello group I wanted to install ffmpeg under Debian 9 and got some errormessages (in German): root@primergy:~# apt install ffmpeg Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: ffmpeg : Hängt ab von: libavcodec58 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libavdevice58 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libavfilter7 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libavformat58 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libavresample4 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libavutil56 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libpostproc55 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libswresample3 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libswscale5 (>= 10:4.1.6) soll aber nicht installiert werden E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete. root@primergy:~# / /and a 2nd mail on this issue: I tried to install one of the "not-installed" modules and got the following root@primergy:~/software-env# apt install libavcodec58 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: libavcodec58 : Hängt ab von: libavutil56 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libc6 (>= 2.27) aber 2.24-11+deb9u4 soll installiert werden # here another version should be installed Hängt ab von: libcodec2-0.8.1 ist aber nicht installierbar Hängt ab von: libgsm1 (>= 1.0.18) aber 1.0.13-4+b2 soll installiert werden Hängt ab von: libmfx1 soll aber nicht installiert werden # this module is not installable - why? Hängt ab von: libopenh264-5 (>= 2.0.0) soll aber nicht installiert werden Hängt ab von: libswresample3 (>= 10:4.1.6) soll aber nicht installiert werden Hängt ab von: libva2 (>= 2.2.0) ist aber nicht installierbar# this module is not installable - why? Hängt ab von: libvpx6 (>= 1.8.1) soll aber nicht installiert werden Hängt ab von: libwebpmux3 (>= 0.6.1-2) ist aber nicht installierbar # this module is not installable - why? Hängt ab von: libx264-157 (>= 4:0.157.2980+git34c06d1) soll aber nicht installiert werden E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete. // /
Re: how to enable trim for an external encrypted SSD?
Am Wed, 15 Nov 2017 22:00:54 -0500 schrieb Stefan Monnier: > I highly doubt that TRIM would help. IOW, it's just a gut feeling you > have, but I strongly doubt you have concrete data that can show it might > be related to the presence/absence of TRIM-support. May be you are right. I hope so... ;-)
Re: how to enable trim for an external encrypted SSD?
Am 11.11.17 15:27, schrieb Christian Seiler: If it's the kernel driver there's a chance that'll be fixed in a future kernel version. Hmm... Arch Linux (that I tried) comes with a recent kernel and this still not work. Unfortunately I can't say much more about that, I've never had an external SSD. I had the same situation with my Sandisc Exreme thumb drive before! Here heparin reports TRIM too, and fstrim failed too. At that time I thought that the problem is the thumb drive controller. A thumb drive is no SSD. As a result of the missing TRIM, the drive shows IO errors after just 1 year of usage. That could become an expensive hobby. :-/
Re: how to enable trim for an external encrypted SSD?
Am Sat, 11 Nov 2017 14:13:12 +0100 schrieb Christian Seiler: > Also, did you mount the device with -o discard or set that option with > tune2fs (_before_ mounting it)? No, not now. I want to use fstrim in favour to the discard option. But I've tested it with an Arch Linux installation with a more fresh kernel. There both vairante (fstrim and discard-option in fstab) fails too. In case of the discard option, the error is written to the logs. > What does the command > findmnt | grep /media/jd/TEST $ findmnt | grep /media/jd/TEST ├─/media/jd/TEST /dev/sdg1 ext4 rw,nosuid,nodev,relatime,data=ordered $ sudo lsblk -D [sudo] password for jd: NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 512B 2G 0 ├─sda10 512B 2G 0 └─sda20 512B 2G 0 sdb 00B 0B 0 sdg 00B 0B 0 └─sdg100B 0B 0 In this case, sda is a internal SSD (Samsung EVO) with working TRIM and sdb is a HDD.
Re: how to enable trim for an external encrypted SSD?
Am Mon, 06 Nov 2017 14:28:32 +0100 schrieb Christian Seiler: > I don't what you want is possible. When you plug in an external drive > (that is _not_ in /etc/fstab etc.) the process of how it gets mounted is > different: ... > tune2fs -o +discard /dev/external_disk_device My drive has arrived and even a ext4 without LUKS fails to (fs)trim the mount! Any idea why? $ sudo hdparm -I /dev/sdg1 ... *Data Set Management TRIM supported (limit 8 blocks) *Deterministic read data after TRIM $ sudo fstrim /media/jd/TEST fstrim: /media/jd/TEST: Verwerfungsvorgang wird nicht unterstützt.
Re: how to enable trim for an external encrypted SSD?
Am Tue, 07 Nov 2017 01:00:54 +0500 schrieb Alexander V. Makartsev: > I don't use TRIM feature on my systems because of that, and hope for a > firmware of modern SSD will manage everything automatically. Am I wrong? I've used a ext4 formatted, unencrypted (!) 64GB SanDisk Extreme USB 3.0 thumbdrive together with Unison. I sync a collection of documentation, some application configurations and a bunch of git repositories to it. The sync was done 4-5 days a week. The amount of changes was less than 5MB a day. IMO SanDisk is a trustful company with products of high quality. But the thumbdrive has not even lasted a year! By the way... hdparm reports that the thumbdrive supports TRIM, but I was never able to use it! So much for the topic "the firmware will do that". ;-)
Re: how to enable trim for an external encrypted SSD?
Am Mon, 06 Nov 2017 14:28:32 +0100 schrieb Christian Seiler: > But all that doesn't really help you if the underlying LUKS container > isn't opened with the discard option set. And as far as I know there is > no possibility of tagging a LUKS container with that option, you must > always supply that option to the cryptsetup command (which is done > implicitly via /etc/crypttab). Thanks for your detailed and extensive answer. That's exactly the answer I was afraid of. ;-) So I will add an entry to the /etc/crypttab and hope that fstrim will do it's job. All system without a modified crypttab should mount the device but fstrim will fail. I think I can live with that solution. > You could ask the LUKS developers to include an additional flag in their > headers that allows you to specify that this volume should be opened > with discards allowed by default That is a good idea. I think I will write an ticket for that. Thanks again.
how to enable trim for an external encrypted SSD?
Normally I would enable TRIM support in the /etc/fstab or the /etc/ crypttab by add the discard option. Now I have bought a SanDisk Extreme Portable SSD. My goal is to add a LUKS encrypted partition without an explicit fstab entry. I've done this with some USB thumbdrives before, but not with TRIM support. The drvie should be plugged into any Linux device without the need to change the configuration. What is the correct way to add TRIM support to an external SSD with LUKS encrypted partition?
Re: Bug: updating Debian9 not "allowed".
Am Thu, 26 Oct 2017 13:13:57 +0100 schrieb Darac Marjal: > [Aside: The debian packaging tool is called "synaptic". "Synaptics" are > a company producing touchpads. The two are not related] I know, but I always make this mistake. ;-) > I believe this is a known bug in synaptic: #864640 [1]. It is hard to believe that this bug is known since June and that there is neither a fix nor a solution. Deleting the file has worked for me, but I can't say that there are no side effects. How should a newbie solve this? Without a work-around there are no updates possible.
Bug: updating Debian9 not "allowed".
I'm still running Debian 8 on all of my systems. Since it is time to switch to Debian 9, I've tried to have a first look at it. So I've installed the nonfree DVD-Image 9.2 within a VirtualBox container. All went fine, until I've tried to update the APT database. Both, apt and Synaptics updates fails. In both cases the error reports, that /etc/apt/trusted.gpg is not accessible by user "_apt". The recommendation I've found was to delete trusted.gpg. OK, this was a workaround for using apt. Both update and upgrade works without errors. Trying Synaptics leads to the previous behavior. The file trusted.gpg appears again and with this file, the error returns. By the way... Why is the VirtualBox Guest Utils package not available in the official repositories?
Re: Debian8 is not playing with Synology using NFS/CIFS
Am Tue, 08 Aug 2017 14:31:33 + schrieb Curt: > Did you look on the innertubes? This seems to be quite a popular > question. No help here, for instance? > > https://superuser.com/questions/860553/user-id-mapping-with-nfs-on- synology-nas > > If not I'm sorry for wasting your time. Thanks for the link. I think the whole NFS stuff is a really ugly and partly broken dinosaur. I'm using NFS (v3) for decades now, and all the glitches are still not really solved. And CIFS for Linux clients seems to be no way to go. I'm afraid I have to setup Kerberos to work-around the broken ipmapd stuff. More than a little bit "oversized"... Thanks for the help!
Re: Debian8 is not playing with Synology using NFS/CIFS
Am Tue, 08 Aug 2017 11:34:58 +0100 schrieb Darac Marjal: > On Tue, Aug 08, 2017 at 10:09:42AM +0000, Joerg Desch wrote: >>Am Tue, 08 Aug 2017 11:01:12 +0100 schrieb Darac Marjal: >> >>> I'll assume that the Synology is a black box, and so we can't work out >>> how it's configured. >> >>Yes, more or less. >> >> >>> Try "mount -v -t nfs name.or.ip.of.synology:/ /some/mountpoint" and >>> see what errors result. >> >>Mounting isn't the problem. The mount is working without errors >> >>mount.nfs: trying text-based options >>'hard,intr,vers=4,addr=192.168.1.1,clientaddr=192.168.1.88' >> >>My only problem is the (very old) goal to get different uid/gid working. > > OK, that's good. NFSv4 doesn't send UIDs/GIDs over the wire any more, it > sends Usernames and Groups. Hmm. I'm not so sure On my local workstation, my ID is 3000. On the Synology, the id is 1027. On both machines, my user name is "jd". SO, if the mapping is "name based", I should see all the files with uid 1027 on the servers with the correct name on the client. This is not the case! A "ls -l" shows me all the different UIDs, but neither the corresponding name, nor "nobody". I try cp/chmod/chgrp again tomorrow morning and post the result here. Thanks so far...
Re: Debian8 is not playing with Synology using NFS/CIFS
Am Tue, 08 Aug 2017 11:01:12 +0100 schrieb Darac Marjal: > I'll assume that the Synology is a black box, and so we can't work out > how it's configured. Yes, more or less. > > Try "mount -v -t nfs name.or.ip.of.synology:/ /some/mountpoint" and see > what errors result. Mounting isn't the problem. The mount is working without errors mount.nfs: trying text-based options 'hard,intr,vers=4,addr=192.168.1.1,clientaddr=192.168.1.88' My only problem is the (very old) goal to get different uid/gid working. Thanks
Debian8 is not playing with Synology using NFS/CIFS
It drives me crazy. Really. The company I'm working for is switching from a Dell server running Ubuntu to a Synology HA solution. On my desktop, I'm using Debian 8 and only Debian (Yes I know, I can be lucky ;-)). My first try was to mount the new shares using NFS4 and taraa... imapd. This fails because the ID mapping does not work. On both sides, the (same) domain is inserted into "/etc/imapd.conf". Without any changes. For now, I'm not really sure what ipmapd is for. A hoax? Fun? The second try was the ugly solution using CIFS. The bad insight this morning... Synology disables the "unix extensions". The second... There is no ID mapping too. My hope with CIFS was, that die total user and group stuff is done using "names" and not IDs. So, if anybody out there is running a Synology server. Is there a working solution to get uid/gip mapping, unix access flags and symlinks? I'm happy for every (positive) answer. ;-)
Re: How to use Garmin Connect with Debian 7?
Am 13.07.17 12:13 nachm., schrieb Jörg-Volker Peetz: there's this nice blog in German: https://blog.dafb-o.de/neue-firmware-fuer-garmin-devices-unter-linux/ where the firmware update procedure from Linux is detailed and a link to the firmware files for your device is given http://gawisp.com/perry/edge/ . Thanks for the links. Today I have tried to connect the FR235 to the Garmin Android app. So much pain Damned Bluetooth. After 10 fails to add the FR to the app, I had some luck. After that, the app shows me a running firmware download. The progress was 50% for 20 minutes. So I abort this juke. I will try the step in the blog above. Thanks again.
Re: How to use Garmin Connect with Debian 7?
Am Wed, 12 Jul 2017 14:14:20 +0200 schrieb tomas: > I'm downright appalled to see that a little piece of hardware comes tied > to TahCloud and doesn't give the user any choices in that. I'd be raging > at Garmin, were I their customer, for being (mis)treated like that. My mistake... The Forerunner works like a charm without cloud connection. It's my personal choose to let the companion software sync the data to the cloud in order to get the processed results. So Garmin is doing it right. ;-)
Re: How to use Garmin Connect with Debian 7?
Am Wed, 12 Jul 2017 14:08:22 +0200 schrieb solitone: > Yes, I used to have a VirtualBox instance on my previous laptop, and it > did work. Then I migrated that VirtualBox image to KVM when I prepared > my new laptop, and it continued to work. Just because you mentioned it You have build a VirtualBox image from the content of your harddrive? Which tool have you used for this? Does Windows reconfigure all the drivers after starting inside a VM? What's the benefit in using libvirt / KVM?
Re: How to use Garmin Connect with Debian 7?
Am Wed, 12 Jul 2017 07:43:31 -0400 schrieb Fungi4All: > I think you need to read up to the NMEA183 protocol, which for a while > it was the standard of i/o data ever since the first gps had wired > connections on it. Both devices are visible as filesystem. So I can easily copy and convert the recorded FIT files. My problem is the connection to the Garmin Connect cloud service. I have to initialize the device and bind it to my account.
Re: How to use Garmin Connect with Debian 7?
Am Wed, 12 Jul 2017 13:28:11 +0200 schrieb solitone: > I have a Garmin Edge 520, and I use the Garmin Connect app on my > smartphone to sync it, not the Windows tool. I just needed the Windows > tool during initial configuration, but once it's registered you no > longer need it (except for some rare events when you need it to solve > weird sync issues). I have the same situation here. The Edge 520 is running, only firmware updates needs Windows. > I don't know whether it's possible to perform the initial configuration > steps without the official Garmin tool, I have a Windows 10 installation > on a libvirt virtual machine, that I use just for Garmin and iTunes. That is a good idea. I could use the Windows license key of the dead windows notebook and run it inside VirtualBox. Do you know if the USB connection to the Garmin devices runs through the virtual host?
How to use Garmin Connect with Debian 7?
I'm using a Garmin Edge 520 for my bycicle and a (new) Forerunner for running. How can I access Garmin Connect without installing the Windows tools? The Garmin Edge 520 is already registered to my Garmin Connect account. I've used an old Windows 7 notebook with isn't functional anymore. Now I've tried to sync the Edge 520 and (more important) to register the Forerunner with the garmin-plugin and the garmin-forerunner-tools. But it didn't work. Is there anyone on the list using this tools? I've installed firefox-esr from the official repos. I've tried to change the user agent string as mentioned by Andres Diener. But nothing happens. Neither the expected dialog appears, nor the configurations files are created. garmin_get_info reports "garmin unit could not be opened!". The device itself is deteced and the filesysdtem is mounted: "scsi 6:0:0:0: Direct-Access Garmin FR235 Flash" What's wrong?
Re: shutdown fails to power off host
Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan: > When I shutdown my desktop system, the screen displays messages from > systemd (I presume), the last of which is "Reached target Shutdown". Just a thought... I'm running Debian Jessie and I see the same behavior with my Thinkpad T500. In my case the reason is the Network Manager. I have 2 NFS shares mounted over Wifi. The Network Manager stops Wifi before unmounting the NFS shares. This leads to a long time out. After that, I see the "Reached target Shutdown" message and the system in still powered. I have to unmount the NFS volumes first and than I can shutdown the system.
Difference between LUKS drives with cryptsetup and Disks?
I've created a LUKS partition which I mount on demand. This partition was created using cryptsetup. While mounting the partition, GNOME asks me first for the passphrase and than for the "admin" password. A while ago, I've created a LUKS partition on an USB thumb drive using GNOME Disks. In this case, mounting requires only the passphrase. And that doesn't depend on the used computer! What is the difference? Can I change the behavior of my older LUKS partition too?
Re: System freezes after update to Jessie 8.4 [workaround]
My personal workaround... yesterday, I had used GNOME3 Classic which reduced the freezes down to "every3 hours". ;-) Today morning, I've downgrades the kernel back to the previous version and I'm back to GNOME3 and Firefox for 2 hours now. No freeze so far... What I've done is: aptitude install linux-image-3.16.0-4-amd64=3.16.7-ckt20-1+deb8u4 linux- headers-3.16.0-4-common=3.16.7-ckt20-1+deb8u4 linux-headers-3.16.0-4- amd64=3.16.7-ckt20-1+deb8u4
Re: System freezes after update to Jessie 8.4
Some additional information... After the X-Crash, neither CTRL-ALT_F1 nor CRTL-ALT-DEL works. Even CRTL- ALT-BACKSPACE doesn't work. But I've tried ALT-PRINT-REISUB and the system reboots.
Re: System freezes after update to Jessie 8.4
Am Mon, 04 Apr 2016 15:21:09 +0200 schrieb Sven Arvidsson: > 3.16 was mentioned later in the thread: > https://lkml.org/lkml/2016/3/9/373 OK. If I find some time, I will have a look at this. > You might want to file a bug if there isn't one open already. For the kernel-image package? Is the "radeon" stuff part of that package?
Re: System freezes after update to Jessie 8.4
Am Mon, 04 Apr 2016 13:17:53 +0200 schrieb Sven Arvidsson: > What kernel are you running? Looks like it might be this: > https://lkml.org/lkml/2016/3/6/257 The changlelog of the current kernel image pakcage lists these changes for "radeon": - radeon/cik: Fix GFX IB test on Big-Endian - radeon: Fix VCE ring test for Big-Endian systems - radeon: Fix VCE IB test on Big-Endian systems
Re: System freezes after update to Jessie 8.4
Am Mon, 04 Apr 2016 13:17:53 +0200 schrieb Sven Arvidsson: > On Mon, 2016-04-04 at 11:11 +0000, Joerg Desch wrote: >> After the upgrade (and a restart), the system freezes from one second >> to the other. It seems to be independent from the used application. >> >> As a work-around, I'm running GNOME classic now. Without the EGL >> features, the desktop is running now. Currently I avoid using Firefox, >> because I don't know if the renderer uses EGL. >> >> Can someone help? > > > What kernel are you running? 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux > Looks like it might be this: > https://lkml.org/lkml/2016/3/6/257 The 3D part seems to be the correct location, but the mentioned kernel is older. > If so, you could probably work around it by installing/booting an > earlier kernel. This was the last upgrade. How can I get a changelog (on the package web site there is now changelog available) and how can I downgrade to the previous package. Only linux-image-3.16.0-4-amd64, linux-headers-3.16.0-4- amd64 and linux-headers-3.16.0-4-common were updated. Start-Date: 2016-04-04 06:26:37 Commandline: apt-get dist-upgrade Upgrade: subversion:amd64 (1.8.10-6+deb8u2, 1.8.10-6+deb8u3), apt:amd64 (1.0.9.8.2, 1.0.9.8.3), multiarch-support:amd64 (2.19-18+deb8u3, 2.19-18 +deb8u4), linux-image-3.16.0-4-amd64:amd64 (3.16.7-ckt20-1+deb8u4, 3.16.7- ckt25-1), libimage-magick-q16-perl:amd64 (6.8.9.9-5, 6.8.9.9-5+deb8u1), librsvg2-2:amd64 (2.40.5-1, 2.40.5-1+deb8u1), libgail18:amd64 (2.24.25-3, 2.24.25-3+deb8u1), libpam0g:amd64 (1.1.8-3.1+deb8u1, 1.1.8-3.1+deb8u1 +b1), libsane-common:amd64 (1.0.24-8, 1.0.24-8+deb8u1), libc6-i686:i386 (2.19-18+deb8u3, 2.19-18+deb8u4), libgif4:amd64 (4.1.6-11, 4.1.6-11 +deb8u1), libfglrx:amd64 (15.9-4~deb8u1, 15.9-4~deb8u2), apt-utils:amd64 (1.0.9.8.2, 1.0.9.8.3), fglrx-atieventsd:amd64 (15.9-4~deb8u1, 15.9-4~deb8u2), fglrx-control:amd64 (15.9-4~deb8u1, 15.9-4~deb8u2), libebml4:amd64 (1.3.0-2, 1.3.0-2+deb8u1), libgudev-1.0-0:amd64 (215-17 +deb8u3, 215-17+deb8u4), tzdata-java:amd64 (2015g-0+deb8u1, 2016c-0 +deb8u1), libc-dev-bin:amd64 (2.19-18+deb8u3, 2.19-18+deb8u4), libpam- systemd:amd64 (215-17+deb8u3, 215-17+deb8u4), gtk2-engines-pixbuf:amd64 (2.24.25-3, 2.24.25-3+deb8u1), libc-bin:amd64 (2.19-18+deb8u3, 2.19-18 +deb8u4), libc6:amd64 (2.19-18+deb8u3, 2.19-18+deb8u4), libc6:i386 (2.19-18+deb8u3, 2.19-18+deb8u4), ruby:amd64 (2.1.5+deb8u1, 2.1.5 +deb8u2), libglib2.0-0:amd64 (2.42.1-1, 2.42.1-1+b1), libsvn1:amd64 (1.8.10-6+deb8u2, 1.8.10-6+deb8u3), amd64-microcode:amd64 (2.20141028.1, 2.20160316.1~deb8u1), libglib2.0-dev:amd64 (2.42.1-1, 2.42.1-1+b1), libapt-inst1.5:amd64 (1.0.9.8.2, 1.0.9.8.3), libgtk2.0-bin:amd64 (2.24.25-3, 2.24.25-3+deb8u1), libgtk2.0-common:amd64 (2.24.25-3, 2.24.25-3+deb8u1), udev:amd64 (215-17+deb8u3, 215-17+deb8u4), base- files:amd64 (8+deb8u3, 8+deb8u4), gir1.2-gtk-2.0:amd64 (2.24.25-3, 2.24.25-3+deb8u1), gnupg:amd64 (1.4.18-7, 1.4.18-7+deb8u1), linux- headers-3.16.0-4-amd64:amd64 (3.16.7-ckt20-1+deb8u4, 3.16.7-ckt25-1), chromium:amd64 (49.0.2623.87-1~deb8u1, 49.0.2623.108-1~deb8u1), libsrtp0:amd64 (1.4.5~20130609~dfsg-1.1, 1.4.5~20130609~dfsg-1.1+deb8u1), initramfs-tools:amd64 (0.120, 0.120+deb8u1), libcairo-gobject2:amd64 (1.14.0-2.1, 1.14.0-2.1+deb8u1), libpam-modules:amd64 (1.1.8-3.1+deb8u1, 1.1.8-3.1+deb8u1+b1), libsndfile1:amd64 (1.0.25-9.1, 1.0.25-9.1+deb8u1), libcairo2:amd64 (1.14.0-2.1, 1.14.0-2.1+deb8u1), libudev-dev:amd64 (215-17 +deb8u3, 215-17+deb8u4), libudev1:amd64 (215-17+deb8u3, 215-17+deb8u4), libimage-magick-perl:amd64 (6.8.9.9-5, 6.8.9.9-5+deb8u1), libsane:amd64 (1.0.24-8, 1.0.24-8+deb8u1), imagemagick-6.q16:amd64 (6.8.9.9-5, 6.8.9.9-5 +deb8u1), libservlet2.5-java:amd64 (6.0.41-3, 6.0.45+dfsg-1~deb8u1), libapt-pkg4.12:amd64 (1.0.9.8.2, 1.0.9.8.3), libfglrx-amdxvba1:amd64 (15.9-4~deb8u1, 15.9-4~deb8u2), libpcre3-dev:amd64 (8.35-3.3+deb8u2, 8.35-3.3+deb8u4), libhogweed2:amd64 (2.7.1-5, 2.7.1-5+deb8u1), librsvg2- common:amd64 (2.40.5-1, 2.40.5-1+deb8u1), sane-utils:amd64 (1.0.24-8, 1.0.24-8+deb8u1), systemd-sysv:amd64 (215-17+deb8u3, 215-17+deb8u4), libgtk2.0-0:amd64 (2.24.25-3, 2.24.25-3+deb8u1), libcairo2-dev:amd64 (1.14.0-2.1, 1.14.0-2.1+deb8u1), imagemagick:amd64 (6.8.9.9-5, 6.8.9.9-5 +deb8u1), linux-compiler-gcc-4.8-x86:amd64 (3.16.7-ckt20-1+deb8u4, 3.16.7- ckt25-1), systemd:amd64 (215-17+deb8u3, 215-17+deb8u4), fglrx-modules- dkms:amd64 (15.9-4~deb8u1, 15.9-4~deb8u2), gpgv:amd64 (1.4.18-7, 1.4.18-7 +deb8u1), libpcrecpp0:amd64 (8.35-3.3+deb8u2, 8.35-3.3+deb8u4), libnettle4:amd64 (2.7.1-5, 2.7.1-5+deb8u1), libpam-modules-bin:amd64 (1.1.8-3.1+deb8u1, 1.1.8-3.1+deb8u1+b1), libmagickwand-6.q16-2:amd64 (6.8.9.9-5, 6.8.9.9-5+deb8u1), fglrx-driver:amd64 (15.9-4~deb8u1, 15.9-4~deb8u2), tzdata:amd64 (2015g-0+deb8u1, 2016c-0+deb8u1), libmagick+ +-6.q16-5:amd64 (6.8.9.9-5, 6.8.9.9-5+deb8u1), libglib2.0-
System freezes after update to Jessie 8.4
I have an extremely hard problem after upgrading Debian Jessie from 8.3 to 8.4 today. The system is a Dell Vostro with an AMD/ATI Turks PRO [Radeon HD 7570]. The free radeon driver is used for X. Desktop is GNOME3. The resolution is 25560x1440. I've used this resolution for about 3-4 weeks now. After the upgrade (and a restart), the system freezes from one second to the other. It seems to be independent from the used application. As a work-around, I'm running GNOME classic now. Without the EGL features, the desktop is running now. Currently I avoid using Firefox, because I don't know if the renderer uses EGL. Can someone help? Here is one of the several logged crashes: Apr 4 07:07:11 jd-dell kernel: [ 2025.042433] BUG: unable to handle kernel NULL pointer dereference at 0008 Apr 4 07:07:11 jd-dell kernel: [ 2025.042460] IP: [] radeon_fence_ref+0xd/0x50 [radeon] Apr 4 07:07:11 jd-dell kernel: [ 2025.042491] PGD 0 Apr 4 07:07:11 jd-dell kernel: [ 2025.042498] Oops: 0002 [#1] SMP Apr 4 07:07:11 jd-dell kernel: [ 2025.042508] Modules linked in: sha256_ssse3 sha256_generic dm_crypt algif_skcipher af_alg dm_mod rpcsec_gss_krb5 nfsv4 dns_resolver joydev hid_logitech_dj usb_storage hid_generic bnep binfmt_misc usbhid hid pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc ath3k ecb btusb bluetooth 6lowpan_iphc wl(PO) x86_pkg_temp_thermal intel_powerclamp intel_rapl arc4 coretemp kvm_intel kvm ath9k crc32_pclmul ath9k_common ath9k_hw fglrx(PO) ath aesni_intel mac80211 aes_x86_64 lrw gf128mul cfg80211 glue_helper ablk_helper iTCO_wdt iTCO_vendor_support snd_hda_codec_realtek snd_hda_codec_generic dcdbas cryptd rfkill serio_raw snd_hda_codec_hdmi i2c_i801 pcspkr snd_hda_intel snd_hda_controller snd_hda_codec lpc_ich mfd_core snd_hwdep snd_pcm snd_timer snd battery soundcore ie31200_edac shpchp mei_me edac_core mei processor evdev vmhgfs(O) vmw_vmci fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 sg sd_mod crc_t10dif sr_mod crct10dif_generic cdrom radeon ahci crct10dif_pclmul libahci i2c_algo_bit crct10dif_common crc32c_intel ttm ehci_pci libata drm_kms_helper xhci_hcd psmouse ehci_hcd scsi_mod drm r8169 mii usbcore i2c_core usb_common fan thermal video thermal_sys button Apr 4 07:07:11 jd-dell kernel: [ 2025.042873] CPU: 1 PID: 1207 Comm: Xorg Tainted: P O 3.16.0-4-amd64 #1 Debian 3.16.7-ckt25-1 Apr 4 07:07:11 jd-dell kernel: [ 2025.042894] Hardware name: Dell Inc. Vostro 470/0NW73C, BIOS A10 10/19/2012 Apr 4 07:07:11 jd-dell kernel: [ 2025.042910] task: 88040a1b1530 ti: 88040852c000 task.ti: 88040852c000 Apr 4 07:07:11 jd-dell kernel: [ 2025.042927] RIP: 0010: [] [] radeon_fence_ref+0xd/0x50 [radeon] Apr 4 07:07:11 jd-dell kernel: [ 2025.042955] RSP: 0018:88040852fb18 EFLAGS: 00010292 Apr 4 07:07:11 jd-dell kernel: [ 2025.042967] RAX: RBX: 8804091d95f8 RCX: 8804091d8d08 Apr 4 07:07:11 jd-dell kernel: [ 2025.042982] RDX: 0001 RSI: RDI: Apr 4 07:07:11 jd-dell kernel: [ 2025.042998] RBP: 8804091d9550 R08: 8804091d8000 R09: Apr 4 07:07:11 jd-dell kernel: [ 2025.043014] R10: 0002 R11: 88040852fe08 R12: 0020 Apr 4 07:07:11 jd-dell kernel: [ 2025.043029] R13: 88040852fbe0 R14: 88040852fbb0 R15: 8804091d95f8 Apr 4 07:07:11 jd-dell kernel: [ 2025.043045] FS: 7f0057df7980 () GS:88041ec4() knlGS: Apr 4 07:07:11 jd-dell kernel: [ 2025.043063] CS: 0010 DS: ES: CR0: 80050033 Apr 4 07:07:11 jd-dell kernel: [ 2025.043076] CR2: 0008 CR3: 00040bce3000 CR4: 001407e0 Apr 4 07:07:11 jd-dell kernel: [ 2025.043091] Stack: Apr 4 07:07:11 jd-dell kernel: [ 2025.043096] a03130bc 0028d7c0 ee400100 88040852fcd0 Apr 4 07:07:11 jd-dell kernel: [ 2025.043116] 8804091d8000 88040a1b1530 88040a1b1530 0001 Apr 4 07:07:11 jd-dell kernel: [ 2025.043136] Apr 4 07:07:11 jd-dell kernel: [ 2025.043155] Call Trace: Apr 4 07:07:11 jd-dell kernel: [ 2025.043173] [] ? radeon_sa_bo_new+0x25c/0x460 [radeon] Apr 4 07:07:11 jd-dell kernel: [ 2025.043197] [] ? radeon_ib_get+0x2e/0xd0 [radeon] Apr 4 07:07:11 jd-dell kernel: [ 2025.043220] [] ? radeon_cs_ioctl+0x13c/0x730 [radeon] Apr 4 07:07:11 jd-dell kernel: [ 2025.043241] [] ? drm_ioctl+0x1c7/0x5b0 [drm] Apr 4 07:07:11 jd-dell kernel: [ 2025.043258] [] ? __do_page_fault+0x1d1/0x4f0 Apr 4 07:07:11 jd-dell kernel: [ 2025.043277] [] ? radeon_drm_ioctl+0x46/0x80 [radeon] Apr 4 07:07:11 jd-dell kernel: [ 2025.043294] [] ? do_vfs_ioctl+0x2cf/0x4b0 Apr 4 07:07:11 jd-dell kernel: [ 2025.043307] [] ? SyS_ioctl+0x81/0xa0 Apr 4 07:07:11 jd-dell kernel: [ 2025.043321] [
Using github as repository for apt?
I've tried to find a way to use github or github-pages as host to provide a repository for apt. Does anyone knows such a solution?
Re: Differences Between ThinkPad Models
Am Thu, 03 Dec 2015 13:35:35 -0800 schrieb GC: > Can someone help me compare the differences with each of these laptops? > - Lenovo ThinkPad X60/X60s - Lenovo ThinkPad X60 Tablet - Lenovo > ThinkPad T60 - Lenovo ThinkPad X200 - Lenovo ThinkPad R400 - Lenovo > ThinkPad R500 - Lenovo ThinkPad T400 - Lenovo ThinkPad T500 ThinkWiki is your friend. ;-) http://www.thinkwiki.org
VPN connection no longer available for me as user
I run into a bug where nm-connection-editor doesn't read the password out of the settings. And without password it doesn't save changes. I hadn't recognized this first, so that I tested editing the setup as root. The console outputs leads me to a solution. After saving my changes as root, I no longer have access to the VPN. Even the entry isn't visible. Within the configuration file, I have found the following line. permissions=user:root:; I've changed it back to my login name, but it still doesn't work. How can I change the permissions back to me as owner?
gnome-power-manager compatible with systemd?
I have installed a standard Debian Jessie (with systemd and GNOME3) on my older T500 (dual core). For some reasons, the *power statistics monitor* is not installed by default. Is there a reason for that? Is it save to install gnome-power-manager (only to get the monitor) or does it may cause an conflict with the power management (if any) of systemd? If have installed gnome-power-manager now without warnings. After that, the T500 doesn't shutdown completely. I had not have the time to debug this on the weekend, but as far as I remember, this wasn't the case before the installation of gnome-power-manager.
Re: Brightness configuration issue
Am Thu, 24 Sep 2015 00:05:11 +0200 schrieb sp113438: > sudo redshift-gtk -b 0.5 > > dims 50% >From the homepage: Redshift has a brightness adjustment setting, but it does not work the way most people might expect. In fact it is a *fake brightness adjustment* obtained by manipulating the gamma ramps, which means that it does not reduce the backlight of the screen. ;-)
Re: Wie restauriert man alte NetworkManager Konfigurationen?
Sorry, wrong group! Please, ignore the post it was to early in the morning and the coffee was not cooked. ;-)
Wie restauriert man alte NetworkManager Konfigurationen?
Ich habe nach meinem Upgrade von Wheezy auf Jessie die VPN-Konfiguration aufgeschoben. Nun wollte ich das nachholen und habe (ganz blauäugig) die alte Datei unter /etc/NetworkManager/system-connections wieder einsortiert. Leider erkennt der NetworkManager die Datei nicht. Zumindest zeigt er die Verbindung nicht and. Muss ich sonst noch etwas machen?
problems with moving the toolsbars of Inkscape
I'm using Inkscape from Jessie and have some trouble with the arrangement of the toolbars. I've written a bug report (#797148) two weeks ago, but without reactions for now. The positioning of the toolbars is only in some (rare) cases possible. It is very hard to find a place where the moved toolbar snaps into a position. Most bars doesn't snap to any position. A second effect is the length of the bar. While moving the toolbar, the length of the bar is not truncated to the space needed, so that dragging a bar in fullscreen mode is not possible. What are your experiences with moving the toolsbars? Are there any solutions or work-arounds?
Re: systemd for administrators, printable version.
Am Mon, 17 Nov 2014 15:29:21 +0100 schrieb Erwan David: > Is there a printable/epub/pdf version of systemd for administrators ? http://www.bandwidthco.com/whitepapers/os/linux/systemd/systemd%20for% 20Administrators.pdf Google leads me to this link... ;-) I don't know the state of this document, but it seems to be the file you are looking for. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m4ep45$eju$1...@ger.gmane.org
Re: Whats your way of sharing data between PCs?
Am Mon, 22 Sep 2014 19:01:36 -0400 schrieb PaulNM: > Questions for the OP: > Is the Desktop always on? If so, it could be the master server. No the Desktop is only used if the screens of the notebooks are to small. ;-) > Do you want to sync even if the laptops are not home, not just have > copies of the files on them? Yes and now. For the first step *No*, but I plan to sync parts of the data with my Desktop in the office too. If you use PCs to store informations, libraries, Codes and project data, it makes sense to "take this stuff with you". So I should anseer *Yes*, but may be later. > Do you want the laptops to sync with each other if the desktop isn't > around? No, that isn't important. My first idea was a VPN to my server at home. It is Debian based and 24/7 up and running. But my internet here in Germany is poor. I only have 450kB downstream and 35kB upstream. I think these is may be not much. At least not for Unison, since it tries to read to much stuff while checking / scanning for changes. How much data is transfered by BTsync if no changes are made? Have you ever had conflicts? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lvs4uj$61m$1...@ger.gmane.org
Re: Whats your way of sharing data between PCs?
Am Sun, 21 Sep 2014 19:52:51 +0200 schrieb lee: > Joerg Desch writes: > >> I currently use Unison to sync the data between the notebooks and the >> NAS. > > NFS over VPN? Nope. Currently not. My first step is a solution which works in the local network. Later I would like to add my office PC too, but internet in Germany is slow (asymmetric DSL). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lvpo6v$std$2...@ger.gmane.org
Re: Whats your way of sharing data between PCs?
Am Sun, 21 Sep 2014 11:45:23 +0200 schrieb Hans: >> Unison doesn't use rsync. As far as I know, Unison uses a rsync alike >> algorithm which is bidirectional, while rsync is only unidirectional. > > Nope, rsync is bidirectional, too. Are you shure? I'm only aware of the unidirectional sync. The man page tells me this as description: Rsync is a fast and extraordinarily versatile file copying tool. It can copy locally, to/from another host over any remote shell, or to/from a remote rsync daemon. Which option enables bidirectional syncing? How are conflicts handled? I could find the infos in the man page. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lvpo25$std$1...@ger.gmane.org
Re: Whats your way of sharing data between PCs?
Am Sun, 21 Sep 2014 09:48:14 +0100 schrieb Joe: > I wouldn't have thought so, to any great extent. You can use rsync over > ssh if you're worried about the data being intercepted on your network, > but I doubt that it will be much quicker as Unison is just a front-end > to rsync. Unison doesn't use rsync. As far as I know, Unison uses a rsync alike algorithm which is bidirectional, while rsync is only unidirectional. > Some small amount of time will be saved by not updating the > display during copying, as Unison does, some will be lost in ssh > encryption. Unison is still reading much data over my WLAN. Even in "fast check mode"! So comparing 20G data takes a lng time (up to 10 minutes) even is no new / changed files where found. > The best gain will be in separating current/recent data from older data, > if your work allows it. I've though about this, but I'm afraid that I forget to start a sync in the case the older archives have changed. My first idea was a daemon which uses the inotify protocol of the kernel to get informations which files has changed. But this only works on local file systems. Changes on the server side would be invisible. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lvm5hs$ieg$1...@ger.gmane.org
Whats your way of sharing data between PCs?
Hi. I'm using Debian Wheezy on two Notebooks and one Desktop. All systems are using NFS to access a NAS. While the notebooks have all data on there local SSDs, the Desktop is working directly on the NFS share. I currently use Unison to sync the data between the notebooks and the NAS. This is very time consuming even with enabled "fast checking". I choose this solution because I need to take the notebooks with me. So I must have the data always up to date. Is anyone in the same situation? Is there a faster and more secure workflow? Thanks for sharing your ideas. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lvlvod$fjb$1...@ger.gmane.org
Re: How to mount a LUKS partiotion with Nautilus with option discard?
Am Wed, 03 Sep 2014 14:41:03 +0200 schrieb Jochen Spieker: > I have no idea. I've got two tips by G+. (1) a mount point below ~ and (2) the option x- gvfs-show as fstab option. Both doesn't change anything. > I suggested to file the bug against Nautilus because it > is the interface you are using. I will collect all infos and file a report this evening. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lu93an$m5p$1...@ger.gmane.org
Re: How to mount a LUKS partiotion with Nautilus with option discard?
Am Tue, 02 Sep 2014 23:59:38 +0200 schrieb Jochen Spieker: > This is missing the discard flag from your crypttab entry. It appears > that Gnome ignores your settings. Is it ignored by Gnome or by udisk? > Either ask upstream (i.e. Gnome people) or open a bug report for > nautilus. Are you sure that Nautilus handles mounting of discs? > I like the following pattern for bug reports: Thanks for the info. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lu66m0$30d$1...@ger.gmane.org
Re: How to mount a LUKS partiotion with Nautilus with option discard?
Am Mon, 01 Sep 2014 12:19:39 +0200 schrieb Hans: > As far as I remember (and someone may correct me, if I am wrong) if > there is an entry in fstab, the devices are not mounted by the GUI (I > guess you mean dolphin). I'm using Nautilus in GNOME. Dolphin is KDE. IMO fstab entries without the option 'auto' are visible in the sidebar could be mounted by the GUI. This seems to be not the case for LUKS entries. > Fstab is used for mounting at boot. Try to comment out the entry in > fstab, but leave the entry in crypttab. Tested. It doesn't work. There is no visible change. Even a single entry in crypttab isn't shown in the Desktop GUI. Any further tips? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lu3j9f$9m1$1...@ger.gmane.org
Re: How to mount a LUKS partiotion with Nautilus with option discard?
Am Mon, 01 Sep 2014 08:18:09 +0200 schrieb Hans: > cryptsetup luksOpen /dev/sda4 home2 > mount /dev/mapper/home2 /mnt > Thanks. The manual way on the shell is working, but I has some hopes that the GUI would be working too! An mentioned in my other followup, LUKS encrypted USB sticks are handled as expected. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lu1fo3$abc$2...@ger.gmane.org
Re: How to mount a LUKS partiotion with Nautilus with option discard?
Am Mon, 01 Sep 2014 09:48:30 +0200 schrieb Jochen Spieker: > Joerg Desch: >> >> I'm using a separate LUKS encrypted partition on my SSD, which I only >> mount after login. Since there is now way to to this with >> crypttab/fstab, I have to use Nautilus to do this. > > Hm? I don't understand why you say mounting manually is not possible > with crypttab/fstab. Just make the entries as usual and add the option > "noauto" in fstab. OK, here is my /etc/crypttab private_luks UUID=... none luks,noauto,discard And this is my /etc/fstab /dev/mapper/private_luks /media/privates ext4 user,nofail,noauto,noatime The LUKS partition is installed on a PC where several people have access! So I don't want the system to ask for the passphrase at boot time! It must aks for the passphrase after the login! If I use a LUKS encrypted USB stick, all this is done. But with a partition on the SSD, Wheezys GNOME don't do it. I don't know why. > The crypttab file supports the noauto option as well. Then > you have to run two commands for mounting the filesystem: > > cryptdisks_start $mapped_device mount $mount_point Is it possible to get this working with the GUI? > You don't need the discard option for your filesystem to run fstrim. You > only need it in /etc/crypttab. How do you tell that you "can't use > fstrim"? > Do you receive an error message when running fstrim? Yes! ioctl failes while TRIm is not supported. fstrim: /media/PRIVAT_C/: FITRIM ioctl failed: Die Operation wird nicht unterstützt > As pointed out above, this only shows the filesystem option. The status > of your LUKS device can be queried like this: > > # cryptsetup status home-decrypted /dev/mapper/home-decrypted is active > and is in use. > type:LUKS1 cipher: aes-xts-plain64 keysize: 256 bits device: > /dev/mapper/kida-home--crypt--lv offset: 4096 sectors size: > 88436736 sectors mode:read/write flags: discards > /dev/mapper/udisks-luks-uuid- is active and is in use. type:LUKS1 cipher: aes-cbc-essiv:sha256 keysize: 256 bits device: /dev/sdb7 offset: 4096 sectors size:408795136 sectors mode:read/write -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lu1fjn$abc$1...@ger.gmane.org
How to mount a LUKS partiotion with Nautilus with option discard?
I'm using a separate LUKS encrypted partition on my SSD, which I only mount after login. Since there is now way to to this with crypttab/fstab, I have to use Nautilus to do this. I'm running a regular Debian Wheezy. After clicking on the (unmounted) LUKS partition, the system asks for the LUKS passphrase and than for the admin password. Now the partition is mounted as expected. The only problem is the missing 'discard' option, so I can't use fstrim with this partition. Does anyone knows some tricks how to add discard support? This is the current output of mount: /dev/mapper/udisks-luks-uuid-... on /media/PRIVAT_C type ext4 (rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,uhelper=udisks) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lu0vib$kle$1...@ger.gmane.org
Re: How to mount a LUKS partition from within GNOME?
Does nobody have a solution for this? Am Thu, 07 Aug 2014 18:21:51 + schrieb Joerg Desch: > My configuration entries are: > > # /etc/crypttab private_luks /dev/sdb7 none luks,noauto > > # /etc/fstab /dev/mapper/private_luks /media/privates ext4 > user,nofail,noauto,noatime\ > 1 2 GNOME (Nautilus) shows me the unmounted LUKS partition. But is labeled with the size of the partition. "Clicking" on the entry mounts the partition, but I always have to enter the admin password too. After this, the partition is mounted, but the entries in fstab/crypttab are totally ignored! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lshf5j$djd$2...@ger.gmane.org
How to mount a LUKS partition from within GNOME?
I have successfully prepared a partition for the usage with LUKS. After that, I've added some entries to /etc/fstab and /etc/crypttab. Using "cryptdisks_start/stop" with "mount/umount" works fine. Now I want to be able to mount the partition manually from within GNOME. I want to have the GUI requesting the passphrase. For this reason, my entries in the configuration files uses noauto be avoid the automatic mounting at startup. My problem is, that Nautilus doesn't show an unmounted device! How do I mount a LUKS partition with Wheezys GNOME 3.4? My configuration entries are: # /etc/crypttab private_luks /dev/sdb7 none luks,noauto # /etc/fstab /dev/mapper/private_luks /media/privates ext4 user,nofail,noauto,noatime\ 1 2 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ls0g3v$6h5$2...@ger.gmane.org
Re: Different behaviour handling NFS mounts after login
Am Thu, 03 Jul 2014 02:42:05 -0600 schrieb Bob Proulx: > Joerg Desch wrote: > Warning. Using "soft" can cause silent data corruption. That's the reason I'm using "hard". > Same with _netdev. Personally I am > only using "async" and nothing more these days. "intr" is okay. "_netdev" is good for notebooks. I've there is no WLAN available, the entries are not mounted. Since NetworkManager is brain-dead ;-), I'm no longer able to mount "shares" depending on the connected network. OK, that is only the half truth, since the dispatcher scripts allows mounting, but the developer of NetworkManager have cut-off the pre-down scripts, so it isn't possible to unmount the "shares". No idea why they have done this... > But I am also not sure what you are asking. Initially you wrote: > >> Two of the machines opens Nautilus after each login. Neither the other >> installation of Debian nor a remaining MINT installations shows this >> behaviour. >> >> What's the problem here? Should I change something in the mount >> options? >> Or is this a setting within GNOME? > > So the problem is that Nautilus opens after a login? Exactly. > I don't see how > that is related to NFS. How would NFS mount options cause Nautilus to > automatically start up at login time? Me too. ;-) But I'm not sure. Joseph wrote a reply with this recommendation, so I want to give it a try. > That sems like an autostart > configuration of GNOME. If you are wanting to prevent that then I would > concentrate on looking there. OK. I want USB thumb drives to be opened automatically, but not the NFS mounts. Is this possible? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lp36r4$en0$3...@ger.gmane.org
Re: Different behaviour handling NFS mounts after login
Am Thu, 03 Jul 2014 00:12:15 -0700 schrieb Joseph Loo: >> rw,_netdev,hard,intr,user,nosuid,exec,async,auto >> > You might want to try soft instead of hard. Thanks for your tip. I will try it this evening. I'm no NFS expert and I've "created" the mount entries a long time ago. The option "hard" was added because of the weakness of my first WLAN (years ago... now it is stable). Why do you think that changing this option influences the behaviour of GNOME? Do you have recommendations for "more modern" NFS mount options? I've already removed the entries of the buffer sizes. ;-) I'm not sure if "nosuid" or "user" are still necessary. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lp324j$en0$2...@ger.gmane.org
Different behaviour handling NFS mounts after login
I've recently replaced Linux MINT on 3 machines with Debian Wheezy and GNOME3.4. All of my "shares" are mounted with NFS. For this purpose I use the following options (on all installations): rw,_netdev,hard,intr,user,nosuid,exec,async,auto Two of the machines opens Nautilus after each login. Neither the other installation of Debian nor a remaining MINT installations shows this behaviour. What's the problem here? Should I change something in the mount options? Or is this a setting within GNOME? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lp2urb$en0$1...@ger.gmane.org
Re: How do package wallpapers for GNOME in Wheezy?
some new infos (but still no solution): I've installed the package on Linux MINT 15 (or 16) and here it works as expected. After the installation of the package the wallpapers are visible inside the settings dialog. Is there a difference to the GNOME 3.4 in Wheezy? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lop9ug$s7p$2...@ger.gmane.org
How do package wallpapers for GNOME in Wheezy?
Hi. I've build a package with some of my favorite wallpapers. The package installs fine and I've created a XML file too. But the GNOME settings dialog of Wheezy doesn't show me my wallpapers. I've installed all files below /usr/share/backgrounds/joede-collection/1650x1050/ and installed the XML to /usr/share/gnome-background-properties/joede-wallpaper- collection-1366x768.xml Here is a shortened copy of the XML content. fictive_view_on_earth.jpg /usr/share/backgrounds/joede-collection/1650x1050/ fictive_view_on_earth.jpg zoom #00 #00 solid Forever-Shady.jpg /usr/share/backgrounds/joede-collection/1650x1050/Forever- Shady.jpg zoom #00 #00 solid Is there something wrong? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lof289$mbd$1...@ger.gmane.org
Installation of Wheezy on a Fujitsu Primergy Raid1
Hi, I have a Fujitsu primergy TX100 S1 and installed a bios-raid1 (LSI raid from Fujitsu - 2 disks prepartitioned into 1 primary and 5 extension disks each - done by -M). This machine used to have Lenny but an important component was destroyed so I decided to proceed to Wheezy skipping squeeze (which I do not have as netinst disk!!!) When I tried to install wheezy via netinst from CD I could not get out of the partition menue for installation of basic components ... The parted-menue shows: 1. Raid (the whole disk - no partitions so far) 2. the 1st scsi-device with all partition on that device (contains important data which must not be destroyed) 3. the 2nd scsi-device with all partition on that device (contains important data which must not be destroyed) 1st and 2nd scsci devices are partitioned the same way from the previous Lenny installation. My question: How can I proceed with the LSI raid 1 to get a functioning system again? tia for some useful hints -- = Tel: +49-177-276-3140 www.ibk-consult.de www.researchgate.net/profile/Joerg_Kampmann https://www.xing.com/profile/Joerg_Kampmann = -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5289f404.3010...@ibk-consult.de
Re: console DVD writer?
Volkan YAZICI wrote: >On Sat, 21 Feb 2009, asdf asdf writes: >> What is the "best" DVD writing solution "without GUI"? :D >wodim. wodim does not support to write DVDs. wodim is a dead fork from an extremely outdated cdrecord release where the working DVD support from the original software was replaced by something half baken. If you like to use working software, use a recent original from ftp://ftp.berlios.de/pub/cdrecord/alpha/ Upgrading to recent original software let's you also get rid of the illegal fork Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
"Boyd Stephen Smith Jr." wrote: > >> "Unfortunately Sun then developed the CDDL[1] and Jörg Schilling > >> released parts of recent versions of cdrtools under this license." > >> > >> True. > >Given the fact that attacking Sun (the largest donator of OpenSOurce > > software) is definitely FUD, we can safely ignore your post. > > I not sure how you characterize this as "attacking Sun". Is it not true > that Sun released the CDDL? Is it not true that parts of cdrtools are Using the word "unfortunately" in relation with a OSS donation is a really bad attack. Please tell me why Sun was attacked? Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
"Boyd Stephen Smith Jr." wrote: > On Saturday 17 January 2009, Joerg Schilling > wrote about 'Re: k3b & brasero don't > work, nerolinux does- works ar 2X': > >Chris Bannister wrote: > >> http://lwn.net/Articles/198171/ > > > >Everything starting with the word "Unfortunately" in this article is > > plain FUD. > > Could please take it point by point? Here's my take: > > "Unfortunately Sun then developed the CDDL[1] and Jörg Schilling > released parts of recent versions of cdrtools under this license." > > True. Given the fact that attacking Sun (the largest donator of OpenSOurce software) is definitely FUD, we can safely ignore your post. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
Chris Bannister wrote: > Maybe Jörg could comment on the below article: > > http://lwn.net/Articles/198171/ Let me answer as quick as your question was: Everything starting with the word "Unfortunately" in this article is plain FUD. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
Jochen Schulz wrote: > Joerg Schilling: > > > > As mentioned before: cdrkit is neither free nor working. > > Jörg, is there anything we can do to make you recognize the fact that > there are different opinions on that subject and that there is no sense > in trying to educate anyone on this list? You are doing yourself and > this list a disservice by repeating your sermon every few months. Jochen, is there anything that I can do to help you to understand that a straightforward obvious Copyright violation is not subject to something you may call an "opinion"? You as a user are not going to run into problems as the Copyright law allows to run software independent from whether it has been published illegally. Debian however is definitively in conflict with the Copyright law Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
"Boyd Stephen Smith Jr." wrote: > >So you are happy if someone givey you pre-alpha's and calls them "stable"? > >This sounds really strange. > > My first requirement is that the release team does not feel the need to use > the qualifier "alpha". I did not say that was my only condition. Please > don't put words into my mouth. That's strange, you happily use pre-alpha code as long as it is not called alpha? > >> >cdrkit is not working > >> > >> I disagree. Next time I burn a CD with wodim, shall I send you the logs > >> to show that wodim is working? Or perhaps post them to a public forum? > > > >This does not prove anything. There are too many cases where it does nto > > work at all (e.g. on laptops, ...). I am talking on usability and not > > whether wodim may work sometimes under specific conditions. > > I have burned on my laptop many times in the last 2 years, using wodim. > Shall > I send you logs of it working on a laptop? I can show you many cases where > wodim is working. I can show you many cases when I have used wodim, showing > that it is usable. As far as usability is concerned, wodim and cdrecord have > virtually the same interface so they have roughly the same usability.[1] This is definitely not true. Wodim does not work for many (if not most) people. This alone causes differences in usability. As cdrtools introduced _many_ new features during the past 3 years, even iff wodim would work, it did not give you the same usability. > What would convince you that wodim is working? I've offered logs, I'm not > sure what else I can offer. Or, have you simply closed your mind to the > possibility that working CD/DVD/BD burning free software other than cdrtools > exists? You cannot convince people to believe things that are verifiably wrong. http://bugs.debian.org/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;src=cdrkit;dist=unstable;repeatmerged=0 https://bugs.launchpad.net/ubuntu/+source/cdrkit Note that many of these bugs are showstopper bugs and that there are more bugreports that have been removed although they are of course present. > I prefer to use working, free software like cdrkit. See my earlier messages > for why I consider cdrtools non-free software. As mentioned before: cdrkit is neither free nor working. If you like to use free and working software, you need to use the original cdrtools. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
"Boyd Stephen Smith Jr." wrote: > >The minimum requirements one need to have on a "stable release" is that it > >does not have known bugs at the time of piublishing. > > We have different requirements for a stable release. > > >Cdrecord had 50 stable releases that match the requirements within the past > >three years. > > These do not meet my requirements for a stable release. They are explicitly > marked as "alpha" by the person/group releasing them. For me, that means > they are not stable releases. So you are happy if someone givey you pre-alpha's and calls them "stable"? This sounds really strange. > >cdrkit is not working > > I disagree. Next time I burn a CD with wodim, shall I send you the logs to > show that wodim is working? Or perhaps post them to a public forum? This does not prove anything. There are too many cases where it does nto work at all (e.g. on laptops, ...). I am talking on usability and not whether wodim may work sometimes under specific conditions. > I like to write CDs and DVDs; I use wodim (and other programs from the cdrkit > project). Unfortunately, I do not yet own a BD writer. If you like to do this, you better use working software like cdrtools. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
"Boyd Stephen Smith Jr." wrote: > On Friday 2009 January 09 09:25:31 Joerg Schilling wrote: > >There recently have been some mails from Boyd Stephen Smith Jr. and > >Johannes Wiedersich that have not been send to me, so it seems that the > >authors are not interested in a discussion. > > Actually, we are interested in discussion, but the are following the Then please follow the Nettiquette rules and send Cc:'s! > I never claimed that there were no new releases of cdrtools. I claimed that > wodim has had more stable releases since the fork than cdrtools. Anyone can > verify my claim be going to http://www.cdrkit.org/releases/ and > ftp://ftp.berlios.de/pub/cdrecord/ then counting the number of releases since > 2005 displayed. Well, face the reality: The minimum requirements one need to have on a "stable release" is that it does not have known bugs at the time of piublishing. With this contraints, wodim never had a stable release in it's lifetime. Cdrecord had 50 stable releases that match the requirements within the past three years. For wodim (better cdrkit in general), there are dozens of documented bugs that are not fixed since years. Instead the people behind wodim publish fix typos in the man pages and in the source comment in order to pretend activity. If you speak for the Debian community, then it looks like Debian is if Debian is completely uninterested in the Debian users. > cdrkit, wodim in particular, is working. I've used it many times in the last > few years. cdrkit is not working and besides the problems from the _current_ thread there are dozens of other bugs in cdrkit. Many of them are show stopper bugs as they make it impossible to use th software at all. > > Did the > > initiator of wodim intentionally introduce bugs that make "cdrkit" unusable > > in order to support closed source software? > > Doubtful. Still, Debian and the cdrkit project welcome bug reports, which > will not be ignored. Are you again ignoring reality? There is a Debian user (Paul) who cannot write DVDs because Debian does not include working software (cdrtools). Paul asked here and did not get help from the Debian cummunity. Paul did get help from me and simply going to the vanilla original software fixed his problem. If Paul makes a bug report, this will just add another bug to the long list of bugs in cdrkit but it will not result in a bugfix. People who like to write CDs, DVDs or BDs just use the original software because Debian does anything to prevent a vanilla Debian to be useful for this task. Do whatever you like but don't forget that your current habbit is anti-OSS and against Debian users. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
There recently have been some mails from Boyd Stephen Smith Jr. and Johannes Wiedersich that have not been send to me, so it seems that the authors are not interested in a discussion. Their mail contained the usual accusations: the claim that cdrtools is not free and that there is no new releases in cdrtools. As these claims have lready been proven to be incorrect, we will not go any further in trying to discuss at this level. Let me go back to the original topic. Given the fact that the initator of wodim stopped working on wodim on May 6th 2007 and started to advertize for nerolinux instead, it is interesting to read the term nerolinux in the subject of this thread. Is Debian moving to closed software like nerolinux or what is the backgrund for not distrubuting working CD/DVD/BD writing software with Debian? Did the initiator of wodim intentionally introduce bugs that make "cdrkit" unusable in order to support closed source software? Is Debian no longer interested in free and working software? The Original poster was Paul Cartwright and I had some conversations with him during the past week. First, Paul Cartwright had problems to download cdrtools and it turned out that a bug in the firewall implementation of his linksys router was the reason. After disabling the fireall for the time of the ftp transfer, he could download cdrtools without problems. Yesterday, Paul Cartwright was able to write a perfectly readable DVD using mkisofs and cdrecord at 10x speed. He did this out of the box after he send me the command line he was trying to use and I send him simething like please use these commands instead: mkisofs -o xxx.iso -dvd-video -V "video.2008" "/disk2/pauls/movies/some-name" cdrecord -v xxx.iso It turns out that it is not easy to make CD/DVD/BD recording working on Debian as _all_ related software has been modified to call the defective "genisoimage", "wodim" and similar even after the correctly working original software was made available. People could file dozens of bugreports just for these modifications. The software that he was originally using called growisofs and growisofs called "genisoimage". It is unclear whether both fgrowisofs and growisofs are broken on Debian or whether the problem is only related to the defective genisoimage program. My questions are: - Are people interested in getting a working CD/DVD/BD writing toolchain on Debian? - Is there anybody inside Debian willing to support this by doing the needed administrative work? Please note that there is a Debian cdrtools package available from the "grml" Author, so there is no need to find a Debian package maintainer for cdrtools. Also note that last Summer, Sun lawyers did an in depth license analysis on the original cdrtools source and the conclusion from Sun Legal was that there is neither a legal problem with the original software nor with distributing binaries made from the original software. Is someone likes to prove that, the Solaris Express Community Edition build 105 will be available in a few days and it will include cdrtools release 2.01.01a54 which is fairly recent. The a55 release could not be included as the build 105 snapshot date was in mid-Decedmber. Note also that before the initiator of wodim appeared at Debian, there was a good coperation. I am in hope that it is possible to correct mistakes from the past and that soon, Debian users are able again to do CD/DVD/BD writing. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
John Hasler wrote: > > The people behind wodim do not follow the conditions of the GPL and they > > do not follow the conditions in the higher worthy Urbebertrechts law. > > > Whether the name is used directly or via a symlink does not matter. The > > original names are used without permission and in addition, there are > > other Copyright violations. > > Are you threatening to file a lawsuit? If so, against who, for what, and > in what jurisdiction? It does not make sense to inform you about these details. The people who are responsible for the violations and the redistributors are informed, they know that they are in conflit GPL and Urheberrecht and that cdrkit cannot be legally distributed. I try to avoid suing people but I am not willing to tolerate violations forever. The related people need to understand that they need to follow the lawful rules. If they don't, they will be sued at some time Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
"Boyd Stephen Smith Jr." wrote: > On Wednesday 2009 January 07 10:23:52 Joerg Schilling wrote: > > Boyd Stephen Smith Jr. wrote: > > The problem with wodim is that it is not a real fork. > > A fork is something that is supported, > > Not true. "In software engineering, a project fork happens when developers > take a copy of source code from one software package and start independent > development on it, creating a distinct piece of software." -- The people behind wodim did not start an independent development. All they did was to take an old source, remove the pefectly working build system, replace it by something that is broken and add some other bugs to the source. After 8 months of speudo activity, wodim is dead since May 6th 2007. > > but wodim is unsupported. > > Also not true. Debian supports all the software shipped in main, and > provides > best-effort support to software shipped in contrib and non-free. In > addition, wodim's upstream is still very much alive. See above, there is no support. Bugs reports are either marked as closed altough the bug still exist or they are ignored. This is not what I would call "mainteied". Wodim is dead since May 6th 2007. > > Wodim is in conflict with both GPL and Urheberrecht (*). > > > > *) http://www.gesetze-im-internet.de/urhg/index.html > > > > Wodim (cdrkit) cannot be legally distributed > > I disagree and I don't think either of us can point to established precedent. > > I also don't think there has been any legal analysis (meaning: done by a > lawyer as legal advice) done on the particulars. Well, I did discuss the problems with a German specialized lawyer who is also active on the OSS community and it turns out that I am of course able to sue the people behind wodim for more than violation. On the other side, there is no professional that supports the claims/FUD by the "wodim people" against me. All those claims are done by laymen and these people did not even give evidence for their claims. > Wodim identifies itself in both documentation and at runtime as a separate > work form cdrecord. That's all that is required to satisfy the GPL. I can't > speak to satisfying the Urheberrecht, as I do not speak the original > language. The GPL gives you the right to use the code if you follow the conditions. The GPL does not give you the right to use the original name for a fork. The people behind wodim do not follow the conditions of the GPL and they do not follow the conditions in the higher worthy Urbebertrechts law. Whether the name is used directly or via a symlink does not matter. The original names are used without permission and in addition, there are other Copyright violations. > > Cdrtools (the original) had 55 releases in the last 100 months. > > All labeled "alpha", not "stable". I was very clear that I was only counting > stable releases. All those releases are more stable than any of the wodim releases, so what? > > >Wodim certainly had and has it's share of issues, but so has cdrecord. If > > > > This is a funny claim. Please tell me about a single problem with cdrecord. > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;package=cdrecord > > Anything with a bug number < 350738 is or was a problem with cdrecord. Wrong: none of those reports applies to the original cdrtools source code as Debian has a 4-5 year history of distributing broken modified versions. Even if a single bug report _could_ have applied to cdrtools at the time it was made, the bug has been fixed years ago in thge original but is still present in wodim. I asked you to name me a single bug in the original cdrtools and you seem to be unable to point to such a problem - thank you! > > I am not sure about your intention here. If you care about legallity, you > > cannot use wodim, so what is your point? > > I disagree. I personally have no doubt that wodim is legal. I personally do > doubt that distributing binaries of cdrecord is legal. I know that wodim is not legal and my laywer supports this. As mentioned above, there is more than one way to sue the people behind wodim because there is more than one violation in wodim. > > The original software is of course free software. It seems that you are in > > doubt because you listen to the wrong people ;-) > > Other than you, I couldn't name anyone I listen to. Instead I listen to the > argument, independent of the person making it. Your arguments seem to be on > more tenuous foundation, and counter-intuitive. That said, some legal > decision on the matter could demonstrate effectively that I am quite wrong. You sound confused. > Both the author
Re: k3b & brasero don't work, nerolinux does- works ar 2X
Eduardo M KALINOWSKI wrote: > Joerg Schilling wrote: > > Debian on the other side violates GPL and Urheberrcht with the cdrkit fork. > > > > I've seen you say that several times on this thread (an in other times), > but I've missed the explanation of exactly why did this allegedly > happen. I also did not find it in the cdrecord site, but I confess I > only looked briefly there, as there is too much text there. :-) See the cdrecord web page for the information you asked for... > So would you care to briefly explain why you say the GPL was violated? > > Secondly, did you contact the FSF about that at > license-violat...@gnu.org ? Did they say anything? Eben Moglen knows about both, the Debian violations and the GPL/Copyright violations done by the FSF when using code from the cdrtools project for FSF projects. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
John Hasler wrote: > Joerg.Schilling writes: > > This seems to be an interesting claim. > > > If you only believe a lawsuit in court, then you would obviously not > > believe the > > claims from Debian. Nice to see! > > Debian is accusing no one of copyright infringement. In case you did not get it: Debian acuses me for creating an alleged GPL problem. Debian on the other side violates GPL and Urheberrcht with the cdrkit fork. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
John Hasler wrote: > Joerg.Schilling writes: > > On the other side, Debian introduced problems with GPL and Urheberrecht > > in the fork so wodim/cdrkit cannot be legally distributed (see above). > > When and in what court was your lawsuit filed? Where can we read the > decision? If no suit has been filed, where can we read the opinion you > obtained from an attorney with appropriate credentials and qualifications? This seems to be an interesting claim. If you only believe a lawsuit in court, then you would obviously not believe the claims from Debian. Nice to see! When will Debian continue to ship the official non-crippled software? Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
Boyd Stephen Smith Jr. wrote: >Joerg doesn't like wodim, because he doesn't really believe people should be >able to fork his code. (He is the primary developer of cdrecord.) His This is wrong. The problem with wodim is that it is not a real fork. A fork is something that is supported, but wodim is unsupported. This pseudo fork has been initiated by a person that soon stopped working on the "fork" and then started to advertize for Nerolinux. Please explain me the background for this kind of habbit! >assertion that wodim violates the GPL and Germany's "Author's Rights" (I >can't spell the original German word.) does not appear to be supported by >precident or even trained legal analysis of the specifics. I don't think >wodim can be reasonably held to hurt Joerg's reputation or integrity. Wodim is in conflict with both GPL and Urheberrecht (*). *) http://www.gesetze-im-internet.de/urhg/index.html Wodim (cdrkit) cannot be legally distributed >Providing symlinks from the old binary names to the new ones, and giving >similar output are, in fact, required for interoperability. The problem is that many people still believe that they have a real cdrecord when they call "cdrecord" and this is not true. These people then are confused when features that have been introduced three years ago are missing in their (expected to be recent) "version" of cdrecord. >That said, wodim was forked from a "really old" version of cdrecord (the last >version that was clearly licensed under the GPL). Of course, browsing >Joerg's site shows you that cdrecord hasn't had a stable release in 4.5 years >and wodim had a stable release 2 months ago. Cdrtools (the original) had 55 releases in the last 100 months. Wodim had 7 releases in the same period of time and there are still more bug inside than the source they are based on. >Wodim certainly had and has it's share of issues, but so has cdrecord. If This is a funny claim. Please tell me about a single problem with cdrecord. >either (a) you don't intend to distribute cdrecord OR (b) you agree with >Joerg's interpretation of the GPL, I strongly encourage you to install >cdrecord from Joerg's site. If it works and wodim doesn't, there's clearly a >bug in wodim, and you should file one. IMO, Joerg interpretation is >incorrect as he assumes "source code" (which is a defined phrase in the GPL) >means something other than what it is defined to mean. I am not sure about your intention here. If you care about legallity, you cannot use wodim, so what is your point? But if you are talking about bugs, guess from where I know about the long list of bugs in wodim? I did just read the bugtracking systems of the Linux distributors that publish wodim. There are dozens of bugs that are documented since more than two years and there is little hope that they will ever be fixed. On the other side, the typical time to fix a bug in the original software is 1-2 weeks. For the same reason, there are no known issued with the original software. >IANADD, but I read the archives: >debian-legal also doesn't agree with Joerg's interpretation of the GPL and >is "in the business" of distributing software. They feel that distributing >binaries of cdrecord produced from the source after the fork is not allowed >by copyright law, and would expose Debian to legal action. However, they >would like to continue providing cdburning software to Debian users. Since >Debian could not convince Joerg to change the licensing to something they >felt they could distribute, they had to begin a project to make cdburning >software, which brought us wodim. Debian legal is a discussion board of laymen, I gave up having a useful discussion with them. On the other side, Debian introduced problems with GPL and Urheberrecht in the fork so wodim/cdrkit cannot be legally distributed (see above). >Personally, I use wodim and will continue to use it, because I don't doubt >it's status as free software. I have some doubt that cdrecord is free >software; I don't doubt Joerg intends it to be free software, but I think his >particular love of the CDDL causes problems. The original software is of course free software. It seems that you are in doubt because you listen to the wrong people ;-) Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
Paul Cartwright wrote: > > We had a server outage last weekend. If you still have problems, ask your > > ISP for help, thousands of people are using ftp.berlios.de without any > > problem. > > > > Jörg > > I am having problems getting to this site and downloading updates: > > http://freshmeat.net/projects/cdrecord/?branch_id=1139&release_id=287422 > > when I try to download the file: > http://freshmeat.net/redir/cdrecord/1139/url_tgz/cdrtools-2.01.01a55.tar.gz > I get timeouts. > is it my setup, or are you guys blocking belios.de sites via ftp? > I can get to the site, but can't download the files. We are blocking only IP addresses for some time if an IP address was used to run a denial of service attack against on of our servers. If you can go to our sites, I am asuming that you get a directory listing. So you seem to have a local problem at your side. Ftp uses _two_ port numbers and the usual problem is that the firewall at your side blocks the second port number. This usually can be circumvented by using passive FTP mode. As a general hint: do not run more than 3 downloads at the same time. I recommend you to ask your local sysadmin or your ISP for help. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
Please keep me on the CC! Paul Cartwright wrote: >> I recommand to have a look at the latest release (2.01.01a55) in >> ftp://ftp.berlios.de/pub/cdrecord/alpha/ >> make sure to be root when calling make install, to allow cdrecord to be >> installed suid root as needed on Linux. >I have a48 >ftp.berlios.de has been a peoblem for me to connect to, even in passive mode, >it is timing out.. We had a server outage last weekend. If you still have problems, ask your ISP for help, thousands of people are using ftp.berlios.de without any problem. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b & brasero don't work, nerolinux does- works ar 2X
Chris Bannister wrote: >Are you sure it it using the "new cdrecord"? What do you understand by "new cdrecord"? wodim has been created from a very old version of cdrecord by adding new bugs and by changing things in a way that makes wodim be in conflict with the GPL and the Copyright law. The mature DVD support from cdrecord (introduced February 1998) has been replaced by half baken code in wodim without reason. As a result DVD support in wodim not really existent. The clean and generic SCSI low level support (in libscg) has been modified, resulting in a low tolerance on Linux kernel modifications like e.g. introducing libsata. Tests for missing root privileges, done early in the original cdrecord code have been removed resulting in code that looks as if it could work without root privileges, but this just lets wodim fail later with unclear reasons. There are no real bug fixes and there is no development in wodim. Wodim still has more bugs than the original cdrecord it was based on. Since May 2007, the initiator of the fork did not work on a single change but rather advertizes for the closed source software "nerolinux". ... >It would be a shame if wodim wasn't "doing its job for Debian Users." "would" seems to be an inapropriate word in this relation. It _is_ a shame that Debian does not come with the bug-free original software but with a replacement that causes many problems for the Debian Users. Paul Cartwright wrote: >no, how would I know? the man page doesn't show any options for cdrcord vs >wodim.. The people behind wodim claim that there are no differences and for this reason, they don't document. If you compare the very old source, wodim was based on with a current cdrtools source, you will find that nearly 50% of the code has been replaced or added during the past three years. There are many new features in the original software and there is a lot more tolerance against firmware bugs in drives. I recommand to have a look at the latest release (2.01.01a55) in ftp://ftp.berlios.de/pub/cdrecord/alpha/ make sure to be root when calling make install, to allow cdrecord to be installed suid root as needed on Linux. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: k3b won't burn, nerolinux will
>Configuring Cdrkit, version 1.1.9 >CMake Error at wodim/CMakeLists.txt:18 (MESSAGE): > Error: found a Linux system but no libcap header. Install libcap-dev. Thanks! this is another hint that wodim is in conflict with the GPL. Some notes: k3b works best with cdrecord as cdrecord is well maintained software. I recommend you to get a real cdrecord from ftp://ftp.berlios.de/pub/cdrecord/alpha/ the latest release is cdrtools-2.01.01a55.tar.bz2 Make sure to call "make install" as root to install cdrecord suid root. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: cdda2wav default device customization
>> $ cdda2wav dev=/dev/hdc -t 4 >>. How can manage things so to omit the device specification? > when I do: icedax -t 4 (now (in debian) cdda2wav is a symbolic link to > icedax) > I get: > icedax: No such file or directory. Cannot open '-1'. Cannot open SCSI driver. > icedax: For possible targets try 'wodim -scanbus'. Make sure you are root. > Use the script scan_scsi.linux to find out more. The feature that allows cdda2wav to work without dev= has been introduced in Summer 2006. As the questionable fork called "icedax" is based on a cdda2wav source that is much older, it cannot support this feature. Note that is is a bad idea to use something like dev=/* as any dev=parameter that contains a slash tells cdda2wav to use the low quality OS based ioctl interface instead of the SCSI based implementation from cdda2wav. For a correctly working cdda2wav just compile and install a recent cdrtools from ftp://ftp.berlios.de/pub/cdrecord/alpha/ Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wodim does not write DVD
>If the inclusion of cdrecord into GPL-strict Linux distros were >important to you (I'm assuming it ain't, why should it) you could >just GPL it and take the wind out of the stupid Debian maintainers' >sails. After all it's you who insists that the CDDL and the GPL are >compatible. It seems that you are not well informed about the license used on Linux distrbutions. Well, it may be that you _never_ use a GUI on Linux but this is highly improbable A big part of the code (if not a majority) of a complete Linux distro is under a more free license than the GPL, as is cdrecord. Some people may whine if they read that a former GPLd package converts to a more free license but a license change is the right and the privilege of the authors ;-) People who do not contribute (like the Debian people that took the cdrecord code and created wodim without adding Copyrightable own parts) should know that they need to follow the Authors. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wodim does not write DVD
>Fixating... >Errno: 0 (Success), close track/session scsi sendcmd: no error >CDB: 5B 00 02 00 00 00 00 00 00 00 >status: 0x2 (CHECK CONDITION) >Sense Bytes: 70 00 02 00 00 00 00 10 00 00 00 0E 04 08 00 80 >Sense Key: 0x2 Not Ready, Segment 0 >Sense Code: 0x04 Qual 0x08 (logical unit not ready, long write in progress) >Fru >0x0 >Sense flags: Blk 0 (not valid) operation 0% done >cmd finished after 0.002s timeout 1000s >Fixating time:0.196s This is a result from incorrect device handling by wodim. As you see, wodim does not support to write DVDs, conclusion: Just don't use unsupported software like wodim. Instead use recent maintained original software from: ftp://ftp.berlios.de/pub/cdrecord/alpha/ Cdrecord correctly writes DVDs since 10 years. Wodim has been created by some people in order to harm free software development. These people don't care whether the users of the software they publish have problems Wodim has been created from a 2.5 year old version of cdrecord. The mature build system has been replaced by something of questionable quality. The mature DVD support code has been ripped off and replaced by something half-baken... There was 8 months of speudo activity in the "project", but it is dead since nearly 9 months now. BTW: make sure to install cdrecord/readcd/cdda2wav suid root and take care to also replace the broken Debian variant of mkisofs by the official code. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Burn CD
Steve Kemp wrote: > Please stop feeding the troll. Well, it seems that you did also feed this troll. Sometimes it is hard to stay quiet, in special if someone publishes incorrect claims about free software. I believe it is important to post real numbers after someone tried to lower the number of bug reports for "cdrkit" in order to make people believe "cdrkit" is not full of bugs. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Burn CD
> Yes, I can see that the Debian community is having an absolutely > terrible time trying to get wodim to work. Six "Important bugs." Nice trolling attempt let me forward _unedited_ real numbers instead of your fake: Outstanding bugs -- Important bugs; Patch Available (1 bug) Outstanding bugs -- Important bugs; Unclassified (12 bugs) Outstanding bugs -- Normal bugs; Patch Available (1 bug) Outstanding bugs -- Normal bugs; Unclassified (28 bugs) ... The bug list contains system freezes, infinite loops, core dumps, completely hosed up ISO-9660 filesystems and more nasty bugs. All these problems go away if you upgrade to a recent original cdrtools. Most of the above problems have _never_ been in the original software. If you like to compare, look at: https://bugs.launchpad.net/ubuntu/+source/cdrtools/ It contains one bug that really is a linux kernel bug and 2 packaging bugs that are not related to the software itself. Compare with: https://bugs.launchpad.net/ubuntu/+source/cdrkit 25 bugs Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Burn CD
> > The real problem is a problem caused by the fact that the people > > who "created" the wodim "project" don't like to cooperate in a way > > that results in quality. I cannot accept patches that don't fix > > the problems they are intended to fix but introduce bugs instead. > Hey Joerg. Surely, from a software development viewpoint, that's > quantifiable, yes? Are there any pointers to the list of bugs? I'm > not up to date on the situation, sorry. I'll go dig into > bugs.debian.org and see what I can learn. As Debian user, you sould know where the bug replrts are and able to read them... For a short review on the problems, you may read this: http://cdrecord.berlios.de/private/linux-dist.html > > 2) rip off the working build system and replace it by > > something broken > Debian builds broken installers? I think the rest of the Universe > will disagree with you on that. If you don't know the difference between an installer and a build system, I don't know how to help you - sorry. Your other claims have no relation to my text either, I don't believe it makes sense to reply to them separately. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Burn CD
>> What's stopping cdrecord from being in Debian alongside wodim? > Its license (mix). Many people see various problems: > http://weblogs.mozillazine.org/gerv/archives/006193.html > http://lwn.net/Articles/195167/ > http://lwn.net/Articles/199061/ > He is mixing CDDL with GPL code and even has invariant sections in GPL Please don't repeat lies and FUD! Cdrecord is 100% CDDL and there are no invariant sections. The text quoted in http://weblogs.mozillazine.org/gerv/archives/006193.html is a text that has been added as agreed on with the Debian maintainers in order to fend a GPL violation from SuSE. The two other quoted articles verify that lwn is an enemy of OSS, it is pure FUD. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Burn CD
> Wodim is nothing but a fork of a quite old version of cdrecord and, as > far as I know, only exists inside Debian. The main reason for this fork > are a dispute over Jörg Schilling's (cdrecord author) licensing and (at There is a lot of missinformation spread from a few Debian people. These people now claim that there is a license problem but they started the dispute by attacking the cdrtools project _before_ I changed the license. The license change was a reaction on these attacks. Later these Debian people started to claim that there is a license problem with the original project. There was (and still is) a lot of FUD spread by these people. It makes no sense to try commenting this in detail. Let me give a short comment on the claims: These Debian people missinterpret the GPL and if you follow their interpretation, wodim would be definitely violating the GPL. If you use an GPL interpretation under that wodim is legal, cdrtools is of course also legal. The real problem is a problem caused by the fact that the people who "created" the wodim "project" don't like to cooperate in a way that results in quality. I cannot accept patches that don't fix the problems they are intended to fix but introduce bugs instead. > However, from a user's point of view, wodim is a drop-in replacement for > cdrecord as a CD (and DVD?) burning application. It works almost Given the fact that wodim misses a lot of features that are supported by cdrecord since a long time and given the fact that wodim is completely unable to talk to the drive under some conditions (e.g. suse 10.2 on a IBM laptop), I don't see wodim as a "drop in replacememt" > exactly, if not better in some respects, like cdrecord did a few years > ago (I don't know which version of cdrecord wodim is based on). On the Let me give you a simple explanation that verifies that your claim is wrong: wodim does not implement a single feature that cdrecord did not already implement _before_ wodim came up in September 2006. > other hand, wodim doesn't appear to be actively developed anymore, only > maintained. But since I have never had any problems with it, I don't > care very much. Wodim is neither developed nor maintained. It replicates the same stages as a similar "fork" from 2001: 1) declare a license problem 2) rip off the working buid system and replace it by something broken 3) the code does not even work on Linux on x86 anymore 4) fix the bugs introduced by the build system change 5) stop working on the code after 80% of these bugs have been fixed. Debian lists more than 60 important bugs for the project. None of these problems has been fixed during the past 8 months. If wodim was still maintained, I would expect to see bug fixes. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Burn CD
>Hello, that is apparently a long story if you start to read into it. It >has somenthing to do with licensing and philosophy. As far as I can tell The story has nothing to do with licensing or philosophy but with the missing will for quality oriented collaboration with the Author. The attacks against the cdrtools project started after I rejected to integrate a patch into the official source because it did not solve the problem but instead added bugs. >from a user standpoint, the programs appear to be almost pin for pin >from the command line as far as options and what not. Also if your sure >that the device your trying to write to is a burner, I would create a >symbolic link called "cdrw" in your /dev directory to that specific >device file. It keeps the fudge factor down, and keeps you from >declaring the device in your command. Or, wodim from trying to guess the >device. You do not need to play these silly /dev/ games if you use the original cdrecord. If you only have one drive (this should be the case for > 95% of all users), simply omit the dev= parameter and cdecord will automagically find your drive. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Burn CD
>Ok, I am going to install wodim (I've never used it, may take me days >to learn it). Years ago, seems everyone used cdrecord for burning CD. >Is it in now days that the wodim is more popular than the cdrecord? Why do you believe that an extremely outdated version from cdrecord where somebody even added bugs could become more popular than the official maintained software? If you don't know this, wodim _is_ an extremely outdated cdrecord where some people added bugs that never have been in the original. The answer is that some Linux distributions try to force their users to use the defective fork instead of the original because they don't like to cooperate with the author. Get a recent original from ftp://ftp.berlios.de/pub/cdrecord/alpha/ and make sure to install cdrecord/readcd/cdda2wav suid root. Note that even the mkisofs variant from the fork (called genisoimage) is full of nasty bugs that cause filesystem inconsisties. Linux may ignore these filesystem inconsisties but if you like to use your media on other platorms or even with future Linux versions you should prefer maintained original software. The "cdrkit" project is dead since more than 8 months and it had only 8 months of speudo activities do not bet on a dead horse. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CD burnt in sid unreadable on windows
>I have been using the command: > mkisofs -J -v -l -r -o file.iso directory > to create an iso image for burning to cd. Never had any problem with it > until recently when a couple of my friends started complaining that they > were unable to read those cds in windows. > Upon investigating, I found that 'mkisofs' has been replaced by > 'genisoimage' and 'cdrecord' by 'wodim'. Also, > "isoinfo -f -R -J -i image.iso" produces the following output: > === > ../ > **BAD RRVERSION (0) > **BAD RRVERSION (0) > / > === > No files are listed. If I burn the iso, I am able to mount the cd and It is unlikely that the original software has this problem. If you read the Debian bug list for 'genisoimage', you will find several bug Joliet related bug reports that are unique to the fork. > read the files without any problem in linux. A google search for the > error message took me to: > https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/57796 This is not related mkisofs but to Apple software and the Linux kernel. > but it appears to be unrelated to my experience. > What should I do to ensure that my cd is readable on both linux and windows? Go back to maintained recent original software. ftp://ftp.berlios.de/pub/cdrecord/alpha/ The latest snapshot usually is in the "schily" source consolidation at: ftp://ftp.berlios.de/pub/schily/ Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: choice
> > The CDDL is a free software license that gives more freedom than the GPL > > does > > and it is definitely accepted even by Debian. > It's accepted by Debian? I've never seen any consensus that it's Of yourse it is and if you really care, you of course have no problem to find the related mails in the net! > DFSG-free, and it's certainly not GPL-compatible, since AIUI it includes > restrictions that the GPL doesn't (or at least the GPLv2, I don't know > about v3). And AFAIK there are no CDDL packages in Debian ATM. What > makes you say that it's "definitely accepted"? Try to inform yourself from serious sources... The CDDL does not restrict the code, the GPL hovever has some restrictions that prevent you from using GPLd code from within CDDLd (or any other license) projects. As the GPL is an asymmetric license, it allows to use CDDLd code to be used inside GPLd projects! When people write that CDDL & GPL are incompatible they mean that they are not _fully_ compatiple because of restrictions in the GPL. Not fully compatible means: you need to check your specific case to find out whether it is possible or not. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: choice
> do not make me out for a liar without any proof from your side. in > intended to send you a bugreport after conclusive trials: i still do > *when i have time*: i am a working man with a rather large family. I do not call you a liar, I just explain that it is impossible to deal with unspecific claims for problems. You did talk about problems writing cdroms and compared it to growisofs. Well, growisofs does not support to write CDs. And growisofs used mkisofs which is from cdrtools. I have no problems to comment specific reports, I cannot with unspecific ones. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: choice
>dvd+rw-tools: > .allways success. just curious after all the things schily writes on > his website about wodim ao. am a kind of practical. found out that > schily's latest beta of cdrecord on my machine gives unsurmountable > problems: destroyed without a warning two brandnew cdroms. the last > point is the immediate reason for asking. Free software authors like me unfortunately need to live with useless claims like this one :-( The fact that the person did not give _any_ hint on what happened makes his claim extremely unreliable/unbelievable. Just compare https://bugs.edge.launchpad.net/ubuntu/+source/cdrtools/ with https://bugs.edge.launchpad.net/ubuntu/+source/cdrkit to understand realiability of cdrtools and cdrkit. I am of course _always_ open to real bug reports. This can be verified that Ubuntu currently has not a single bug against cdrecord. Bug # 13729 is a Linux kernel bug and all other bugs listed for cdrtools are going to be closed in a week as they are related to bugs that have been fixed within the last year but not been verified again on Ubuntu. >You gave the answer yourself. I don't know about cdrecord vs wodim etc., > but what Schily writes about debian is plainly not true. He changed the > license to be incompatible with DFSG, so debian didn't have another > choice but to fork. This is another lie that is often spread The CDDL is a free software license that gives more freedom than the GPL does and it is definitely accepted even by Debian. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord problem
>I have both cdrecord (Cdrecord-Clone 2.01.01a01) and wodim (1.1.6) on my >Sarge system. I'm using kernel 2.6.22 right now. This is a very very old version of cdrecord! It is definitely unable to work around the bugs in a Linus-2.6 kernel. Use a recent version of cdrecord http://cdrecord.berlios.de/old/private/linux-dist.html#packages Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord problem
>"I have an Etch box with a linux-image-2.6.18-5-k7. All works well but > wodim -devices > Beginning native device scan. This may take a while ... > wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT >Apt-get install wodim confirms I have the latest release. I have also >run apt-get dist-upgrade but still get the same result from wodim -devices. >What's wrong? >" >The problem is still unsolved. Do not expect this to be fixed in wodim. Wodim was an attempt to harm free software at the expense of the users. The first 8 months, there was some speudo acticivies but since 4.5 months it is dead. >linux-image-2.6.18-5-amd64 kernel, a Lite-On DVDRW drive and a CompUSA >CD_RW drive.With the linux cdrecord (wodim) I get the wodim: >Invalid argument. Cannot Set SG_SET_TIMEOUT message. With the >original cdrecord the cdrecord -scanbus finds both drives immediately >but when I try to burn a cd neither works. If I specify the Lite-On >drive there are grinding noises and, after several delays, most of the Did you use a recent cdrecord version? Recent is 2.01.01a35 and the old versions (including wodim) you find on the non-cooperative Linux distributions do not include workarounds for the bugs in recent Linux kernels. http://cdrecord.berlios.de/old/private/linux-dist.html#packages If you did never compile software, you may try to use the Ubuntu binaries... Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wodim:Can't Set SG_SET_TIMEOUT
> I have an Etch box with a linux-image-2.6.18-5-k7. All works well but > >wodim -devices >Beginning native device scan. This may take a while ... >wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT > > Apt-get install wodim confirms I have the latest release. I have also > run apt-get dist-upgrade but still get the same result from wodim -devices. > What's wrong? Well, you are using wodim instead of cdrecord. Wodim is broken with respect to many reasons. Read: http://cdrecord.berlios.de/new/private/linux-dist.html#problems for more information, you want to read http://cdrecord.berlios.de/new/private/linux-dist.html completely. All known issues that are not kernel related will go away if you upgrade to the free original project. Make sure to install cdrecord suid root. If you are looking for a binary packet, look here: http://cdrecord.berlios.de/new/private/linux-dist.html#ask Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CLI tools for checking out CDROM drive
>I only asked the question, as I thought there might be a diagnostic tool that >could interrogate the cdrom drive to see if all was ok. ># cdrecord --devices seems to show the drive as available. Cdrecord does not have a --devices option: Calling this commandline will pass "ices" to the dev= option. The correct commandline is: cdrecord -scanbus If you do not get an error mesasage with cdrecord --devices, you are using a fake program but definitely not cdrecord. Cdrecord is here: ftp://ftp.berlios.de/pub/cdrecord/alpha/ Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [OT] How much open is OpenSolaris?
> From time to time I grab a diferent OS to install and try my hands at >it. This time was OpenSolaris. The thing is, at some point in the >install, OpenSolaris throws a license at my face that doesn't seem open >at all. I can run the software, but I can't redistribute, copy, etc. I >am no law expert, but that license doesn't seem really open or free. You did confuse terms. I don't know what you did install (most likely Solaris 10 or Solaris Express - the latter is the Solaris 11 betas) You did not install OpenSolaris, you simply can't as you cannot install "Linux". You did rather install a Solaris distribution. If it shows something like: #uname -a SunOS opt 5.11 snv_xx i86pc i386 i86pc then the Solaris distribution you did install was OpenSolaris _based_. OpenSolaris is (in contrary to Linux) a complete OS like e.g. FreeBSD, it is however not a distribution that may be installed. You need to add a few things even to make a simple installable OS distribution. Sun Solaris is free but not as free as "free beer" as you need to pesonally aggree on the license (which is needed because Sun still needs to pay for some of the added software). Sun still gives you more "freedom" than e.g. Intel as Sun allows you to compile software you like to sell using the Sun Studio Compiler, Intel does not ;-) The Sun Studio compiler will be OpenSource in the near future, the Intel compiler most likely not. There are other OpenSolaris based distributions (e.g. SchilliX) that add different code in order to make an installable distribution. For this reason SchilliX is free software _and_ completely freely redistributable. Although you are not allowed to redistribute Sun Solaris, you still may do anything you like with Sun Solaris, you may even use it for commercial purposes. >As far as I could tell, at least grub and (a javified version of) gnome >are free, and OpenSolaris is using it. OpenSolaris uses an enhanced version of grub (Linux boots from the Solaris grub, but Solaris does not boot from the unmodified grub found on Linux distriibutions). OpenSolaris does not include gnome, Sun Solaris does. Sun is the biggest contributor for the gnome project, do you see a problem? >are free, and OpenSolaris is using it. Maybe it uses other free >software. So, doesn't that license conflicts with the gpl? The Debian distribution uses a lot of free software from Sun. In fact, 28% of the Debian distribution is from Sun (3x more than RedHat contributed and 5x more than IBM contributed). Do you see a licence conflict in Debian? >Its not to flame Sun, I know the company has contributed a lot with the >community, and many folks respects them. Just trying to get things clearer. If it helps, OpenSolaris is a really free project. Sun did follow my advise from November 2004 and we now have a OpenSolaris constitution as well as a OpenSolaris Government Board. OpenSolaris is not controlled by Sun but by the OGB. This makes OpenSolaris easier to deal with than the Linux Kernel that depends on a single person that controls what goes in and what not. The CDDL (used by OpenSolaris) is a license that is accepted as doubtlessly free by the OSS community. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Tool to monitor system downtimes?
On 3/28/07, Ron Johnson <[EMAIL PROTECTED]> wrote: Parse this single line file: /proc/loadavg. Thats what I already do in the perl program I wrote, in order to get the latest load (first number is the average per 1 minute)... Is there anything else you want to tell me, something that I missed? Anyway, it seems that there is not such a tool. cacti and snmp seem to be complex, the program from Hugo seems to be for a slightly different purpose. All are not command line oriented. QUESTION FOR ALL OF YOU: Would anyone find it benefitial for them what I have in my mind (see first email)? If yes, I would continue work and try to put together a debian package one day. Best regards, Joerg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Tool to monitor system downtimes?
On 3/28/07, Roberto C. Sánchez <[EMAIL PROTECTED]> wrote: Perhaps something SNMP-based? Hmm I have briefly looked at that now, but it seems to be quite an overkill for what I want to archieve, or am I wrong? For system traffic monitoring I use "vnstat" at the moment, which is a very small and very easy to install and use. I am looking ideally for something as easy as that :-) Joerg
Tool to monitor system downtimes?
Hi all, is there a simple tool to monitor high system loads and outages in debian? For me, it would be completely sufficient if there would be a tool that samples every minute or every few minutes (e.g. in a cron job) the system load and reports any issues to the user in a simple way like this: day > load 5 | > load 10 | > load 15 | DOWN +-+-+-- 26.01. 6.31% | 1.20% | 0.53% | 0.00% 27.01. 6.31% | 1.20% | 0.53% | 0.00% 28.01. 6.31% | 1.20% | 0.53% | 0.00% 29.01. 6.31% | 1.20% | 0.53% | 4.43% 30.01. 6.31% | 1.20% | 0.53% | 0.00% +-+-+-- Average: 6.31% | 1.20% | 0.53% | 1.31% Purpose is to get an overview about the "performance" of the server provider in case of "sandbox" vservers, so where I would not be aware of any issues like the server is not available some hours during nighttime for example. I have started writing such a program in perl, it works great but monitors only real downtimes at the moment, so not by system load as the figure above indicates. Best regards, Joerg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
