about apt and aptitude update
I use both apt and cmdline aptitude. Mostly cmdline aptitude I'm curios if when I call `apt update' or `aptitude update', if they are refreshing the same database files... wondering if I could do just one update on either tool and that would do both.
Re: debian exim4 smarthost and relay
> Reco writes: > David Wright writes: > Brian writes: Thanks to all for the succinct and helpful answers Sometimes googling excessively can confuse me a bit.
debian exim4 smarthost and relay
I hope this is the correct group for debian exim4 questions. I'm sure someone will point me elsewhere if not - Setup: New install of debian 10, in VBox vm attempting to get exim4 working. - Internet host with no recognized or dns resolvable name, or domain - Receives dhcp address, but made mostly permanent by router capabilities When editing a smarthost line in udpate-exim4.conf.conf How does one enter a server that requires ssl 465. Is adding 465 port all that is necessary? ..like dc_smarthost='smtp.server.com:465' I've also seen two colons used while googling on this: dc_smarthost='smtp.server.com::465' Which if any is correct? --- --- ---=--- --- --- If one uses the port number in update-exim4.conf.conf is it also required in passwd.client? smtp.server.com:465:user@some.domain:SECRETpw And again .. one or two colons? Or is this not required? --- --- ---=--- --- --- My googling has also caused some confusion to me about editing something for smtp transport: Will it also be necessary to edit something into smtp transport regarding the use of ssl 465? If so, can anyone show an example of how that is done?
Re: uefi boot install and disk partitions
Bonno Bloksma writes: > Hi, > > > > I have been creating a small (300MB) primary /boot partition at the > beginning of the disk for as long as I can remember... That is after > disks got to be too big for the BIOS to reach all of the disk to be > able to boot from a file anywhere on the disk. > > So far so good, that still works but do I still need that > partition when I create an EFI System Partition (ESP) to boot using > UEFI? > [...] First off, I'm pretty sure that Pascal is far more knowledgeable than I but I just had some experience with setting up Uefi. Still working on it so not tested yet. It is on a zfs-on-root-linux install so that might be different. But the part of preparing the disk for booting seems to be the same. I used `gsdisk' which is in the package `gdisk' in the debian repo. There are detailed direction by Richard Laager: I'm quoting a small bit from URL: https://github.com/zfsonlinux/zfs/wiki/Debian-Buster-Root-on-ZFS 2.3 Partition your disk(s): [...] section on non efi boot snipped Run this for UEFI booting (for use now or in the future): sgdisk -n2:1M:+512M -t2:EF00 $DISK Run this for the boot pool: sgdisk -n3:0:+1G -t3:BF01 $DISK He's taking about a zpool setup but I think Its the same far as preparing the disk for uefi booting. There are more details further on concerning actually installing the boot code on the disk where booting will occur. You probably want to read this part: 4.8b Install GRUB for UEFI booting
What program is capturing key press on root window of X?
cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=debian (running LXDE desktop) Somewhere in the last few months my Debian OS has acquired an input box on upper right of base window (in X) that appears to grab any key presses aimed at the base window and print them in that small input window. Since I have run the `xbindkeys' program (An keybinding program that takes its intput from key presses in base window and calls programs thru a control script ~/.xbindkeys.scm), this new key grabbing program that seems to run at startup is ruining that whole process. I wasn't able to tell which program it is by examining the autostart programs ... can anyone tell me what that is that is running so I can turn it off?
Re: Not finding openssl during a pkg build (mailsend)
Greg Wooledge writes: > On Mon, Oct 01, 2018 at 12:47:01PM -0400, Harry Putnam wrote: >> cat /etc/debian_version >> 9.4 > >> I do have openssl and libssl-dev installed; > > In stretch, libssl-dev is the development package for OpenSSL version 1.1. > This is a relatively new version of OpenSSL, and it is not compatible with > version 1.0. > > Most programs that use OpenSSL will be expecting to use the version 1.0 API. > I don't know your particular program, but it's a reasonable guess that > it wants the older version. > > Try installing libssl1.0-dev (which will remove libssl-dev) and see if that > works. You can switch back and forth as needed when compiling various > programs, but you can't have both installed at the same time. Thanks for the helpful and precise input. So far haven't managed to make it work Something else must be a problem. After some more testingh/tinkering I may have a new query. Your response was helpful information anyway.
Not finding openssl during a pkg build (mailsend)
cat /etc/debian_version 9.4 Summary: Trying to compile a tool called `mailsend' (https://github.com/muquit/mailsend/releases/) (Which does not appear to be available in the regular repo). But cannot get it to find openssl. I do have openssl and libssl-dev installed; --- --- ---=--- --- --- Details A check of apt-get search openssl A quick check of ./configure file suggests using: grep [\-]-with.*openssl ./configure --with-openssl=PATH where the root of OpenSSL is installed --with-openssl-includes where the OpenSSL includes are. --with-openssl-libraris where the OpenSSL library is installed. I tried --with-openssl=/usr/bin/openssl and --with-openssl=/usr/lib/ssl and --with-openssl-includes=/usr/include/openssl using dpkg -L and `grep -v' (to keep down the amount of data) shows: dpkg -L openssl |grep -v share /etc /etc/ssl /etc/ssl/certs /etc/ssl/openssl.cnf /etc/ssl/private /usr /usr/bin /usr/bin/c_rehash /usr/bin/openssl /usr/lib /usr/lib/ssl /usr/lib/ssl/misc /usr/lib/ssl/misc/CA.pl /usr/lib/ssl/misc/tsget /usr/lib/ssl/certs /usr/lib/ssl/openssl.cnf /usr/lib/ssl/private and dpkg -L libssl-dev (95 lines of output omitted) Are there other parts of openssl I need to install? I'm not figuring out how to direct this build toward openssl, but the configure process continues to show: [...] checking for OpenSSL... no [...]
What is available for setting services to run levels
What tools do we have for setting services to run levels
[OT] debian (or debian like) terminal program for android
aside: , | Having such a time trying to google this. It seems google has been | dumbed down to the point where +word or "these words" no longer force | those things to be in the hits. ` Can anyone tell me if there is a serious terminal program for android phones? I mean a full OS and the basic commands. Especially I'd like to have ssh and scp among them. What I've already tried and found lacking: Terminux simple sshd ConnectBot Material Terminal (Supposed to be an improvement over Terminal Emulator for Android so didn't try that one)
preferences > openbox configuration manager no start
setup: OS = Debian Testing (running as guest in a Vbox vm on an openindiana (solaris-11 offshoot [illumos powered])) Virtualbox-5.6.2 desktop=lxde I've reported a problem about the desktop icons unable to display their *.png images in another thread... the problem described below is probably part of the same root cause What I'm seeing is at the lxde main menu > preferences > openbox configuration manager When clicked nothing happens I just see the mouse cursor show the `busy' icon. Nothing ever starts After doing a few dpkg -L pkgname looking for something that might be the binary of that manager... I'm not able to find it. Even chking on a `stable' version (stretch) I can't really tell what runs when you click the openbox config manager. I guess it is reading '.config/openbox/lxde-rc.xml' Anyway, I'm not able to tell what is supposed to happen when that menu item is clicked. I can see whatever it is ... is not starting ... the `busy' mouse icon eventually stops and I get the regular mouse cursor back... takes about 10-15 seconds but configurator never appears. One thing that may be of note is that the .config/openbox/lxde-rc.xml Is getting read at login... If I make changes in that file they do show up if I relogin. But for some reason the configurator that edits that file is not starting.
testing running lxde cannot diplay desktop icon images
Setup Testing running as guest in vbox vm on a Solaris (openindiana) host. This OS has been in operation since before the release of stretch ... It sees little use and has exibited very few problems. I run the lxde desktop. The problem I am seeing is that the desktop starts but only diplays a small white box with a red X in it, where-ever there should be an item in the bottom panel. Like the main menu item or the iceweasel item. those and several other `normal' lxde items that reside in the bottom panel all show a small white box with red x. Something one sees when an icons image file is missing or not viewable for some reason. A right click on the Main Menu icon shows where the image file should be: /usr/share/lxde/images/xde-icon.png So to dispaly the permissions we'll show just directory and then the file: ls -ld /usr/share/lxde/images I've attached a small screen shot showing what I'm describing. I cut it down to just the bottom of the screen, but in full width.
testing running lxde cannot diplay desktop icon images
Setup Testing running as guest in vbox vm on a Solaris (openindiana) host. This OS has been in operation since before the release of stretch ... It sees little use and has exibited very few problems. I run the lxde desktop. The problem I am seeing is that the desktop starts but only diplays a small white box with a red X in it, where-ever there should be an item in the bottom panel. Like the main menu item or the iceweasel item. those and several other `normal' lxde items that reside in the bottom panel all show a small white box with red x. Something one sees when an icons image file is missing or not viewable for some reason. A right click on the Main Menu icon shows where the image file should be: /usr/share/lxde/images/xde-icon.png So to dispaly the permissions we'll show just directory and then the file: ls -ld /usr/share/lxde/images I've attached a small screen shot showing what I'm describing. I cut it down to just the bottom of the screen, but in full width.
Following full-upgrade panel icons cannot display the image files
Setup: Running stretch as guest vm on Openindiana (a solaris 11 off shoot) inside Virtualbox Using lxde desktop, but set to boot into console mode, and I use startx to get to X with I want it. Following a startx, I see the buttons on bottom panel just show a white rectangle with red X in it. I see the image files they point to at /usr/share/lxde/images/ are present. I tried chowning that directory to my user with sudo chown -R reader:reader /usr/share/lxde/images on the off chance there is a permission problem somewhere in that chain. But appears to make no difference It must be some kind of clue that the images are not able to display, but I'm not figuring out what it is.
Re: vbox cannot find headers, although they are installed
Eike Lantzsch <zp6...@gmx.net> writes: > On Saturday, January 6, 2018 8:36:38 PM -03 Harry Putnam wrote: >> Having a problem getting the vbox guest additions on a `testing' >> install to allow for larger monitor resolution. >> >> When I attempt to install the additions the ouput says it cannot find >> the headers for the running kernel. >> >> I have checked, rechecked and reinstalled the headers but still get >> the message that they cannot be found and the kernel module build then >> fails. >> >> (Note: All debian systems mentioned below are running as guests on an >> `openindiana' (a solaris offshoot) host) >> >> (Full output of attempted guest additions install are at the end) >> >> But briefly . . . . >> Harry wrote: >> >From the host with the failure: >> uname -r 4.14.0-2-amd64 Eike responded: > This is not Stretch? Stretch is still with 4.9.0-5-amd64. I overlooked your comment above in my previous response Sorry I wasn't clear... but I did indicate in OP that the problem is on a `testing' host: Harry wrote in OP... first lines , | Having a problem getting the vbox guest additions on a `testing' | ^^^ | install to allow for larger monitor resolution. ` I went on to say that I am running two `stretch' hosts that did not display this problem... even though all hosts have the proper header files installed.
Re: vbox cannot find headers, although they are installed
Eike Lantzschwrites: Harry wrote: >> What am I missing? > Eike Replied: > Did you by any chance install a kernel higher than 4.14.0-2 to check it out, > then went back to 4.14.0-2 or installed 4.14.0 and then went back to 4.9.0? > In that case VBox is most probably still looking for the headers of the > higher > kernel version and cannot find them. I ran into that problem before. > In that case you will have to deinstall VBox completely and install it again. > You can retain the virtual installations and later incorporate them into VBox > again. No, I've only ever installed kernels when an upgrade included a new one... that is what happened in this case to get to 4.14*. Is it possible that Debian just doesn't know where to look for the header files? Seems unlikely since two `stretch' systems, following a full-upgrade had no such problems even though new kernels were installed as part of that upgrade. I see notations regarding more than one error in the full log output I posted in this thread... but am not savvy enough to know what they mean. Early on: , | grep: /lib/modules/4.14.0-2-amd64/build/include/linux/version.h: No such file or directory | make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.14.0-2-amd64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules | make -C /usr/src/linux-headers-4.14.0-2-amd64 KBUILD_SRC=/usr/src/linux-headers-4.14.0-2-common \ | -f /usr/src/linux-headers-4.14.0-2-common/Makefile modules | test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ | echo >&2; \ | echo >&2 " ERROR: Kernel configuration is invalid."; \ | echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ | echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ | echo >&2 ;\ | /bin/false) | | [...] ` and then at the end: , | [...] | | /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:313:47: error: implicit declaration of function ‘set_pages_x’; did you mean ‘get_page’? [-Werror=implicit-function-declaration] | # define MY_SET_PAGES_EXEC(pPages, cPages)set_pages_x(pPages, cPages) |^ | /tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c:444:13: note: in expansion of macro ‘MY_SET_PAGES_EXEC’ | MY_SET_PAGES_EXEC([iPage], 1); | ^ | /tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c: In function ‘VBoxGuest_RTMemContFree’: | /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:314:47: error: implicit declaration of function ‘set_pages_nx’; did you mean ‘set_page_node’? [-Werror=implicit-function-declaration] | # define MY_SET_PAGES_NOEXEC(pPages, cPages) set_pages_nx(pPages, cPages) |^ | /tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c:492:13: note: in expansion of macro ‘MY_SET_PAGES_NOEXEC’ | MY_SET_PAGES_NOEXEC([iPage], 1); | ^~~ | cc1: some warnings being treated as errors | /usr/src/linux-headers-4.14.0-2-common/scripts/Makefile.build:319: recipe for target '/tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.o' failed | make[4]: *** [/tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.o] Error 1 | /usr/src/linux-headers-4.14.0-2-common/Makefile:1522: recipe for target '_module_/tmp/vbox.0' failed | make[3]: *** [_module_/tmp/vbox.0] Error 2 | Makefile:146: recipe for target 'sub-make' failed | make[2]: *** [sub-make] Error 2 | Makefile:8: recipe for target 'all' failed | make[1]: *** [all] Error 2 | /tmp/vbox.0/Makefile.include.footer:79: recipe for target 'vboxguest' failed | make: *** [vboxguest] Error 2 | Creating user for the Guest Additions. | Creating udev rule for the Guest Additions kernel module. ` Any help on what those indicate needs doing?
Re: vbox cannot find headers, although they are installed
"x9p" <deb...@x9p.org> writes: > On Sat, January 6, 2018 11:36 pm, Harry Putnam wrote: > ... >> (Look at /var/log/vboxadd-install.log to find out what went wrong) > ... > > the line above can explain a lot. Looked at that for some length before posting... it didn't explain dodo to me... didn't understand what I was reading, maybe it will to you: grep: /lib/modules/4.14.0-2-amd64/build/include/linux/version.h: No such file or directory make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.14.0-2-amd64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules make -C /usr/src/linux-headers-4.14.0-2-amd64 KBUILD_SRC=/usr/src/linux-headers-4.14.0-2-common \ -f /usr/src/linux-headers-4.14.0-2-common/Makefile modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/* make -f /usr/src/linux-headers-4.14.0-2-common/scripts/Makefile.build obj=/tmp/vbox.0 gcc-7 -Wp,-MD,/tmp/vbox.0/.VBoxGuest-linux.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include -I./arch/x86/include/generated -I/usr/src/linux-headers-4.14.0-2-common/include -I./include -I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I/usr/src/linux-headers-4.14.0-2-common/include/uapi -I./include/generated/uapi -include /usr/src/linux-headers-4.14.0-2-common/include/linux/kconfig.h -I/tmp/vbox.0 -I/tmp/vbox.0 -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-declaration-after-statement -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.14.0-2-amd64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/ -I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux -D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -DKBUILD_BASENAME='"VBoxGuest_linux"' -DKBUILD_MODNAME='"vboxguest"' -c -o /tmp/vbox.0/.tmp_VBoxGuest-linux.o /tmp/vbox.0/VBoxGuest-linux.c if [ "-pg" = "-pg" ]; then if [ /tmp/vbox.0/VBoxGuest-linux.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount "/tmp/vbox.0/VBoxGuest-linux.o"; fi; fi; gcc-7 -Wp,-MD,/tmp/vbox.0/.VBoxGuest.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include -I./arch/x86/include/generated -I/usr/src/linux-headers-4.14.0-2-common/include -I./include -I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I/usr/src/linux-headers-4.14.0-2-common/include/uapi -I./include/generated/uapi -include /usr/src/linux-headers-4.14.0-2-common/include/linux/kconfig.h -I/tmp/vbox.0 -I/tmp/vbox.0 -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gn
vbox cannot find headers, although they are installed
Having a problem getting the vbox guest additions on a `testing' install to allow for larger monitor resolution. When I attempt to install the additions the ouput says it cannot find the headers for the running kernel. I have checked, rechecked and reinstalled the headers but still get the message that they cannot be found and the kernel module build then fails. (Note: All debian systems mentioned below are running as guests on an `openindiana' (a solaris offshoot) host) (Full output of attempted guest additions install are at the end) But briefly . . . . >From the host with the failure: uname -r 4.14.0-2-amd64 aptitude search headers |grep ^i i linux-headers-4.14.0-2-amd64 - Header files for Linux 4.14.0-2-amd64 i A linux-headers-4.14.0-2-common - Common header files for Linux 4.14.0-2 , | On two other debian systems (both running stretch, not `testing') everything works as | expected and the kernel module build succeeds... monitor settings then | act accordingly. | | From 2 stretch hosts: | Of course, it is a different kernel and headers (4.9.0-5-amd64) on the | `stretch' systems and with like named header files. | | i A linux-headers-4.9.0-5-common | i A linux-headers-4.9.0-5-amd64 | | With those in place on the stretch systems the guest additions build | just like they should. ` What am I missing? = Terminal output from attempting install of guest additions = [Did not post the full log referred to in the output below... it is very long... but I can post it if necessary] root # bash ./VBoxLinuxAdditions.run Verifying archive integrity... All good. Uncompressing VirtualBox 5.0.40 Guest Additions for Linux VirtualBox Guest Additions installer Removing installed version 5.0.40 of VirtualBox Guest Additions... Removing existing VirtualBox non-DKMS kernel modules ...done. update-initramfs: Generating /boot/initrd.img-4.14.0-2-amd64 Copying additional installer modules ... Installing additional modules ... Removing existing VirtualBox non-DKMS kernel modules ...done. Building the VirtualBox Guest Additions kernel modules The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason. Building the main Guest Additions module ...fail! (Look at /var/log/vboxadd-install.log to find out what went wrong) Doing non-kernel setup of the Guest Additions ...done.
reconstitute /boot on stretch
I managed to delete /boot and all contents, on a `stretch' system. Of course it will not boot now. So maybe work from a live cd or install media... How can I go about reconstituting the /boot directory and contents that match my install? Not sure how to create the initrd, Sysmap, grub directory and so forth. Really just kind of stunned and drawing blanks about how to proceed.
on non-running OS find all installed pkgs
The hosts in this query are both on vbox vms. One not running but with OS disk mounted on a different host. How can I get a list of all debian pkgs installed on the OS that is not running? That is, when I have the debian OS disk mounted on a different HOST. Is there something in var (or anywhere else for that matter) that can be used to get all installed pkgs?
Re: Peculiar problem with root login
Tom Dialwrites: [...] >From Harry's settings: >> LoginGraceTime 120 >> PermitRootLogin without-password Tom D wrote: > This will prevent root login using a password. Only other methods, such > as RSA authentication are to be permitted. That turned out to be exactly the problem. Somewhere amongst my fiddling, weeks ago now. I must have uncommented that or something like. [...] >From Harry's settings: >> PermitRootLogin yes > This may or may not be effective owing the the above setting of > "PermitRootLogin without-password" depending on how sshd treats > duplicate setting. My (jessie) man page does not say whether the first > or last setting will be effective. I guess we may assume it goes by the first since 'PermitRootLogin yes' was the very last line of my config. [...] David Christensen writes: [...] >> ChallengeResponseAuthentication no >> PasswordAuthentication yes > > I use: > > PasswordAuthentication no > > > This requires all users to have their remote user public keys entered > into their authorized_keys files to log in from those remote hosts. > > >> X11Forwarding yes >> X11DisplayOffset 10 >> PrintMotd no >> PrintLastLog yes >> TCPKeepAlive yes >> AcceptEnv LANG LC_* >> Subsystem sftp /usr/lib/openssh/sftp-server >> UsePAM yes >> PermitRootLogin yes > > This conflicts with the above setting (which is what I use): > > PermitRootLogin without-password Yup, that was the problem Thank you both for the excellent input.. (snipped in this response but kept on hand for future reference..)
Re: Peculiar problem with root login
Harry Putnam <rea...@newsguy.com> writes: >> >> # ls -1 /root/.ssh >> Sorry ... I managed to overlook this one: root # ls -la .ssh total 12 drwx-- 2 root root 4096 May 30 21:44 . drwx-- 6 root root 4096 Jun 18 11:35 .. -rw-r--r-- 1 root root 666 May 30 22:17 known_hosts
Re: Peculiar problem with root login
Harry Putnam <rea...@newsguy.com> writes: >> >> # ls -1 /root/.ssh >> Sorry ... I managed to overlook this one: root # ls -la .ssh total 12 drwx-- 2 root root 4096 May 30 21:44 . drwx-- 6 root root 4096 Jun 18 11:35 .. -rw-r--r-- 1 root root 666 May 30 22:17 known_hosts
Re: Peculiar problem with root login
David Christensen <dpchr...@holgerdanske.com> writes: > On 06/12/2017 06:39 AM, Harry Putnam wrote: >> Running debian jesse in a vbox vm on a Solaris host >> >> I have what seems like an unusual problem with root login on this >> host. [...] >> I'm fresh out of ideas as to what else to do here. >> >> The auth log shows: >> >> Jun 11 14:50:55 d2 sshd[2830]: pam_unix(sshd:auth): authentication >> failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.local.lan >> user=root >> >> Jun 11 14:50:57 d2 sshd[2830]: Failed password for root from >> 127.0.0.1 port 54522 ssh2 > > Please run the following commands from the console of the jesse vm as > root and paste your console session (prompts, commands entered, output > obtained). If you redact anything, substitute the phrase > '': > > # cat /etc/debian_version > > # uname -a > > # dpkg-query --show openssh-server > > # dpkg-query --show openssh-client > > # ls -1 /etc/ssh/*ssh* > > # ls -1 /root/.ssh > > # egrep -v '^.*#' /etc/ssh/sshd_config | grep . > > # ssh localhost > > # tail /var/log/auth.log Thanks for the prod... I should have included at least some of that. --- --- ---=--- --- --- diagnostic_data: root # cat /etc/debian_version 8.8 root # uname -a Linux d2 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux root # dpkg-query --show openssh-server openssh-server 1:6.7p1-5+deb8u3 root # dpkg-query --show openssh-client openssh-client 1:6.7p1-5+deb8u3 root # ls -1 /etc/ssh/*ssh* /etc/ssh/ssh_config /etc/ssh/sshd_config /etc/ssh/sshd_config~ /etc/ssh/ssh_host_dsa_key /etc/ssh/ssh_host_dsa_key.pub /etc/ssh/ssh_host_ecdsa_key /etc/ssh/ssh_host_ecdsa_key.pub /etc/ssh/ssh_host_ed25519_key /etc/ssh/ssh_host_ed25519_key.pub /etc/ssh/ssh_host_rsa_key /etc/ssh/ssh_host_rsa_key.pub root # egrep -v '^.*#' /etc/ssh/sshd_config | grep . Port 22 Protocol 2 HostKey /etc/ssh/ssh_host_rsa_key HostKey /etc/ssh/ssh_host_dsa_key HostKey /etc/ssh/ssh_host_ecdsa_key HostKey /etc/ssh/ssh_host_ed25519_key UsePrivilegeSeparation yes KeyRegenerationInterval 3600 ServerKeyBits 1024 SyslogFacility AUTH LogLevel INFO LoginGraceTime 120 PermitRootLogin without-password StrictModes yes RSAAuthentication yes PubkeyAuthentication yes IgnoreRhosts yes RhostsRSAAuthentication no HostbasedAuthentication no PermitEmptyPasswords no ChallengeResponseAuthentication no PasswordAuthentication yes X11Forwarding yes X11DisplayOffset 10 PrintMotd no PrintLastLog yes TCPKeepAlive yes AcceptEnv LANG LC_* Subsystem sftp /usr/lib/openssh/sftp-server UsePAM yes PermitRootLogin yes root # ssh localhost root@localhost's password: Permission denied, please try again. root@localhost's password: Could not login -ed Harry root # tail /var/log/auth.log Jun 18 11:43:17 d2 sshd[1894]: Accepted password for reader from 192.168.1.42 port 40945 ssh2 Jun 18 11:43:17 d2 sshd[1894]: pam_unix(sshd:session): session opened for user reader by (uid=0) Jun 18 11:43:17 d2 systemd-logind[477]: New session 185 of user reader. Jun 18 11:43:17 d2 sshd[1897]: Setting tty modes failed: Invalid argument Jun 18 11:43:59 d2 su[1917]: Successful su for root by reader Jun 18 11:43:59 d2 su[1917]: + /dev/pts/4 reader:root Jun 18 11:43:59 d2 su[1917]: pam_unix(su:session): session opened for user root by reader(uid=1000) Jun 18 11:45:56 d2 sshd[1963]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.local.lan user=root Jun 18 11:45:58 d2 sshd[1963]: Failed password for root from 127.0.0.1 port 54526 ssh2 Jun 18 11:46:03 d2 sshd[1963]: Connection closed by 127.0.0.1 [preauth]
Peculiar problem with root login
Running debian jesse in a vbox vm on a Solaris host I have what seems like an unusual problem with root login on this host. I've done the normal things one does to allow root login; that is, add PermitRootLogin yes to /etc/ssh/sshd_config Restart ssh, and in fact this host has been rebooted a few times since adding that Permit line. I set sudo up to work with no passwd for a certain user long ago and so I was able to redo root passwd just to make sure there wasn't some error there. Still, I cannot login as root user I don't mean at the main login screen one gets on bootup, but from an xterm in a running session. Of course, checked to see if Caps lock was on... I've checked output of ssh -vvv root@localhost, and see nothing very exciting.. just asking for password and rejecting it repeatedly: debug1: Next authentication method: password root@localhost's password: debug2: we sent a password packet, wait for reply debug1: Authentications that can continue: publickey,password Permission denied, please try again. This password has been in use for many years on vm hosts behind firewall etc etc. So, there is literally NO chance I'm just getting it wrong. Not to mention as I said above that I redid the passwd in this most recent attempt to get it working. I'm fresh out of ideas as to what else to do here. The auth log shows: Jun 11 14:50:55 d2 sshd[2830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.local.lan user=root Jun 11 14:50:57 d2 sshd[2830]: Failed password for root from 127.0.0.1 port 54522 ssh2
Re: Unable to compile newest emacs with gnutls
Harry Putnam <rea...@newsguy.com> writes: [...] Reco <recovery...@gmail.com> writes: [...] > ... >> I suspect it might be the dev pkgs that is needed: >> >> libgnutls-dev > > Indeed, but not this one. Not unless you're using wheezy. > > >> But when I try to install it, I run into a complicated dependency >> problem I don't know how to solve: >> >> aptitude install libgnutls-dev > > aptitude install libgnutls28-dev Sven Joachim <svenj...@gmx.de> writes: [...] >> I suspect it might be the dev pkgs that is needed: >> >> libgnutls-dev > > That guess seems likely, but is wrong: libgnutls-dev exists only in > oldstable, you should install libgnutls28-dev instead. Thanks to you both, yes it works now after that install.
Unable to compile newest emacs with gnutls
Attempting to build latest emacs I run into a problem gnutls not being available. ./configure --prefix=/usr/local/src/vcs/git/test --with-x=yes --with-x-toolkit=athena --with-imagemagick --with-gpm --with-sound=no [...] configure: error: The following required libraries were not found: gnutls Maybe some development libraries/packages are missing? If you don't want to link with them give --with-gnutls=no as options to configure I have these gnutls related pkgs installed: i A libcurl3-gnutls - easy-to-use client-side URL transfer libra i libgnutls-deb0-28 - GNU TLS library - main runtime library i libgnutls-openssl27 - GNU TLS library - OpenSSL wrapper i A libneon27-gnutls - HTTP and WebDAV client library (GnuTLS ena I suspect it might be the dev pkgs that is needed: libgnutls-dev But when I try to install it, I run into a complicated dependency problem I don't know how to solve: aptitude install libgnutls-dev The following NEW packages will be installed: libgcrypt11{a} libgcrypt11-dev{ab} libgcrypt20-dev{a} libgnutls-dev{b} libgnutls26{a} libgnutlsxx27{a} libgpg-error-dev{a} libp11-kit-dev{a} libtasn1-3{a} libtasn1-3-dev{a} 0 packages upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 2,990 kB of archives. After unpacking 7,831 kB will be used. The following packages have unmet dependencies: libgnutls-dev : Depends: libgnutls-openssl27 (= 2.12.20-8+deb7u5) but 3.3.8-6+deb8u4 is installed. libgcrypt11-dev : Breaks: libgnutls-dev (< 2.12.23-18) but 2.12.20-8+deb7u5 is to be installed. The following actions will resolve these dependencies: Keep the following packages at their current version: 1) libgnutls-dev [Not Installed] Accept this solution? [Y/n/q/?] The offered solution ends with libngutls-dev not installed. I walked thru several other solutions by pressing `. ' But none of the first 6 offer a way to end up with libgnutls-dev installed. I'm not even sure that is the missing pkg to allow emacs to compile with gnutls... Hopefully someone here will have experience compiling emacs from source and will know or have a good idea what needs to be done here.
Re: How to >>COMPLETELY<< remove an application?
Cindy-Sue Causeywrites: > Do Synaptic, Aptitude, and possibly anything else of that family have > similarly close but still different flags/commands? I haven't seen this mentioned in the thread... but may have missed it. I've noticed that some times aptitue purge does not remove everything as show by running aptitude search on the pkg name and seeing the 'c' (lower case `c' ) the indicates some files remain that have user changes. When that happens I've found that `dpkg' will most often complete the job. `dpkg purge pkgname'
Re: -dec-terminal fonts
Siardwrites: [...] > So, tech14.pcf.gz etc. are the fonts you're looking for. Thanks for the leg work.. gives a good start. Except I think you may have meant to say: /usr/share/fonts/X11/75dpi/fonts.dir:termB14.pcf.gz and /usr/share/fonts/X11/75dpi/fonts.dir:term14.pcf.gz writes: [...] > COPYRIGHT > Copyright (c) 1991 Digital Equipment Corporation. All Rights Reserved. > _DEC_PRODUCTINFO > DECterm Fonts V2.2, 11-Nov-1991 > FULL_NAME > Terminal > FONT > -DEC-Terminal-Medium-R-Normal--14-140-75-75-C-80-ISO8859-1 > WEIGHT > [...] > > That looks promising, does it? Now -- which package provided that? > tomas@rasputin:~$ dpkg -S /usr/share/fonts/X11/75dpi/term14.pcf.gz > xfonts-75dpi: /usr/share/fonts/X11/75dpi/term14.pcf.gz That was a heck of a walk thru... gives all kinds of help.. thanks I see now that they are part of the `xfonts-75dpi' package on the repos
-dec-terminal fonts
I have these fonts as displayed by xlsfonts xlsfonts|grep dec [...] -dec-terminal-bold-r-normal--0-0-75-75-c-0-dec-dectech -dec-terminal-bold-r-normal--0-0-75-75-c-0-iso8859-1 [...] -dec-terminal-medium-r-normal--14-140-75-75-c-80-iso8859-1 -dec-terminal-medium-r-normal--14-140-75-75-c-80-iso8859-1 decw$cursor decw$session Chopped out a longish list but still showing the type of fonts I'm interested in. The lst two I can find easy enough under /usr/share/fonts where I find /usr/share/fonts/X11/misc/deccurs.pcf.gz /usr/share/fonts/X11/misc/decsess.pcf.gz /usr/share/fonts/X11/encodings/dec-special.enc.gz But I want to know where the ones listed in xlsfonts come from. Not finding anything on aptitude search that looks likely. But may under a name not including `dec'. I may have installed them separate but if so, I do not recall where they came from. Not finding them on google either. Are they part of a debian install? Or does anyone no there origin? Or where to get them?
Re: autofs config
Recowrites: [...] >> 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 solved with your previous post. Here is how All this time my map file said dv --type[...] 2x:/projects/dv instead of: dv-type[...] [...] I had two dashes instead of one. When copying the part you specified as being verbatim ... I finally saw my mistake I'm really sorry I jerked you around so much. Now that I got the right formulation I notice that `ls /projects-nfs/dv' mounts so fast that the ls displays instantly. I didn't post the debug data... since it was a fool mistake on my part. You've been very patient. Thank you. > > cd /prj//d0 > cd /prj//dv > > If d0 and dv are host names - poke them with 'showmount -e' first, and > use them like this: Sorry for that confusion too. No they are not host names in this usage. They are host names on my lan but on the server that is serving these shares (Solaris host 2x) they are share names. [...] >> So ls /prj/gv after a pause shows /prj/gv/merb/ > > Therefore 'gv' is a host name and 'merb' is a share on that host. > Assuming you're using stock auto.net. > Debug autofs output confirms this: Egad... sorry I wrote it all wrong. I should have said: ls /prj/gv merb `gv' is a share name on host 2x. and merb is a directory under that share. So on host 2x: ls /projects/gv/ merb And on host DEBIAN `ls /prj/gv merb I wrote it wrong and thoroughly confused things. When I meant to show that it some shares were mounted as expected 2 strikes against me... I hope to be more careful in any more posting on this list.
Re: autofs config
Recowrites: [...] 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 four. At least these are defaults starting with > Solaris 10. > > The thing that's broken here is autofs, not NFS implementation. 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. Still unable to mount the shares I'm after `d0' and `dv' but, those fail still with auto.master like: /prj /etc/auto.net --timeout=90 The good news is other shares in that same SOLARIS:/projects can be mounted as expected (see attached automount -fg output) 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. So ls /prj/gv after a pause shows /prj/gv/merb/ If I cd in there /prj/gv/merb as plain user reader I can: touch file; rm file and etc. However, all those directories exist at SOLARIS-HOST/projects/* All have the same permissions set, all are zfs fs with sharenfs=on >From solaris host: ls -al projects total 17 drwxrwxrwx+ 9 reader nfsu10 Jan 10 12:34 . drwxrwxrwx+ 2 root sys 3 Jan 8 01:48 .$EXTEND drwxr-xr-x 38 root staff 43 Jan 10 11:20 .. drwxrwxrwx+ 8 reader nfsu10 Nov 12 10:11 2x drwxrwxrwx+ 4 reader nfsu 7 Sep 29 2014 adm drwxrwxrwx+ 4 reader nfsu 5 Jan 10 01:57 d0 drwxrwsrwx+ 26 reader nfsu31 Jan 10 00:49 dv drwxrwxrwx+ 18 reader nfsu22 Jan 12 2015 gv drwxrwxrwx+ 2 reader nfsu 3 Feb 9 2015 prj-fossil -rwxrwxrwx+ 1 reader nfsu 1349 Jan 27 2015 srpscr You may notice output about /projects/reader in the attached automounter output but it has been since deleted from SOLARIS:/projects Also notice the odd looking permissions. A result of: /bin/chmod -R A=everyone@:full_set:fd:allow /projects See home sharenfs is set the same all around >From Solaris:/projects/ for ii in 2x d0 dv gv; do zfs get sharenfs rpool/projects/$ii; done NAME PROPERTY VALUE SOURCE rpool/projects/2x sharenfs onlocal NAME PROPERTY VALUE SOURCE rpool/projects/d0 sharenfs onlocal NAME PROPERTY VALUE SOURCE rpool/projects/dv sharenfs onlocal NAME PROPERTY VALUE SOURCE rpool/projects/gv sharenfs onlocal So still having a time seeing why thos specific shares cannot be mounted. Starting automounter version 5.0.8, master map /etc/auto.master using kernel protocol version 5.02 lookup_nss_read_master: reading master file /etc/auto.master parse_init: parse(sun): init gathered global options: (null) spawn_mount: mtab link detected, passing -n to mount spawn_umount: mtab link detected, passing -n to mount lookup_read_master: lookup(file): read entry /prj master_do_mount: mounting /prj automount_path_to_fifo: fifo name /var/run/autofs.fifo-prj lookup_nss_read_map: reading map file /etc/auto.net parse_init: parse(sun): init gathered global options: (null) spawn_mount: mtab link detected, passing -n to mount spawn_umount: mtab link detected, passing -n to mount mounted indirect on /prj with timeout 90, freq 23 seconds st_ready: st_ready(): state = 0 path /prj handle_packet: type = 3 handle_packet_missing_indirect: token 96, name d0, request pid 3369 attempting to mount entry /prj/d0 lookup_mount: lookup(program): looking up d0 >> clnt_create: RPC: Program not registered lookup(program): lookup for d0 failed dev_ioctl_send_fail: token = 96 failed to mount /prj/d0 handle_packet: type = 3 handle_packet_missing_indirect: token 97, name d0, request pid 3369 dev_ioctl_send_fail: token = 97 handle_packet: type = 3 handle_packet_missing_indirect: token 98, name dv, request pid 3378 attempting to mount entry /prj/dv lookup_mount: lookup(program): looking up dv >> clnt_create: RPC: Program not registered lookup(program): lookup for dv failed dev_ioctl_send_fail: token = 98 failed to mount /prj/dv handle_packet: type = 3 handle_packet_missing_indirect: token 99, name dv, request pid 3378 dev_ioctl_send_fail: token = 99 st_expire: state 1 path /prj expire_proc: exp_proc = 140587597362944 path /prj expire_cleanup: got thid 140587597362944 path /prj stat 0 expire_cleanup: sigchld: exp 140587597362944 finished, switching from 2 to 1 st_ready: st_ready(): state = 2 path /prj handle_packet: type = 3 handle_packet_missing_indirect: token 100, name gv, request pid 3390 attempting to mount entry /prj/gv lookup_mount: lookup(program): looking up gv lookup_mount: lookup(program): gv -> -fstype=nfs4,soft,intr,nodev,nosuid,async /merb gv:/merb parse_mount: parse(sun): expanded entry: -fstype=nfs4,soft,intr,nodev,nosuid,async /merb gv:/merb parse_mount: parse(sun): gathered
Re: autofs config
Recowrites: > 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 from the start. Must be shipped with autofs that way, as I did not do it. So then apparently it is not #828217 at the bottom of this. Or at least not because of `net -hosts' being in play.
Re: autofs config
Recowrites: [...] > Won't it be fun otherwise? > > The good thing is - autofs is working as intended. > The bad thing is - mount is failing. , | NOTE: I've rearranged your post to put the next question and answer at | the bottom of this reply ` [...] missing q and a >> One question... am I supposed to create the directories >> /projects/dv /projects/d0 ? >> >> It appears from the instructions I've seen that .. no I am not to >> create those dir... just /projects/. however, I did try it both ways >> and can report that nothing gets mounted in either test. > > No, you definitely do not. Either autofs creates a directory for you, or > you're unable to mount it. Top-level directory *must* be created, but > you did it. Well at least I got that part right. [...] >>/projects /etc/auto.net --timeout=180 (Note: It now says >> `auto.net') >>+dir:/etc/auto.master.d >>+auto.master > Reco wrote > Should be something like this: > > /projects program:/etc/auto.net --timeout=180 Ok, commented out the 2 lines that were uncommented by default [...] > A small nit. Do not use 'hard' mount option unless you absolutely need > it. It is painful, and it's by design. It has nothing to do with your > current problem, though. What you probably need is: > > -fstype=nfs4,soft,intr,nodev,nosuid,async All right, good to know. --- --- ---=--- --- --- And now the question answer I moved: 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 appears to be sys (sec=sys) 192.168.1.42:/projects/dv /projects/dv nfs4 rw,relatime,vers=4.0,\ rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,\ timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.29,local_lock=none,\ ^^^ addr=192.168.1.42 0 0 [...] > 3) Stop autofs, start it like this: > > /usr/sbin/automount -fd > > Mount a filesystem. Watch the debug output. Terminate it with Ctrl+C. (below I marked with *** what might be a clue) --- --- ---=--- --- --- parse_init: parse(sun): init gathered global options: (null) spawn_mount: mtab link detected, passing -n to mount spawn_umount: mtab link detected, passing -n to mount mounted indirect on /test with timeout 90, freq 23 seconds st_ready: st_ready(): state = 0 path /test handle_packet: type = 3 handle_packet_missing_indirect: token 47, name dv, request pid 11696 attempting to mount entry /test/dv lookup_mount: lookup(file): looking up dv lookup_mount: lookup(file): dv -> --fstype=nfs4,rw,soft,intr 191.168.1.42:/test parse_mount: parse(sun): expanded entry: --fstype=nfs4,rw,soft,intr 191.168.1.42:/test parse_mount: parse(sun): gathered options: -fstype=nfs4,rw,soft,intr parse_mount: parse(sun): dequote("191.168.1.42:/test") -> 191.168.1.42:/test parse_mount: parse(sun): core of entry: options=-fstype=nfs4,rw,soft,intr, loc=191.168.1.42:/test sun_mount: parse(sun): mounting root /test, mountpoint dv, what 191.168.1.42:/test, fstype nfs, options -fstype=nfs4,rw,soft,intr mount_mount: mount(nfs): root=/test name=dv what=191.168.1.42:/test, fstype=nfs, options=-fstype=nfs4,rw,soft,intr mount_mount: mount(nfs): nfs options="-fstype=nfs4,rw,soft,intr", nobind=0, nosymlink=0, ro=0 get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 6 version 0x30 get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 17 version 0x30 *** mount(nfs): no hosts available dev_ioctl_send_fail: token = 47 failed to mount /test/dv handle_packet: type = 3 handle_packet_missing_indirect: token 48, name dv, request pid 11696 dev_ioctl_send_fail: token = 48 st_expire: state 1 path /test expire_proc: exp_proc = 140662262839040 path /test expire_cleanup: got thid 140662262839040 path /test stat 0 expire_cleanup: sigchld: exp 140662262839040 finished, switching from 2 to 1 st_ready: st_ready(): state = 2 path /test st_expire: state 1 path /test expire_proc: exp_proc = 140662262839040 path /test expire_cleanup: got thid 140662262839040 path /test stat 0 expire_cleanup: sigchld: exp 140662262839040 finished, switching from 2 to 1 st_ready: st_ready(): state = 2 path /test [...] --- --- ---=--- --- --- As I mentioned in the OP: The host involved is a solaris x86 host. The file systems set for nfs availability are not put into an /etc/exports type setup. The way it is done on solaris with the zfs file system... is during the creation of a file system with `zfs create' One usees an option (-o) that looks like: zfs create -o sharenfs=on -o sharesmb=on somezpool/some/path So in the case above nfs (and smb access) will be turned on. So maybe that has something to do with the problem... But then again, maybe not. Because as I have demonstrated, the share is readily
Re: autofs config
Recowrites: [...] > And it gone haywire from here. Hehe... thats a good description... > Autofs has a concept of master map ( auto.master(5) ) which can contain > lines referring to either direct or indirect maps ( autofs(5) ). > > /etc/auto.master.d is intended for extending master map, and the files > inside it should contain master map entries, not indirect ones like you > did below. Thanks... and I got that all squared away. [...] Harry wrote >> created /etc/auto.master.d/prj-nfs.autofs like so (as suggested in >> auto.master): >> >> d0 --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/d0 >> dv --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/dv > Reco wrote: > Note that it be simplified to: > > * --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/& I created /etc/auto.nfs and tried that forumulation. Restarted autofs. Nothing gets mounted under (now simplified to /projects in auto.master) /projects when I do ls /projects/d0 or /projects/dv There is a bit of a pause with `ls /projects/dv (or d0) but then I get: ls: cannot access /projects/dv: No such file or directory To clarify my above comments: root # grep -v '^#\|^$' /etc/auto.master /projects /etc/auto.nfs --timeout=180 +dir:/etc/auto.master.d +auto.master root # grep -v '^#\|^$' /etc/auto.nfs *--fstype=nfs4,rw,soft,intr191.168.1.42:/projects/& I also tried this: root # grep -v '^#\|^$' /etc/auto.nfs d0 --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/d0 dv --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/dv A `ls /projects/dv' pauses maybe 10 seconds and returns: ls: cannot access /projects/dv: No such file or directory One question... am I supposed to create the directories /projects/dv /projects/d0 ? It appears from the instructions I've seen that .. no I am not to create those dir... just /projects/. however, I did try it both ways and can report that nothing gets mounted in either test. > Also please note that they give you /etc/auto.net just for your case > (i.e. mounting nfs). Not sure what you mean by `give you'. Do you mean to use as is? I tried: root # grep -v '^#\|^$' /etc/auto.master /projects /etc/auto.net --timeout=180 (Note: It now says `auto.net') +dir:/etc/auto.master.d +auto.master Made sure auto.net is chmod 755 Changed (in auto.net) opts="-fstype=nfs,hard,intr,nodev,nosuid" #opts="-fstype=nfs4,hard,intr,nodev,nosuid,async" To: #opts="-fstype=nfs,hard,intr,nodev,nosuid" opts="-fstype=nfs4,hard,intr,nodev,nosuid,async" Restarted autofs Again, nothing is mounted under /projects/ A `ls /projects/dv (or d0)' returns immediately with output: ls: cannot access /projects/dv: No such file or directory And once again .. to test nfs: mount -t nfs 192.168.1.42:/projects/dv /nfs/dv ls /nfs/dv (Yup... lots of files under here) I'm not able to see what I am doing wrong...
autofs config
, | NOTE: A similar post was accidently posted to gentoo list but was | intended to be posted here ` Setup: Running Debian jessie-stable I've never used autofs and am trying to get it setup. Following the debian wiki and an Ubuntu howto. Also this site: http://www.linuxtechi.com/automount-nfs-share-in-linux-using-autofs/ I've installed the pkg: aptitude search ^autofs|grep ^i i autofs - kernel-based automounter for Linux created mount point: mkdir /projects-nfs I've edited /etc/auto.master by adding this line: /projects-nfs /etc/auto.master.d/prj-nfs.autofs --timeout=180 Created the directory `mkdir /etc/auto.master.d' created /etc/auto.master.d/prj-nfs.autofs like so (as suggested in auto.master): d0 --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/d0 dv --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/dv Those directories on that host are available. They reside on an solaris (x86) host and set to be available to nfs. They can be mounted manually: mount -t nfs 2x:/projects/dv /nfs/dv Checking /nfs/dv... I find it is mounted. So umounting /nfs/dv And starting autofs with: /etc/init.d/autofs start However when I chk status I get [asterisks added for clarity]: /etc/init.d/autofs status ● autofs.service - LSB: Automounts filesystems on demand Loaded: loaded (/etc/init.d/autofs) Active: active (running) since Sun 2017-01-08 13:40:45 EST; 4s ago Process: 3638 ExecStop=/etc/init.d/autofs stop (code=exited, status=0/SUCCESS) Process: 3671 ExecStart=/etc/init.d/autofs start (code=exited, status=0/SUCCESS) CGroup: /system.slice/autofs.service └─3676 /usr/sbin/automount --pid-file /var/run/autofs.pid Jan 08 13:40:45 d0 systemd[1]: Starting LSB: Automounts filesystems on demand... *** Jan 08 13:40:45 d0 automount[3676]: syntax error in map near [ d0 --fstype=nfs4,rw,soft,intr191.168.1.42: ] *** Jan 08 13:40:45 d0 automount[3676]: syntax error in map near [ projects ] Jan 08 13:40:45 d0 autofs[3671]: Starting automount Jan 08 13:40:45 d0 systemd[1]: Started LSB: Automounts filesystems on demand. No way to tell what the syntax error is. I thought it might be spaces instead of tabs so when back and made sure the whitspaces are tabs. The above sited URL shows the entries for map file are to include: And gives the example: db_backup -fstype=nfs,rw,soft,intr 192.168.1.21:/db_backup I'm not seeing what the `syntax error' is in my file.
Re: kernel header for 4.6.0-1-686
Joe Pfeiffer <pfeif...@cs.nmsu.edu> writes: > Harry Putnam <rea...@newsguy.com> writes: > >> Joe Pfeiffer <pfeif...@cs.nmsu.edu> writes: >>> >>> Any particular reason you need that particular version? Could you >>> upgrade your virtualbox VM to a different kernel and use the headers >>> for that kernel (or if I'm misremembering which kernel requires the >>> headers, upgrade the host machine kernel)? >> >> I'm not sure about what you say there. I'm not particularly >> knowledgable about this but far as I can tell The guest addtions >> require the guest OS's kernel headers to compile certain >> modules... without them... no guest additions. > > Just tried it, so I could be sure I was giving good advice... > > I'm suggesting you go into your package manager in the guest machine (I > use aptitude, but that shouldn't matter) and do an upgrade to the > current versions of everything (this will include the current kernel). > Once you've done that, you should be able to install > virtualbox-guest-utils (also inside the package manager); this should > pull in everything needed to run the guest additions including the > headers for the now-current kernel. > >> I already tried to upgrade the kernel on the guest OS to one with >> headers available with apt-get but got into some trouble ending >> with an non-bootable mess... > > You don't want to do it like that -- simply upgrading everything should > upgrade to the current version. > >> I'd rather leave the kernel building etc to someone who better knows >> what they are doing. It's said to be easily done(Updating a >> kernel) but my experience is a little different. Or I'm just a little >> dimmer than the average bear. > > No kernel building is needed for this. Done and done thank you. The experience came off a little nicer than last time ;)
Re: kernel header for 4.6.0-1-686
Joe Pfeiffer <pfeif...@cs.nmsu.edu> writes: > Harry Putnam <rea...@newsguy.com> writes: > >> Juanjo Benages <jua...@benages.eu> writes: >> >>> El 25/10/16 a las 19:48, Harry Putnam escribió: >>>> Where can I get the kernel headers for my kernel 4.6.0-1-686? >>>> >>>> apt-get does not show that version. >>>> >>>> Googling for awhile here and not finding it either >>>> >>>> Trying to install vbox guest additions and it needs those headers. >>>> >>>> >>>> >>> Have you tried on snapshot.debian.org? It should be there. >> >> Using the binary tool search I finally found linux-headers-4.6.0-1-686 >> But when I click on it, it listes available versions all of which >> start at 4.6.1 or better. >> >> I guess that means its not there eh? >> >> Any other suggestions? > > Any particular reason you need that particular version? Could you > upgrade your virtualbox VM to a different kernel and use the headers > for that kernel (or if I'm misremembering which kernel requires the > headers, upgrade the host machine kernel)? I'm not sure about what you say there. I'm not particularly knowledgable about this but far as I can tell The guest addtions require the guest OS's kernel headers to compile certain modules... without them... no guest additions. I already tried to upgrade the kernel on the guest OS to one with headers available with apt-get but got into some trouble ending with an non-bootable mess... I'd rather leave the kernel building etc to someone who better knows what they are doing. It's said to be easily done(Updating a kernel) but my experience is a little different. Or I'm just a little dimmer than the average bear.
Re: kernel header for 4.6.0-1-686
Juanjo Benages <jua...@benages.eu> writes: > El 25/10/16 a las 19:48, Harry Putnam escribió: >> Where can I get the kernel headers for my kernel 4.6.0-1-686? >> >> apt-get does not show that version. >> >> Googling for awhile here and not finding it either >> >> Trying to install vbox guest additions and it needs those headers. >> >> >> > Have you tried on snapshot.debian.org? It should be there. Using the binary tool search I finally found linux-headers-4.6.0-1-686 But when I click on it, it listes available versions all of which start at 4.6.1 or better. I guess that means its not there eh? Any other suggestions?
kernel header for 4.6.0-1-686
Where can I get the kernel headers for my kernel 4.6.0-1-686? apt-get does not show that version. Googling for awhile here and not finding it either Trying to install vbox guest additions and it needs those headers.
Re: exim4 some config error causing error how to pinpoint
Liam O'Toolewrites: [...] >> When I try to send a message from USER@HOST2 to USER@HOST1, instead of >> just delivering to USER@HOST1 it appears to be sending that message on >> to the gmail smtp server. >> >> The local lan is not a real FQDN so not suprising that the gmail >> server cannot deliver it but how to prevent that local mail from >> being sent to gmail server to start with? >> >> > > You need to tell exim4 on HOST1 that it is the 'final destination' for > emails within your local network. If you go back through the debconf > questions for exim4-config, you'll be asked about 'Other destinations > for which mail is accepted'. In your case the answer should be > '*.local.lan'. Then local emails will no longer be forwarded upstream. > Obviously, you will need to ensure that the various local fully > qualified domain names are resolvable, either by running your own DNS or > maintaining /etc/host files correctly. Thank you. That fixed HOST1. Still haven't worked out how to be able to send mail from a user@HOST2 to a user@HOST1 (both inside home lan ). With the setting you suggest above... mail from user@HOST2 to user@HOST1 fails with smtp output: sending like this: mailx -v -s "TEST 161001_092048 d2" ha...@dv.local.lan < ~/txtmsg.txt LOG: MAIN <= ha...@d2.local.lan U=harry P=local S=442 delivering 1bqKDj-9o-AK R: smarthost for ha...@dv.local.lan T: remote_smtp_smarthost for ha...@dv.local.lan LOG: MAIN ** ha...@dv.local.lan R=smarthost T=remote_smtp_smarthost: retry time not reached for any host after a long failure period LOG: MAIN <= <> R=1bqKDj-9o-AK U=Debian-exim P=local S=1680 LOG: MAIN Completed delivering 1bqKDj-9s-Hi R: system_aliases for ha...@d2.local.lan R: userforward for ha...@d2.local.lan R: procmail for ha...@d2.local.lan R: maildrop for ha...@d2.local.lan R: lowuid_aliases for ha...@d2.local.lan (UID 1000) R: local_user for ha...@d2.local.lan T: appendfile for ha...@d2.local.lan LOG: MAIN => harry R=local_user T=mail_spool LOG: MAIN Completed And from /var/log/exim4/mainlog: 2016-10-01 09:20:51 1bqKDj-9o-AK <= ha...@d2.local.lan U=harry P=local S=442 2016-10-01 09:20:51 1bqKDj-9o-AK ** ha...@dv.local.lan R=smarthost T=remote_smtp_smarthost: retry time not reached for any host after a long failure period 2016-10-01 09:20:51 1bqKDj-9s-Hi <= <> R=1bqKDj-9o-AK U=Debian-exim P=local S=1680 2016-10-01 09:20:51 1bqKDj-9o-AK Completed 2016-10-01 09:20:51 1bqKDj-9s-Hi => harry R=local_user T=mail_spool 2016-10-01 09:20:51 1bqKDj-9s-Hi Completed I think those ouputs mean that the local mail being sent from HOST2 to HOST1 is still attempting to be sent to smtp.gmail.com (The smarthost for HOST1) I have HOST2 set like this in /etc/exim4/update-exim4.conf.conf: dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='d2.local.lan' # (HOST2) dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='dv.local.lan' # (HOST1) CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' Is this wrong? Is setting HOST1 as smarthost for HOST2 a mistake? Contents of /etc/exim4/update-exim4.conf.conf on HOST1 dc_eximconfig_configtype='smarthost' dc_other_hostnames='*.local.lan' # NOTE: This was supposed to tell # HOST1 that mail from the local # lan is to be delivered to local # users... not sent to smarthost dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='192.168.1.0/24' dc_smarthost='smtp.gmail.com::587' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' smtp_accept_queue_per_connection=300 The attempted send from HOST2 to HOST1 does not appear in the /var/log/exim4/mainlog on HOST1 at all. I'm sorry to be so confused about setting this up... but am pretty confused at this point.
Re: exim4 some config error causing error how to pinpoint
Liam O'Toolewrites: >> Mail never appears at HOST1 /var/spool/mail/user2 >> >> > > Does user2 appear in the file /etc/aliases on HOST1? Is there a No > /home/user2/.forward file on that host? Either of those would cause mail No > Is there anything suspicious in the file /var/log/exim4/mainlog on > HOST1? Yes, there is this bit that seems to indicate that the message is being processed by procmail. dv.local.lan is HOST1 smarthost set to smtp.gmail.com d2.local.lan is HOST2 smarthost set to HOST1 There is a user named `harry' on both hosts. --- --- ---=--- --- --- 2016-09-15 12:40:29 1bkZi9-Ne-MU <= ha...@d2.local.lan H=(d2.local.lan) [192.168.1.17] P=esmtp S=608 id=e1bkza7-0006mb...@d2.local.lan 2016-09-15 12:40:31 1bkZi9-Ne-MU => harry R=procmail T=procmail_pipe 2016-09-15 12:40:31 1bkZi9-Ne-MU Completed 2016-09-15 12:52:31 Start queue run: pid=1574 2016-09-15 12:52:31 End queue run: pid=1574 --- --- ---=--- --- --- There is a ~/.procmailrc for user2 but no specifc recipe that would grab mail addressed to USER2@HOST1 (harry@dv). However my .procmailrc has a final rule that catches anything not already handled: :0 post_ex.in However the mail addressed user2@host1 is not going to that inbox (or any other) either. But dropping that mystery for the time being there seems to be something bigger happening. Since my previous post I have found that all those test messages to user2 and user1 on HOST1 from HOST2 are being sent out to the HOST1 smarthost and piling up as undeleverable on a gmail account. My smarthost is smtp.gmail.com I guess that does make sense. However I guess I just supposed that somehow HOST1 would magically know not to try to send mail from other lan hosts addressed to users on HOST1, out to the internet smarthost. Maybe I need some other mechanism for that to happen? To summarize the setup again very briefly... since it seems to be getting more confusing ... at least to me. HOST1 is setup to relay mail from its users to an internet smarthost (smtp.gmail.com). HOST2 is setup to relay mail from its users to HOST1 as its smarthost When I try to send a message from USER@HOST2 to USER@HOST1, instead of just delivering to USER@HOST1 it appears to be sending that message on to the gmail smtp server. The local lan is not a real FQDN so not suprising that the gmail server cannot deliver it but how to prevent that local mail from being sent to gmail server to start with?
Re: exim4 some config error causing error how to pinpoint
Liam O'Toolewrites: > dpkg-reconfigure exim4-config Thanks, that was pretty painless. And thanks for the url to the documentation section. I've now progressed on to where I was aiming for. I wanted to have one debian box as main mail client. Yet be able to send mail from a couple of others. I've managed to get that working by aiming the secondary hosts at the main mail host as smarthost. That main host is inturn aimed at an internet smarthost. So far all working except one glitch. Here is the cast of characters: HOST1 Main mail host HOST2 secondary host User1 HOST1 User2 HOST1 user HOST2 I can send a mail from HOST2 to a user on HOST1 using the correct address. user1@HOST1 That main host has only two users. I can send mail from HOST2 to only one of those users. That is. if, from HOST2, I send mail to a HOST1 user like: user1@HOST1 It arrives in user1 slot at /var/spool/mail/user1 on HOST1. However If I try sending to user2@HOST1 it never gets there. Even though the smtp output on sending HOST2 appears to be saying it was sent and received successfully. --- --- ---=--- --- --- orignating on HOST2 tmail user2@HOST1 sending like this: mailx -v -s "TEST 160914_163910" user1@HOST1 < ~/txtmsg.txt LOG: MAIN <= u...@host2.local.lan U=user1 P=local S=422 smtp output: delivering 1bkGxi-0002L3-U4 R: smarthost for user2@HOST1 T: remote_smtp_smarthost for user1@HOST1 Connecting to HOST1.local.lan [192.168.1.5]:25 ... connected SMTP<< 220 dv ESMTP Exim 4.86 Wed, 14 Sep 2016 16:47:36 -0400 SMTP>> EHLO HOST2.local.lan SMTP<< 250-dv Hello HOST2.local.lan [192.168.1.17] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250 HELP SMTP>> MAIL FROM: SIZE=1464 SMTP>> RCPT TO: SMTP>> DATA SMTP<< 250 OK SMTP<< 250 Accepted SMTP<< 354 Enter message, ending with "." on a line by itself SMTP>> writing message and terminating "." SMTP<< 250 OK id=1bkH5k-0008FT-UQ SMTP>> QUIT LOG: MAIN => user2@HOST1 R=smarthost T=remote_smtp_smarthost H=HOST1.local.lan [192.168.1.5] C="250 OK id=1bkH5k-0008FT-UQ" LOG: MAIN Completed Mail never appears at HOST1 /var/spool/mail/user2
exim4 some config error causing error how to pinpoint
I've attempted to setup exim4 on a second debian OS, using the working configuration from the older one. Before getting too detailed I think I see something in output of my debug technique that indicated somewhere my host is telling exim the wrong host name. (dv is host with working config ) I use this technique; sending a mail like this: mailx -v -s "TEST 160912_211756 dv" rea...@newsguy.com < ~/txtmsg.txt I run that command then watch the smtp output from the little test script named `tmail'. On the working host the first bit of output: $ tmail rea...@newsguy.com sending like this: mailx -v -s "TEST 160912_211756 dv" rea...@newsguy.com < ~/txtmsg.txt LOG: MAIN <= harry@dv U=harry P=local S=546 [...] Now the second, non-working host: tmail rea...@newsguy.com sending like this: (Non-working host is `d2') mailx -v -s "TEST 160912_211617 d2" rea...@newsguy.com < ~/txtmsg.txt LOG: MAIN <= ha...@d2local.lan U=harry P=local S=440 ^ Notice the above difference .. in the working host it shows harry@dv (hostname is dv.local.lan) In the non-working host: ha...@d2local.lan (hostname is d2.local.lan) Somewhere in my setup exim4 is finding the hostname without the separating dot in d2.local.lan and is using d2local.lan Which may be causing the failure: Following the smtp otuput: --- --- ---=--- --- --- delivering 1bjcKi-0001Ey-9B R: nonlocal for rea...@newsguy.com LOG: MAIN ** rea...@newsguy.com R=nonlocal: Mailing to remote domains not supported LOG: MAIN <= <> R=1bjcKi-0001Ey-9B U=Debian-exim P=local S=1650 LOG: MAIN Completed delivering 1bjcKi-0001F0-Fy R: nonlocal for ha...@d2local.lan LOG: MAIN ** ha...@d2local.lan R=nonlocal: Mailing to remote domains not supported LOG: MAIN Frozen (delivery error message) --- --- ---=--- --- --- Or am I making too much of the missing dot and it really is that I've missed an important setting that lets exim4 deliver to outside of lan?
Re: How to arrange for booting to console
The Wanderer <wande...@fastmail.fm> writes: > On 2016-09-11 at 17:04, Harry Putnam wrote: > >> How can I arrange to boot to console mode rather than X. With the >> ability to startx when I feel like it. >> [...] > The way I usually do it is to uninstall gdm, kdm, xdm, et cetera; those > are the packages which hook in to provide a graphical login prompt. With > none of them present, what you get is the traditional text-mode login > prompt, and your configured shell after login. > [...] That sounds promissing. Used one of the methods below and quickly realized I was expecting a nice big framebuffered text console with a much higher resolution than the standard. (Previously my OS of choice was gentoo), But of course all that has to be setup as I recall it is done with a few extra bits on the kernel line grub.conf Using grub2 I'm thoroughly lost what or where one would edit to allow a console frame buffer. Michael Biebl <bi...@debian.org> wrote: > Assuming you use jessie (and systemd), > > systemctl set-default multi-user.target > > should do the trick. You can get the current default with > > systemctl get-default > > It's typically graphical.target. Thanks, I actually used your suggestion of systemctl set-default multi-user.target Worked just as suggested. I have the job running that was running out of memory.. so I'll see if leaving X out of things is enough to allow it to complete. See above for some sniveling about the default console. david...@freevolt.org writes: > If using systemd, these look relevant: > >> How can I arrange to boot to console mode rather than X. > > > https://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks/#changingthedefaultboottarget > > # ln -sf /usr/lib/systemd/system/multi-user.target > /etc/systemd/system/default.target > >> With the ability to startx when I feel like it. > > https://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions > > # systemctl isolate graphical.target Thanks, your suggestion is a little more complete version of Davidson above again thanks.
How to arrange for booting to console
How can I arrange to boot to console mode rather than X. With the ability to startx when I feel like it. I'm not familiar with grub2 and the debian vm I'm using on a solaris host appears to be using grub2. Can anyone stear me to the files I'd need to edit?
Re: odd internal mail failure
David Wrightwrites: > The obvious candidate is /etc/mailname which I don't see > any reference to your changing. /etc/mailname appears to be the culprit ... thanks.
odd internal mail failure
On a recently installed jessie OS I've found an odd situation happing with the internal mail. root is getting a message from root. At least that is what appears in >From and To. However the message is showing up in users directory as a file named `$'. Here is the header: From r...@d.local.lan Sun Feb 21 07:35:07 2016 Return-path:Envelope-to: r...@d.local.lan Delivery-date: Sun, 21 Feb 2016 07:35:07 -0500 Received: from root by d2.local.lan with local (Exim 4.84) (envelope-from ) id 1aXTEB-0008C5-5J for r...@d.local.lan; Sun, 21 Feb 2016 07:35:07 -0500 Subject: exim paniclog on d2.local.lan has non-zero size To: r...@d.local.lan Message-Id: From: root Date: Sun, 21 Feb 2016 07:35:07 -0500 As you see the hostname is shown as "d" and in fact that was the hosts name up until several days ago so, several days ago the host was renamed to d2. You can also see the correct host name appears in the "Received" header. So the old name must be stored somewhere and getting used on the mail. The name change was done by editing /etc/hostname to the new name editing /etc/hosts to the new name and at the command line with # hostname d2. And yes, I have verified that both are correctly edited. The host has been rebooted several times since that was done. You can see in the header the date is today. This is not the only message I deleted one inadvertently whan I saw the Dollar sign as file name the first time. I've never gotten a filename of "$" before. And haven't noticed any hosts having trouble knowning there name before. Where would the original host name be coming from?
Re: Long neglected OS ... updating
Stefan Monnierwrites: > [ Speaking as someone who re-installs as rarely as possible, and whose > machines almost all derive (via upgrades like yours) from an install > from around 2006. ] OK, now were talking Thanks again to all posters... really good expert help here. [...] main bulk of post snipped Thank you Stefan... once again you've provided concise and very helpful input.
Long neglected OS ... updating
Resurrecting a neglected OS, need a little coaching about the output of `aptitude full-upgrade'. I want to know if this output is fairly typical or what one might expect after neglecting an OS a good while... but mostly if going ahead is likely to land my subpar skilled behind in hot water. I've stripped the hefty lists of pkgs leaving only what I thought would be enough for an experienced hand to be able to offer an educated opinion if this looks like a problematic `full-upgrade' or if it is one to pursue. aptitude upgrade blah blah , | aptitude full-upgrade | | The following NEW packages will be installed: | [...] | {141 pkgs} | | The following packages will be REMOVED: | [...] | {76 pkgs} | | The following packages will be upgraded: | [...] | {957 pkgs} | | The following packages are RECOMMENDED but will NOT be installed: | [...] | { 19 pkgs} | | [...] | | The following packages have unmet dependencies: | | liblognorm2 : Breaks: liblognorm0 but 0.3.7-1 is installed. | libsigc++-2.0-0v5 : Conflicts: libsigc++-2.0-0c2a but 2.4.1-1 is installed. | libxapian22v5 : Conflicts: libxapian22 but 1.2.21-1 is installed. | libcwidget3v5 : Conflicts: libcwidget3 but 0.5.17-2 is installed. | libtag1v5-vanilla : Breaks: libtag1-vanilla but 1.9.1-2.1 is installed. | libtag1v5 : Conflicts: libtag1c2a but 1.9.1-2.1 is installed. | | The following actions will resolve these dependencies: | | Remove the following packages: | 1) aptitude | 2) liblognorm0 | 3) libtag1-vanilla | 4) libtag1c2a | 5) synaptic | | Keep the following packages at their current version: | 6) gstreamer0.10-plugins-good [Not Installed] | 7) libcwidget3v5 [Not Installed] | 8) libept1.4.16 [Not Installed] | 9) libsigc++-2.0-0v5 [Not Installed] | 10) libxapian22v5 [Not Installed] NOTE: I'm a little puzzled at the above (6-10). Seems to be a bit of an oxymoron or something. | Leave the following dependencies unresolved: | 11) aptitude-common recommends aptitude | 12) task-lxde-desktop recommends synaptic | 13) iceweasel recommends gstreamer0.10-plugins-good | | Accept this solution? [Y/n/q/?] ` One thing bugging me is the idea of leaving the odd dependencies unresolved (the last items 11, 12, 13) Are there red flags in the above output that mean I need to do preliminary work before `full-uptrade' ?
How to find pkg specific font belongs to
I want to find the exact package font: -dec-terminal-medium-r-normal--14-140-75-75-c-80-iso8859-1 belongs to. I did search `find /usr/share/fonts -iname '*dec*' /usr/share/fonts/X11/misc/deccurs.pcf.gz /usr/share/fonts/X11/misc/decsess.pcf.gz /usr/share/fonts/X11/encodings/dec-special.enc.gz And, of course I search those filenames with apt-file to get package name. The trouble is, I don't (yet) know which, if any, contains the above mentioned exact font name. 'zcat FNAME|grep -i dec' on the above file names ... is not usefull either.
change sources.list to follow testing, not jessie
My current sources.list: , | deb http://ftp.us.debian.org/debian testing main contrib non-free | deb-src http://ftp.us.debian.org/debian testing main contrib non-free | | deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free | deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free | | deb http://security.debian.org/ jessie/updates main contrib non-free | deb-src http://security.debian.org/ jessie/updates main contrib non-free ` And a couple to keep certain wheeze software but not important for my question (included here just for completness only) , | deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free | deb-src http://ftp.us.debian.org/debian/ wheezy main contrib non-free | | deb http://security.debian.org/ wheezy/updates main contrib non-free | deb-src http://security.debian.org/ wheezy/updates main contrib non-free ` In the first three, if I just change the word `jessie' to `testing' will that work seemlessly or lead to problems? I'm a little loath to just test it for fear of causing immediate problems, I mean testing beyond an `aptitude update' after changing all occurences of `jessie' to testing. Running `aptitude update' with the changes in place does not produce any output that looks problematice (to me). But maybe that is not a thorough test? --- --- ---=--- --- --- `aptitude update' included for more experienced eyes to check: (Oh, and incidently, can any one tell me what the indicator `Ign' just below Get: 4 below means I mean beyond `Ignore'? Does it mean I need to change something in my `sources.list'?) Get: 1 http://ftp.us.debian.org testing InRelease [206 kB] Get: 2 http://security.debian.org testing/updates InRelease [84.1 kB] Get: 3 http://ftp.debian.org testing-updates InRelease [117 kB] Get: 4 http://security.debian.org wheezy/updates InRelease [103 kB] Ign http://ftp.us.debian.org wheezy InRelease Hit http://ftp.us.debian.org wheezy Release.gpg Hit http://ftp.us.debian.org wheezy Release Get: 5 http://security.debian.org testing/updates/main Sources [694 B] Get: 6 http://security.debian.org testing/updates/contrib Sources [14 B] Get: 7 http://security.debian.org testing/updates/non-free Sources [14 B] Get: 8 http://security.debian.org testing/updates/main i386 Packages [516 B] Get: 9 http://security.debian.org testing/updates/contrib i386 Packages [14 B] Get: 10 http://security.debian.org testing/updates/non-free i386 Packages [14 B] Get: 11 http://security.debian.org testing/updates/contrib Translation-en [14 B] Get: 12 http://security.debian.org testing/updates/main Translation-en [360 B] Get: 13 http://security.debian.org testing/updates/non-free Translation-en [14 B] Get: 14 http://security.debian.org wheezy/updates/main Sources [168 kB] Get: 15 http://security.debian.org wheezy/updates/contrib Sources [14 B] Get: 16 http://security.debian.org wheezy/updates/non-free Sources [14 B] Get: 17 http://security.debian.org wheezy/updates/main i386 Packages [307 kB] Get: 18 http://security.debian.org wheezy/updates/contrib i386 Packages [14 B] Get: 19 http://security.debian.org wheezy/updates/non-free i386 Packages [14 B] Get: 20 http://security.debian.org wheezy/updates/contrib Translation-en [523 B] Get: 21 http://security.debian.org wheezy/updates/main Translation-en [172 kB] Get: 22 http://security.debian.org wheezy/updates/non-free Translation-en [14 B] Get: 23 http://ftp.us.debian.org testing/main Sources/DiffIndex [7,876 B] Get: 24 http://ftp.us.debian.org testing/contrib Sources/DiffIndex [7,819 B] Get: 25 http://ftp.us.debian.org testing/non-free Sources/DiffIndex [7,819 B] Get: 26 http://ftp.us.debian.org testing/main i386 Packages/DiffIndex [7,876 B] Get: 27 http://ftp.us.debian.org testing/contrib i386 Packages/DiffIndex [7,819 B] Get: 28 http://ftp.us.debian.org testing/non-free i386 Packages/DiffIndex [7,819 B] Get: 29 http://ftp.us.debian.org testing/contrib Translation-en/DiffIndex [7,819 B] Get: 30 http://ftp.us.debian.org testing/main Translation-en/DiffIndex [7,876 B] Get: 31 http://ftp.us.debian.org testing/non-free Translation-en/DiffIndex [7,819 B] Get: 32 http://ftp.us.debian.org testing/main 2015-04-09-0246.06.pdiff [2,671 B] Get: 33 http://ftp.us.debian.org testing/main 2015-04-09-1446.56.pdiff [71 B] Get: 34 http://ftp.us.debian.org testing/main 2015-04-10-0246.55.pdiff [1,211 B] Get: 35 http://ftp.us.debian.org testing/main 2015-04-10-1448.56.pdiff [413 B] Get: 36 http://ftp.us.debian.org testing/main 2015-04-11-0243.50.pdiff [2,750 B] Get: 37 http://ftp.us.debian.org testing/main 2015-04-12-0250.40.pdiff [2,513 B] Get: 38 http://ftp.us.debian.org testing/main 2015-04-12-1444.23.pdiff [286 B] Get: 39 http://ftp.us.debian.org testing/main 2015-04-13-0247.33.pdiff [3,505 B] Get: 40 http://ftp.us.debian.org testing/main 2015-04-14-0249.52.pdiff [1,181 B] Get: 41 http://ftp.us.debian.org testing/main 2015-04-14-1447.10.pdiff [33 B] Get:
Re: how to debug this fuse problem
Guanqing.lu guanqing...@gameloft.com writes: Hi I met the same error message today and got it fixed in following way: root@myhost01 grub]# dmesg |grep fuse [5174104.384024] fuse: disagrees about version of symbol iov_iter_get_pages [5174104.384027] fuse: Unknown symbol iov_iter_get_pages (err -22) [5174118.853162] fuse: disagrees about version of symbol iov_iter_get_pages [5174118.853166] fuse: Unknown symbol iov_iter_get_pages (err -22) ... [root@myhost01 grub]# modprobe fuse ERROR: could not insert 'fuse': Invalid argument [root@myhost01 grub]# uname -r 3.16.0-0.bpo.4-amd64 [root@myhost01 grub]# dpkg-query -W 'linux-image-3.16.0-0.bpo.4-amd64' linux-image-3.16.0-0.bpo.4-amd643.16.7-ckt4-3~bpo70+1 No such output here: uname -r 3.16.0-4-586 [...] [root@myhost01 ~]# dpkg -l |grep fuse ii libfuse2:amd64 2.9.0-2+deb7u1amd64 Filesystem in Userspace (library) aptitude search ^fuse$ i A fuse So it is installed here As well as: i A libfuse2 [...] Not sure what else to do here -- 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/87twwsiwww@reader.local.lan
encfs quit wrking after full upgrade (jessie)
Following a fairly recent `full-upgrade', I'm no longer able to mount and enfs directory I've had for a good while. I installed it on jessie using wheezy on my sources.list. That worked for some months... but my most recent `full-upgrade' has done something that causes it to fail now. Error from attempted encfs mount: EncFS Password: fuse: device not found, try 'modprobe fuse' first fuse failed. Common problems: - fuse kernel module not installed (modprobe fuse) - invalid options -- see usage message Error when attempting to modprobe fuse. modprobe fuse modprobe: ERROR: could not insert 'fuse': Invalid argument Somehting happened to the kernel during that upgrade but I'm not sure what. uname -a: Linux dv 3.16.0-4-586 #1 Debian 3.16.7-ckt2-1 (2014-12-08) i686 GNU/Linux Shouldn't the `chk' part match the kernel version? Is that likely to be the problem? -- 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/87d23n3kov@reader.local.lan
Re: how to debug this fuse problem
Eduard Bloch e...@gmx.de writes: searching with `aptitudue search ckt7' (or ckt4) finds nothing at all. It's just an arbitrary version string. It can be (almost) anything, even 1.2.3.myCuteVersion-10.9.8. I suspect I could/should be running i686 with pae. Not sure why the installer choose a 486 kernel originally ... (it changed to 586 during a full-upgrade a mnth or two ago) The jessie OS here is running as vbox guest on a 2x Xeon on HP xw8600 I don't know why the installer chose that kernel, your Xeon should be fully i686 compatible. If the installation is damaged somehow (see above) then switching to another kernel might make the problem disappear. Many thanks to all posters... this is quite a useful thread to me. Still haven't got to fixing the problem but with the information here I am now well armed. Thanks posters -- 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/87sicx3or2@reader.local.lan
how to debug this fuse problem
Running `jessie' I've been using encfs, drawn from wheeze for months. But following a `full upgrade' I can no longer mount an encfs file system. The error message from mount attempt: , | fuse: device not found, try 'modprobe fuse' first | fuse failed. Common problems: | - fuse kernel module not installed (modprobe fuse) | - invalid options -- see usage message ` Attempting to modprobe fuse gets this error: , | root # modprobe fuse | modprobe: ERROR: could not insert 'fuse': Invalid argument ` I did try downgrading fuse and dependencies, but got the same errors The upgrade log shows no upgrade for fuse at the last `full-upgrade' but does show something happening with the kernel. However, I don't understand what it means. , | [UPGRADE] linux-compiler-gcc-4.8-x86:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-headers-3.16.0-4-586:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-headers-3.16.0-4-common:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-image-3.16.0-4-586:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-libc-dev:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 ` Running `uname -r' still shows: 3.16.0-4-586, so I'm not sure what: 3.16.7-ckt4-3 - 3.16.7-ckt7-1 means. Anyone have an idea what's going on here... and what I might have to do to mount my encfs filesystem? -- 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/87619y4jbt@reader.local.lan
Re: how to debug this fuse problem
Eduard Bloch e...@gmx.de writes: [...] Attempting to modprobe fuse gets this error: , | root # modprobe fuse | modprobe: ERROR: could not insert 'fuse': Invalid argument Something is wrong with your modules installation. Run dmesg to see what happened there. Run depmod -a once, it might help if some stupid tool damaged the module database (I had that fun with old dkms before). Check the installed files (debsums linux-image-3.16.0-4-586) Reinstall if needed (apt-get --reinstall install linux-image-3.16.0-4-586) dmesg shows what looks like quite a mess. I' don't know what it might mean, perhaps someone here has seen it before or understands what it means? , | dmesg|grep fuse | | [7.166080] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [7.166143] fuse: disagrees about version of symbol iov_iter_get_pages | [7.166188] fuse: Unknown symbol iov_iter_get_pages (err -22) | [ 313.475402] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [ 313.475416] fuse: disagrees about version of symbol iov_iter_get_pages | [ 313.475418] fuse: Unknown symbol iov_iter_get_pages (err -22) | [38952.902191] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [38952.902224] fuse: disagrees about version of symbol iov_iter_get_pages | [38952.902239] fuse: Unknown symbol iov_iter_get_pages (err -22) | [38965.865410] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [38965.865413] fuse: disagrees about version of symbol iov_iter_get_pages | [38965.865584] fuse: Unknown symbol iov_iter_get_pages (err -22) | [38989.899913] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [38989.904530] fuse: disagrees about version of symbol iov_iter_get_pages | [38989.904530] fuse: Unknown symbol iov_iter_get_pages (err -22) | [39204.559898] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [39204.559947] fuse: disagrees about version of symbol iov_iter_get_pages | [39204.559970] fuse: Unknown symbol iov_iter_get_pages (err -22) | [39718.223622] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [39718.223683] fuse: disagrees about version of symbol iov_iter_get_pages | [39718.223726] fuse: Unknown symbol iov_iter_get_pages (err -22) | [40037.891183] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [40037.891353] fuse: disagrees about version of symbol iov_iter_get_pages | [40037.891495] fuse: Unknown symbol iov_iter_get_pages (err -22) | [40056.750094] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [40056.750148] fuse: disagrees about version of symbol iov_iter_get_pages | [40056.750186] fuse: Unknown symbol iov_iter_get_pages (err -22) | [40209.000103] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [40209.015074] fuse: disagrees about version of symbol iov_iter_get_pages | [40209.015080] fuse: Unknown symbol iov_iter_get_pages (err -22) | [40219.713514] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [40219.713570] fuse: disagrees about version of symbol iov_iter_get_pages | [40219.713608] fuse: Unknown symbol iov_iter_get_pages (err -22) | [40284.303346] fuse: Unknown symbol pagecache_get_page_fixed (err 0) | [40284.303361] fuse: disagrees about version of symbol iov_iter_get_pages | [40284.303363] fuse: Unknown symbol iov_iter_get_pages (err -22) ` The upgrade log shows no upgrade for fuse at the last `full-upgrade' but does show something happening with the kernel. However, I don't understand what it means. , | [UPGRADE] linux-compiler-gcc-4.8-x86:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-headers-3.16.0-4-586:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-headers-3.16.0-4-common:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-image-3.16.0-4-586:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 | [UPGRADE] linux-libc-dev:i386 3.16.7-ckt4-3 - 3.16.7-ckt7-1 It's just the kernel from Jessie. See https://packages.debian.org/jessie/linux-image-3.16.0-4-586 Sorry to be so dense here but: Apparently it is a little more going on in those lines above. I don't see anything on the page you cite with names like: 3.16.7-ckt4-3 3.16.7-ckt7-1 searching with `aptitudue search ckt7' (or ckt4) finds nothing at all. What is the meaning of the names with ckt in them? I suspect I could/should be running i686 with pae. Not sure why the installer choose a 486 kernel originally ... (it changed to 586 during a full-upgrade a mnth or two ago) The jessie OS here is running as vbox guest on a 2x Xeon on HP xw8600 Would it be likely to solve any of this if I upgraded to a 686 pae kernel? Or more likely to make the mess worse and I should get the fuse mess cleared up first? -- 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/87wq2d3mce@reader.local.lan
Been out of it, when will there be a new `testing'
I've been dinking with gentoo and not paying attention here. I see no upgrades and we are in a freeze with jessie I guess. Can anyone hazard a guess when there will be a new `testing'? -- 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/87k30x5vi1@reader.local.lan
puzzling aptitude full-upgrade outptu
I get this from 2 separate debian installs of jessie host1 aptitude full-upgrade The following partially installed packages will be configured: gnome-icon-theme sgml-base sgml-data No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Host2 aptitude full-upgrade The following partially installed packages will be configured: sgml-base sgml-data No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Is this normal when there is a code freeze in force... should I see some action taken or recommended regarding the pkgs mentioned above? -- 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/87egrbansr@reader.local.lan
is sshd really restarting?
Setup: very new install of gentoo When I restart ssh like so: sudo /etc/init.d/ssh restart I see very little output. Should it be more verbose? , |harry sudo /etc/init.d/ssh restart | Restarting ssh (via systemctl): ssh.service ` Can I get more verbose output? -- 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/87mw6kswxg@reader.local.lan
Re: is sshd really restarting?
berenger.mo...@neutralite.org writes: Le 18.12.2014 18:13, Harry Putnam a écrit : Setup: very new install of gentoo Why not asking on a gentoo list, instead of a Debian one? Sorry that setup info is wrong... it is a debian (jessie) install where I get that brief output that makes me think nothing really happened: Debian (jessie) uname -a: Linux dv 3.16.0-4-586 #1 Debian 3.16.7-2 (2014-11-06) i686 GNU/Linux harry sudo /etc/init.d/ssh restart Restarting ssh (via systemctl): ssh.service. Should there be more output? -- 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/87ioh8svhm@reader.local.lan
Re: is sshd really restarting?
Harry Putnam rea...@newsguy.com writes: Setup: very new install of gentoo TYPE ALERT: Setup: not so new install of debian (jessie) When I restart ssh like so: sudo /etc/init.d/ssh restart I see very little output. Should it be more verbose? , |harry sudo /etc/init.d/ssh restart | Restarting ssh (via systemctl): ssh.service ` Can I get more verbose output? uname -a Linux dv 3.16.0-4-586 #1 Debian 3.16.7-2 (2014-11-06) i686 GNU/Linux -- 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/87egrwsvf5@reader.local.lan
Re: [minor bitch] about the panel (taskbar) LXDE
Harry Putnam rea...@newsguy.com writes: Some mnths ago (not sure how many) the icons (running program indicators) that appear in the bottom (taskbar like ) panel changed from showing icons of the running program such as the emacs icon, xterm icon, vim icon etc. to just showing a generic icon and text, making it hard to identify witch icon is which program quickly. I got good news on this by posting on the lxde.devel group: See this short thread: http://thread.gmane.org/gmane.comp.desktop.lxde.devel/5529 -- 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/87d27lwnli@reader.local.lan
Re: [minor bitch] about the panel (taskbar) LXDE
Jape Person jap...@comcast.net writes: On 12/11/2014 01:56 PM, Harry Putnam wrote: Andrei POPESCU andreimpope...@gmail.com writes: On Mi, 10 dec 14, 13:57:01, Harry Putnam wrote: Andrei POPESCU andreimpope...@gmail.com writes: So far every application *except xterm* I have tried has the same icon in the top left corner of its window as well as the taskbar. I tried GTK as well as Qt applications. To me this seems to indicate a bug in xterm rather than lxpanel. [...] Thanks for clearing up my misreading xterm may have a bug, but that would also mean emacs gui does too, but may also be using an xterm. Can anyone say if xterm shows an icon in taskbar with other desktops than lxde? Debian testing / Xfce / xterm. The proper xterm icon definitely shows up in both Window Buttons and in Window Menu (which is what I normally use). [...] Is one of the places you mention above, located in the taskbar like area across the bottom of screen? And appears there when you start the app? That is, the icon that represents the running program when it is running? -- 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/8761dg9a7n@newsguy.com
Re: [minor bitch] about the panel (taskbar) LXDE
Andrei POPESCU andreimpope...@gmail.com writes: On Mi, 10 dec 14, 13:57:01, Harry Putnam wrote: Andrei POPESCU andreimpope...@gmail.com writes: So far every application *except xterm* I have tried has the same icon in the top left corner of its window as well as the taskbar. I tried GTK as well as Qt applications. To me this seems to indicate a bug in xterm rather than lxpanel. [...] Thanks for clearing up my misreading xterm may have a bug, but that would also mean emacs gui does too, but may also be using an xterm. Can anyone say if xterm shows an icon in taskbar with other desktops than lxde? -- 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/87k31yow1j@reader.local.lan
Re: [minor bitch] about the panel (taskbar) LXDE
Andrei POPESCU andreimpope...@gmail.com writes: On Ma, 09 dec 14, 11:05:23, Harry Putnam wrote: Further, some indicators still show the regular icon. One I notice is iceweasel. I'd like the old behavior back but have no idea how to start digging into it. I'm guessing the icon is set by the application, in this case your terminal emulator, not the panel. As far as I recall I was already using rxvt-unicode when I switched to LXDE and never saw vim's icon in the taskbar when running it under rxvt. I may be remembering gvim... I do run gvim from time to time. And I nearly always use real Thomas Dickie Xterm rather the various desktop wannabees. Were there any recent changes related to your terminal emulator? Well, the changed involved in with `full-upgrades'. Which I've probably done at least twice in last month, but I'm pretty sure the situation I see is older than that... I did mention that it might have been going on for several months already. --- --- ---=--- --- --- Hugo Vanwoerkom hvw59...@care2.com writes: Harry Putnam wrote: Running jessie Using an lxde desktop... for a long time now (Note: for lack of a fuller vocabulary, the word icon is used to cover a few different things below:) (Attached at bottom is a screen grab showing what I'm talking about) snip Running uptodate sid with lxde. I see none of the behaviour you are describing. Can you post a screen grab of the task panel with several things running? Tixy t...@yxit.co.uk writes: On Tue, 2014-12-09 at 11:05 -0500, Harry Putnam wrote: Some mnths ago (not sure how many) the icons (running program indicators) that appear in the bottom (taskbar like ) panel changed from showing icons of the running program such as the emacs icon, xterm icon, vim icon etc. to just showing a generic icon and text, making it hard to identify witch icon is which program quickly. I started getting the same problem at a similar time with Jessie LXDE. Do your applications have the correct icons in the top left of their windows still? Mine does, it's just the taskbar which is wrong. Yes they do (I've attached a tiny snippet screen grab for running emacs and xterm windows laid over each other to show the icons) A (possibly wild) speculation is there's some race condition where the task bar button gets created before the application sets it's icon and then doesn't get notice or act on the change. I don't see this problem with all applications. The one I most notice it with is a (QT based?) commercial application: Beyond Compare. That sounds just like what I'm seeing; but with the exception I have no qt based apps. Do you see icons for xterm? -- 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/87a92vr8rt@reader.local.lan
Re: [minor bitch] about the panel (taskbar) LXDE
Andrei POPESCU andreimpope...@gmail.com writes: [...] Hugo Vanwoerkom hvw59...@care2.com writes: [...] Tixy t...@yxit.co.uk writes: [...] Whoops, forgot the promised screen grab:
Re: [minor bitch] about the panel (taskbar) LXDE
Andrei POPESCU andreimpope...@gmail.com writes: So far every application *except xterm* I have tried has the same icon in the top left corner of its window as well as the taskbar. I tried GTK as well as Qt applications. To me this seems to indicate a bug in xterm rather than lxpanel. I maybe mis-interpreting your meaning above. Do you mean you see the generic icon I posted both in corner of applicaitons and on the application indicator in taskbar? That is, you see NONE of the icons applications are supposed to have in either place? -- 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/871to7qqo2@reader.local.lan
Re: [minor bitch] about the panel (taskbar) LXDE
Hugo Vanwoerkom hvw59...@care2.com writes: Harry Putnam wrote: Running jessie Using an lxde desktop... for a long time now (Note: for lack of a fuller vocabulary, the word icon is used to cover a few different things below:) (Attached at bottom is a screen grab showing what I'm talking about) snip Running uptodate sid with lxde. I see none of the behaviour you are describing. Hugo Hugo, can you post a screen grab of your taskbar with several applicaitons running? -- 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/87wq5zpc0p@reader.local.lan
Re: [minor bitch] about the panel (taskbar) LXDE
Tixy t...@yxit.co.uk writes: On Wed, 2014-12-10 at 07:25 -0500, Harry Putnam wrote: Tixy t...@yxit.co.uk writes: A (possibly wild) speculation is there's some race condition where the task bar button gets created before the application sets it's icon and then doesn't get notice or act on the change. As an experiment I removed the taskbar from the panel, rebooted, opened some apps then added the taskbar back to the panel. The icons were still wrong, so my theory about timing looks like it's shot down. Thanks for that input... 1 thing tested I don't see this problem with all applications. The one I most notice it with is a (QT based?) commercial application: Beyond Compare. That sounds just like what I'm seeing; but with the exception I have no qt based apps. Do you see icons for xterm? xterm has the correct icon in its window's title bar but not in the taskbar. Thanks for this too... ditto for me -- 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/87signpbyg@reader.local.lan
[minor bitch] about the panel (taskbar) LXDE
Running jessie Using an lxde desktop... for a long time now (Note: for lack of a fuller vocabulary, the word icon is used to cover a few different things below:) (Attached at bottom is a screen grab showing what I'm talking about) Some mnths ago (not sure how many) the icons (running program indicators) that appear in the bottom (taskbar like ) panel changed from showing icons of the running program such as the emacs icon, xterm icon, vim icon etc. to just showing a generic icon and text, making it hard to identify witch icon is which program quickly. You can stop and and hold cursor on an icon (running program indicator) to see the full text it has, which will identify the program in most cases or you can click the panel entry and see which diplayed window iconizes or opens, but it used to be just a glance would tell you. Further, some indicators still show the regular icon. One I notice is iceweasel. I'd like the old behavior back but have no idea how to start digging into it. Perhaps it is an icon package or something ... hopefully someone here will know something about it...
Re: Haven't seen this ssh output before
Jochen Spieker m...@well-adjusted.de writes: Harry Putnam: harry-on-REMOTE-sol ssh REMOTE-deb no common kex alg: client 'diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1', server 'curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1' This means client and server couldn't agree on a key exchange algorithm. If you compare the client's and the server's list you will notice they have nothing in common. Seems odd that it should fail then since I'm not using a key based access. Just password. Perhaps I don't understand how ssh works. What flavor if Debian is the remote host running? The package openssh-server from unstable has this more or less recent changelog entry: The first line of OP mentions that I'm running `jessie'. openssh (1:6.7p1-1) unstable; urgency=medium * New upstream release (http://www.openssh.com/txt/release-6.7): - sshd(8): The default set of ciphers and MACs has been altered to remove unsafe algorithms. In particular, CBC ciphers and arcfour* are disabled by default. The full set of algorithms remains available if configured explicitly via the Ciphers and MACs sshd_config options. … -- Colin Watson cjwat...@debian.org Thu, 09 Oct 2014 14:05:56 +0100 Thanks for the usefull input... I'm now trying to investigate some way to get these two versions to comply with each other --- --- ---=--- --- --- Hard to believe that I haven't `full-upgraded' in over a month but apparently it is the case. It seems none of the client list from error output are mentioned as being an unsafe alg. but yet it fails. Seems unreasonable to put such a weak clue in the changelog... neither sshd_config on REMOTE or LOCAL have any mention of such options. I would assume that wheezy has the same version of openssh installed eh? I'm not at all clear on how one would go about making an adjustment in sshd_config to allow the algs used by my REMOTE-sol to be recognized. REMOTE-sol does not appear to be using OpenSSH .. maybe a solaris version of SSH. In light of the comments above; if you have any more info on this and have the time... please post. -- 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/87tx1lhcmt@newsguy.com
Re: Haven't seen this ssh output before
Harry Putnam rea...@newsguy.com writes: I'm not at all clear on how one would go about making an adjustment in sshd_config to allow the algs used by my REMOTE-sol to be recognized. REMOTE-sol does not appear to be using OpenSSH .. maybe a solaris version of SSH. In light of the comments above; if you have any more info on this and have the time... please post. I managed to get a bit of a solution after careful study of the error output and man sshd_config (Largely from being guided by your post) It shows the default kex algorithems and the possible kex alg. I thought of just adding one that matched the list of my clients available choices to sshd_config on REMOTE-deb like so: KexAlgorithms diffie-hellman-group-exchange-sha1 Then restart sshd. That works, but I was afraid that might mean the defaults would be dropped and only `diffie-hellman-group-exchange-sha1' would be offered. I was afraid that might cause failure on some other hosts. It was not clear to me from `man sshd_config' just how exactly to do this. I finally opted for listing all the defaults + diffie-hellman-group-exchange-sha1 Like this (in REMOTE-deb /etc/ssh/sshd_config): KexAlgorithms curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 That also works. Now, since debian chose to follow the new upstream sshd defaults and limits due to `UNSAFE' alg. I'm wondering if by adding one of those discarded algs back in there... I may be creating a security hole. The REMOTE-deb host is exposed to ssh via the internet... not just through the lan. Any opinions on what I may have created? -- 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/87mw7dh8d5@newsguy.com
Haven't seen this ssh output before
Running debian jessie I have one openindiana (solaris) host on my home lan. That host has had no updates or changes recently. Following a `full-upgrade' yesterday on a debian host, I am now seeing an ssh failure with output I have not seen before, when ssh from openindian host to debian host (newly full upgraded). From here on I'll refer to the hosts as LOCAL-sol and REMOTE-deb The LOCAL-sol host can ssh to all other lan hosts without problems, including 2 other debian hosts (not recently upgraded) So cutting to the chase: It appears likely that something changed on REMOTE-deb that is causing incoming ssh from LOCAL-sol to fail. Apparently something in the OS makeup of LOCAL-sol host disagrees with some recent change in REMOTE-deb. I use the following command very often until now: from: LOCAL-sol ssh to REMOTE-deb Note that I do not use any kind of key matching, agents or what not... just straight ssh password access for quite a long time. Also note as posted above... this same LOCAL-sol host can ssh to other (non-upgraded) debian hosts on my lan with no problem. --- --- ---=--- --- --- harry-on-REMOTE-sol ssh REMOTE-deb no common kex alg: client 'diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1', server 'curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1' --- --- ---=--- --- --- (ssh Verbose output is posted futher along). Its possible I've changed something on the LOCAL-sol host... but can't think what it might be. Further, the ssh -vv ouput below is pretty confusing to me, and did not help me debug it. Googling the above error output lead to some similar occurances but from quite a good while ago... 2005-2006 and I did not see the solution. --- --- ---=--- --- --- from LOCAL-sol ssh -vv REMOTE-deb (I've edited host names below, where ever I saw them) Sun_SSH_1.5, SSH protocols 1.5/2.0, OpenSSL 0x0090819f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to REMOTE-deb [192.168.0.5] port 22. debug1: Connection established. debug1: identity file /home/harry/.ssh/identity type -1 debug1: identity file /home/harry/.ssh/id_rsa type -1 debug1: identity file /home/harry/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Debian-3 debug1: match: OpenSSH_6.7p1 Debian-3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-Sun_SSH_1.5 debug1: use_engine is 'yes' debug1: pkcs11 engine initialized, now setting it as default for RSA, DSA, and symmetric ciphers debug1: pkcs11 engine initialization complete debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: en-US debug2: kex_parse_kexinit: en-US debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug1: Failed to acquire GSS-API credentials for any mechanisms (No credentials were supplied, or the credentials were unavailable or inaccessible ) debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: en-US debug2: kex_parse_kexinit: en-US debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519
Re: moving from 3.16-3-486 to 686
Pascal Hambourg pas...@plouf.fr.eu.org writes: Harry Putnam a écrit : My question is whether continuing to use the 486 versions of kernels has any down sides? The -486 kernel lacks support for multiprocessing/hyperthreading and PAE (which is required for NX/XD bit). I see in my latest `full-upgrade' that I've now gone to a 586 kernel: uname -r 3.16.0-4-586 I did nothing purposely to make that happen but there it is. Does your comment about multiprocessing/hyp ... hold true for 586 as well? Oh, and what is `NX/XD'? -- 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/87d28cec25@reader.local.lan
moving from 3.16-3-486 to 686
Months ago, installing jessie as guest on win7-64, I somehow ended up with a 486 kernel. In other previous installs it was a 686 kernel... not sure what I did. But no doubt I selected it without realizing or the like. My question is whether continuing to use the 486 versions of kernels has any down sides? I haven't run into anything I noticed to be a problem related to kernel version... but not sure I would be able to tell anyway. My usage is as single user on home lan, light programming, email, browse net, maybe small lan mail server. So with that kind of light usage in mind... is there likely to be anything that 686 offers that I'm likely to need? -- 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/87y4r2rfhw@reader.local.lan
no C-h i m emacs ??
[NOTE: Originally miss-posted on ... emacs.help] , | From: Harry Putnam rea...@newsguy.com | Subject: no C-h i m emacs ?? | Newsgroups: gmane.emacs.help | To: help-gnu-em...@gnu.org | Date: Mon, 17 Nov 2014 13:29:46 -0500 (2 minutes, 9 seconds ago) | Message-ID: 87egt14r51@reader.local.lan ` With emacs24-lucid installed, I can find no info files for emacs-24 /usr/share/info IXNEY for emacs /usr/local/share/ IXNEY for info So with all this installed: aps emacs|grep ^i i emacs-goodies-el- Miscellaneous add-ons for Emacs i A emacs24-bin-common - GNU Emacs editor's shared, architecture de i A emacs24-common - GNU Emacs editor's shared, architecture in i emacs24-el - GNU Emacs LISP (.el) files i emacs24-lucid - GNU Emacs editor (with Lucid GUI support) i A emacsen-common - Common facilities for all emacsen I still have no emacs-info files. Checking them all with dpkg -L shows no main info/emacs installed. /usr/share/info/dir has no entry for emacs other than: * Emacs FAQ: (emacs-24/efaq). Frequently Asked Questions about Emacs. * Emacs-Goodies-el: (emacs-goodies-el). * Emacs FAQ: (emacs-24/efaq). Frequently Asked Questions about Emacs. * Emacs-w3m: (emacs-w3m). An Emacs interface to w3m * Emacs-w3m-ja: (emacs-w3m-ja). An Emacs interface to w3m (Japanese) So apparently I'm missing something here. -- 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/871tp14qsw@reader.local.lan
Re: [exim4] rewrite left hand of email on outgoing mail
Jonathan Dowland j...@debian.org writes: My sympathies, I don't think it's an obvious location (ie outside of /etc/exim4) and I recall feeling similar when I eventually stumbled over it. On 18 Oct 2014, at 00:52, Harry Putnam rea...@newsguy.com wrote: So, I just insert things the way I want them... and restart exim4? Yes but I don't think the restart is needed. Do I need to use both of the forms that may occur for my user? Yes. Well that did it... thanks for your time and patience. Now if I can just set things so that this host can accept mail from the rest of the lan and relay it to my smarthost. But before I create some openended monster spam hole... Is that just a matter of inserting the networks who's mail you want to relay? I mean in /etc/exim4/update-exim4.conf.conf: dc_relay_nets='10.0.0.0/24;192.168.2.0/24' Those are the two networks making up my home lan. Or is there some more specific/explicit way to tell exim to relay for them? -- 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/87d29odgf0@reader.local.lan
[exim4] rewrite left hand of email on outgoing mail
Just now ran thru the ncurses interface you get with dpkg-reconfigure exim4.config On question you are asked is if you want to put a different domain on outgoing email I chose yes and inserted `newsguy.com' I never saw a way to rewrite the lefthand side of outgoing email. I need it to be `reader' instead of my UID (harry). That is, my outgoing `From: ' line and `envelope' info needs to say: rea...@newsguy.com and so then the return-path will have the right address. I'm on a small home lan with single user on my localhost. I have a fictitious domain `local.lan' so, `ha...@2xd.local.lan' will be meaningless on outgoing mail. And, of course, will fail if anyone tried to respond to `From: ' line. So, where is that done in exim config? (The domain part of the rewrite is apparently handled during dpkg-reconfigure exim.config) Here is the ncurses screen that handles the domain name change: ─┤ Mail Server configuration ├──┐ The option to hide the local mail name in outgoing mail was enabled.│ it is therefore necessary to specify the domain name this system│ should use for the domain part of local users' sender addresses.│ │ Visible domain name for local users:│ │ newsguy.com_│ │ OkCancel │ │ ┘ Contents of /etc/exim4/update-exim4.conf.conf: dc_eximconfig_configtype='smarthost' dc_other_hostnames='2xd.local.lan;local.lan' dc_local_interfaces='127.0.0.1 ; ::1' ( this line below should handle the domain rewrite but what about the uid being rewritten?) dc_readhost='newsguy.com' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='10.0.0.0/24;192.168.2.0/24' (smarthost munged) dc_smarthost='.xxx.xxx:587' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='true' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' -- 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/87d29qoba0@reader.local.lan
Re: [exim4] rewrite left hand of email on outgoing mail
Jonathan Dowland j...@debian.org writes: iirc it's /etc/email-addresses. See also man etc-email-addresses Oh man don't tell me its that easy... I've been fussing around with this for a good while. I've read a good bit about it, Been thru several key documents, but never heard mention of this file, So, I just insert things the way I want them... and restart exim4? Do I need to use both of the forms that may occur for my user? For example (my take from the man page but maybe bent a little): /etc/mail-addresses harry: rea...@newsguy.com USER2: rea...@newsguy.com --- --- ---=--- --- --- USER2 is also me and isn't used much. Only for certain kinds of testing etc. But if I did decide to send a msg from there I guess it should be set? Or am I missing how this file is supposed to work? -- 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/87zjcumey0@reader.local.lan
[sendmail] outgoing mail leaves dead letter
I managed to get sendmail sort of working on one of my vbox guest debian vms. It was kind of rough sledding and still not really working properly. I use a smarthost from fastmail.fm where I have accounts. Finally seems to have gotten the auth working thru access.db. But an odd thing is happening. I've been using mail-x to test things and use a little wrapper script that does this: mailx -v -s Subject recipi...@some.com txt_file The -v allows me to watch the smtp conversation as the mail gets processed. I'm going to post the smtp output shortly but first; a note of what I'm doing here; sending to mail to another domain where I have a shell account and am watching for my incoming tests by tailing the procmail.log. It's kind of a lot of smtp output but not sure what is pertinent to understanding why its leaving a dead litter on my end. I've sprinkled a few notes thru the output. --- --- ---=--- --- --- OK, here we go. mailx -v -s TEST 141014_184452 2xd1 rea...@jtan.com /tmp/tstmsg.txt rea...@jtan.com,2xd1... Connecting to [127.0.0.1] via relay... 220 2xd1.local.lan ESMTP Sendmail 8.14.4/8.14.4/Debian-8; Tue, 14 Oct 2014 18:44:56 -0400; (No UCE/UBE) logging access from: 2xd1.local.lan(OK)-2xd1.local.lan [127.0.0.1] EHLO 2xd1.local.lan 250-2xd1.local.lan Hello 2xd1.local.lan [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH LOGIN PLAIN 250-STARTTLS 250-DELIVERBY 250 HELP VERB 250 2.0.0 Verbose mode STARTTLS 220 2.0.0 Ready to start TLS EHLO 2xd1.local.lan 250-2xd1.local.lan Hello 2xd1.local.lan [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH LOGIN PLAIN 250-DELIVERBY 250 HELP VERB 250 2.0.0 Verbose mode MAIL From:ha...@2xd1.local.lan SIZE=428 AUTH=ha...@2xd1.local.lan 250 2.1.0 ha...@2xd1.local.lan... Sender ok RCPT To:rea...@jtan.com RCPT To:2...@2xd1.local.lan DATA 250 2.1.5 rea...@jtan.com... Recipient ok 550 5.1.1 2...@2xd1.local.lan... User unknown 354 Enter mail, end with . on a line by itself Here the mail content is piped in . 050 rea...@jtan.com... Connecting to mail.messagingengine.com. port 587 via relay... 050 220 mail.messagingengine.com ESMTP ready 050 EHLO 2xd1.local.lan 050 250-mail.messagingengine.com 050 250-PIPELINING 050 250-SIZE 7100 050 250-ENHANCEDSTATUSCODES 050 250-8BITMIME 050 250 STARTTLS 050 STARTTLS 050 220 2.0.0 Start TLS 050 EHLO 2xd1.local.lan 050 250-mail.messagingengine.com 050 250-PIPELINING 050 250-SIZE 7100 050 250-ENHANCEDSTATUSCODES 050 250-8BITMIME 050 250-AUTH PLAIN LOGIN 050 250 AUTH=PLAIN LOGIN 050 AUTH LOGIN 050 334 VXNlcm5hbWU6 050 aHB1dDNAZmFzdG1haWwuZm0= 050 334 UGFzc3dvcmQ6 050 aW5qeDAyMTc= 050 235 2.0.0 OK 050 MAIL From:ha...@newsguy.com SIZE=662 AUTH= 050 250 2.1.0 Ok 050 RCPT To:rea...@jtan.com 050 DATA 050 250 2.1.5 Ok 050 354 End data with CRLF.CRLF 050 . below jtan.com accepts 050 250 2.0.0 Ok: queued as 72F91C00012 050 rea...@jtan.com... Sent (Ok: queued as 72F91C00012) 250 2.0.0 s9EMiuN0027130 Message accepted for delivery Why does it go to a dead letter? rea...@jtan.com... Sent (s9EMiuN0027130 Message accepted for delivery) /home/harry/dead.letter... Saved message in /home/harry/dead.letter the message has showed up on jtan within seconds of mailxing I don't understand what happens here at the end. Closing connection to [127.0.0.1] QUIT 221 2.0.0 2xd1.local.lan closing connection Another second or two pass and the message shows up at jtan.com in the procmail.log of incoming mail. -- 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/8738aqb642@reader.local.lan
Re: [exim4] Testing and making sense of smtp output
lee l...@yagibdah.de writes: [...] Thanks for the tips. SMTP EHLO 2xd That's an invalid helo string. Is a valid one made up of just the full fqdn? And if so, is that not acquired from /etc/hosts? /etc/hosts 127.0.0.1dv.local.lan dvlocalhost 10.0.0.9 dv.local.lan dv [...] Is that setup incorrectly or is this even the place I should be looking? -- 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/87k345f87r@reader.local.lan
Re: [exim4] Testing and making sense of smtp output
lee l...@yagibdah.de writes: I accidentally let my prior response get away before I remembered to ask these questions. [...] LOG: MAIN = ha...@2xd.local.lan U=harry P=local S=569 $ delivering 1Xauru-0003TT-Fh R: smarthost for rea...@newsguy.com T: remote_smtp_smarthost for rea...@newsguy.com Transport port=25 replaced by host-specific port=587 Connecting to mail.messagingengine.com [66.111.4.52]:587 ... connected SMTP 220 mail.messagingengine.com ESMTP ready SMTP EHLO 2xd That's an invalid helo string. SMTP 250-mail.messagingengine.com 250-PIPELINING 250-SIZE 7100 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 STARTTLS SMTP STARTTLS SMTP 220 2.0.0 Start TLS SMTP EHLO 2xd That's an invalid helo string. SMTP 250-mail.messagingengine.com 250-PIPELINING 250-SIZE 7100 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-AUTH PLAIN LOGIN 250 AUTH=PLAIN LOGIN SMTP AUTH PLAIN SMTP 235 2.0.0 OK SMTP MAIL FROM:ha...@2xd.local.lan SIZE=1609 AUTH=ha...@2xd.local.lan SMTP RCPT TO:rea...@newsguy.com SMTP DATA SMTP 250 2.1.0 Ok SMTP 250 2.1.5 Ok SMTP 354 End data with CRLF.CRLF SMTP writing message and terminating . SMTP 250 2.0.0 Ok: queued as E25066800A8 SMTP QUIT LOG: MAIN = rea...@newsguy.com R=smarthost T=remote_smtp_smarthost H=mail.messagingengine.com [66.111.4.52] X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 DN=C=AU,ST=Victoria,L=Melbourne,O=FastMail Pty Ltd,CN=*.messagingengine.com A=plain C=250 2.0.0 Ok: queued as E25066800A8 LOG: MAIN Completed It worked because the MTA on mail.messagingengine.com is misconfigured in that it accepts invalid helo strings. What part of the smtp stream tips you off that it worked? I was just sort of baffled by it. You want to make sure that TLS is actually required before sending the password. Otherwise you may end up sending the password over an open connection. So do I pass somekind of query to smarthost first? or in some other part of config? -- 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/87fvetf80u@reader.local.lan
Re: [exim4] Testing and making sense of smtp output
Martin Read zen75...@zen.co.uk writes: On 12/10/14 14:52, lee wrote: Harry Putnam rea...@newsguy.com writes: Can any of you experienced exim4 hands interpret this output? Reading RFC-821 would tell you more. Reading RFC 2821 would be even better, since RFC 821 is obsoleted by RFC 2821. Thanks. I pounded thru that but I have to say I really didn't know any more about interpreting smtp output when done. What really happened is that I realized I'm probably a basic dimwit or severely under educated. -- 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/87bnphf7s5@reader.local.lan
Re: [exim4] Testing and making sense of smtp output
Harry Putnam rea...@newsguy.com writes: lee l...@yagibdah.de writes: [...] Thanks for the tips. SMTP EHLO 2xd That's an invalid helo string. Is a valid one made up of just the full fqdn? And if so, is that not acquired from /etc/hosts? /etc/hosts 127.0.0.1dv.local.lan dvlocalhost 10.0.0.9 dv.local.lan dv [...] Is that setup incorrectly or is this even the place I should be looking? Egad ... I just noticed that was from a different machine... but the format is the same on all of mine. So still should stand as something to critique/ -- 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/877g05f7on@reader.local.lan
Re: [exim4] Testing and making sense of smtp output
Joe j...@jretrading.com writes: [...] (I'm not sure if this output means it worked or it failed. I can tell you that nothing is showing up at the other end) Can any of you experienced exim4 hands interpret this output? Did the Authentication work or fail? The message was transmitted and accepted. The authentication must have worked, it would have been checked during the SMTP conversation, not afterwards. Thanks for the diagnosis and helpful points. [...] Snipped large chunk of very helpful and informative input (Thank you sir) Jonathan Dowland j...@debian.org writes: On Sun, Oct 12, 2014 at 02:45:44PM -0400, Harry Putnam wrote: And if so, is that not acquired from /etc/hosts? snip Egad ... I just noticed that was from a different machine... but the format is the same on all of mine. So still should stand as something to critique/ Debian's exim4 will take the contents of /etc/mailname over the dns name by default. I'd recommend putting the fqdn that you want exim to use there. OK that is very good tip to know about. Thanks -- 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/87lholdqh2@reader.local.lan
Re: [exim4] mixed up about terminology
Joel Rees joel.r...@gmail.com writes: So they would all be sending mail by way of server host. I guess that is not what is meant by relaying? I think that's relaying, but not open relay (if you get it set up right). But you should consider why you want to send out through a central server, unless your firewall is for some reason set up to only allow outbound mail from that server, in which case you probably do want to authenticate on the lan, too. (Think, for example, about the possibility of malware on a local box.) My reason was just to simplify the mail setup. I expect to have a dozen or so vms (of a variety of OS) at some point in the future. -- 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/87lhot7cx8@reader.local.lan
[exim4] Fresh config of lan smtp server question
Setup: Running 64bit Jessie Exim4-daemon-heavy pkg installed I'm working my way thru the `dpkg-reconfigure exim4-config' question answer session. It must be about the 2nd screen where it asks you the address of any hosts you expect to accept mail from. dpkg-reconfigure exim4-config: │ Please enter a semicolon-separated list of IP addresses. The Exim SMTP | │ listener daemon will listen on all IP addresses listed here. | │ An empty value will cause Exim to listen for connections on all│ │ available network interfaces. │ [...] Since my lan IPs sometimes change I'd rather give a network name. Just making sure that will work as well as individual IPs. The wording of the question makes it sound as if only exact HOST IP addresses are acceptable. I would like to give two networks as answer: 10.0.0.0/24 192.168.2.0/24 And, of course, I would like to filter out any others so don't want it blank. Can anyone tell me if that network notation will work, or will it gum up the works? -- 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/87tx3i8r4e@reader.local.lan
[exim4] mixed up about terminology
when running `dpkg-reconfigure exim4-config' I've run accross a few of the questions that are confusing to me... The current one I'm stumbling over is 1) A question about listing of host IPs the smtp listener will listen for... And then later on there is 2) A question about which hosts your server will relay for. (NOTE: These question do not appear back to back as I have them here) I probably have this all wrong but isn't the first question referring to remote IPs that will be using the server as smtp server. And the second one, is referring to using the server as smart host? which is also as an smtp server. That is, they are the same question in different words. Incoming smtp traffic (in question 1) (I guess) is referring to mails sent from remote IP to smtp server IP, to be sent on there way. And in question 2 the relaying question... their talking about sending from remote IP to server IP to perform ... smtp service ... I'm pretty sure I'm leaving out some major piece of the smtp puzzle but not at all sure what it might be. -- 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/87ppe68pzn@reader.local.lan
What problem does this log indicate?
System: 64bit jessie running as vbox vm guest Running on HOST Solaris (x86) (openindiana) I'm getting lots of lines in logs like below. Can anyone tell me what kind of a problem this log output is pointing to? /var/log/syslog:Oct 5 06:53:35 2xd systemd[1]: \ [/lib/systemd/system/rtkit-daemon.service:32] \ Unknown lvalue 'ControlGroup' in section 'Service' -- 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/87lhou8mey@reader.local.lan
Re: [exim4] mixed up about terminology
Brian a...@cityscape.co.uk writes: On Sun 05 Oct 2014 at 12:01:48 -0400, Harry Putnam wrote: when running `dpkg-reconfigure exim4-config' I've run accross a few of the questions that are confusing to me... The current one I'm stumbling over is 1) A question about listing of host IPs the smtp listener will listen for... And then later on there is 2) A question about which hosts your server will relay for. (NOTE: These question do not appear back to back as I have them here) I probably have this all wrong but isn't the first question referring to remote IPs that will be using the server as smtp server. I cannot find the first question you describe. It might be best to quote it in full and relate it to mail relaying. Pay no attention to the numbers I used, they have no baring on order of questions on the ncurses questionnaire one gets when running: `dpkg-reconfigure exim4-config' I posted this as 1) │ Please enter a semicolon-separated list of IP addresses. The Exim SMTP│ │ listener daemon will listen on all IP addresses listed here. │ │ │ │ An empty value will cause Exim to listen for connections on all │ │ available network interfaces. │ │ │ │ If this system only receives mail directly from local services (and not │ │ from other hosts), it is suggested to prohibit external connections to│ │ the local Exim daemon. Such services include e-mail programs (MUAs) │ │ which talk to localhost only as well as fetchmail. External connections │ │ are impossible when 127.0.0.1 is entered here, as this will disable │ │ listening on public network interfaces. │ And this as 2) │ Please enter a semicolon-separated list of IP address ranges for which│ │ this system will unconditionally relay mail, functioning as a smarthost. │ │ │ │ You should use the standard address/prefix format (e.g. 194.222.242.0/24 │ │ or 5f03:1200:836f::/48). │ │ │ │ If this system should not be a smarthost for any other host, leave this │ │ list blank. │ │ │ │ Machines to relay mail 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/87h9zi8jqq@reader.local.lan
Re: [exim4] mixed up about terminology
Simon Hollenbach ionpowe...@gmail.com writes: Hello Harry, On 05/10/14 18:01, Harry Putnam wrote: when running `dpkg-reconfigure exim4-config' I've run accross a few of the questions that are confusing to me... The current one I'm stumbling over is 1) A question about listing of host IPs the smtp listener will listen for... All the hosts listed here will be able to send mails to your server. And then later on there is 2) A question about which hosts your server will relay for. All the hosts listed here will be able to send any mail via your server to a remote host, your server is not the destination for the mail. OK, got it. I see when you explain it... it is quite a dramatic difference really. thanks You should leave the relay-list empty unless you really know what you are doing. Mail to remote hosts should generally only be processed for users that have authenticated to your SMTP-server. I don't have much of a clue of what I'm doing... but I should have mentioned earlier that my setup is a single user setup on a home lan. It gets a little confusing to me because the server itself needs to send out to my IP smart host, while at the same time it will serve s the smart host for my other lan machines. I do want to be able to use this server as the smart host for my other lan machines. So is that second one (about relaying) the place to list my lan networks? -- 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/87d2a68jdc@reader.local.lan
Re: What problem does this log indicate?
Brian a...@cityscape.co.uk writes: On Sun 05 Oct 2014 at 13:19:01 -0400, Harry Putnam wrote: System: 64bit jessie running as vbox vm guest Running on HOST Solaris (x86) (openindiana) I'm getting lots of lines in logs like below. Can anyone tell me what kind of a problem this log output is pointing to? /var/log/syslog:Oct 5 06:53:35 2xd systemd[1]: \ [/lib/systemd/system/rtkit-daemon.service:32] \ Unknown lvalue 'ControlGroup' in section 'Service' https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747568 May 10 seems like kind of an old bug to still be cropping up eh? Or is that about how it goes with that sort of bug? Further, it was not clear to be after reading the write up there whether I can just ignore the thing or what. -- 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/8761fy8iup@reader.local.lan
[exim4] Testing and making sense of smtp output
Setup: jessie 64 bit Freshly configured exim4 I'm quite new to exim4 although I've had it running on another Debian install for few months now. At any rate I'm not experienced enough to know how to find the source of a problem once I've gotten to the point where I'm attempting to send mail. Watching the smtp conversation but not sure what it is telling me. There may better ways to get some verbose output. If so, I hope someone points them out. I'm using `mailx -v' to get some verbose output regarding the smtp conversation like the example a couple of para below: (I'm not sure if this output means it worked or it failed. I can tell you that nothing is showing up at the other end) Can any of you experienced exim4 hands interpret this output? Did the Authentication work or fail? [NOTE: Just for the information, my lan is a fake one 2xd.{local.lan} was just invented right out of thin air some yrs ago] --- --- ---=--- --- --- $ mailx -v -s TEST $(dtf) $(hostname -f) rea...@newsguy.com txtmsg.txt LOG: MAIN = ha...@2xd.local.lan U=harry P=local S=569 $ delivering 1Xauru-0003TT-Fh R: smarthost for rea...@newsguy.com T: remote_smtp_smarthost for rea...@newsguy.com Transport port=25 replaced by host-specific port=587 Connecting to mail.messagingengine.com [66.111.4.52]:587 ... connected SMTP 220 mail.messagingengine.com ESMTP ready SMTP EHLO 2xd SMTP 250-mail.messagingengine.com 250-PIPELINING 250-SIZE 7100 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 STARTTLS SMTP STARTTLS SMTP 220 2.0.0 Start TLS SMTP EHLO 2xd SMTP 250-mail.messagingengine.com 250-PIPELINING 250-SIZE 7100 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-AUTH PLAIN LOGIN 250 AUTH=PLAIN LOGIN SMTP AUTH PLAIN SMTP 235 2.0.0 OK SMTP MAIL FROM:ha...@2xd.local.lan SIZE=1609 AUTH=ha...@2xd.local.lan SMTP RCPT TO:rea...@newsguy.com SMTP DATA SMTP 250 2.1.0 Ok SMTP 250 2.1.5 Ok SMTP 354 End data with CRLF.CRLF SMTP writing message and terminating . SMTP 250 2.0.0 Ok: queued as E25066800A8 SMTP QUIT LOG: MAIN = rea...@newsguy.com R=smarthost T=remote_smtp_smarthost H=mail.messagingengine.com [66.111.4.52] X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 DN=C=AU,ST=Victoria,L=Melbourne,O=FastMail Pty Ltd,CN=*.messagingengine.com A=plain C=250 2.0.0 Ok: queued as E25066800A8 LOG: MAIN Completed -- 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/871tqm85rq@reader.local.lan
Re: [exim4] mixed up about terminology
Jerry Stuckle jstuc...@attglobal.net writes: On 10/5/2014 4:38 PM, Brian wrote: On Sun 05 Oct 2014 at 16:16:22 -0400, Jerry Stuckle wrote: On 10/5/2014 12:01 PM, Harry Putnam wrote: I'm pretty sure I'm leaving out some major piece of the smtp puzzle but not at all sure what it might be. Two things here: First of all, are you sure your ISP allows connections to Port 25 on other hosts? Many ISPs (especially residential accounts) are now blocking such attempts due to trojans creating spam relays. You may not have noticed but the OP is attempting to connect to machines on his own network and to his ISP's mail server. Please try not to bring confusion to an already sorted situation. I KNOW he's trying to configure for his own network. I also KNOW it is connected to the internet. My advice stands - a misconfigured exim server can quickly become a SPAM source. Spammers all over the world are looking for just such servers, and quickly spread the word around. Second - be *very careful* in configuring Exim. Misconfiguration can easily allow your system to become an open relay for spammers. Such an operation at a minimum can get your IP (and ISP) a bad reputation, and at a maximum can get your account cancelled. Exim can be configured to be safe, but it's not necessarily straightforward. It's very straightforward when it is known what network exim is on. Not necessarily. Thinking it is very straightforward is what leads to open relays. Especially when you don't know what you're doing. In this case .. I've attempted to limit the relaying to the 2 networks making up my home lan. And the outbound ISP smtp server is an authenticating server. Can you give some hints what kind of holes incautious thinking has left? And if possible some ideas about how I might go about fixing them. -- 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/87wq8e6pfs@reader.local.lan
Re: [exim4] mixed up about terminology
Jerry Stuckle jstuc...@attglobal.net writes: The first question - why do you think you need to relay to other networks, even if they're your own? Do you have other SMTP servers running on those networks? Good question and apparently thee is no reason. It stemmed from a deep seated confusion about what relaying means. All I really want is to be able to do this: On my lan machines: HOST-1 HOST-2 [...] HOST-mail-server now being configured HOST-[12...N] would have the server host above listed as smarthost in there respective mail config. So they would all be sending mail by way of server host. I guess that is not what is meant by relaying? -- 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/87sij17urh@reader.local.lan
32/64 bit ... downloading install images
I want to download a jessie weekly build for 64 bit PC. What is the appropriate architecture on the downloads? My machine has nothing to do with amd but that is the only thing listed as 64 bit on the pages including jessie or testing. However, at https://www.debian.org/distrib/ the starting page for `Getting Debian, at least the netinst images are separated into: 64-bit PC netinst.iso or 32-bit PC netinst.iso These are only wheezy far as I can tell. Surprisingly that page gives no reference to jessie downloads. You would never know there were jessie downloads by looking at `Getting Debian' link. To find anything about debian jessie one must go to: https://www.debian.org/CD/http-ftp/ And if you follow the link to testing you will find no reference whatever to 64-bit PC. Maybe we are just supposed to KNOW somehow... but I don't... so is amd64 what I should download for a 64 bit PC? -- 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/878ukw0wvx@reader.local.lan
Re: 32/64 bit ... downloading install images
Andrei POPESCU andreimpope...@gmail.com writes: My machine has nothing to do with amd Well, AMD created the x86-64 architecture we are all using (Intel's IA-64 never became really popular), so actually it does ;) http://en.wikipedia.org/wiki/Amd64 That is interesting. I would not have guessed at that fact. As we see online many even thousands of bits that separate architecture in a sort of quickie non exacting way... as being amd PC PowerPC (maybe more) So the unwary reader is led to believe that amd means an architecture different from `pc'. Thanks for the clarity. -- 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/874mvj27ju@reader.local.lan
bash vulnerability jessie
After an `aptitude full-upgrade' this morning. I still get the `VULNERABLE' answer to `x='() { :;}; echo VULNERABLE' bash -c :' I hope that is the correct string... (extracted while googling on vulnerability) I did ssh to my user from the same shell I ran aptitude in to make sure I had a new login... but I still see `Vulnerable' in answer to the string above. Incidentally I get that same `Vulnerable' answer to `ksh' as well. After googling a bit about ksh... I haven't really found solid info about whether ksh is a problem too. I was a little surprised to see so little mention of this bash thing here too. Is this bash vulnerability not really a major concern? -- 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/87sije2x62@reader.local.lan
Re: bash vulnerability jessie
The Wanderer wande...@fastmail.fm writes: On 09/26/2014 at 11:56 AM, Harry Putnam wrote: After an `aptitude full-upgrade' this morning. I still get the `VULNERABLE' answer to `x='() { :;}; echo VULNERABLE' bash -c :' I hope that is the correct string... (extracted while googling on vulnerability) I've seen a few different ones, and that isn't any of them, but it seems to work just as well as the canonical one which I've seen demonstrate the vulnerability in the past. [...] Thanks for that input. I did ssh to my user from the same shell I ran aptitude in to make sure I had a new login... but I still see `Vulnerable' in answer to the string above. With what version of bash? I just upgraded to 4.3-9.1, from current testing, which includes the existing partial fix (a more complete one is apparently now in sid). I retested with the same test command you listed, as well as with what I'd seen the failyure on before, and it now shows as non-vulnerable. [...] I appear to have left out the fact that I'm talking about `jessie'. Sorry, a foolish slip... I usually do include that info. I may be a simpleton but I assumed anyone freshly `full-upgraded' with jessie would have the same version. Apparently not... here, after a full-upgrade of jessie about 2 hrs ago at a litte before noon or so Eastern standard (US) time I see: bash --version GNU bash, version 4.3.24(1)-release (i586-pc-linux-gnu) x='() { :;}; echo VULNERABLE' bash -c : VULNERABLE But also I did read in the few threads that have come thru that either wheezy or jessie (very recently upgraded) should not return `VULNERABLE', That is not tru for me here. It appears your version of bash if a bit newer than mine... so I guess it has been updated withing a few hours. However, as I mentioned above from what I've read in our threads, a full-upgrade only 2 hrs old should not have a version of bash that returns VULNERABLE. In practice, if your computer doesn't run any services (such as a Web or SSH server) that can be accessed from a non-trusted IP address (such as the outside Internet), you're probably safe. That pretty well describes me ... I run a ssh and web server on a home lan so no ssh or www requests from the internet are allowed. Just the nome network. ... As a matter of course I have `gone out of my way' as you say for yrs so maybe not too much threat here. Thanks for the input.. -- 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/87ioka2ots@reader.local.lan
Re: bash vulnerability jessie
Lisi Reisz lisi.re...@gmail.com writes: So little mention?? There have been three threads. I said little... I did not say none. Compared to systemd cyclone of threads and posts, it is `little' and probably much more important at least right now. I guess I expected more than I see here. -- 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/87h9zu2oqw@reader.local.lan