considering a new system and a sshd hybrid drive

[shirish शिरीष]

Dear all,

Last year I had read some articles when I was looking to build a
system there seemed to problems with hybrid drives. Does anybody know
how things stand/look today and if anybody had any good/bad experience
with them ?  IIRC, the issues were more to do with the firmware rather
than the hardware, is it the same or have things improved ? which
package I should be looking at if I'm looking for solutions ?


I am ok with using either a stable or an alpha/debian-installer
snapshot if people have had good experience.

Just so people have an idea about what hybrid drives are all about,
here are couple of links

https://www.seagate.com/in/en/do-more/how-to-choose-between-hdd-storage-for-your-laptop-master-dm/

https://www.howtogeek.com/195262/hybrid-hard-drives-explained-why-you-might-want-one-instead-of-an-ssd/

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Re: systemdq

[chris]

dont worry the resistance to systemd is still strong not everyone drinks
the kool aid

https://linux.slashdot.org/story/19/12/08/2131220/debian-begins-voting-on-supporting-non-systemd-init-options

https://www.debian.org/vote/2019/vote_002#textb


On Fri, Dec 27, 2019 at 6:40 PM ghe  wrote:

> SSH isn't starting at boot on my server. When I try to set it to do
> that, systemd says it can't do that 'without a command.'
>
> What kind of command makes it happy? Where does it need to be?
>
> (I've futzed with the ssh file in /etc/default, even entered a command:
> (qwerty="42" -- it wasn't impressed). I looked around on the web (lots
> of info about systemd commands, but nothing about what I need.)
>
> Help??
>
> --
> Glenn English
>
>

Re: systemdq

[ghe]

On 12/28/19 2:57 PM, Charles Curley wrote:

> Oddly enough, the sshd package does not provide sshd.service as a file
> at all, but may create it as part of the installation process. It does
> provide ssh.service. 

I haven't looked at the Debian unit files, but SSH and SSHD both seem to
be in the Raspian ssh.service file. I suspect I would have been OK
enabling the plain old SSH file.

> This leads me to wonder if something is not right
> with the rasbian package.

Not a big surprise to those who've spent some time fighting with the 4.

> Do you have both the server and the client installed? On Debian, you
> need openssh-client and openssh-server.

Yes. All is working as expected now.

-- 
Glenn English

Re: INQUIRY

[Gene Heskett]

On Saturday 28 December 2019 16:50:53 John Hasler wrote:

> > Place was built in 74, before the NEC became the law in most
> > municipalities.
>
> Where do you live?  I doubt that the NEC had not been incorporated
> into law in most municipalities in the USA in 1974.

Weston WV. County seat of Lewis County. Current pop about 5500.
I bought a pocket copy in 1996, about a foot away as I type this. When I 
had already been the CE at WDTV-5 since 1984. Everything I touched was 
wrong and grandfathered in. A car dealership, remodeled for the tv 
station in 'early 84. Took me nearly 15 years to just get the 60 hz hum 
out of the video in the output of the studio cameras.

I took us off the air for 3 hours or so as I took a service box down and 
corrected it to get a little closer to code. The perp was a carpenter, 
and played mix and match with the neutrals and statics all over an 80 by 
175 foot building. Because all the coax was BBLD West Penn, I replaced 
several miles of it as the shielding wasn't.  By the time I hung it up 
in mid-2002 I finally had good video and audio being delivered to the 
STL.

We won't discuss in fine detail the tx building on Fisher Hill which was 
so old the buildings entrance fuses were in the 7200 up on the 
substation pole. And they had been blown so many times the inside of the 
ceramic tubing they were in was almost as good a conductor as the fuse 
was. Had to stomp out a grass fire under the pole several times.

No 3 pin duplexes in the place except the Weber's in the racks, and the 
third pin wasn't wired to anything. That building is still live today 
but has not been used since June 30th 2008, but the tower is tall enough 
to need lights so its still powered. I got an estimate once to bring it 
up to code and darned near gave the GM a heart attack.  Because it had 
no place to shut it off, I once replaced a smokeing kearney bolt joining 
4, 750 mcm cables while it was hot and on the air.

Needless to say, the pair of 24" crescent wrenches I used to put the 
finishing touches on tightening that up had about 2 rolls of scotch 88 
each on the handles. I did get one short buzz while re-wrapping it in 
Cambric, then a couple layers of scotch 88.

Lets just say its been an interesting ride and I have to remind folks I 
didn't get to be old by accident. ;-)

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: systemdq [Solved]

[ghe]

Trivial in retrospect.

There were several ssh* files in /lib/systemd/service. None named sshd*.
I copied the one named ssh.service to sshd.service, enabled it,
rebooted, and there is was.

An interesting question is why things are different in Raspian Stretch
on a 3+. For the time being, I'll just blame the RPi4 OS/motherboard. Or me.

Thanks all.

-- 
Glenn English

Re: systemdq

[Linux-Fan]

ghe writes:


>>Have you tried commands of this sort?

# systemctl enable sshd.service
# systemctl start sshd.service
# systemctl status sshd.service

>From asking it to start at boot:

Failed to save action : Systemd service ssh cannot be created unless a
command is given

Trying the suggested commands:

Failed to enable unit: Unit file sshd.service does not exist.

Failed to start sshd.service: Unit sshd.service not found.

Unit sshd.service could not be found.


Now that are some "good" error messages :)

