Re: autofs config [SOLVED]

Hi. On Tue, 10 Jan 2017 19:32:54 -0500 Harry Putnam wrote: > Reco writes: > > [...] > > >> ls /prj/d0 or ls /prj/dv both fail. However another share on that > >> same setup on the solaris host `gv' and 2x comes up as expected. > > > > You

detecting hardware for custom kernel

Is there a command to detect hardware for a custom kernel? I would like to take advantages of the newer kernels. Thanks -- HP Garcia, Photographer www.HPGPhotography.com

Re: CDROM device suddenly doesn't exist....

On Wed, 11 Jan 2017 13:09:59 +1100 Charlie sent: > Hello, > > Debian testing 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 > GNU/Linux > > Suddenly have a CDROM problem: > $ mount /media/cdrom > mount: /dev/sr0 is write-protected, mounting read-only > mount: special device

CDROM device suddenly doesn't exist....

Hello, Debian testing 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 GNU/Linux Suddenly have a CDROM problem: $ mount /media/cdrom mount: /dev/sr0 is write-protected, mounting read-only mount: special device /dev/sr0 does not exist Did: # ls -l /dev/sr0 ls: cannot access

Re: autofs config

Reco writes: [...] >> ls /prj/d0 or ls /prj/dv both fail. However another share on that >> same setup on the solaris host `gv' and 2x comes up as expected. > > You lost me here. If 'd0' and 'dv' are share names, you should use > auto.net like this: This problem is

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

