June 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Watching videos in openSUSE 12.3
by James Knott 12 Jun '13

12 Jun '13

I occasionally watch videos with my computer and use my notebook computer to display on my TV via HDMI. I have noticed two issues. One, the desktop will blank out after a while and I have to press a key to bring it back. The other is when I use HDMI to carry the audio, I have to reconfigure PulseAudio to switch the audio from the internal speakers to Digital Stereo output. On Windows, the screen does not blank when playing a video and the audio is switched automatically to HDMI. Is there any way to configure openSUSE to behave in a similar manner as Windows. The audio switching is a minor inconvenience, but the screen blanking is da*n irritating, especially when watching a show that runs a couple of hours. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 19

[opensuse] grub2 and xen guests ?
by Per Jessen 12 Jun '13

12 Jun '13

Any known issues in using grub2 with a xen domu? I tried installing 12.3 on a xen guest and chose grub2 as the bootloader (it defaulted to grub1). The 2nd phase doesn't start now, the xen bootloader script pygrub can't find the grub2 config. -- Per Jessen, Zürich (14.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] purging old kernels
by Peter 12 Jun '13

12 Jun '13

I've just run into the problem of my /boot partition filling up due to multiple kernel versions, but I don't understand how to resolve it. As with all my openSUSE installations of the last few years I allotted only about 125MB to /boot having previously read that that was more than sufficient, and I've never seen any official recommendation to the contrary, but some googling now shows me that the kernel multiversioning will likely require a fair bit more space than that, which I cannot do easily given the partioning layout. I looked at the notes on this page: http://lizards.opensuse.org/tag/kernel-update/ and thought of removing the 'latest-1' element from the line 'multiversion.kernels = ' since my currently installed kernel seems to be okay. After a reboot nothing is removed from /boot. The above section in zypp.conf talks about creating a directory for multiversion definitions, but I don't know if the example file it shows can really be named 'example' or something else, and don't wish to try in case I cannot reboot. So I tried commenting out the 'multiversion = provides:multiversion(kernel)' line above that. Again, a reboot makes no difference. It seems to suggest that a change would only be applied after a kernel update, but that could take months, besides which the partition is already 100% full so a new kernel likely won't install successfully anyway. How can I purge at least one older kernel (there are currently 3) directly? There's no facility in YaST software management. I could merely remove some files in /boot that wouldn't touch other files related to those kernels and is surely not a good idea. What is the proper way to go about this? Cheers, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 22

[opensuse] new network interfaqce naming scheme
by Per Jessen 12 Jun '13

12 Jun '13