My next step would be to check were the unit is gone (might save the time to
create one). On my system (not Rapsbian, but Debian 10.2 "Buster"), one can
use these commands:

$ systemctl | grep ssh
ssh.service loaded active running   OpenBSD Secure Shell server

If `ssh.service` is present in `systemctl` output, it might be interesting
to give the enable/start/status sequence another try with `sshd.service`
replaced by `ssh.service`?

$ dpkg -L openssh-server
[...]
/etc/init.d/ssh
[...]
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/rescue-ssh.target
/lib/systemd/system/ssh.service
/lib/systemd/system/ssh.socket
/lib/systemd/system/ssh@.service
[...]

This indicates that the actual unit name is `ssh.service` although on my
system, `systemctl status sshd.service` (with additional `d`) works just as
well :)

It would be interesting to see, if the files are also present on the system
which produces the error messages mentioned above. If no `.service` files
can be identified this way, it would be interesting to check the version and
origin of the `openssh-server` package like this (with the output from my
system included as an example):

$ apt-cache policy openssh-server
openssh-server:
  Installed: 1:7.9p1-10+deb10u1
  Candidate: 1:7.9p1-10+deb10u1
  Version table:
 *** 1:7.9p1-10+deb10u1 500
500 http://security.debian.org buster/updates/main amd64 
Packages
500 file:/fs/e01/normal/debianmirror/cnt buster/main amd64 
Packages
100 /var/lib/dpkg/status

HTH
Linux-Fan


pgpNaKqxO9sGT.pgp
Description: PGP signature

Re: systemdq

[Charles Curley]

On Sat, 28 Dec 2019 14:15:36 -0700
ghe  wrote:

> >>Have you tried commands of this sort?  
> 
> # systemctl enable sshd.service
> # systemctl start sshd.service
> # systemctl status sshd.service
> 
> >From asking it to start at boot:  
> 
> Failed to save action : Systemd service ssh cannot be created unless a
> command is given
> 
> 
> Trying the suggested commands:
> 
> Failed to enable unit: Unit file sshd.service does not exist.
> 
> Failed to start sshd.service: Unit sshd.service not found.
> 
> Unit sshd.service could not be found.

That seems pretty unambiguous to me. You don't have the file
sshd.service where systemd can find it.

> 
> > Have you tried removing openssh-server package and reinstalling it?
> > If you re using any version of Debian the default
> > installation comes with sane defaults and it leaves the service
> > enabled and running.  
> 
> Reinstalling (from an RPi mirror) did nothing. Trying to get it
> started at boot gave the same error message as before.

Debian (not rasbian) seems to put sshd into place at installation time.

charles@hawk:~$ locate sshd.service
/etc/systemd/system/sshd.service
/var/lib/systemd/deb-systemd-helper-enabled/sshd.service
charles@hawk:~$

The second one has to be there. The first is optional and overrides the
second.

Oddly enough, the sshd package does not provide sshd.service as a file
at all, but may create it as part of the installation process. It does
provide ssh.service. This leads me to wonder if something is not right
with the rasbian package.

Do you have both the server and the client installed? On Debian, you
need openssh-client and openssh-server.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: INQUIRY

[John Hasler]

> Place was built in 74, before the NEC became the law in most
> municipalities.

Where do you live?  I doubt that the NEC had not been incorporated into
law in most municipalities in the USA in 1974.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: systemdq

[ghe]

>>Have you tried commands of this sort?

# systemctl enable sshd.service
# systemctl start sshd.service
# systemctl status sshd.service

>From asking it to start at boot:

