Archive for the ‘Linux’ Category
Posted by jpluimers on 2018/12/13
For my link archive:
Non-stable repos:
–jeroen
Posted in *nix, Linux, Monitoring, Nagios, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2018/12/05
A (long!) while ago, I wrote about list date with seconds from ls command – Dev Shed that showed how to list the full ISO timestamp (including seconds) of files.
This is an update.
The previous post showed that you could use this statement to list all files with their full ISO timestamps (and therefore get both the seconds and milliseconds) on (open)SuSE Linux, Mac OS X and Cygwin:
ls -l --time-style=full-iso
What Linux and displaying dates in ISO 8601 format… : Little Green Delusions proposes are two solutions to make this more permanent:
alias ls='ls -l --time-style=long-iso'
or edit one of your profile files (he prefers /etc/profile.local, but that is system wide, so I usually prefer ~/.bash_profile) to add this line:
export TIME_STYLE=long-iso
The thing is: I do not always want to have ls -l show ISO 8601 dates. I like the way that ls-l lists timestamps for very old or future files: Read the rest of this entry »
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2018/11/30
From a long time ago:
[WayBack] how can I free up space on /boot as “openSUSE-2014-462” fails to install on openSUSE 12.3 (x86_64):
Installation of kernel-desktop-3.7.10-1.40.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: installing package kernel-desktop-3.7.10-1.40.1.x86_64 needs 16MB on the /boot filesystem
Based on that thread, I figured out the steps:
Read the rest of this entry »
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2018/11/22
One occasion I had SSH throw a Connection Reset by Peer on my when was the SD-card of a Raspberry Pi started failing and the ext4 filesystem got mounted in read-only mode.
Then sshd was still listening on port 22, but since it could not write to disk any more, it threw a Connection Reset by Peer to the client.
It was on OpenSuSE Tumbleweed, but would failed just as well using Raspbian.
Lessons learned:
- IoT hardware will fail.
ext4 breaks when the hardware breaks.
–jeroen
Reference:
Posted in *nix, *nix-tools, Debian, Development, Hardware Development, IoT Internet of Things, Linux, Network-and-equipment, openSuSE, Power User, Raspberry Pi, Raspbian, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2018/10/11
Hopefully I get this to work after fixing
The first part of the fix was to
- re-image the SD card.
- boot
- wait 5 minutes (there is no output on HDMI apart from some flickering and no output on TTY using 115200 bits/second despite trying [WayBack] en:c1_hardware_uart [ODROID Wiki])
The second part is getting the USB web cameras to work.
I’ve got two types, but the label on them doesn’t list their common name, only their P/N sometimes with M/N:
- P/N 860-000049 M/N V-UBC40 (really old USB cameras)
- P/N 860-000334 (new USB camera)
The MotionEyeOS web interface didn’t list any working cameras so I had to do some digging.
Luckily [WayBack] Webcam software and driver support for Windows has a table of part and model numbers combined with product names, so they got revealed them as these:
- P/N 860-000334 = M/N V-U0028 with name HD Pro Webcam C920
- P/N 861225 = M/N V-UBC40 with name Quick Cam Messenger
(which is funny as the P/N on the label is different)
Both are supported by motion according to [WayBack] Logitech < Motion < Foswiki though the Quick Cam Messenger needs [WayBack] Quickcam Messenger & Communicate driver for Linux which I should try to cross-compile one day.
The latter works fine. Below are some settings I used.
Read the rest of this entry »
Posted in *nix, Development, Hardware Development, Linux, Odroid, Power User | Leave a Comment »
Posted by jpluimers on 2018/09/28
A while ago, I documented some links for In case I ever need to record calls on my Fritz!Box devices.
By now, I’ve done a bit more investigation: I’ve enabled the call monitor, did some port scans, installed domoticz and got deeper into fritzcap.
Oh and I got packet capturing to work too: Fritz!Box – capture network packets in Wireshark format or ISDN in dtrace format.
A small recap so I don’t forget what I did and what the effects were.
Enabling CallMonitor
[WayBack] Fritzbox – Domoticz showed how to enable the CallMonitor option in your Fritz!Box
- Dial
#96*5* to enable (response “CallMonitor On”)
- Dial
#96*4* to disable (response “CallMonitor Off”)
- It seems not possible to ask for the current state (enabled/disabled)
- After it is enabled, the TCP port 1012 on your Fritz!Box is available for tools like [WayBack] Domoticz and
fritzcap.
Read the rest of this entry »
Posted in *nix, Fritz!, Fritz!Box, Internet, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2018/09/15
Not sure in which changeset this happened, but here is one example:
- old DHCP client ID
1:b8:27:eb:1a:b1:ec
- new DHCP client ID
ff:eb:78:a9:4:0:1:0:1:22:6:67:49:b8:27:eb:78:a9:4
The first one was marked static in the DHCP server, which means the Raspberry Pi now did get a different IP address.
This messes up a few places that cannot do proper address resolution.
Anyone who knows where this has changed / is configured?
These did not help finding the cause:
Edit
As commented by Leen below, this is about
Wicked changed its defaults to use this DHCPv6 compatible RFC4361 client-id in favour of the older RFC2132 client-id. However, this has caused some issues with older DHCPv4 servers and existing setups where the client-id stored by the server is used to assign a (static) address. It is recommended to fix this server-side, but still, wicked provides several ways of addressing this issue
So here are some links:
–jeroen
Posted in *nix, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, SuSE Linux, Tumbleweed | 6 Comments »
Posted by jpluimers on 2018/09/07
Too bad most of them are very picky to the Linux distributions they run on.
–jeroen
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2018/08/24
This tutorial explains how to find out network bandwidth usage per process in real time using nethogs tool under Linux operating systems.
Cool tool!
Source: [WayBack] Linux: See Bandwidth Usage Per Process With Nethogs Tool – nixCraft
An alternative is iftop – Wikipedia.
via:
–jeroen
Posted in *nix, *nix-tools, Linux, openSuSE, Power User, RedHat, SuSE Linux, Tumbleweed | Leave a Comment »
The Wiert Corner - irregular stream of stuff 