Re: Planning a Debian NAS
On 26/01/20 2:58 pm, Josef Grosch wrote: The document I used as a guide to set this up is https://wiki.debian.org/ZFS Two things I would advise when using ZFS is 1) never let the filesystem get to more than 80% full and 2) run a weekly zpool scrub. Mine runs our of cron. Thanks, this looks fairly straightforward.
Re: Planning a Debian NAS
On 27/01/20 12:40 pm, Tom Dial wrote: I can't tell whether or not this response is facetious. If it is, and you are not determined for other reasons to use Linux, I recommend FreeNAS No, I was serious, but I do have limits. I've looked at FreeNAS, but I would much rather use Debian, partially for familiarity, and party because this will be a multi-purpose server, not just a NAS.
Re: Planning a Debian NAS
On 27/01/20 3:58 am, Stefan Monnier wrote: I want to set up a file server on my home LAN with just consumer-grade hardware, and run Debian stable on it. For hardware, I am probably going to get a refurbished mid-range tower with a four to six 3.5" SATA drive capacity, and put WD Reds in it. Unless you already own that hardware you might want to take a look at something like http://gnubee.org/ I have considered the gnubee, and my main problem with it is the poor physical support for the drives, and the orientation of the drives. It is also too low spec to run the extra services I need (secondary to serving files).
Re: Planning a Debian NAS
On 28/01/20 7:00 am, Aidan Gauland wrote: On 27/01/20 12:59 am, ghe wrote: If you don't already have all the router(s) and WiFi access points and such, may I suggest a pile of Raspberry Pis. Can a r-pi be set up with RAID easily? Going by all the replies on this subthread, even the latest model r-pi sounds like a terrible choice for a NAS, unless all you want is a single HDD on ethernet.
Re: Planning a Debian NAS
On 27/01/20 12:59 am, ghe wrote: If you don't already have all the router(s) and WiFi access points and such, may I suggest a pile of Raspberry Pis. Can a r-pi be set up with RAID easily?
Re: Planning a Debian NAS
On 26/01/20 3:17 pm, Paul Johnson wrote: ext4 is the best way to go unless you have extremely specific needs or you really want to overcomplicate things for a hobby. I love over-complicating my hobbies.
Planning a Debian NAS
I want to set up a file server on my home LAN with just consumer-grade hardware, and run Debian stable on it. For hardware, I am probably going to get a refurbished mid-range tower with a four to six 3.5" SATA drive capacity, and put WD Reds in it. What I'm not sure of which filesystem to use. I could just use ext4 with RAID5 or RAID6 to get striping with some fault tolerance (i.e. time to replace a failed drive without losing everything). ZFS looks easier, but only if you're on BSD. btrfs sounds like ZFS for Linux, but it appears to still be of beta quality, and I can't tell whether it can yet do striping with parity. Any advice? Regards, Aidan Gauland
Re: Pulse error using module-loopback
On 2/09/19 6:46 am, deloptes wrote: Which debian and pulse audio version are you on? pactl info spits out this: Server String: /run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 245 Tile Size: 65472 User Name: aidan Host Name: aidalbox14 Server Name: pulseaudio Server Version: 12.2 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-_00_1b.0.analog-stereo Default Source: alsa_input.usb-046d_0825_51B4D860-02.analog-mono Cookie: 9226:7bfd And I'm on Debian 10.0
Pulse error using module-loopback
Hi, I'm trying to follow a guide on setting up PulseAudio sinks for setup with Open Broadcast Studio <https://obsproject.com/forum/threads/capture-single-pulseaudio-stream.35170/>, but the "pactl load-module module-loopback" step fails with the error "Failure: Module initialization failed". I have been unable to find any reports of this error elsewhere, and I don't know how to get Pulse to give more verbose output. Can anyone more familiar with Pulse hackery offer any insight? Regards, Aidan Gauland
Re: Giving remaja (teens) group full administrator privileges through sudo - dangerous?
On 25/06/19 3:38 PM, Bagas Sanjaya wrote: > On 24/06/19 06.27, Aidan Gauland wrote: > >> I can't really offer an opinion on whether it is dangerous without a >> more detailed hypothetical scenario, but I would say that is >> overbroad, and this rule should be narrowed down to only allow >> running certain commands via sudo as required for this group to >> perform their work. > > In this hypothetical scenario, the sudoers rule is applied to ALL > systems, including production ones, and sysadmins doesn't have proper > backups. OK, not having a (good) backup system is definitely bad. You should always have that even if your security is very tight, in case something slips through, or an admin makes a mistake.
Re: Unreliable systemd user service
On 25/06/19 3:46 AM, Michael Biebl wrote: >> Why is there no "the graphical session is ready" >> systemd target? > There is, incidentally it is named graphical-session.target :-) > See man systemd.special > > Unfortunately, no display/session manager is hooked up yet to manage the > lifetime of that target, so you can't make use of that target as of now. Ah, that would be why using that was valid but did not work. Good to know, thanks!
Re: Unreliable systemd user service
On 21/06/19 8:33 PM, Jonathan Dowland wrote: > On Fri, Jun 21, 2019 at 06:50:14PM +1200, Aidan Gauland wrote: >> Someone else suggested running xautolock from my .xsessionrc script so >> that it is always run after X is running, and that seems to work. I >> wanted to run this via systemd because that's easier to restart after >> making tweaks than something run as part of a startup script, > > What about starting the service *via systemd* in your .xsessionrc? > something like "systemctl start xautolock". I had thought of that, but it feels even messier to use both .xsessionrc and systemd together. Why is there no "the graphical session is ready" systemd target?
Re: Unreliable systemd user service
On 21/06/19 7:24 PM, john doe wrote: > Is it always working if you run the command manually? It has so far, yes.
Re: Unreliable systemd user service
On 21/06/19 6:25 PM, Ansgar Burchardt wrote: > Aidan Gauland writes: >> I have a user service for running xautolock that does not start on login >> reliably, and I have no idea why, because there is no error message, >> just an exit code of 1. (Unit file and output of systemctl status >> attached.) Any suggestions on what to do next to troubleshoot this? > I would guess `xautolock` might be started before X is > running/accessible by your user. > > Does the journal contain any useful log messages? Note that there is a > race condition that some messages might not be logged as part of the > user service[1], so you might have to check all log messages and cannot > rely on journalctl's `--user-unit` option. Nope, absolutely nothing in the logs. Someone else suggested running xautolock from my .xsessionrc script so that it is always run after X is running, and that seems to work. I wanted to run this via systemd because that's easier to restart after making tweaks than something run as part of a startup script, but I have not been able to find any mechanism to delay starting a /user/ service until the graphical login is ready.
Unreliable systemd user service
I have a user service for running xautolock that does not start on login reliably, and I have no idea why, because there is no error message, just an exit code of 1. (Unit file and output of systemctl status attached.) Any suggestions on what to do next to troubleshoot this? Regards, Aidan Gauland ● auto-screen-lock.service - Lock the screen automatically after a timeout Loaded: loaded (/home/aidan/.config/systemd/user/auto-screen-lock.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-06-16 16:29:26 NZST; 43min ago Process: 1542 ExecStart=/usr/bin/xautolock -time 5 -locker /home/aidan/bin/i3lock (code=exited, status=1/FAILURE) Main PID: 1542 (code=exited, status=1/FAILURE) [Unit] Description=Lock the screen automatically after a timeout [Service] Environment=DISPLAY=:0 ExecStart=/usr/bin/xautolock -time 5 -locker /home/aidan/bin/i3lock [Install] WantedBy=default.target
Re: IPv4 v IPv6
On 17/06/19 9:09 PM, to...@tuxteam.de wrote: > On Mon, Jun 17, 2019 at 10:05:11AM +0100, mick crane wrote: >> hello, >> I know nothing about IPv6. >> Can somebody point to a good explanation ? > I'd recommend skimming the relevant Wikipedia [1] page. > > Cheers > > [1] https://en.wikipedia.org/wiki/IPv6 I don't entirely agree that's a good introduction for someone without any background knowledge in TCP/IP, but certainly a good resource when one has some of the basics already. To answer OP's questions, > Without knowing anything about it I'm wondering if I should request an > IPv6 range from my ISP to use locally. Given that you do not already have a reason to do so, I would say not. > A network card have IPv4 and IPv6 addresses that are different, not > the same address in different notation? A network card (also called an interface) can have both, and they are not the same address. IPv4 and IPv6 are two different network stacks, with different addressing, routing, etc. > Then with firewalling do you need to specify both IPv4 and IPv6 ranges? Yes, for the same reason as above. Sadly, most of the world is still on IPv4, so until IPv6 is deployed across the majority of the Internet, then if you're not a large entity, there's not much reason to use IPv6 other than playing around. Here's a gentler introduction to IPv6 that might also help: http://www.steves-internet-guide.com/ipv6-guide/ Regards, Aidan Gauland
Re: systemd WantedBy for X login
On 19/05/19 6:40 PM, Sven Joachim wrote: > On 2019-05-19 15:58 +1200, Aidan Gauland wrote: > >> I have a bunch of systemd user services for headless daemons that I want >> to run in both console and graphical logins, which all work fine, but I >> have one that I only want to start for graphical logins, and that works >> when I start it manually, but it is not being started when I log in, >> even though I have the WantedBy field set to graphical.target. I am >> using lightdm and i3. > How do you start lightdm? It should only be started automatically in > graphical.target. I'm not sure. I just installed the lightdm package and it is started automatically at boot-time. >> The other services' WantedBy field is set to >> default.target. What is the correct way to specify that a service >> should be started only for X logins? > The wantedBy field is the correct place to specify that, but you also > have to make sure that your X login is actually reached via > graphical.target. OK, good. Is there a way to test this? I just found this tidbit on the Arch wiki suggesting that the only valid target for user services is default.target: “When a systemd user instance starts, it brings up the target default.target”
systemd WantedBy for X login
I have a bunch of systemd user services for headless daemons that I want to run in both console and graphical logins, which all work fine, but I have one that I only want to start for graphical logins, and that works when I start it manually, but it is not being started when I log in, even though I have the WantedBy field set to graphical.target. I am using lightdm and i3. The other services' WantedBy field is set to default.target. What is the correct way to specify that a service should be started only for X logins? Regards, Aidan Gauland
Re: please do *never* use GitHub for free software, was Re: Salsa vs Github
On 18/05/19 11:08 AM, Dominik George wrote: >> Can you give sources for your claim about their discrimination? That >> one is new to me. > I did. Please read my mails in this thread. I have, and I just re-read the articles you gave, and I still do not see anything about discrimination by age, or against any group of people, only the usual issues with hosting free software on/with non-free services (which reason enough to avoid GitHub).
Re: please do *never* use GitHub for free software, was Re: Salsa vs Github
On 17/05/19 7:28 PM, Dominik George wrote: >>> please do*never* use GitHub for free software >> Please explain, in detail, why. > If discrimination against parts of the community is not enough for you, > here's why: > > https://mako.cc/writing/hill-free_tools.html > > https://www.adamhyde.net/another-good-reason-not-to-use-github/ > > https://www.mirbsd.org/permalinks/wlog-10_e20170301-tg.htm Can you give sources for your claim about their discrimination? That one is new to me.
Re: Mysterious ssh-agent session
On 25/04/19 6:37 PM, Reco wrote: > Hi. > > On Thu, Apr 25, 2019 at 04:58:28PM +1200, Aidan Gauland wrote: >> I need to know how to either >> a) disable the instance started under "(sd-pam)", so I can use my >> systemd user service, or > Comment out use-ssh-agent in /etc/X11/Xsession.options . Ah ha! That's where it was. Thanks! >> b) configure the instance started under "(sd-pam)", and use that >> instead of my system user service. > Modify /etc/X11/Xsession.d/90x11-common_ssh-agent , SSHAGENTARGS in > particular. I will probably go with option a), but is there a way to option b) per-user?
Mysterious ssh-agent session
While troubleshooting my ssh-agent setup, I discovered that an extra ssh-agent instance was running, and I have no idea what is starting this. What I want is to have ssh-agent run as a systemd user service (following the instructions at <https://wiki.archlinux.org/index.php?title=SSH_keys=571850#Start_ssh-agent_with_systemd_user>), but the other instance is interfering. Here is where it is in the process tree (via htop): 1756 ├─ /lib/systemd/systemd --user 31808 │ ├─ /usr/lib/flatpak/flatpak-session-helper 26143 │ ├─ /usr/lib/dconf/dconf-service 22233 │ ├─ /usr/bin/dunst 22204 │ ├─ /usr/lib/xdg-desktop-portal/xdg-desktop-portal-gtk 22187 │ ├─ /usr/lib/flatpak/xdg-permission-store 22184 │ ├─ /usr/lib/flatpak/xdg-document-portal 22180 │ ├─ /usr/lib/xdg-desktop-portal/xdg-desktop-portal 21243 │ ├─ /usr/bin/dirmngr --supervised 18747 │ ├─ /usr/lib/gvfs/gvfsd-trash [snip] 18672 │ ├─ /usr/lib/gvfs/gvfs-udisks2-volume-monitor 18534 │ ├─ /usr/lib/gvfs/gvfsd-metadata 5759 │ ├─ /usr/bin/gpg-agent --supervised 1934 │ ├─ /usr/lib/x86_64-linux-gnu/gconf/gconfd-2 1856 │ ├─ /usr/lib/gvfs/gvfsd 1849 │ ├─ /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session 1835 │ ├─ /usr/lib/at-spi2-core/at-spi-bus-launcher 1847 │ │ └─ /usr/bin/dbus-daemon [snip] 1790 │ ├─ /usr/bin/pulseaudio --start --log-target=syslog 1932 │ │ └─ /usr/lib/x86_64-linux-gnu/pulse/gconf-helper 1771 │ ├─ /usr/bin/dbus-daemon [snip] 1762 │ ├─ /usr/bin/ssh-agent -t 2m -D -a /run/user/1000/ssh-agent.socket 1761 │ ├─ /usr/bin/mpd --no-daemon 1757 │ └─ (sd-pam) 1763 │ │ └─ i3 1876 │ │ ├─ /usr/bin/ssh-agent i3 1833 │ │ ├─ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 1832 │ │ └─ clipit (The ssh-agent instance with PID 1762 is the one I want; PID 1876 is the unwanted instance.) I need to know how to either a) disable the instance started under "(sd-pam)", so I can use my systemd user service, or b) configure the instance started under "(sd-pam)", and use that instead of my system user service. I am using lightdm to start X, and my session is the i3 WM. In case it's relevant, I also start /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 in my ~/.xsessionrc file. I am running Debian 9.8 on x86_64. Thanks, Aidan Gauland
Mimic an Xbox 360 controller with an Xbox One controller
Hello, I recently bought an Xbox One controller and kept my Xbox 360 (wired) controller as a spare controller for playing with friends, and I've run into several games that worked fine with my 360 controller but have slightly off button-mappings with the XBOne controller, or simply don't see the controller. For games that don't (or poorly) support the Xbox One controller, is it possible to force xpad to present an Xbox One controller to userspace in exactly as it would with an Xbox 360 (wired, of course) controller? Or maybe there is a program that can set up a virtual 360 device that simply wraps the XBOne device? Of course, if developers provided a controller configuration interface instead of hard-coding everything for the Xbox 360 controller, I wouldn't even be having this problem. (In case you haven't already guessed, these are all Linux ports of Windows games that are giving me trouble.) Regards, Aidan Gauland
Re: sudoers vs admin group
Jean-Marc jean-m...@6jf.be writes: Michael jm...@jagmail.southalabama.edu wrote: Is there any (significant) difference between editing (adding a user to) the _/etc/sudoers_ file and adding a person to the _admin group?_ Am I comparing apples and oranges? Usually, groups are used on GNU/Linux for access control, to control access to the files, directories, and peripherals. So, being in the admin group will allow users to get access to the files having admin as group. /etc/sudoers determines a user's sudo privileges. Privileges do not always mean getting root privileges. It is not the same thing, indeed. See also http://www.debian.org/doc/manuals/securing-debian-howto/ch12.en.html#s12.1.12.1 for an explanation of each group on Debian (distros vary). sudoers controls who can run what with sudo; groups grant access (not root access) to certain files with permissions for that group. --Aidan -- 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/87wqrjqxrv@dimension8.tehua.net
Eee PC freeze on wakeup
I am running Debian squeeze on a Eee PC 1015B. I can sleep the system with pm-suspend, but when I wake it up, I get a blank screen, the OS doesn't seem to be coming back *at all* (i.e. the machine just freezes on wake up), since I get nothing on netconsole when I wake it up. With the kernel console log level set to 8 (via dmesg -n 8), the console shows this on suspend: [ 188.174330] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 188.401118] atl1c :02:00.0: atl1c: eth0 NIC Link is Up100 Mbps Full Duplex [ 188.710339] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 188.936808] atl1c :02:00.0: atl1c: eth0 NIC Link is Up100 Mbps Full Duplex [ 191.721237] PM: Syncing filesystems ... done. [ 191.745161] PM: Preparing system for mem sleep [ 191.745299] Freezing user space processes ... (elapsed 0.00 seconds) done. [ 191.746346] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [ 191.746802] PM: Entering mem sleep [ 191.746876] Suspending console(s) (use no_console_suspend to debug) Nothing unusual there. And then I get nothing when I wake it up, although it could just be that the interface is not up in time for anything to be sent; I'm pretty sure it's frozen, though, since pressing the power button doesn't cause a clean shutdown (or anything at all). I'm also getting erratic screen flickering semi-frequently. Not just blinking on and off, but liney white noise, like what you can get from a loose monitor connection. I'm not sure whether this is related, or actually just a loose connection. I suspect it's unrelated, since I get at the BIOS screen, before the OS has even *started*. A more likely related problem is the machine (or at least the display) freezing after it's been on for a while, but this happens rather infrequently, so I'm not worrying about that now, but I thought it should be mentioned. I've tried the --quirk-* options to pm-suspend that seemed relevant: * --quirk-s3-bios --quirk-s3-mode * --quirk-vbe-post * --quirk-vbemode-restore * --quirk-vbestate-restore Same symptom. I tried creating /etc/pm/config.d/00sleep_module with the following contents: SUSPEND_MODULES=xhci_hcd as described here: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/711501/comments/4 No joy. I installed the newer kernel from backports (package linux-image-3.2.0-0.bpo.4-686-pae) and tried that, which boots to what looks like white noise (like VRAM corruption) almost right away (in the virtual console, before X is started). The system definitely finishes booting, as I can still shut it down cleanly by pressing the power button (press and release; not press and hold). I tried rebooting with the vga=771 boot parameter, but that made no difference. Right now, I'm want to get the backports kernel to boot cleanly – because that *should* work – and go from there, but I'll try any other solutions. Regards, Aidan Gauland -- 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/87k3og3ft7@dimension8.tehua.net
Re: Using wheezy or squeeze.
rodrigo tavares rodrigofar...@yahoo.com.br writes: I have used debian 6.0 squezze, and some packages is old, since the wheezy, have a packages new version. I need to install a mail server with potfix, LDAP, e Cyrus IMAP. I want install version Cyrus 2.4, is in squeeze is 2.2. Can I to trust in Wheeezy? If there are only a few packages you need from testing (wheezy), you should not upgrade your entire system to wheezy and instead only get the newer packages you need. First, see if they have been backported to squeeze: http://backports-master.debian.org/. If they're not in squeeze-backports, get the Debian source packages from wheezy and build them on your squeeze system. I'll let someone who is more familiar with the Debian packaging tools instruct you on this, but BE SURE TO VERIFY THE SIGNATURES OF THE SOURCE PACKAGES! Hope this helps, Aidan Gauland -- 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/87sj6bzbms@dimension8.tehua.net
Re: pmount-hal not using labels on encrypted filesystems
Michael Biebl bi...@debian.org writes: On 14.12.2012 05:06, Aidan Gauland wrote: How can I fix this? Given that HAL is deprecated, I suspect there is some other tool that serves the same purpose as pmount-hal that I should be using instead. yeah, hal is dead. You might try udisks --mount instead. I get Mount failed: Not a mountable file system It seems that udisks does not handle encrypted partitions. -- 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/87ehit2ekf@dimension8.tehua.net
Re: pmount-hal not using labels on encrypted filesystems
Michael Biebl bi...@debian.org writes: udisks-daemon does handle luks/cryptsetup encrypted partitions but it seems the udisks command line tool is too limited. Try gvfs-mount -d /dev/foo. This should prompt you for the passphrase, unlock and mount the file system under /media/FS_LABEL Can be unmounted again via umount /media/FS_LABEL Yep, that does the job. Thanks! I think I'll file a feature request against udisks. —Aidan -- 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/87a9tg35e2@dimension8.tehua.net
pmount-hal not using labels on encrypted filesystems
When I mount a filesystem on an encrypted partition with pmount-hal, it just mounts it on /media/usbdisk instead of using the filesystem's label to name the mount point, as it does with unencrypted filesystems. For example, $ pmount-hal /dev/sdb1 Enter passphrase for /dev/sdb1: /dev/mapper/_dev_sdb1 on /media/usbdisk type ext4 (rw,noexec,nosuid,nodev,errors=remount-ro) But I want the mount point to be named after the label of the (encrypted) filesystem on /dev/sdb1, in this case, Gauland_HDD. How can I fix this? Given that HAL is deprecated, I suspect there is some other tool that serves the same purpose as pmount-hal that I should be using instead. Regards, Aidan Gauland -- 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/87ip852s6y@dimension8.tehua.net
Re: man in the middle attack ?
Dr Beco r...@beco.cc writes: After disconnecting the net cable, I realized the server was still up! :O I logged with a innocuous account to read that that was the old server which miraculous revived. Some intern from TI turned on the old server and it took precedence over the new one. That explained the change of the KEY. The /var/log/auth.log shows: Jun 20 14:17:01 zebu CRON[24183]: pam_unix(cron:session): session closed Aug 20 10:16:23 zebu sshd[1301]: Server listening on port 22. Mistery solved. Now I'm really curious, but confused. Why did the presence of another server change the key on the original server? Or did you mean that an old server was, in error, put up in place of the one you set up earlier (before the warning from SSH)? Kind regards, Aidan Gauland -- 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/87393g8ru2@dimension8.tehua.net
Re: Server software
Alex Rodriguez xarodrigu...@gmail.com writes: 1. I can't find the version or name to download. Can you just provide the correct name and version to get. There is no separate server edition; just install Debian without X11. You might want to take a look at the Installation Guide: http://www.debian.org/releases/stable/installmanual 2. Were can I donate money to your company to continue the great work you guys do? http://www.debian.org/donations Hope this answers your questions. :) --Aidan -- 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/87mx1vjzem@no8wireless.co.nz
Re: Wheezy and Sun-Java
Rob Owens row...@ptd.net writes: On Tue, Aug 14, 2012 at 08:29:41PM -0300, Dr Beco wrote: Unfortunately, my internet baking does not recognize openjdk. Only sun-java seems to work. When calling technical support, the attendant insist I should upgrade to the last sun-java plugin. There is simply no alternatives for me. Did you install the icedtea plugin? That is the browser plugin that works with openjdk. Just make sure that doesn't work before you go through the trouble of installing sun/oracle java from squeeze or from source. I can vouch for the icedtea plugin. I have to run Java applets for some of my classes, and this has never given me any trouble. (Also using wheezy.) --Aidan -- 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/87393pngfz@no8wireless.co.nz
Re: Freeze on wake
On 03/04/12 03:58, Camaleón wrote: Being an EEEPC, I would also post into their mailing list: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/ I will do that. Thank you for pointing that out. Debugging resuming can be tricky and hard, it can be almost anything (BIOS, kernel version, a faulty/conflicting driver...). I'd start by reviewing the logs (/var/log/pm-suspend.log) just in the event there is something of usefulness. There is nothing about resuming at the end of the log file; just saying that the last suspend went well. Regards, Aidan Gauland -- 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/jlh2db$2k6$1...@dough.gmane.org
Re: Freeze on wake
On 03/04/12 03:58, Camaleón wrote: Being an EEEPC, I would also post into their mailing list: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/ I will do that. Thank you for pointing that out. Debugging resuming can be tricky and hard, it can be almost anything (BIOS, kernel version, a faulty/conflicting driver...). I'd start by reviewing the logs (/var/log/pm-suspend.log) just in the event there is something of usefulness. I looked there first, and there's nothing about the failed resume, only messages about the last suspend and that it went well. Regards, Aidan Gauland -- 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/jlh2h4$2k6$2...@dough.gmane.org
Freeze on wake
After returning my 1015BX and getting a 1015B Eee PC, I have a hardware compatibility problem (at least I think it's a hardware problem): sometimes on wakeup from sleep, the system freezes and can only be reset by removing the battery; holding the power button shuts it off, but it comes back frozen instead of cold booting when I press it again. There doesn't appear to be any pattern to the freezes, so I haven't been able to find a workaround. I'm using Gnome3, so whatever backend that uses is what I'm using for suspend (I'm assuming pm-utils). I know pm-utils has some workaround for hardware quirks, but I can't figure out how to enable them system-wide (so it's used when I suspend from Gnome). Can anyone offer any help? Regards, Aidan Gauland -- 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/jlc0i4$b0p$1...@dough.gmane.org
Eee PC video corrupted on boot
I just got a Eee PC because my Aspire One is only sputtering along. I just finished installing Debian squeeze and upgrading from that to wheezy, and now the screen goes to white noise during boot up. It is certainly not X, because the Ctrl+Alt+Fx keys do nothing and, besides, the corrupt video appears when the console resolution is changed, which is well before X starts. I tried booting with the kernel option vga=771, but it didn't make a difference. Regards, Aidan Gauland -- 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/jirtq4$nqe$1...@dough.gmane.org
Re: Eee PC video corrupted on boot
On 03/03/12 15:42, Carl Fink wrote: Basic suggestion: post the actual model number of your Eee (there are many) and the video hardware. Ah, yes, that would help a lot. :P Sorry about that. The model is 1015BX, and the GPU is an AMD Radeon HD 6250. --Aidan -- 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/jiscvs$ag6$1...@dough.gmane.org
Re: Eee PC video corrupted on boot [SOLVED]
Er, problem solved: forgot to install linux-firmware-nonfree Sorry to waste your time. --Aidan -- 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/jise2u$fr2$1...@dough.gmane.org
Re: Eee PC video corrupted on boot
Er, problem solved: forgot to install linux-firmware-nonfree _ Well, that was stupidly simple. --Aidan -- 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/jise5g$fr2$2...@dough.gmane.org
Keeping a laptop backlight off
I just installed a Pixel Qi screen in my Acer Aspire One am already enjoying the increased readability in sunlight, but there is a small problem I need to address: when I turn the screen backlight off via the Fn key (Fn+F6), the screen goes into minimal-power, monochrome mode; only problem is the screen comes back on as soon as I move the mouse or press a key, which makes it impossible to use the laptop with the screen in this mode. Is there some /proc hack to *keep* the backlight off? --Aidan -- 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/jghe09$jp3$1...@dough.gmane.org
Re: Downgrading?
I seem to remember asking this on IRC a while ago, and the answer I got (from multiple people) was to backup system config files and, of course, /home, and do a fresh install of stable. (In the end, I went with this method.) I am quite certain that downgrading from testing to stable is not supported, and would probably blow up in your face with much carnage if you tried. --Aidan On 04/02/12 08:39, Julien Claassen wrote: I just wondered, if it would be possible to downgrade my Debian distro from - say - Wheezy to Squeeze? I thought, that it must work, but I can't for the life of me think, which exact command to use. -- 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/jghef0$qip$1...@dough.gmane.org
Re: Wiping hard drives
On 14/09/11 02:10, yudi v wrote: I will be wiping partitions on my hard drive before sending it back to the manufacturer for replacement. I usually prefer dd if=/dev/urandom of=/dev/sdX# for the unencrypted partitions and just over write the first few sectors on the LUKS partition to destroy the header file. I just want to hear some opinions as to what precautions you take before parting with hard drives. I would be very interested to hear from SSD owners. I think you want scrub. It provides somewhat more felxibility than dd if=/dev/urandom of=/dev/sdXn. There's a Debian pacakge for it. Kind regards, Aidan Gauland -- 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/j4prg3$e16$1...@dont-email.me
Re: Xfce not locking screen on suspend
On 09/09/11 18:20, John A. Sullivan III wrote: Could it be the xscreensaver daemon is not running. I found I had to copy the /etc/xdg/xfce4/xinitrc to ~/.config/xfce4/ AND I had to tell GDM to explicitly invoke an Xfce session or else it did not read the xinitrc file - John The xscreensaver daemon is certainly running; it shows up in htop and I can lock the screen manually. --Aidan -- 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/j4dodm$soi$1...@dont-email.me
Xfce not locking screen on suspend
Hi, I'm using Xfce4.8 from wheezy. I have ticked the Lock screen when going for suspend/hibernate checkbox in the Extended section of the Power Manager settings, but the screen is never locked when I bring my computer back from suspend or hibernate. This appears to be an upstream bug, not a bug in the packaging, as this has also been reported in Arch Linux: https://bbs.archlinux.org/viewtopic.php?id=80661 Can anyone else confirm this? Thanks, Aidan -- 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/j4c6tn$83l$1...@dont-email.me
Re: Tap to click not working
Sridhar M.A. m...@mylug.org writes: I am currently running debian testing on Acer laptop. Everything was working as expected. Since a couple of days, the tap to click on the touchpad has stopped working. Of course, I can set it Gnome preferences. But, when I switch to openbox, I have lost that functionality. When I installed Debian squeeze, I had to set this in my .xinitrc file xinput --set-prop --type=int --format=8 'SynPS/2 Synaptics TouchPad' 'Synaptics Tap Action' 0 0 0 0 1 0 0 I don't know if there is a way to enable this system-wide, but I avoid editing system-wide files, so I went with this solution. Hope this helps, Aidan Gauland -- 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/87zkk92vgj@no8wireless.co.nz
Re: Shrinking encrypted LVM partition
Aaron Toponce aaron.topo...@gmail.com writes: 6) Shrink the partition of /dev/sda5 using fdisk(8) or parted(8) I've run into trouble at this step: when I try to resize the partition with parted, it complains that it could not detect file system, and refuses to do touch the disk. fdisk does not seem to be able to resize partitions, so I tried cfdisk, which quit as soon as I ran it on /dev/sda1 with the FATAL ERROR: Bad primary partition 1: Partition ends in the final partial cylinder. I have not touched the partition table and can still boot into my system, so the disk appears to be just fine, and the partition table was set up by the Debian (squeeze) installer and has not been touched since, so I don't know what cfdisk is on about. Here's the partition table of sda... # fdisk -cu /dev/sda Command (m for help): p Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002f08e Device Boot Start End Blocks Id System /dev/sda1 *2048 499711 248832 83 Linux /dev/sda2 501758 625141759 3123200015 Extended /dev/sda5 501760 625141759 31232 83 Linux How should I proceed from here? --Aidan -- 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/87hb6hkyjn@no8wireless.co.nz
Multiple logins with XDM
Hi, I am on squeeze using XDM as my display manager and XScreenSaver. When I click the New Login button from the locked screensaver dialog, XScreenSaver complains about not being able to find gdmflexiserver. So it seems to expect GDM, but I prefer a simpler display manager such as XDM. Do I have to use GDM if I want to have multiple logins, or do I simply need to tweak XScreenSaver's configuration? Regards, Aidan Gauland -- 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/87ei1m1ywf@no8wireless.co.nz
Shrinking encrypted LVM partition
Hello everyone, I have to make room on my hard drive for another operating system on my hard disk. I currently have /boot on sda1, encrypted LVM on sda5 (which, I think, an extended partition); this was set up by the installer. I just want to install the other OS on a primary partition, instead of trying to get it set up with LVM. What is the easiest way to rearrange my disk to make room for a primary partition? As far as I know, it is not possible to resize a partition encrypted with the method used by Debian, so I will have to backup the data on the LVM partition, shrink sda5, and then reformat it and restore the LVM logical volumes. I'm hoping there is a simpler way. Is there? Regards, Aidan Gauland -- 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/87fwma9zlu@no8wireless.co.nz
Re: Shrinking encrypted LVM partition
Aaron Toponce aaron.topo...@gmail.com writes: I have gathered that /dev/sda1 is mounted on /boot, and /dev/sda5 is a physical volume. With that, how many logical volumes do you have from that volume group, and where are they mounted? Are you using LUKS for your encrypted volumes? I have / and /home as LVM volumes. I don't have each volume encrypted separately; sda5 is an encrypted partition, and LVM is on top of that. The general order of the steps you will be taking is this: 0) BACKUP ALL DATA 1) Find the logical volume(s) with the most space you can give up 2) Reduce the filesystem of each logical volume to the desired size with resize2fs(8) (assuming it's an ext-based filesystem) 3) Reduce each logical volume with lvreduce(8) 4) Reduce each encrypted filesystem with cryptsetup(8) (assuming you're using LUKS) [snip] Great, thanks for that! I'll try following your instructions this weekend. Thanks, Aidan Gauland -- 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/87aaci9fn1@no8wireless.co.nz
Re: Nvidia drivers from sid on squeeze [SOLVED]
Aidan Gauland aidal...@no8wireless.co.nz writes: I just upgraded my video card (from a 9400 GT to a GT 430), and when I booted my system, X failed to start. When seeing that the Nvidia drivers in sid are the same version as those direct from Nvidia's website, I tried upgrading the nvidia driver packages on my system to the sid versions. I then restarted X via sudo invoke-rc.d xdm restart, but it still failed to start. [snip] So I then tried purging (and downgrading back to squeeze any packages that were upgraded as dependencies of) the nvidia packages and installing nvidia-kernel-dkms (as directed by http://wiki.debian.org/NvidiaGraphicsDrivers#Use_DKMS). Still no joy; the same error. OK, the problem was that pulling the nvidia-kernel-dkms version from sid was also pulling in the sid kernel-header packages, so the kernel module was being built for the wrong kernel version. Manually downgrading back to the squeeze kernel-header packages caused the module to be rebuilt for the current kernel. One point for the Debian way; minus one point for the Nvidia installer. ;) --Aidan -- 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/87oc1kbc76@dimension8.tehua.net
Nvidia drivers from sid on squeeze
Hi, I just upgraded my video card (from a 9400 GT to a GT 430), and when I booted my system, X failed to start. When seeing that the Nvidia drivers in sid are the same version as those direct from Nvidia's website, I tried upgrading the nvidia driver packages on my system to the sid versions. I then restarted X via sudo invoke-rc.d xdm restart, but it still failed to start. Here is the error from /var/log/xdm.conf: FATAL: Module nvidia not found. (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your (EE) NVIDIA: system's kernel log for additional error messages. (EE) Failed to load module nvidia (module-specific error, 0) (EE) No drivers available. Fatal server error: no screens found So I then tried purging (and downgrading back to squeeze any packages that were upgraded as dependencies of) the nvidia packages and installing nvidia-kernel-dkms (as directed by http://wiki.debian.org/NvidiaGraphicsDrivers#Use_DKMS). Still no joy; the same error. What do I need to do to use the Nvidia drivers from sid on squeeze? Regards, Aidan Gauland (Note: I have attached my xorg.conf file.) xorg.conf Description: xorg.conf
Nvidia drivers from sid on squeeze
Hi, I just upgraded my video card (from a 9400 GT to a GT 430), and when I booted my system, X failed to start. Seeing that the version of the Nvidia drivers in sid were the same as those direct from Nvidia's website, I tried upgrading the drivers to those from sid. I restarted XDM (via sudo invoke-rc.d xdm restart), but it still failed to start. (I have attached the relevant parts of /var/log/xdm.log from immediately after this failure, as well as my xorg.conf file.) I then tried purging all nvidia packages (and downgrading back to squeeze any dependencies that were pulled in from sid) and installing nvidia-kernel-dkms (as instructed by http://wiki.debian.org/NvidiaGraphicsDrivers), but still no joy; the same error. What do I need to do to use the Nvidia drivers from sid on squeeze? Regards, Aidan Gauland xdm.log Description: XDM log file xorg.conf Description: xorg.conf
Re: Nvidia drivers from sid on squeeze
Hans-J. Ullrich hans.ullr...@loop.de writes: Hi Aidan! Did you install the nvidia-glx package? Yes, that was pulled in by nvidia-kernel-dkms (directly or indirectly). A good way to see, what is happening, is to move /etc/init.d/kdm out of the way, Doing so, it will not start at boot. After boot, you can start X by the command startx. The console is now showing you, what is happening. Can't I just look at the log files to see the same thing? If you want to use the drivers from sid in squeeze, I doubt, this will work. It has something to do with the kernel-version and the compiler. I suppose, you will need to use the kernel from sid to. To install the stuff from sid, add the repository in /etc/apt/sourcers.list, then apt-get update and then apt-get install myrequiredstuff -t sid. Yes, I had wondered myself if there aren't incompatibilities, even if the packages are not marked as conflicting. I think it might be easier to go the non-Debian, Nvidia way (sadly). On Debian, how can I undo whatever the Nvidia installer does? I'd feel more comfortable running it, knowing how to (safely) reverse its effects. Thanks, Aidan -- 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/87k4caxiji@no8wireless.co.nz
Re: Nvidia drivers from sid on squeeze
Camaleón noela...@gmail.com writes: You better try with nvidia own drivers to avoid messing with dependencies. Yes, I think I'll go that route. Bit of a problem, though: the Nvidia installer warns me that The compiler used to compile the kernel (gcc 4.3) does not exactly match the current compiler (gcc 4.4). The Linux 2.6 kernel module loader rejects kernel modules built with a version of gcc that does not exactly match that of the compiler used to build the running kernel. Why on Earth is the squeeze kernel image not built with the version squeeze version of gcc? http://packages.debian.org/squeeze/gcc Regards, Aidan Gauland -- 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/874o3d6y6l@no8wireless.co.nz
Re: Squeeze. Can't cd in directory which begin with .[dot]
Mark Goldshtein mark.goldshtein at gmail.com writes: On Mon, Oct 4, 2010 at 7:16 PM, Kousik Maiti kousikster at gmail.com wrote: Hello Mark Try from $HOME directory $cd .wine Oh, Thanks! It works! What was that? :) . (dot) is the current working directory and / (slash) is the pathname separator (on UNIX). So ./wine is actually a path where the first component is the current working directory and the second component is wine, so you're saying the file named 'wine' in the current working directory. .wine is a filename beginning with a dot. If you're still confused, try these commands... $ ls -a $ ls . $ ls ./ $ ls .. (.. (dot dot) is the parent directory) --Aidan -- 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/loom.20101005t000421-...@post.gmane.org
Re: nvidia problems after upgrade
Steven Demetrius wrote: Please list the full contents of the /etc/X11/xorg.conf file and the kernel version you are using. Ok, I've attached my xorg.conf file to this message, and my kernel version is 2.6.26-1-686 (as reported by uname -r). You can also get xorg to generate a xorg.conf file for you. Try this first. As root use the following command. # Xorg -configure It will create a xorg.conf file in the current directory. Now you can test Xwindow with this config file. # Xorg -config ./xorg.conf See man Xorg, for more information. I didn't try this, because X seems to detect the free nv driver when the package for it is installed, but, as I said before, freezes the system after a few minutes of use. If you want to use the non-free driver you will need to either download the driver for your kernel version if its available or compile it. I know. I was using it before I upgraded. And the free nv driver was working also before I upgraded. Thanks, Aidan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
nvidia problems after upgrade
Hello, I just upgraded to lenny without any problems, except for one: I'm using the vesa xorg driver, because using the free nv driver causes the display to freeze after a few minutes of use (I can move the mouse, but I can't even switch to a virtual console). I was using the non-free nvidia driver before the upgrade, but after upgrading, X wouldn't start until after I ran... dpkg-reconfigure xserver-xorg ...and added the following lines to /etc/X11/xorg.conf... SubSection Display Depth 24 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection ...(before I added that subsection, my monitor gave the out of range message when X started). I want to be able to use the free nv driver (without problems) before I even try to get the non-free dirver working. I'm really stumped here; can anyone help? (By the way, this is the first time I've upgraded a Debian system.) Thanks, Aidan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
