You are not logged in.
Thanks. Yes. It looks like a code bug; that the edit code picks up the topic's timestamp rather than the post's timestamp.
This might have been fixed now by my spurios replacing of a 't' with a 'p'; otherwise it'll require thought.
The timeout is a day, or 86400 seconds, since the creation of the post.
@Vernon, it shouldn't have stopped you from editing that post so I'm not sure what is happening there.
'edit' and 'delete' are treated the same based on my reasoning that editing lets you remove all content, and a blank post is basically the same as a deleted post.
Wouldn't you neeed to use xvfb to run an X server remotely without displaying on a real console?
The package dqcache comes without any init.d script so it thus needs hand crafting.
1) Edit /etc/default/dqcache by adding "export" to every variable setting. For example:
# dqcache runs chrooted in the directory specified
# by the $ROOT environment variable
#
export ROOT="/var/lib/dqcache/root"# dqcache listens for incoming UDP packets and TCP connections
....
2) Create /etc/init.d/dqcache with the following:
#!/usr/bin/env /lib/init/init-d-script
### BEGIN INIT INFO
# Provides: atd
# Required-Start: $syslog $time $remote_fs
# Required-Stop: $syslog $time $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: DNS Cacher
# Description: Debian init script to start the dbcacher daemon
### END INIT INFO
DESC="DNS cacher daemon"
DAEMON=/usr/sbin/dqcache
PIDFILE=none
NAME=dqcache
START_ARGS=--background
export UID=$(id -u $NAME)
export GID=$(id -g $NAME)
3) Finalize with usual hands-on
# update-rc.d dqcache defaults
# update-rc.d dqcache enable
# service dqcache restartThe first point of call for that would be
$ dpkg -S bin/mate-system-log@GNUser: please note that R2 is an off-the-shelf router (TL-WR841N) and it offers only an http(s) admin panel rather than shell access.
@Devuman: with forwarding set up, you should use only
ssh <PC1user>@192.168.18.8That's the whole idea of forwarding. It makes R2 to channel tcp connections on its port 22 WAN side (ie 192.168.18.8:22) onto port 22 on PC1 (ie 192.168.1.101:22) without involving itself in the traffic.
The double-hop is used when you have ssh access to an intermediate host, to use that as a temporary forwarding channel.
That looks like a bug with that package, but you might be able to side-step that bug by temporarily making /usr/bin/update-alternatives be something else... something like
# mv /usr/bin/update-alternatives /usr/bin/update-alternatives.ORIG
# ln -s /bin/true /usr/bin/update-alternativesthen remove debian-edu-artwork
and then restore:
# mv /usr/bin/update-alternatives.ORIG /usr/bin/update-alternativesIf the ISP has port 22 closed outside of R1 then you probably need to contact them to open it. But that's only to get access to PC1 from the Internet.
The R1 virtual server set up you show on the screenshot makes it possible to access port 22 on PC1 from the Internet, provided that R2 is set up similarly, and that it has that IP address 192.168.18.8 mentioned on the screenshot as its WAN side IP address.
sftp access from LT2 to PC1 only requires the R2 set up (not the R1 set up), and PC1 would then be accessed using that same IP address.
An alternative could be to declare port 22 on PC1 to be a "virtual server" on R2, the TL-WR841N router.
https://www.tp-link.com/us/user-guides/ … ub-title-7
EDIT: Note that then LT2 would access PC1 by using the IP address of R2 on LAN1 rather than the PC1 IP address on LAN2.
Might you have forgotten to do
apt-get updateas well, so as to update your local package lists?
Please note the opening of the new well of knowledge: Freedom Hacks
How i can delete this account ?!?
It's not clear to me what "delete this account" means to you, but I've now disabled access by that userid.
It was installed some years ago from a FluxBB 1.5.10 distribution, which I believe was under GPLv2, although not all files are stamped.
Great. Give me another day or two to pack up and send you the phrase tables.
Me? Idiot? Help! And I that soo admire unarticlated, aggressive one-liners!
Firstly you might test by using ctrl-alt-f1 to shift to VT-1 and log in as root. Does that result in the same experience as your su --login, i.e. blank password is fine, and then bash complains about ash?
In your post #7, it looks like your attempts with "su" fails because "ash" is not found, which suggests that "ash" is wanted to be used by the initial file(s) that are loaded at login, but is found missing. It looks odd, and maybe you should check up on that first, i.e. specifically why do you get the output:
bash: ash: Kommando nicht gefundenJust in parenthesis, regardless of your recent experiences, the program su works perfectly fine in beowulf, and it is directly brought in from debian buster. Though, it works differently from how it worked some time period ago, when its juggling of environment variables was different.
I can help with spanish too smile
haroldG75 wrote:Would like to contribute to the spanish version.
hmm I think I missed yours @haroldG75, did I? ... Let me collate the basis and email it to you both, and you coordinate who does what of it.
Thanks @berni51. I now got the German translations installed.
Hmm for me it is like:
stolpe% wmctrl -l
0x01000004 -1 stolpe xfce4-panel
0x01200003 -1 stolpe Desktop
0x03000003 -1 stolpe
0x03400010 -1 stolpe logs - ralph.ronnquist@realthing.com.au - Mozilla Thunderbird
0x030010c7 0 stolpe
0x02e00003 -1 stolpe gworldclock
0x030013d8 0 stolpe files
0x0360007f 0 stolpe desktop / workspaces / Off-topic / Dev1 Galaxy Forum - Pale Moon
0x0300341e 4 stolpe hello
0x03200003 4 stolpe Xfburn
0x03a00017 3 N/A TkDiff 4.1.4It appears the second column is the _NET_WM_DESKTOP property of the windows; "-1" means that the window is to be shown on all workspaces, and otherwise it's the workspace where the window is shown. At that time, my monitors show workspace 0.
This is not cinnamon though; it might use some other window property, or it might keep that information elsewhere. The use of _NET_WM_DESKTOP property is in the wm-spec "standard", e.g. at https://specifications.freedesktop.org/ … 6085202544
but there's no compelling reason for cinnamon to adhere to that standard.
Hmm wmctrl -l gives me a list of all windows across all workspaces, detailing window id, workspace number (with a - in some cases for some reason), host name(?), and window title.
@toru, what does cat /sys/class/backlight/acpi_video0/max_brightness say?
Presumably something less than 100, as according to your post #7, the complaint was about the value, not the writing.
If that's the case, you should try again with @Head_on_a_Stick's tee method and a number between 0 and that maximal number. Ideally half of max should result in 50% brightness.
@danista: thanks. Afaiui, that boot entry says (to grub booting)
"after using the kernel and initrd of the boot-up partition, use the file system at partition 2 as (post-pivot) root file system"
That's a different thing from boot-up using the ISO kernel and initrd on partition 2.
It might possibly work if you copy the kernel and initrd from the ISO, where they actually reside in its /boot/isolinux/ directory, to replace the ones you have under /boot on partition 1. You should do that after having otherwise set up partition 1 with a full grub boot including that menuentry to identify partition 2 as (post-pivot) root file system.
I suppose this still brings a period of confusion for the kernel upon pivoting to the root file system, as it results in shadowing the partition 1 /boot tree, but that shouldn't cause an issue unless you then try to install onto partition 1 (or partition 2, of course).
Would you mind explain what using a hd-media method means with respect to install a devuan_beowulf_3.0.0_i386-netinstall.iso ?
In my mind you either use devuan_beowulf_3.0.0_i386-netinstall.iso or that which you find under https://pkgmaster.devuan.org/devuan/dis … nt/images/. They are two different and separate approaches to use for achieving a situation where you have Devuan installed.
I can understand if one of them, or both, have problems dealing with some hardware (even though at a glance your hardware seems far from obscure) but I'm afraid I can't immediatly understand how to conflate the two installation approaches into one.
Hey, friends; no need to get defensive and personal when the OP has taken the trouble of putting their mind to articulating how their experience differed from their expectation. Be positive: the OP wants to help.