Re: Sharing files LINUX-LINUX / LINUX-WINDOWS / WINDOWS-WINDOWS
On Tue, Dec 1, 2020, 9:10 AM Anssi Saari wrote: > Kanito 73 writes: > > > At first I thought to use both SAMBA for LINUX-WINDOWS and maybe NFS for > LINUX-LINUX but I used NFS long time > > ago and it was slow as a turtle. Is there another networking service > available that runs faster only for > > LINUX-LINUX or it is better to use SAMBA for everything_ > > Personally I don't bother with Samba for file sharing on my home network > since Microsoft's seen the light and Windows 10 (Pro) includes NFS > support. And no, NFS is not slow as a turtle. > Hello Anssi, I am helping a friend make Windows 10 Pro talk to a variation of Debian (Linux Mint 20). Separately, I am running Windows 8.1, under QEMU-KVM on Bullseye. Can you provide a Microsoft (or related) link to the Windows NFS Support? (On this List. You do not need to cc me). Thanks! Kenneth Parker
Re: doing this does not make touchpad work
kaye@laptop:~$ ls -l /etc/X11/xorg.conf.d/40-libinput.conf -rw-r--r-- 1 root root 209 Dec 1 18:02 /etc/X11/xorg.conf.d/40-libinput.conf kaye@laptop:~$ dpkg -l | grep -i xserver-xorg-input ii xserver-xorg-input-all1:7.7+19 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 0.28.2-2 amd64X.Org X server -- libinput input driver ii xserver-xorg-input-wacom 0.34.99.1-1 amd64X.Org X server -- Wacom input driver kaye@laptop:~$ l0f4r0 bash: l0f4r0: command not found thank you! On Wed, Dec 2, 2020 at 3:06 AM wrote: > Hello, > > 1 déc. 2020 à 12:26 de guik...@gmail.com: > > > From this web page, > https://wiki.debian.org/SynapticsTouchpad > > I tried this > > > > $ mkdir -p /etc/X11/xorg.conf.d > > $ echo 'Section "InputClass" > > Identifier "libinput touchpad catchall" > > MatchIsTouchpad "on" > > MatchDevicePath "/dev/input/event*" > > Driver "libinput" > > Option "Tapping" "on" > > EndSection' > /etc/X11/xorg.conf.d/40-libinput.conf > > $ systemctl restart lightdm > > > > It did not work. I guess it's to be expected since I'm using Debian 10 > and not 9? > > > > Any workaround? > > > What are the following outputs please? > > ls -l /etc/X11/xorg.conf.d/40-libinput.conf > > dpkg -l | grep -i xserver-xorg-input > > l0f4r0 > >
Re: Installation instructions.
On Wed, 2 Dec 2020 at 10:06, wrote: > Installation instructions. > the CD image is not found. Please describe at exactly what point in your attempt you reached this conclusion. What screen messages did you see exactly? Due to the flexibility of Debian installation there are so many possible scenarios that to write a comprehensive reply would be time consuming for us and probably lack clarity for you (eg the existing documentation). If you provide more information (requested below) to exactly describe your situation, someone might be able to offer custom suggestions or even a tested solution ... > https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd Quoting paragraphs 2 and 3 from your link above ... """ If you intend to use the hard drive only for booting and then download everything over the network, you should download the netboot/debian-installer/i386/initrd.gz file and its corresponding kernel netboot/debian-installer/i386/linux. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care. Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the hd-media/initrd.gz file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from the CD/DVD image, without needing the network. """ So: 1) Which of the above are you attempting? Paragraph 2 or paragraph 3? Please describe what is on the hard drive before the installation, and what you want to be there after. 2) Given that choice (para 2 or 3), where did you get the vmlinuz and initrd.gz you are using? Please provide a full URL to them so we can reproduce your situation. 3) Which CD image are you using? Please provide a full URL to it so we can reproduce your situation. 4) The instructions that you linked to begin with this sentence: """ To boot the installer from hard disk ... """ So from that we might assume (you didn't explicitly say yet) that your goal is to run the Debian installer from a CD image data that is available in a file on an ext4 partition on a local hard drive. Is that correct? And your CD image is *not* on a removable media, is that correct? > Does anyone > happen to know how the ISO should be accessed? Loop mount at > /dev/cdrom? In my recent experience (using para 3 method), the installer searches the local hard drives for files that it recognises. And this search can fail to succeed if I haven't done the proper dance first. The vmlinuz and initrd must match the iso. I don't know about para 2 method, I never tried that.
Installation instructions.
https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd
gives this sample Grub2 configuration.
menuentry 'New Install' {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
linux /boot/newinstall/vmlinuz
initrd /boot/newinstall/initrd.gz
}
No problem with vmlinuz and initrd.gz but the CD image is not found.
The configuration which worked in the past had parameters on the linux
command. Similar to this.
linux /vmlinuz root=UUID=50e0fa4b-6c62-40f8-8a84-46ab1413eb5a ro from=hd
fromiso=debian-10.6.0-i386-netinst.iso load=all reboot=bios
The instructions at the URL above appear incomplete. Does anyone
happen to know how the ISO should be accessed? Loop mount at
/dev/cdrom?
Thx, ... P.
--
Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Fixing a Grub Foul-up Solved!
David writes: > Your lack of success is because the the command you used has designed > behaviour to install the grub bootloader to the boot sector of > /dev/sdd, and also install the grub files you listed into the current > system /boot/grub (which was not on sdd at the time). That is the > reason why you see those files on /dev/sda1, because it was the boot > partition at the time you ran the command. Aha!! that makes perfect sense now that I think a bit. > > If you want a grub-install command that writes /boot/grub files > somewhere onto /dev/sdd then you will first have to mount the desired > target boot partiton of /dev/sdd on some mountpoint that you choose, > and then run a command something like this: > sudo grub-install > --boot-directory=/some/mountpoint/where/is/the/sdd/boot /dev/sdd I tried it and by Joe, it wrote to the correct drive so I don't feel quite so paranoid about using grub. Interestingly, I goofed again and grub ended up in what is the / directory instead of /boot/grub so it still didn't work but I knew immediately that the new grub was working because there was no error message about symbols not found, etc. I mounted the drive back on the good system and simply removed the grub from the top of the tree and then did the grub-install command again but thihs time, I installed to /mnt/boot. It wrote to /boot/grub as it should have and the system came right up. There was a minor glitch when I powered the box up as the keyboard reported a stuck condition and advised me to press F1 to continue. I thought this was a bit amusing since the keyboard appeared to be malfunctioning but F1 did the trick and about a tenth of a second later, I heard the beep that grub plays when the kernel is about to fire off. In short, the faulty grub that made it onto the system was all that was really wrong. Thanks to a lot of you, I appreciate grub more as this has been quite a little mini course in what it does. Martin
Re: doing this does not make touchpad work
Hello, 1 déc. 2020 à 12:26 de guik...@gmail.com: > From this web page, > https://wiki.debian.org/SynapticsTouchpad > I tried this > > $ mkdir -p /etc/X11/xorg.conf.d > $ echo 'Section "InputClass" > Identifier "libinput touchpad catchall" > MatchIsTouchpad "on" > MatchDevicePath "/dev/input/event*" > Driver "libinput" > Option "Tapping" "on" > EndSection' > /etc/X11/xorg.conf.d/40-libinput.conf > $ systemctl restart lightdm > > It did not work. I guess it's to be expected since I'm using Debian 10 and > not 9? > > Any workaround? > What are the following outputs please? ls -l /etc/X11/xorg.conf.d/40-libinput.conf dpkg -l | grep -i xserver-xorg-input l0f4r0
Some packages missing for latest zsh version on stretch security repo
Hello, On a Debian Stretch server with the security repo enabled, I have an error today when trying to install zsh : The following packages have unmet dependencies: zsh : Depends: zsh-common (= 5.3.1-4) but 5.3.1-4+deb9u4 is to be installed This is caused by the security repo having only the zsh-common package in version 5.3.1-4+deb9u4, and missing the zsh package. This version was accepted today, as show in the following message : https://lists.debian.org/debian-lts-changes/2020/12/msg4.html `apt-cache policy` shows this : $ > apt-cache policy zsh zsh: Installed: 5.3.1-4+b3 Candidate: 5.3.1-4+b3 Version table: *** 5.3.1-4+b3 500 500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages 100 /var/lib/dpkg/status $ > apt-cache policy zsh-common zsh-common: Installed: 5.3.1-4 Candidate: 5.3.1-4+deb9u4 Version table: 5.3.1-4+deb9u4 500 500 http://security.debian.org stretch/updates/main amd64 Packages *** 5.3.1-4 500 500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages 100 /var/lib/dpkg/status I downloaded the package list at http://security.debian.org/debian-security/dists/stretch/updates/main/binary-all/Packages.gz It contains the following packages : Package: zsh-common Source: zsh Version: 5.3.1-4+deb9u4 Package: zsh-doc Source: zsh Version: 5.3.1-4+deb9u4 But the other packages from the zsh source are missing. I tried reaching out to t...@security.debian.org but they haven't answered yet. Is it the right way to deal with this problem, or should I open a bug on some tracker ?
Graphical environment; was, Re: Instructions for command line usage of WiFi.
From: Wim Date: Sun, 29 Nov 2020 20:14:05 +0100 > ... Sway, a Wayland compositor is now available in Sid. It's a drop > in replacement for i3wm. Works very well. Debian 10 here. Since 2000 I've jumped to "testing" twice. In both cases problems surfaced. After the second foray I resolved to refrain from "testing" except for a spare machine not in regular use. In mid-November I started Weston. In the first five or ten minutes it was useable with brief delays noticeable when Xwayland was required. Then artifacts appeared. Closed a window and artifacts remained in the display. Rapid flashing of patches of display associated with pointer movement. So not useable in 10. Definitely I'll be trying again in 11. Thanks, ... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Fixing a Grub Foul-up
On Mon, 30 Nov 2020 at 14:53, Martin McCormick wrote: > I typed sudo grub-install /dev/sdd. It ran for a few > seconds, announced that grub was installed without any errors and > exited. > After looking at /dev/sdd1/grub and seeing no updated > date stamps, I had a sinking feeling and looked at /dev/sda1 > which is the boot partition on the system I haven't killed yet > and, sure enough, grub-install had run on that drive. > $ ls -lt /boot/grub [...] > It didn't even touch any part of /dev/sdd1. The bootloader on /dev/sdd would have been updated. [...] > What am I failing to do to make the changes occur on the > designated drive? Your lack of success is because the the command you used has designed behaviour to install the grub bootloader to the boot sector of /dev/sdd, and also install the grub files you listed into the current system /boot/grub (which was not on sdd at the time). That is the reason why you see those files on /dev/sda1, because it was the boot partition at the time you ran the command. If you want a grub-install command that writes /boot/grub files somewhere onto /dev/sdd then you will first have to mount the desired target boot partiton of /dev/sdd on some mountpoint that you choose, and then run a command something like this: sudo grub-install --boot-directory=/some/mountpoint/where/is/the/sdd/boot /dev/sdd
Re: Sharing files LINUX-LINUX / LINUX-WINDOWS / WINDOWS-WINDOWS
Kanito 73 writes: > At first I thought to use both SAMBA for LINUX-WINDOWS and maybe NFS for > LINUX-LINUX but I used NFS long time > ago and it was slow as a turtle. Is there another networking service > available that runs faster only for > LINUX-LINUX or it is better to use SAMBA for everything_ Personally I don't bother with Samba for file sharing on my home network since Microsoft's seen the light and Windows 10 (Pro) includes NFS support. And no, NFS is not slow as a turtle.
Re: 780 files in /usr/share/zoneinfo/
I am very sorry for my Input. On Tue, Dec 1, 2020 at 12:28 AM David Wright wrote: > On Mon 30 Nov 2020 at 18:25:00 (-0600), John Hasler wrote: > > Stefan writes: > > > Is there leap-second information in the zoneinfo files? > > > > No, but that is where is should be. > > It appears to be present, at least in the difference between the > "posix" and "right" trees; and its history can be demonstrated: > > $ for j in $(seq 1971 2020) ; do TZ=UTC touch -t "$j"0401.00 "$j-apr" > ; done > $ for j in $(seq 1971 2020) ; do TZ=UTC touch -t "$j"1001.00 "$j-oct" > ; done > $ TZ=right/UTC dirr-time-in-full -Gg > .: > total 0 > -rw-r- 1 0 1971-04-01 00:00:00.0 + 1971-apr > -rw-r- 1 0 1971-10-01 00:00:00.0 + 1971-oct > -rw-r- 1 0 1972-04-01 00:00:00.0 + 1972-apr > -rw-r- 1 0 1972-09-30 23:59:59.0 + 1972-oct > -rw-r- 1 0 1973-03-31 23:59:58.0 + 1973-apr > -rw-r- 1 0 1973-09-30 23:59:58.0 + 1973-oct > -rw-r- 1 0 1974-03-31 23:59:57.0 + 1974-apr > -rw-r- 1 0 1974-09-30 23:59:57.0 + 1974-oct > -rw-r- 1 0 1975-03-31 23:59:56.0 + 1975-apr > -rw-r- 1 0 1975-09-30 23:59:56.0 + 1975-oct > -rw-r- 1 0 1976-03-31 23:59:55.0 + 1976-apr > -rw-r- 1 0 1976-09-30 23:59:55.0 + 1976-oct > -rw-r- 1 0 1977-03-31 23:59:54.0 + 1977-apr > -rw-r- 1 0 1977-09-30 23:59:54.0 + 1977-oct > -rw-r- 1 0 1978-03-31 23:59:53.0 + 1978-apr > -rw-r- 1 0 1978-09-30 23:59:53.0 + 1978-oct > -rw-r- 1 0 1979-03-31 23:59:52.0 + 1979-apr > -rw-r- 1 0 1979-09-30 23:59:52.0 + 1979-oct > -rw-r- 1 0 1980-03-31 23:59:51.0 + 1980-apr > -rw-r- 1 0 1980-09-30 23:59:51.0 + 1980-oct > -rw-r- 1 0 1981-03-31 23:59:51.0 + 1981-apr > -rw-r- 1 0 1981-09-30 23:59:50.0 + 1981-oct > -rw-r- 1 0 1982-03-31 23:59:50.0 + 1982-apr > -rw-r- 1 0 1982-09-30 23:59:49.0 + 1982-oct > -rw-r- 1 0 1983-03-31 23:59:49.0 + 1983-apr > -rw-r- 1 0 1983-09-30 23:59:48.0 + 1983-oct > -rw-r- 1 0 1984-03-31 23:59:48.0 + 1984-apr > -rw-r- 1 0 1984-09-30 23:59:48.0 + 1984-oct > -rw-r- 1 0 1985-03-31 23:59:48.0 + 1985-apr > -rw-r- 1 0 1985-09-30 23:59:47.0 + 1985-oct > -rw-r- 1 0 1986-03-31 23:59:47.0 + 1986-apr > -rw-r- 1 0 1986-09-30 23:59:47.0 + 1986-oct > -rw-r- 1 0 1987-03-31 23:59:47.0 + 1987-apr > -rw-r- 1 0 1987-09-30 23:59:47.0 + 1987-oct > -rw-r- 1 0 1988-03-31 23:59:46.0 + 1988-apr > -rw-r- 1 0 1988-09-30 23:59:46.0 + 1988-oct > -rw-r- 1 0 1989-03-31 23:59:46.0 + 1989-apr > -rw-r- 1 0 1989-09-30 23:59:46.0 + 1989-oct > -rw-r- 1 0 1990-03-31 23:59:45.0 + 1990-apr > -rw-r- 1 0 1990-09-30 23:59:45.0 + 1990-oct > -rw-r- 1 0 1991-03-31 23:59:44.0 + 1991-apr > -rw-r- 1 0 1991-09-30 23:59:44.0 + 1991-oct > -rw-r- 1 0 1992-03-31 23:59:44.0 + 1992-apr > -rw-r- 1 0 1992-09-30 23:59:43.0 + 1992-oct > -rw-r- 1 0 1993-03-31 23:59:43.0 + 1993-apr > -rw-r- 1 0 1993-09-30 23:59:42.0 + 1993-oct > -rw-r- 1 0 1994-03-31 23:59:42.0 + 1994-apr > -rw-r- 1 0 1994-09-30 23:59:41.0 + 1994-oct > -rw-r- 1 0 1995-03-31 23:59:41.0 + 1995-apr > -rw-r- 1 0 1995-09-30 23:59:41.0 + 1995-oct > -rw-r- 1 0 1996-03-31 23:59:40.0 + 1996-apr > -rw-r- 1 0 1996-09-30 23:59:40.0 + 1996-oct > -rw-r- 1 0 1997-03-31 23:59:40.0 + 1997-apr > -rw-r- 1 0 1997-09-30 23:59:39.0 + 1997-oct > -rw-r- 1 0 1998-03-31 23:59:39.0 + 1998-apr > -rw-r- 1 0 1998-09-30 23:59:39.0 + 1998-oct > -rw-r- 1 0 1999-03-31 23:59:38.0 + 1999-apr > -rw-r- 1 0 1999-09-30 23:59:38.0 + 1999-oct > -rw-r- 1 0 2000-03-31 23:59:38.0 + 2000-apr > -rw-r- 1 0 2000-09-30 23:59:38.0 + 2000-oct > -rw-r- 1 0 2001-03-31 23:59:38.0 + 2001-apr > -rw-r- 1 0 2001-09-30 23:59:38.0 + 2001-oct > -rw-r- 1 0 2002-03-31 23:59:38.0 + 2002-apr > -rw-r- 1 0 2002-09-30 23:59:38.0 + 2002-oct > -rw-r- 1 0 2003-03-31 23:59:38.0 + 2003-apr > -rw-r- 1 0 2003-09-30 23:59:38.0 + 2003-oct > -rw-r- 1 0 2004-03-31 23:59:38.0 + 2004-apr > -rw-r- 1 0 2004-09-30 23:59:38.0 + 2004-oct > -rw-r- 1 0 2005-03-31 23:59:38.0 + 2005-apr > -rw-r- 1 0 2005-09-30 23:59:38.0 + 2005-oct > -rw-r- 1 0 2006-03-3
doing this does not make touchpad work
Hello Friends! This is my system: Host: laptop Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux 10 (buster) >From this web page, https://wiki.debian.org/SynapticsTouchpad I tried this $ mkdir -p /etc/X11/xorg.conf.d $ echo 'Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "Tapping" "on" EndSection' > /etc/X11/xorg.conf.d/40-libinput.conf $ systemctl restart lightdm It did not work. I guess it's to be expected since I'm using Debian 10 and not 9? Any workaround? Thank you very much!
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 27 days
Hello,
I quickly grepped my DEBIAN-USER mailing-list file but did not find any
leapsecond in it, thus this message.
I get this error on all of my buster machines although I think they are
uptodate:
Dec 1 09:34:39 virtual ntpd[2432]: leapsecond file
('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 27 days
A quick Internet search shows this:
https://www.mail-archive.com/debian-glibc@lists.debian.org/msg59571.html
Apparently, the Debian distributed file will expire on 2020-12-28.
However, it seems the next Debian point release scheduled on 2020-12-05
contains an update for tzdata, so it should be fixed then.
Re: Apt source for security.debian.org
Thanks Reco, adding the slash did the trick. OpenPGP_signature Description: OpenPGP digital signature