Erwan David wrote: > > systemd is NOT an init system. It is a global system pretending to > replace init, session management,dns, ntp, and more and more other > components with incomplete solutions thought only for the laptops of its > developers (see the "we won't support hard disks, we all use

Como habilitar o botão direito do mouse no painel do gnome3?

Boa noite. Como habilitar o botão direito no painel do gnome3? Quando pressiono o botão direito do mouse na barra nada acontece. Instalei o netspeed_0.16-3 mas ele não aparece mesmo após reiniciar. Alguma sugestão? Como resolver? Obrigado.

Re: Is anyone else experiencing intermittent Plasma freezes as of very recently?

On 01/10/2017 08:10 AM, newbee...@nativobject.net wrote: Le 10/01/2017 à 00:29, fra...@inventati.org a écrit : Hi I'm on Debian Stretch but I'm not experiencing the issues you're discussing here. However I remember to have had similar issues with Plasma 5 and Intel drivers. As a workaround I

Re: Systemd: no error but "maintenance mode"

On Tue, 10 Jan 2017 14:29:17 -0600 David Wright wrote: > > I can see that a post-mortem of what went wrong is useful, but I can't > understand why you say that systemd made the "wrong" assumption. > If you specify something wrongly, you can't really expect it to do >

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

Le 01/10/2017 à 21:49, David Wright a écrit : > On Tue 10 Jan 2017 at 20:54:50 (+0100), Steffen Dettmer wrote: >> On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote: > I'd rather keep it as simple as possible you can still use sysvinit as init >> >> I read that

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue, 10 Jan 2017 08:57:36 -0500 rhkra...@gmail.com sent: > > > This is called evolution. > > > > There are dissenting views, and y'all know that. > > Just to get my $0.02 in, evolution makes many mistakes. In fact, it > is a process of (accidental) trial and error. ;-) After

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue 10 Jan 2017 at 20:54:50 (+0100), Steffen Dettmer wrote: > On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote: > >>> I'd rather keep it as simple as possible > >> > >> you can still use sysvinit as init > > I read that trying to use sysvinit causes trouble and several

Re: Systemd: no error but "maintenance mode"

On Tue 10 Jan 2017 at 20:08:10 (+0100), Steffen Dettmer wrote: > On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote: > >> What happened before: > >> I had issue with a Debian server SATA bus [1]. I noticed because > >> apt-get upgrade hung, because initramfs updater calls "sync" which

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 10, 2017 at 08:54:50PM +0100, Steffen Dettmer wrote: > On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote: > >>> I'd rather keep it as simple as possible > >> > >> you can still use sysvinit as init > > I read that

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue, 10 Jan 2017 20:54:50 +0100 Steffen Dettmer wrote: > On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl > wrote: > >> > >> you can still use sysvinit as init > > I read that trying to use sysvinit causes trouble and several things > depend on

Re: Systemd: no error but "maintenance mode"

On Tue, 10 Jan 2017 20:08:10 +0100 Steffen Dettmer wrote: > On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote: > >> What happened before: > >> I had issue with a Debian server SATA bus [1]. I noticed because > >> apt-get upgrade hung, because initramfs

Re: Systemd: no error but "maintenance mode"

Am 10.01.2017 um 20:08 schrieb Steffen Dettmer: > On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote: >>> What happened before: >>> I had issue with a Debian server SATA bus [1]. I noticed because >>> apt-get upgrade hung, because initramfs updater calls "sync" which >>> hang because

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue, Jan 10, 2017 at 12:51 PM, Dominique Dumont wrote: > On Monday, 9 January 2017 22:49:02 CET Steffen Dettmer wrote: >> I'm looking at Jessie (Debian 8) man fsck. I found no refernce >> to systemd. I think this is some compatiblity feature of systemd. > > See

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue, Jan 10, 2017 at 1:01 AM, Michael Biebl wrote: >>> I'd rather keep it as simple as possible >> >> you can still use sysvinit as init I read that trying to use sysvinit causes trouble and several things depend on systemd at the moment. > The shell scripts used by

Re: Systemd: no error but "maintenance mode"

On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote: >> What happened before: >> I had issue with a Debian server SATA bus [1]. I noticed because >> apt-get upgrade hung, because initramfs updater calls "sync" which >> hang because of [1]. All operations accessing a certain (backup)

Re: autofs config

Hi. On Tue, 10 Jan 2017 12:50:44 -0500 Harry Putnam wrote: > I finally got around to trying the auto.net file you mentioned in your > first reply in this thread. > > I still cannot read it and understand what it does but I may have some > good news to report. The

Re: autofs config

Reco writes: [...] Harry wrote: >> So maybe that has something to do with the problem... Reco replied: > Hardly. The way you're doing on Solaris it you provide NFS shares to > everyone and their dog in read-write mode with sec=sys by NFS versions > ranging from two to

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

rhkra...@gmail.com wrote: > On Tuesday, January 10, 2017 03:39:06 AM to...@tuxteam.de wrote: >> On Tue, Jan 10, 2017 at 09:14:48AM +0100, deloptes wrote: >> > Michael Biebl wrote: >> > > Am 10.01.2017 um 00:43 schrieb deloptes: >> > >> Steffen Dettmer wrote: >> > >>> I'd rather keep it as simple

[Solved] Re: no tty active after system migration to second disk

deloptes wrote: > Hi community, > I recently added a ssd and moved the debian system to it. It might be not > related to this fact but I now do not see the tty login prompt > (CTRL+ALT+F1..F6). I however see it if I boot with sysvinit, so I think it > is something in systemd, but I have no idea

Re: breaks unrelated software (not real issue for Debian)

I found that the issue related has worked after. It's not blocking the boot. I have just installed the USB-card again and it worked. Excelent operating system, sorry for the bug report! Regards Torquato Mesquita de Rezende Borges On 2017-01-10 05:01, recipe@lycos.com wrote: >

Re: two graphics cards and two monitors

On 01/10/2017 11:19 AM, Teemu Likonen wrote: Dan Ritter [2017-01-10 10:56:21-05] wrote: If you are using open drivers, `xrandr` should be able to list the available outputs and modes and change between them. If you are using proprietary NVidia drivers, "nvidia-settings" should be able to work

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tue 10 Jan 2017 at 12:51:09 (+0100), Dominique Dumont wrote: > On Monday, 9 January 2017 22:49:02 CET Steffen Dettmer wrote: > > I'm looking at Jessie (Debian 8) man fsck. I found no refernce > > to systemd. I think this is some compatiblity feature of systemd. > > See systemd.mount(5) and

Re: two graphics cards and two monitors

Dan Ritter [2017-01-10 10:56:21-05] wrote: > If you are using open drivers, `xrandr` should be able to list the > available outputs and modes and change between them. > > If you are using proprietary NVidia drivers, "nvidia-settings" should > be able to work for you. xrandr should work nicely

Re: Dependency problem with virtualbox-guest-x11

On Tue, Jan 10, 2017 at 11:07:54AM +, Darac Marjal wrote: > On Tue, Jan 10, 2017 at 11:46:06AM +0100, Hans wrote: > >Dear maintainers, > > > >since months in debian/testing the xserver-* packages cannot be updated as > >the > >package virtualbox-guest-x11 inhibits the update due to the wrong

Re: two graphics cards and two monitors

On Wed, Jan 11, 2017 at 12:43:02AM +0900, Mark Fletcher wrote: > > So a generic graphics card circa 2009, with a nVidia GeForce 9800 GTX+ > chipset, with an old D-type connector, a DVI connector, and an HDMI > connector -- would you expect it to be able to drive more than one > display? Given

Re: two graphics cards and two monitors

On Wed, Jan 04, 2017 at 10:43:10PM -0500, Felix Miata wrote: > Mark Fletcher composed on 2017-01-04 23:30 (UTC+0900): > > >I've seen several people say or imply this in the past. But I have an > >ignorant question I am almost too embarrassed to ask (almost). Most > >normal cards have only one

Re: autofs config

On Tue, 10 Jan 2017 10:18:53 -0500 Harry Putnam wrote: > Reco writes: > > > To workaround #828217 please comment out the line with '-host' in > > /etc/auto.master. > > Just wanted to get back to you right away about this part. Still > looking into

Re: autofs config

Reco writes: > To workaround #828217 please comment out the line with '-host' in > /etc/auto.master. Just wanted to get back to you right away about this part. Still looking into the other things you mentioned. The `-hosts' line in auto.master has been commented out

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Tuesday, January 10, 2017 03:39:06 AM to...@tuxteam.de wrote: > On Tue, Jan 10, 2017 at 09:14:48AM +0100, deloptes wrote: > > Michael Biebl wrote: > > > Am 10.01.2017 um 00:43 schrieb deloptes: > > >> Steffen Dettmer wrote: > > >>> I'd rather keep it as simple as possible > > >> > > >> you can

Re: Failure searching forfile known to exist

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 10, 2017 at 07:26:59AM -0600, Richard Owlett wrote: [...] > I said I had "a command line outlook", not that I was strongly > anti-GUI. > See, no " required ;/ > Seriously though, I think the default action of Mate's "Find" menu > option

Re: Re: Bash different behaviour of read / strings in jessie versus stretch (regression?)

On Tue, Jan 10, 2017 at 01:10:53AM +0100, foo fighter wrote: > mapfile -t _array <<<"${_inputstring// /$'\n'}" For larger inputs, this will probably be more efficient: mapfile -t _array < <(your command | tr ' ' '\n') Bash's substitution can be rather slow on large strings.

Re: Failure searching forfile known to exist

On 1/9/2017 5:43 PM, Lisi Reisz wrote: On Monday 09 January 2017 15:34:44 Richard Owlett wrote: On 1/9/2017 8:13 AM, Greg Wooledge wrote: On Mon, Jan 09, 2017 at 12:23:47AM -0600, Richard Owlett wrote: I could not remember where "profiles.ini" was stored. locate profiles.ini find ~ -name

How secure are nested/indirect file access restrictions?

Hello! Let's assume the following file permissions: drwxr-xr-x root root /srv drwxr-x--- root srv-www /srv/www drwxrws--x root dev-1/srv/www/dom-1 -rw-rw-r-- usr-1 dev-1/srv/www/dom-1/index.php While the html subfolder perms allow write access only to root and users within

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Monday, 9 January 2017 22:49:02 CET Steffen Dettmer wrote: > I'm looking at Jessie (Debian 8) man fsck. I found no refernce > to systemd. I think this is some compatiblity feature of systemd. See systemd.mount(5) and systemd.swap(5) Compatiblity is done by systemd-fstab-generator HTH --

Re: Mute mutes speaker, but Unmute does not unmute speaker channel (XFCE4)

Just thinking that maybe I should look in: /etc/acpi/events Maybe add my script there on unmute event.

Re: New version of lcdproc in experimental

On Monday, 9 January 2017 20:28:46 CET Brian wrote: > What will happen to a bug report which is clearly an upstream issue and > tagged as such which is sent to the BTS? I forward manually upstream issue to upstream bug tracker. That process does not scale and is often late... All the best --

Re: Mute mutes speaker, but Unmute does not unmute speaker channel (XFCE4)

I will have access to the laptop only later to test these new thing I found: https://wiki.manjaro.org/index.php?title=Volume_Stuck_on_Mute_%28XFCE_Desktop%29 From: https://ubuntuforums.org/showthread.php?t=1796713 I may add a key in XFCE bindings looking like: amixer -c 0 set Speaker playback

Re: Dependency problem with virtualbox-guest-x11

On Tue, Jan 10, 2017 at 11:46:06AM +0100, Hans wrote: Dear maintainers, since months in debian/testing the xserver-* packages cannot be updated as the package virtualbox-guest-x11 inhibits the update due to the wrong dependencies. IMO it is not really a bug and maybe it could be fixed easily.

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

On Mon, Jan 09, 2017 at 10:49:02PM +0100, Steffen Dettmer wrote: > Because man page says so? Because fsck's job is to check fs? > Don't know what systemd interferes at all. See systemd-fsck(8). -- Jonathan Dowland Please do not CC me, I am subscribed to the list. signature.asc Description:

Dependency problem with virtualbox-guest-x11

Dear maintainers, since months in debian/testing the xserver-* packages cannot be updated as the package virtualbox-guest-x11 inhibits the update due to the wrong dependencies. IMO it is not really a bug and maybe it could be fixed easily. The problem seem to be the wrong xserver-*-abi. It

Re: autofs config

Hi. On Mon, Jan 09, 2017 at 06:48:43PM -0500, Harry Putnam wrote: > Reco Wrote: > > Which brings me to this: > > > > 1) What security option are you using (i.e. none, sys, krb5, etc)? > > If unsure, please mount a share by hand and obtain mount options > > from /proc/mounts. > > It

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 10, 2017 at 09:14:48AM +0100, deloptes wrote: > Michael Biebl wrote: > > > Am 10.01.2017 um 00:43 schrieb deloptes: > >> Steffen Dettmer wrote: > >> > >>> I'd rather keep it as simple as possible > >> > >> you can still use sysvinit as

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

Michael Biebl wrote: > Am 10.01.2017 um 00:43 schrieb deloptes: >> Steffen Dettmer wrote: >> >>> I'd rather keep it as simple as possible >> >> you can still use sysvinit as init > > The shell scripts used by sysvinit are not simpler. More familiar maybe, > but not simpler. > > This is

Re: Upgrade Wheezy to Jessie - gave up waiting for root device

On Friday, 6 January 2017 14:38:01 CET Steven Kauffmann wrote: > When booting I get the following output: give up waiting for root device ... Looks like the kernel boots but cannot find the disk that contains '/' > I can still boot into the old kernel (3.2.0-4-amd64). While in grub menu, check