Failed to save action : Systemd service ssh cannot be created unless a
command is given


Trying the suggested commands:

Failed to enable unit: Unit file sshd.service does not exist.

Failed to start sshd.service: Unit sshd.service not found.

Unit sshd.service could not be found.

> Have you tried removing openssh-server package and reinstalling it?
> If you re using any version of Debian the default
> installation comes with sane defaults and it leaves the service
> enabled and running.

Reinstalling (from an RPi mirror) did nothing. Trying to get it started
at boot gave the same error message as before.


My problem was the lame error message -- there are lots of commands on
my server. The suggestions from the list gave me enough info that I feel
I have some things to look after. Looks like creating an sshd.service
unit file would be a good idea.


I was also glad to see that Gene had gone back to Raspian -- my next
step was going to be installing Genuine Debian. Raspian on the RPi4 is,
IMHO, less than stable.

-- 
Glenn English

Re: INQUIRY

[Doug McGarrett]

On 12/28/2019 01:54 PM, Charles Curley wrote:

On Sat, 28 Dec 2019 18:38:56 +0100 (CET)
 wrote:


Hello Debian , I'm getting error while installing grub in Debian.
The error is "unable install grub in dummy"
My intention is to dual boot debian and windows.


Well, I have no idea what "dummy" is in this context.

Most Windows installations are to /dev/sda1 (the main Windows
partition) and /dev/sda2 (the Windows recovery partition). Assuming you
have shrunk your Windows partition, rather than install a second drive
for Linux (you didn't say), your boot partition will be /dev/sda3 or
higher. Other partitions will be /dev/sda5 and/or higher. And all of
that discussion ignores UEFI issues


I bought a new computer last summer, and it came with Windows 10 on FOUR
partitions! I shrank the Windows partition 4 to 100 GiB to allow a 
minimum Windows system for anything that won't run on OpenSUSE TW, and 
made a new partition for Linux, using a disk for GParted. Works fine.

--doug


Since you want a dual-boot setup, you have several options. One is to
have Windows present a boot menu, with an entry for Linux. Another is
to use grub to boot both Linux and Windows. In the former case, you
install grub to the Linux boot partition. In the latter, to /dev/sda.
And again, that ignores UEFI, which is a whole other can of lawyers.

So what is the *exact* error message you got?

Which version of Linux? Debian, I expect. But which version of Debian?
And which of the many possible installation patterns are you trying to
use?

Re: INQUIRY

[Gene Heskett]

On Saturday 28 December 2019 13:39:54 Cindy Sue Causey wrote:

> On 12/28/19, darkskyz...@tutanota.de  wrote:
> > Hello Debian , I'm getting error while installing grub in Debian.
> > The error is "unable install grub in dummy"
> > My intention is to dual boot debian and windows.
>
> Hi... I did a couple quick searches just to see if anything popped. My
> first one using your words landed one result.. this thread The
> second fairly targeted search only pulled up ~570.
>
> What might help the list help you is to know something about your
> setup. Most specifically, it would help if they know the exact command
> you're using. Beyond that, maybe how your hard drive and partition(s)
> is/are set up.
>
> Without actually entering any webpages, I saw a couple references to
> users specifically requesting "grub-install dummy".. so that's why I
> ask. I've never heard of "dummy" for this. That only means that the
> most I've ever needed for my usage is "grub-install /dev/sda" (or
> /dev/sdb, etc). :)
>
> After thinking on it a few more seconds before sending this out, I
> tried this search:
>
> error "grub-install dummy"
>
> That landed something potentially useful from Kali's message boards:
>
> https://forums.kali.org/showthread.php?35926-Executing-grub-install-du
>mmy-failed=d8cf37f9fee08ca29b2ec7aeda842ae0=77478#post77478
>
> If that doesn't jump down to the quote, Comment #40 sounds pretty
> interesting and rational. Am posting in case that also triggers any
> related do/do nots, too. Good luck... :)
>
> Cindy :)

Pasted from your sig Cindy.

* runs with... YET ANOTHER hardware failure. THIS TIME? LIGHTNING
STORM... ATE MY _NEW_ DIALUP MODEM less than 24 hours in. Wanders off
now singing... If it weren't for ba-a-a-ad luck, I'd have no luck at

Have an electrician inspect your service for proper grounding bringing it 
up to code if not. I used to lose a modem everytime I heard thunder. 