This new network interface naming scheme is going to drive me up the wall :-) With 13.1 M1 : system A: "enp13s0" and "enp14s0" system B: "enp3s1f0", "enp3s1f1", "enp6s2" -- Per Jessen, Zürich (12.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

15 62

Re: [opensuse] purging old kernels
by Peter 11 Jun '13

11 Jun '13

On 2013-06-11 15:37:26 +0200, Carlos E. R. wrote: > Something is broken in your mail system. Your answers are not threaded > as answers. Please check it up. This reply will doubtless be the same. It's because I subscribe to the nomail version of the list and have to compose replies by quoting and pasting bits and bobs into a new message from the responses I read via the RSS feeds and the copies on the web. When I reply, sometimes it works and puts the message in the right place in the thread, other times it adds a new reply out of context, and once or twice my replies have vanished into thin air. What criteria is used to determine which thread a message belongs to, i.e. is there something I can paste in to ensure it goes in the right place? I thought it might be a combination of subject and time/date stamp but there must be more to it. It's not ideal but I use the nomail version since I want to monitor a few lists, most of which I never or very rarely post to, so I skim the subject lines from time to time but don't want hundreds of extra emails in my inbox. There's been a flurry of recent postings from me to this group because every time I try to fix one problem I run into a new one :( -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Has anyone ever used the autossh daemon?
by Greg Freemyer 11 Jun '13

11 Jun '13

All, I've struggled to setup autossh as daemon and just got it working. I hope it is reliable because I'm about to drive away and won't be back for a while. If anyone can comment on it's reliability, I'd appreciate feedback Now that I have port 22 (ssh) working, I haven't yet figured out the syntax for port 80 so any help on my second line below would be great. Also, anything else I should do to make this connection more robust? (I hope I have the monitoring port below set right?) === Details for myself or others that want to do this: autossh is designed to let you setup a reverse tunnel. That way I can have a machine behind a NAT firewall expose ssh by tunneling it through a server on the internet. Step one: Get this to work as the user you will log into the public server as: ssh user(a)www.intelligentavatar.net Then copy the ssh keyfile to /root/id_rsa_user (there may be a better way to do that) chown root.root /root/id_rsa_user chmod 600 /root/id_rsa_user Get this to work as root ssh -i /root/id_rsa_user user(a)www.intelligentavatar.net # replace user with the user name you setup on the well-known server and of course replace the server name. # make sure you accept the cert so that the above works without user interaction Then enable autossh as daemon. (I used yast service level editor to do that.) Finally edit /etc/sysconfig/autossh to have =========== ## Type: string ## Default: 0 ## Format: <port>[:echo_port] # # The base monitoring port to use, or alternatively, the monitoring # port and the echo service port to use. Setting 0 will turn the # monitoring off, and autossh will only restart ssh on ssh exit. AUTOSSH_PORT="22" ## Type: integer ## Default: 1 # # Number of autossh instances to spawn on start. AUTOSSH_SPAWNS="2" ## Type: string ## Default: user(a)example.com -p 22 -ynNT -R 30000:localhost:22 -o ExitOnForwardFailure=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=3 # # Options to be passed to ssh # All options except for the first must end with "_<number>". Only the # options upto "_$(($AUTOSSH_SPAWNS-1))" will be started. AUTOSSH_OPTIONS="user(a)www.intelligentavatar.net -i /root/id_rsa_user -p 22 -ynNT -R 30000:localhost:22 -o ExitOnForwardFailure=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=3" AUTOSSH_OPTIONS_1="user(a)www.intelligentavatar.net -i /root/id_rsa_user -p 22 -ynNT -R 8888:localhost:80 -o ExitOnForwardFailure=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=3" =========== Again, the line for port 80 is not yet right. I'm not sure what is wrong with the above, but I'm tired of working on this for a while. fyi: the endpoint for this is just a weatherstation, so don't waste your time trying to hack it. Success will get you to nothing of value on a network with nothing of value. Also I changed the port away from 30000 (the default) Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 9

[opensuse] Persistence of /media across reboots.
by Roger Oberholtzer 11 Jun '13

11 Jun '13

I have encountered some unexpected behavior on openSUSE 12.1: If I create a mount point in /media (mkdir /media/abc), it may or may not be there after a reboot. I know that /media is a tmpfs in 12.1, so the contents are lost at reboot. But since the files sometimes are present after a reboot, some agent must be monitoring /media and arranging the recreation of directories. I can even change a directory name in /media, and it works fine at that time. However, when I reboot, the old named directory - and not the new one - is back. Sometimes... I am guessing that the intention is that I place these things in /mnt. I chose /media instead because the disks are hot swappable SATA disks. They have the flavor of what is usually found in /media. It seems perhaps that /media is no longer a tmpfs in 12.3. Unfortunately I need to get this working on 12.1. I see that /media is not listed in /etc/fstab on 12.1. Who/where/what mounts it as tmpfs? Can I stop it from being mounted as such? Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 38

[opensuse] strange problem decrypting disc?
by Daniel Bauer 11 Jun '13

11 Jun '13

Hello list members, I'm on a OS 12.3 with the latest updates applied. Since an "update accident" (see description below between asterisk lines) there seems to be kind of a problem with mounting the encrypted disks at boot, the disk that contains the encrypted LVM with /, /home and swap. Allthough the respective disc is actually mounted (system runs normal and I can access everything normally without the need to type the password again) I receive the following message (in the kde control panel): > Broadcast message from root(a)Venus.atelier.foto (Mon, 2013-06-10 09:54:37 CEST): Password entry required for 'Please enter passphrase for disk WDC_WD20EARS-00MVWB0 (cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part2)!' (PID 5429). Please enter password with the systemd-tty-ask-password-agent tool! in /var/log/message everything seems normal to me, disks seem to be used, there are several messages about the found reiserfs, but quite late in the list I find the following lines: > 2013-06-10T09:44:26.818639+02:00 Venus systemd-cryptsetup[4468]: Timed out > 2013-06-10T09:44:26.819201+02:00 Venus systemd-cryptsetup[4468]: Failed to query password: Timer expired > 2013-06-10T09:44:26.819466+02:00 Venus systemd[1]: systemd-cryptsetup(a)cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.service: main process exited, code=exited, status=1/FAILURE > 2013-06-10T09:44:26.823561+02:00 Venus systemd[1]: Unit systemd-cryptsetup(a)cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.service entered failed state and a bit later: > 2013-06-10T09:54:37.277691+02:00 Venus systemd[1]: Expecting device dev-mapper-cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.device... > 2013-06-10T09:54:37.283781+02:00 Venus systemd[1]: Starting Cryptography Setup for cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part2... > 2013-06-10T09:54:37.288637+02:00 Venus systemd[1]: Starting Cleanup of Temporary Directories... > 2013-06-10T09:54:37.289437+02:00 Venus systemd[1]: Started Forward Password Requests to Wall. > 2013-06-10T09:54:37.463612+02:00 Venus systemd-tmpfiles[5430]: stat(/run/user/1000/gvfs) failed: Permission denied > 2013-06-10T09:54:41.042632+02:00 Venus systemd[1]: Started Cleanup of Temporary Directories. > 2013-06-10T09:56:07.277793+02:00 Venus systemd[1]: Job dev-mapper-cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.device/start timed out. > 2013-06-10T09:56:07.278261+02:00 Venus systemd[1]: Timed out waiting for device dev-mapper-cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.device. > 2013-06-10T09:56:07.278657+02:00 Venus systemd[1]: Dependency failed for Cryptography Setup for cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part2. > 2013-06-10T09:56:07.279060+02:00 Venus systemd[1]: Job systemd-cryptsetup(a)cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.service/start failed with result 'dependency'. > 2013-06-10T09:56:07.279529+02:00 Venus systemd[1]: Job dev-mapper-cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.device/start failed with result 'timeout'. > 2013-06-10T09:56:07.324209+02:00 Venus systemd-cryptsetup[5429]: Timed out > 2013-06-10T09:56:07.324819+02:00 Venus systemd-cryptsetup[5429]: Failed to query password: Timer expired > 2013-06-10T09:56:07.324973+02:00 Venus systemd[1]: systemd-cryptsetup(a)cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.service: main process exited, code=exited, status=1/FAILURE > 2013-06-10T09:56:07.329651+02:00 Venus systemd[1]: Unit systemd-cryptsetup(a)cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.service entered failed state /var/boot log says something more: > Starting Replay Read-Ahead Data... > Starting Collect Read-Ahead Data... > [[1;32m OK [0m] Listening on Syslog Socket. > [[1;32m OK [0m] Reached target System Time Synchronized. > [[1;32m OK [0m] Reached target Remote File Systems. > [[1;32m OK [0m] Listening on Delayed Shutdown Socket. > [[1;32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe. > [[1;32m OK [0m] Listening on udev Kernel Socket. > [[1;32m OK [0m] Listening on udev Control Socket. > [[1;32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point. > Expecting device dev-system-swap.device... > Expecting device dev-mapper-cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.device... > Expecting device dev-disk-by\x2did-ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.device... > Expecting device dev-disk-by\x2did-ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart1.device... > Expecting device dev-disk-by\x2did-ata\x2dWDC_WD2002FAEX\x2d007BA0_WD\x2dWCAY01001843\x2dpart1.device... > Expecting device dev-mapper-cr_sdb1.device... > Expecting device dev-system-home.device... > [[1;32m OK [0m] Listening on Journal Socket. > Mounting POSIX Message Queue File System... > Mounting Huge Pages File System... > Starting Create dynamic rule for /dev/root link... > Starting Journal Service... > [[1;32m OK [0m] Started Journal Service. > Starting LSB: Set default boot entry if called... > [[1;32m OK [0m] Started Collect Read-Ahead Data. > [[1;32m OK [0m] Started Replay Read-Ahead Data. > Starting Setup Virtual Console... > Starting Load Kernel Modules... > Starting Remount Root and Kernel File Systems... > [[1;32m OK [0m] Started Load Kernel Modules. > Starting Apply Kernel Variables... > [[1;32m OK [0m] Mounted Huge Pages File System. > [[1;32m OK [0m] Mounted POSIX Message Queue File System. > [[1;32m OK [0m] Started Apply Kernel Variables. > [[1;32m OK [0m] Started LSB: Set default boot entry if called. > [[1;32m OK [0m] Started Create dynamic rule for /dev/root link. > Starting udev Kernel Device Manager... > [[1;32m OK [0m] Started udev Kernel Device Manager. > Starting LSB: Start LVM2... > %G(K[[1;32m OK [0m] Started LSB: Start LVM2. > [[1;32m OK [0m] Started Setup Virtual Console. > Starting udev Coldplug all Devices... > [[1;32m OK [0m] Started udev Coldplug all Devices. > Starting Show Plymouth Boot Screen... > [[1;32m OK [0m] Found device WDC_WD2002FAEX-007BA0. > Starting Cryptography Setup for cr_sdb1... > [[1;32m OK [0m] Reached target Sound Card. > [[1;32m OK [0m] Found device WDC_WD20EARS-00MVWB0. > Starting Cryptography Setup for cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part2... > [[1;32m OK [0m] Found device /dev/system/swap. > Activating swap /dev/system/swap... > [[1;32m OK [0m] Found device WDC_WD20EARS-00MVWB0. > Starting File System Check on /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part1... > [[1;32m OK [0m] Activated swap /dev/system/swap. > [[1;32m OK [0m] Reached target Swap. > [[1;32m OK [0m] Found device /dev/system/home. > Starting File System Check on /dev/system/home... > systemd-fsck[688]: Reiserfs super block in block 16 on 0xfd01 of format 3.6 with standard journal > systemd-fsck[688]: Blocks (total/free): 434335744/320681443 by 4096 bytes > systemd-fsck[688]: Filesystem is clean > [[1;32m OK [0m] Started File System Check on /dev/system/home. > Starting File System Check on /dev/system/home... > systemd-fsck[776]: Reiserfs super block in block 16 on 0xfd01 of format 3.6 with standard journal > systemd-fsck[776]: Blocks (total/free): 434335744/320681443 by 4096 bytes > systemd-fsck[776]: Filesystem is clean > [[1;32m OK [0m] Started File System Check on /dev/system/home. > systemd-fsck[683]: /dev/sda1: clean, 356/40000 files, 118258/159744 blocks > [[1;32m OK [0m] Started File System Check on /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part1. > [[1;32m OK [0m] Started Show Plymouth Boot Screen. > Starting Forward Password Requests to Plymouth... > [[1;32m OK [0m] Started Forward Password Requests to Plymouth. > [[1;32m OK [0m] Found device /dev/mapper/cr_sdb1. > [[1;32m OK [0m] Started Cryptography Setup for cr_sdb1. > [[1;31mFAILED[0m] Failed to start Cryptography Setup for cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part2. > See 'systemctl status systemd-cryptsetup(a)cr_ata\x2dWDC_WD20EARS\x2d00MVWB0_WD\x2dWMAZA2401793\x2dpart2.service' for details. > [[1;33mDEPEND[0m] Dependency failed for Encrypted Volumes. > Starting Restart storage after cryptsetup... > Stopping LSB: Start LVM2... > [[1;32m OK [0m] Stopped LSB: Start LVM2. > Starting LSB: Start LVM2... > [[1;32m OK [0m] Started LSB: Start LVM2. > [[1;32m OK [0m] Started Restart storage after cryptsetup. > [[1;32m OK [0m] Started Remount Root and Kernel File Systems. > Starting Load Random Seed... > [[1;32m OK [0m] Reached target Local File Systems (Pre). > Mounting /home... > Mounting /boot... > Mounting Lock Directory... > Mounting /sys/kernel/debug... > Mounting Runtime Directory... > [[1;32m OK [0m] Started Load Random Seed. > [[1;32m OK [0m] Mounted Lock Directory. > [[1;32m OK [0m] Mounted /sys/kernel/debug. > [[1;32m OK [0m] Mounted Runtime Directory. > [[1;32m OK [0m] Mounted /boot. > [[1;32m OK [0m] Mounted /home. > Mounting /home/daniel/disk2... > [[1;32m OK [0m] Mounted /home/daniel/disk2. > [[1;32m OK [0m] Reached target Local File Systems. > Starting Recreate Volatile Files and Directories... > Starting Trigger Flushing of Journal to Persistent Storage... > Starting Tell Plymouth To Write Out Runtime Data... > [[1;32m OK [0m] Started Recreate Volatile Files and Directories. > [[1;32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage. > [[1;32m OK [0m] Started Tell Plymouth To Write Out Runtime Data. > [[1;32m OK [0m] Reached target System Initialization. So it seems there was a problem with encrypting, but somehow the problem must have been solved, no? Otherwise I couldn’t access the disks, wouldn't I? This is my fstab: > /dev/system/swap swap swap defaults 0 0 > /dev/system/root / reiserfs acl,user_xattr 1 1 > /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part1 /boot ext4 acl,user_xattr 1 2 > /dev/system/home /home reiserfs acl,user_xattr 1 2 > /dev/mapper/cr_sdb1 /home/daniel/disk2 reiserfs acl,user_xattr 0 0 > proc /proc proc defaults 0 0 > sysfs /sys sysfs noauto 0 0 > debugfs /sys/kernel/debug debugfs noauto 0 0 > usbfs /proc/bus/usb usbfs noauto 0 0 > devpts /dev/pts devpts mode=0620,gid=5 0 0 It is as setup by Yast at installation.The only thing I added manually is the line /dev/mapper/cr_sdb1, a manually encrypted disk outside the LVM (I was forced to use LVM because there seems no other way anymore to have a completely encrypted system). fstab seems to be unchanged since then. However, I wonder why swap, root, and home are listed the way they are and not with something line /dev/mapper..., because they are within the encrypted LVM (which I encrypted during installation). My partitions look like this: /dev/sda WDC-WD20EARS-00M /dev/sda1 /boot 156 MB, Ext4 /dev/sda2 Linux LVM, encrypted (during fresh install of system) /dev/sdb WDC-WD2002FAEX-0 /dev/sdb1 /home/daniel/disk2, reiserfs, encrypted (manually) The encrypted LVM includes /dev/system LVM2 system /dev/system/home reiserfs /home /dev/system/root reiserfs / /dev/system/swap Swap swap ********************* The described problem appears since an update accident a few days ago when the kernel changed. There was not enough free space on /boot (because I set it up to keep the old versions), so update terminated with an error message. After reboot there was a "kernel panic" and there was no way (known to me) to get the system running, also the older versions ended up with kernel panic causing "daniel-panic"... So I booted with the kde live disk, chroot-ed to the existing system, started yast in character-mode, deleted the oldest "kernel-things" on /boot, started yast in character mode, searched for everything "kernel" and selected to update these parts. After that I booted the system. With the first boot I had to enter the password for the disks 4 times. But since the second boot it is enough to enter it once and the system starts. However, during the boot process I see a "failed" message concerning Cryptography (I guess the one from the boot.log above, it goes away very fast...). It seems to me that booting takes a bit longer than before, and after logging-in as user it takes quite a while until the desktop is ready. But this is a time I feel, it is not measured... ********************** So, I wonder how I can repair my system so it is happy with the encrypted disks as it was before. I have no idea where to start... Thanks for hints! Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com google+: https://plus.google.com/109534388657020287386 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] purging old kernels
by Peter 11 Jun '13

11 Jun '13

On 2013-06-11 14:52:18 +0200, Marcus Meissner wrote: > I released a systemd-branding-openSUSE update actually that should have > enabled it. If you mean the package systemd-presets-branding-openSUSE I have the latest update 0.2.0-2.5.1 installed and all other current updates on 12.3. > Locally you can run: > systemctl enable purge-kernels > > to enable it. Okay thanks, I've done that. At a later date I might be able to see if a couple of other systems have it enabled or not but I can't check now. Cheers, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Thunderbird crashes a lot :-/
by Carlos E. R. 11 Jun '13

11 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 00:13, John Andersen wrote: > On 6/10/2013 3:11 PM, Carlos E. R. wrote: >> >> Do you use NNTP? > > Does anyone still use that? ;-) Of course, openSUSE/SUSE operates an NNTP server interconnected with the openSUSE forums. And sees a lot of service, it is a very fast and practical communication channel. > But, seriously, the answer is no. I didn't realize your lament had > to do with nntp, I thought you were only concerned about mail. I'm not sure where it crashes; I just remember that the last two happened while using nntp. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG2UigACgkQIvFNjefEBxqVKwCfcP7zlJ3o/yExZDVebwnuqo6q 2IgAn0BkVsExPVJF9E7b5bYC4u63kVqh =ym2O -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2