So as a CET I made sure all my static grounds were good back to the 
service, finding this place was wired by an idiot who was never in a 
same room with a copy of the NEC. Place was built in 74, before the NEC 
became the law in most municipalities. Then in 2007 in prep for building 
an attached garage, I installed a new 200 amp service and brought the 
ground up to code, make this house a 60 amp subcircuit. 

Lowes also sells a little tester you can plug into a duplex to verify 
each sockets proper wiring, about a 15 or 20 dollar bill. Get one and 
check them all. 

And since you are on dialup, make sure the demarcation box where the 
phone line enters the house is also well grounded, it has lightning 
arresters in it. They are good ones, Ma Bell has spent 100+ years 
developing them. There s/b a good sized solid wire, probably bare, 
connecting one end of the arresters to a nearby ground rod.

HTH.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: systemdq

[Gene Heskett]

On Saturday 28 December 2019 12:47:16 Curt wrote:

> On 2019-12-28, Gene Heskett  wrote:
> > On Saturday 28 December 2019 11:08:20 ghe wrote:
> >> On 12/27/19 5:02 PM, Nektarios Katakis wrote:
> >> > Have you tried removing openssh-server package and reinstalling
> >> > it?
> >>
> >> Another hopefully good suggestion. Thanks, and I'll try it.
> >>
> >> > If you re using any version of Debian
> >>
> >> Raspian Buster.
> >
> > One problem, raspian buster is armhf, debian is arm64.
>
> I was going to say--but didn't!--that the OP had merely provided a
> bunch of prose ("try to set" etc.) and no genuine technical detail
> (viz. a cut-and-paste of input/output from a terminal session) in his
> problem presentation, so that even Carnac the Magnificent in his prime
> would fail to divine where the error might lie. Then he revealed
> (because the whole process should be like pulling teeth--if they don't
> fall out "naturally," if haphazardly, that is) he was using Raspian
> rather than Debian, and I thought it was the addition of insult to
> injury.
>
> Maybe 'sshd -t' would disclose some snafu in the config (a stray "-"
> without an argument)?
>
Your guess is as good as mine, but I do know of a combination of the 2, 
is in one case an instant pi crasher, that of installing the armhf 
version of the amanda client, on the debian buster arm64 install will 
crash the whole maryann about 2 seconds after the server asks the client 
for an estimate. And it does it without so much as a by-by in the logs. 
That same client, installed on a raspian (armhf) install has been 
running flawlessly for a couple weeks now.

Maybe not, but all the clues point to the debian repo's identical version 
of the amanda client not haveing been rebuilt with arm64 flags set when 
debian changed the architecture of the rpi4 to arm64 from armhf with the 
buster release.  This lets the debian-arm boot useing grub! debian-arm 
ran just as stably for me until I tried to add it to my backup here.

Once I discovered debian-arm was now an arm64 build, I switched back to 
the raspbian build because its smaller armhf stack frame=reduced 
latency, so I stepped up a few releases of the rt kernel, to make sure I 
had the latest video drivers, built it and installed it, worked 
reasonably well reporting glxgears at near 60 fps even when pulled to 
full screen, so I dd a git clone of linuxcnc, pulled in the missing deps 
as the make discovered them, and there was quite a list that 
dpkg-chkbuilddeps did not find, but eventually it did build linuxcnc as 
debs, I installed that and its running an 11x54 Sheldon lathe 
flawlessly, with video fps's right close to 55.  The pi3 only manages 
video fps's in the 1.5-2.5 range running build from the same code, so 
that is a huge diff.

All this of course took place on an SSD plugged into one of the usb-3 
ports of the rpi-4 once it was installed, no way was I going to subject 
the boot u-sd to that abuse.

The only niggle in the linuxcnc operation now is a slight stutter in jog 
motions from the keyboard arrow keys, which does NOT manifest itself 
running gcode or MDI driven moves. I can live with that.
 
You can get that kernel, and the linuxcnc debs from my web site, add 
lathe-stf to the link in the sig, you'll see a linuxcnc4rpi4 link, click 
on that and you can dl it all, but my uplink is slow.  Poor boy net 
connection. I can get gigabyte, for another $30 a month.

If you can't get to it, I have around 35 search bots blocked with 
iptables useing /24 syntax. Let me know your net address and I'll make 
sure your aren't blocked. Most of the bots didn't bother me, just 
indexing my site, till I put that up, then they downloaded my whole site 
repeatedly which was a DDOS because of my limited uplink bandwidth.

> > Cheers, Gene Heskett


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Network-Manager and Fritzbox

[Jürgen Bausa]

I am running a laptop (Xiaomi Air 12) with debian Buster AMD64 and use KDE with network-Manager.
Wifi is supplied by a Fritzbox 7530 wifi-router (2.4 and 5 GHz with same ssid and wpa2).
Since I use the Fritzbox (before that I used a TP-Link router, that did not have this problem)
I experience the following problem:

 

When a new connection is initiated by the laptop (after reboot or resume) in some cases (about 5-10 %)
the connection is made for a very short time only. The laptop is then disconnected and a window appears
on the desktop, saying that the password had been wrong (which is definitely not the case: the correct password
is stored in NMs database) and asking for the correct one. When I type in the correct password,
the connection is made. Or, if I just close the window and clcik on the connection in NM, the
connection is also made.

 

This is what I find in the routers log (lina is my laptop):
(translation from german).

 

20.12.19 22:57:51 WIFI-device has been disconnected (5 GHz), lina, IP 192.168.0.31, MAC XX:XX:XX:XX:XX:XX.
20.12.19 22:57:48 WIFI-device has been connected, WIFI reactivated with full power (5 GHz).

 

These two things are always the same, when the problem happens:
- the router resumes from power saving mode when the first attempt to connect is made (WIFI reactivated with full power)
- 5 Ghz is used

 

This is what I find in the laptops log:

 

wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=DE
wlp1s0: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='meineSSID' freq=5220 MHz)
wlp1s0: Trying to associate with XX:XX:XX:XX:XX:XX (SSID='meineSSID' freq=5220 MHz)
wlp1s0: Associated with XX:XX:XX:XX:XX:XX
wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp1s0: WPA: Key negotiation completed with XX:XX:XX:XX:XX:XX [PTK=CCMP GTK=CCMP]
wlp1s0: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:XX:XX completed [id=0 id_str=]
wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise= txrate=6000
Dec 20 22:57:48 lina avahi-daemon[637]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::31a:e3aa:b668:28ed.
Dec 20 22:57:48 lina avahi-daemon[637]: New relevant interface wlp1s0.IPv6 for mDNS.
Dec 20 22:57:48 lina avahi-daemon[637]: Registering new address record for fe80::31a:e3aa:b668:28ed on wlp1s0.*.
Dec 20 22:57:49 lina dhclient[17036]: DHCPREQUEST for 192.168.0.31 on wlp1s0 to 255.255.255.255 port 67
wlp1s0: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX reason=2
wlp1s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="meineSSID" auth_failures=1 duration=10 reason=WRONG_KEY
dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/5
wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 20 22:57:54 lina systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec 20 22:58:06 lina avahi-daemon[637]: Withdrawing address record for fe80::31a:e3aa:b668:28ed on wlp1s0.
Dec 20 22:58:06 lina avahi-daemon[637]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address :::::.
Dec 20 22:58:06 lina avahi-daemon[637]: Interface wlp1s0.IPv6 no longer relevant for mDNS.
wlp1s0: Reject scan trigger since one is already pending

 

The whole thing only happens with the debian buster laptop. No problem with other clients (android, Mac, iphone, Windows10)

I tried this in another house, where same router is used. There, the same problem appears. However with a different
laptop (Acer),  but also debian buster AMD64 with KDE and network-Manager.

 

Anyone else using a Fritzbox Router? Having or not having this problem? I am not sure if it is related to router, NM,
or kernel. I dont think its related to the wifi driver, because it happened on two laptops with different hardware.

 

Is there any way for me to obtain more information do debug this?

 

Regards,

Jürgen

Re: INQUIRY

[Charles Curley]

On Sat, 28 Dec 2019 18:38:56 +0100 (CET)
 wrote:

> Hello Debian , I'm getting error while installing grub in Debian. 
> The error is "unable install grub in dummy"
> My intention is to dual boot debian and windows.

Well, I have no idea what "dummy" is in this context.

Most Windows installations are to /dev/sda1 (the main Windows
partition) and /dev/sda2 (the Windows recovery partition). Assuming you
have shrunk your Windows partition, rather than install a second drive
for Linux (you didn't say), your boot partition will be /dev/sda3 or
higher. Other partitions will be /dev/sda5 and/or higher. And all of
that discussion ignores UEFI issues

Since you want a dual-boot setup, you have several options. One is to
have Windows present a boot menu, with an entry for Linux. Another is
to use grub to boot both Linux and Windows. In the former case, you
install grub to the Linux boot partition. In the latter, to /dev/sda.
And again, that ignores UEFI, which is a whole other can of lawyers.

So what is the *exact* error message you got?

Which version of Linux? Debian, I expect. But which version of Debian?
And which of the many possible installation patterns are you trying to
use?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: INQUIRY

[Cindy Sue Causey]

On 12/28/19, darkskyz...@tutanota.de  wrote:
> Hello Debian , I'm getting error while installing grub in Debian.
> The error is "unable install grub in dummy"
> My intention is to dual boot debian and windows.


Hi... I did a couple quick searches just to see if anything popped. My
first one using your words landed one result.. this thread The
second fairly targeted search only pulled up ~570.

What might help the list help you is to know something about your
setup. Most specifically, it would help if they know the exact command
you're using. Beyond that, maybe how your hard drive and partition(s)
is/are set up.

Without actually entering any webpages, I saw a couple references to
users specifically requesting "grub-install dummy".. so that's why I
ask. I've never heard of "dummy" for this. That only means that the
most I've ever needed for my usage is "grub-install /dev/sda" (or
/dev/sdb, etc). :)

After thinking on it a few more seconds before sending this out, I
tried this search:

error "grub-install dummy"

That landed something potentially useful from Kali's message boards:

https://forums.kali.org/showthread.php?35926-Executing-grub-install-dummy-failed=d8cf37f9fee08ca29b2ec7aeda842ae0=77478#post77478

If that doesn't jump down to the quote, Comment #40 sounds pretty
interesting and rational. Am posting in case that also triggers any
related do/do nots, too. Good luck... :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with... YET ANOTHER hardware failure. THIS TIME? LIGHTNING
STORM... ATE MY _NEW_ DIALUP MODEM less than 24 hours in. Wanders off
now singing... If it weren't for ba-a-a-ad luck, I'd have no luck at
all-l-l-l-l. *

Re: systemdq

[Curt]

On 2019-12-28, Gene Heskett  wrote:
> On Saturday 28 December 2019 11:08:20 ghe wrote:
>
>> On 12/27/19 5:02 PM, Nektarios Katakis wrote:
>> > Have you tried removing openssh-server package and reinstalling it?
>>
>> Another hopefully good suggestion. Thanks, and I'll try it.
>>
>> > If you re using any version of Debian
>>
>> Raspian Buster.
>
> One problem, raspian buster is armhf, debian is arm64.

I was going to say--but didn't!--that the OP had merely provided a bunch
of prose ("try to set" etc.) and no genuine technical detail (viz. a
cut-and-paste of input/output from a terminal session) in his problem
presentation, so that even Carnac the Magnificent in his prime would
fail to divine where the error might lie. Then he revealed (because the
whole process should be like pulling teeth--if they don't fall out
"naturally," if haphazardly, that is) he was using Raspian rather than
Debian, and I thought it was the addition of insult to injury.

Maybe 'sshd -t' would disclose some snafu in the config (a stray "-"
without an argument)?

> Cheers, Gene Heskett


-- 
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud

INQUIRY

[darkskyz666]

Hello Debian , I'm getting error while installing grub in Debian. 
The error is "unable install grub in dummy"
My intention is to dual boot debian and windows.

Please help
Thank 

Re: systemdq

[Gene Heskett]

On Saturday 28 December 2019 11:08:20 ghe wrote:

> On 12/27/19 5:02 PM, Nektarios Katakis wrote:
> > Have you tried removing openssh-server package and reinstalling it?
>
> Another hopefully good suggestion. Thanks, and I'll try it.
>
> > If you re using any version of Debian
>
> Raspian Buster.

One problem, raspian buster is armhf, debian is arm64.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: systemdq

[ghe]

On 12/27/19 5:02 PM, Nektarios Katakis wrote:

> Have you tried removing openssh-server package and reinstalling it?

Another hopefully good suggestion. Thanks, and I'll try it.

> If you re using any version of Debian 

Raspian Buster.

-- 
Glenn English

Re: systemdq

[ghe]

On 12/27/19 4:50 PM, Linux-Fan wrote:

> Have you tried commands of this sort?

Not yet, but I will in a few minutes. My problem was that the error
message was more of the "Oops" type rather than suggesting what I might
do about it.

> # systemctl enable sshd.service
> # systemctl start sshd.service
> # systemctl status sshd.service
> 
> Even if you already tried them without solving the issue, the commands'
> outputs would still be interesting.

I'll reply to the list.

-- 
Glenn English

Résolu: Résumé et tentative d'explication: Problème avec udevd

[Jean-Marc]

Sat, 28 Dec 2019 11:24:15 +0100
Bureau LxVx  écrivait :

> Bonjour à tous !

salut Sylvie,

> Je reprends l'Inspiron ce matin et
> 
> @JMarc : ça marche ! super !

Content d'avoir pu t'aider, Sylvie.

> En fait, j'avais trouvé cette soluce MAIS ...en ajoutant
> 
> 
> j'avais "oublié" l'espace qui suivait (pas tech, j'avais dit ...)

Pour quelqu'un de "pas tech", c'est impressionant !

> Donc ... merci : mon apprentissage continue par votre aide et par mes erreurs.

Avec grand plaisir !

Dernier détail : tu ne mentionnes pas si tu as copié le fichier 
97-hid2hci.rules dans le répertoire /etc/udev/rules.d/ avant de le modifier.  
Se faisant, tu évites qu'il ne soit remis dans sa version originale en cas de 
mise à jour du paquet bluez, paquet qui contient ce fichier.

Et, pour info, ce bogue fait l'objet d'un suivi dans le rapport de bogue 
suivant :
. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901965

J'y ai ajouté quelques infos en espérant relancer les maintainers en vue d'une 
solution définitive.

> Librement,
> 
> Sylvie

Bonne fin de journée.

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt


pgp5J5kjVWLk5.pgp
Description: PGP signature

problème à l'installation (était: Mise à jour en français)

[Jean-Marc]

Vendredi, 27 Dec 2019 20:09:57 +0100
G2PC  écrivait :

salut G2PC,

J'ai créé un nouveau fil de discussion puisqu'il me semble que la discussion 
s'éloigne de la demande initiale (revision de la doc et appel à volontariat).

> >> Il semble que oui, par exemple, sur une Live Debian 10.2, XFCE, si je
> >> choisi le Français à l'installation, j'aurais un clavier US qwerty lors
> >> de ma première connexion.

D'abord, j'ai lu sur le canal IRC de Debian qu'il n'est pas recommendé 
d'installer Debian à partir d'une image Live.  Malgré ceci, la doc fait bien 
référence à la possibilité de le faire (cf. [1]).  Soit.

Donc, tu dis que si tu choisis la langue française à l'install', lors de la 
1ère connexion, ton clavier est un qwerty.  Tu peux me donner quelques détails, 
histoire de reproduire ce qui semble être un bug ?
. quel clavier as-tu choisis lors de l'install' ?
. quand tu dis "connexion", tu fais référence à l'ouverture d'une session à un 
bureau ou à autre chose ?
. quel gestionnaire de session ?  (gdm, lightdm, ...)
. merci d'aussi préciser le lien vers l'image LiveCD que tu as utilisée.


> >> Ce n'est pas lié directement à la langue, mais, c'est un premier
> >> problème, par contre, la nouvelle interface que j'ai pu observer sur
> >> Debian 10.2 semble bien mieux conçue, pour passer du clavier qwerty vers
> >> azerty.

De quelle interface parles-tu ?

> Il me semble que j'ai le même comportement via une installation sans
> live CD, et, pour ma part, je considère que c'est un problème " de
> langue " du fait de l'usage par défaut d'un clavier qwerty, ce qui est
> une habitude anglophone, donc, paramétrer le clavier pour un usage
> européen, pour moi, c'est lié.

Merci de donner l'URL de l'image d'install' utilisée dans ce cas-ci également 
pour permettre à d'autres de reproduire ce problème, voire de le documenter 
dans un rapport de bogue.

Bonne journée.

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt

[1] https://www.debian.org/CD/live/


pgpPDXaCt5m4A.pgp
Description: PGP signature

Re: Persistent Desktop Environment

[Felix Miata]

Teemu Likonen composed on 2019-12-28 03:03 (UTC-0500):

> Henning Follmann wrote:

>> So is there a way to lock down firefox user interface? I want only
>> bookmarks visible and editable (add). But no accidental drags or
>> clicks to change the user interface. Is that possible?

> I don't know. With Firefox I would start by studying if the internal
> configuration options in about:config page can be edited with external
> tool. Such tool could set some values to the desired value when user's
> session starts. 
If a file named user.js exists in the profile directory, Firefox reads it and
applies its settings on every startup. Firefox never writes to user.js.

In theory, once everything is configured as desired, prefs.js could be copied to
user.js. The problem with that is that prefs.js does not include every setting,
only those that differ from defaults. So, it would take a lot of effort to
determine from about:config those settings that would need to be reset at each
startup and manually insert them into user.js.

I've never looked, but I suppose one might be able to determine all possible
defaults, and there are far more than will ever show up in prefs.js, by 
examining
source. The same examinations would need to be done for any installed extensions
as well.

Note that there is one preference that is never part of prefs.js:
the location of the profile.
That location is included in the file that inventories all existing profiles
~/.mozilla/firefox/profiles.ini.
This enables profiles to be located anywhere that is writeable by the user.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: ip / mac / arp probleem

[Paul van der Vlis]

Op 27-12-19 om 21:02 schreef mj:
> Hoi,
> 
> Tikkeltje off-topic, hopelijk stoort niemand zich eraan... anders bij
> voorbaat: excuus...
> 
> Laatst grote problemen gehad doordat onze debian router / gateway (en
> dat was de link met debian-user-dutch...) met IP adress .1 van ons
> netwerk 'gedrukt' werd door en ander device waar één of andere monteur
> óók IP .1 op gezet had.
> 
> Die twee gingen de strijd met elkaar aan om dat ip adres, met
> voortdurende, rare en onvoorspelbare resultaten. Duurde lang voordat ik
> door had wat er speelde.
> 
> De vraag: heeft iemand hier een idee hoe ik zoiets in de toekomst zou
> kunnen voorkomen?
> 
> Ik denk aan iets op onze procurve switches, bv:
> 
> - het ip adress .1 alleen toestaan op specifieke poorten
> of
> - het ip .1 alleen toestaan in combinatie met een specifiek mac adres
> 
> Iemand met tips of andere ideeen om dit te voorkomen..?

Ik heb zelf ooit zoiets gehad, toen ging het niet om .1.

Wat mij een goede oplossing lijkt is dat 1 persoon verantwoordelijk is
voor het netwerk en de IP-adressen uitdeelt. En dit ook documenteert
voor een vervanger.

Als een manager een andere techneut toelaat zonder overleg, dan lijkt
het me logisch wie hier de fout heeft gemaakt.

Groeten,
Paul


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: ip / mac / arp probleem voorkomen, ARP table bewaken

[mj]

Hoi Geert,

On 12/27/19 9:21 PM, Geert Stappers wrote:

De switch lekker op layer 2 laten en dan arpalert of arpwatch
(ik kan die twee nog steeds goed uit elkaar uithouden).


Dank, die kende ik nog niet, maar ga ik zeker ook inzetten..!

En misschien nog andere ideeën, opties die wel op de switch kunnen..?

MJ

after upgrading to buster, logwatch no longer logging proftpd messages

[John Covici]

Hi.  I have a system in the cloud and after upgrading it to buster,
logwatch is no longer logging proftpd messages.  I looked and they
seem to be in the auth.log file, doesn't logwatch search that file?
How can I get logwatch to check proftpd entries now?

Thanks in advance for any suggestions.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: Persistent Desktop Environment

[Teemu Likonen]

Henning Follmann [2019-12-27T16:17:04-05] wrote:

> Somehow my parents are still messing up their computer.

> So is there a way to lock down firefox user interface? I want only
> bookmarks visible and editable (add). But no accidental drags or
> clicks to change the user interface. Is that possible?

I don't know. With Firefox I would start by studying if the internal
configuration options in about:config page can be edited with external
tool. Such tool could set some values to the desired value when user's
session starts.

> Any advice on how to lock the Desktop Environment?

I have maintained a school computer system which had some computers with
generic user account for all users. In those computers I wanted to
restore specific default settings every time the computer is booted (or
rather, when the user desktop session starts). As the root user I made a
tar package of certain normal user's configuration files and wrote a
script in /etc/X11/Xsessions.d directory. The script would unpack the
tar file and do some other things to get the default settings.

The generic problem is that the files that keep program's configuration
are not always part of program's public configuration interface. The
file names can change, the file format can change etc. Perhaps a good
advice is that configuration should be edited only through documented
configuration interface. Sometimes configuration is in a documented text
file format. Sometimes there is a command-line tool to change
configuration (git config, notmuch config, ${program}ctl etc.).
Sometimes nothing is documented and user should only open the main
application.

You can probably restore some configuration quite easily but if you
build too complex and fragile system it will cause more maintenance work
than the original problem of restoring settings manually from time to
time.

-- 
///  OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450
//  https://keys.openpgp.org/search?q=tliko...@iki.fi
/  https://keybase.io/tlikonen  https://github.com/tlikonen


signature.asc
Description: PGP signature