You are not logged in.
Nope. Just ask a friendly administrator to work their magic. Bribes are not necessary.
Whilst I agree on the idea that strong contrast is better, a glance at the forum style usage rather shows that most people (88%) find the default anywhere on the scale from pleasant to sufficiently acceptable, to not bother to change.
From a quick glance at the source, it looks like both of them essentially are timestamps. The first one is used for deciding about requiring re-login, and the second is for aging a "visit".
I believe the email sending includes an amount of temporal reasoning, which avoids sending emails for posts that are older than your most recent log in. In other words, to gain an email, you must happen to be logged out when a post is made to a thread or forum that you subscribe to, and still remain logged out when some time later the mailer wakes up to consider sending you an email about it.
If you select "edit project" in the "settings" pull-down menu on the project web gui page, you should be able to view the detailed permission settings.
Maybe there's something wrong there?
It seems that in February last year, there was a bug report for ifupdown on Ubuntu's "launchpad", with discussion and fix to something that sounds like your particular problem. One way to verify would be if you can find the same error line
ifup: recursion detected for parent interface wlan0 in post-up phase
in /var/log/syslog, and if so, you should make a bug report to Devuan's BTS.
You might also want to compare the versions of ifupdown and wpasupplicant on your two systems; especially if they are respectively the same, it would talk against having that problem.
We have now added 'Italiano' as another of the dev1galaxy display languages. A huge thank you, (and by google translate: 'merci', 'grazie' and 'dziękuję ci') to the contributors for these.
I'm still struggling with Swedish myself, and we look forward to more people stepping up for more languages.
The task is a plain translation task. You don't need to program or know how to program; you only need an average amount of language skill to map a spreadsheet with a number of English phrases and words into the corresponding expressions in your language. Could it be easier? As I mentioned above, some languages are almost complete and only need some few hundred translations, while "new" languages will require the full 1510 translations.
Step forward now, and get Your language installed even before Swedish!
Let's see if I can help.
1) I always chose auto.mirror.devuan.org which I believe resolves into something good. Did you use that as well, and had problems (even with a working network)?
2) It may depend on the "tasksel" choices. To be sure, you should stop at the grub installation dialog, and type ctrl-alt-f2 to gain command line access on vt2. At that point you can install e.g. either wicd-curses (for use without desktop environment), or wicd (otherwise). The command sequence would be as follows:
# chroot /target /bin/bash
# apt-get install wicd-curses
# exit
Thereafter you go back to the grub installation dialog with ctrl-alt-f5 (if you were doing "Graphical install"), or ctrl-alt-f1 (if you where doing just "Install"), and continue from there.
Great. The answer is "Yes and No". With start-point in those packages, I've prepared spreadsheets containing the "problem case" for this forum, which simply are the phrases (seemingly) without translation; one row for each phrase, associating it with the internal key and the English phrase.
For Italian, it's merely 135 "problem" cases, as all email templates are translated.
I was thinking it would be easiest for an author to work in a "problem" spreadsheet, and then send it back to for mapping into the required format. (Note that this forum has a couple of phrases more than the originating fluxbb).
I'll talk to golinux to get the spreadsheet sent to you.
Flerspråkighet för dev1galaxy! Hurra!
Technically it is easily done. This software is well prepared for the notion; its just a matter of installing a "language pack" that provides the localized translations for the ~1500 words and phrases, and the ~20 email templates used by the forum.
But alas, the language packs available at fluxbb resources are not many (30), and they all suffer some flaws that stops us from installing them. Many of the packs are almost finished, and would only require a couple of hours from a translator to map some (<300) missing words and phrases. A few packs (like the Swedish pack) are lacking significantly, and might need even some few days of translation effort before they can be used.
The "easy ones" are named: Arabic, Basque, Brazilian_Portuguese, Dutch, Finnish, French, German, Greek, Hebrew, Italian, Japanese, Korean, Kurdish, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Simplified_Chinese, Spanish, Traditional_Chinese, Turkish, and Ukrainian. The more involved ones are named: Catalan, Czech, Danish, Icelandic, Persian, and Swedish.
I'm presently doing Swedish, which is one of my languages. We need authors for all other languages; any one of those mentioned, or any language not mentioned that you wish for the forum. Please contact golinux who will synchronize this effort, and tell her which language you will do. She will then send you a translation spreadsheet for the needed translations.
Note that we do expect posts to be in English. This localization primarily applies to the forum display, as it is unlikely to induce much new language knowledge to people posting here.
There is openjdk-8-jre in jessie-backports.
Thanks.
The forum software was indeed sprinkled throughout with that unnecessary constraint on the referrer attribute. This has now been corrected, and it should be possible for you to post and update your profile, with or without a referrer attribute.
Could you tell which thread this concerns?
When you say "something not working well", I assume you are getting some error message or something from the command. Perhaps you could share that with us?
"Works for me" [tm]
I copied your command and tried it: 197M and no errors, 399M when unpacked and configured.
Sorry. I think I don't understand the "ip" man page; and maybe it is that the peer address must be given at the same time as configuring it's own address.
Anyhow, maybe use "ipconfig" instead:
# ifconfig tun0 dstaddr 10.3.0.1
That should accomplish the same thing.
I'm not sure how the tun0 interface is created, but the problem here is that its "remote address" is not configured correctly. The interface correctly should have 10.3.0.42 as its own address, but it should have 10.3.0.1 as its PtP address. To do this manually I think you'd do
ip link set tun0 peer 10.3.0.1
But I would have thought that openvpn would do so itself via its configuration. I'm not using openvpn myself so I don't know exactly, but its configuration should declare that 10.3.0.1 is "its" IP address, whereas 10.3.0.42 is the client's IP address (or one of them, depending on how it assigns those).
Ah. the tun interface is not configured correctly. Its P-t-P address should be 10.3.0.1.
The problem is to determine why. And how come it works on the 32bit host (does it get configured correctly)?
Maybe I misunderstood the set up, because there's no trace of using openvpn there? And there's also nothing stopping network traffic, but rather a quite normal, working set up.
Did you really start openvpn before capturing all that?
Ok. Details, please. When you've started openvpn (not working), include the following:
the routing table
# ip route list all
iptables rules
# iptables-save
DNS configuration
# cat /etc/resolv.conf
the result of
# cat /proc/sys/net/ipv4/ip_forward
and interfaces
# ifconfig -a
.
One or some of those should probably tell what the problem might be.
With a simple command like
dpkg -l | awk '$1=="ii" {print $2}' | xargs -rn1 -I+ sh -c "dpkg -L + | grep --label=+ -Hw systemd" > systemd-references.txt
you'll get a listing of how all installed packages have paths with the word "systemd" in their name.
On my laptop (Devuan beta fully upgraded), I find "systemd" mentioned by 29 packages in a total of 148 times, of which 90 are plain files (the other are directory paths). Specifically:
acpid:/lib/systemd/system/acpid.socket
acpid:/lib/systemd/system/acpid.path
acpid:/lib/systemd/system/acpid.service
alsa-utils:/lib/systemd/system/alsa-state.service
alsa-utils:/lib/systemd/system/alsa-store.service
alsa-utils:/lib/systemd/system/alsa-restore.service
alsa-utils:/lib/systemd/system/basic.target.wants/alsa-state.service
alsa-utils:/lib/systemd/system/basic.target.wants/alsa-restore.service
alsa-utils:/lib/systemd/system/alsa-utils.service
alsa-utils:/lib/systemd/system/shutdown.target.wants/alsa-store.service
anacron:/lib/systemd/system/anacron.service
anacron:/lib/systemd/system/anacron-resume.service
at:/lib/systemd/system/atd.service
augeas-lenses:/usr/share/augeas/lenses/dist/tests/test_systemd.aug
augeas-lenses:/usr/share/augeas/lenses/dist/systemd.aug
binfmt-support:/lib/systemd/system/binfmt-support.service
consolekit:/lib/systemd/system/console-kit-log-system-restart.service
consolekit:/lib/systemd/system/console-kit-log-system-stop.service
consolekit:/lib/systemd/system/console-kit-log-system-start.service
consolekit:/lib/systemd/system/console-kit-daemon.service
consolekit:/lib/systemd/system/reboot.target.wants/console-kit-log-system-restart.service
consolekit:/lib/systemd/system/poweroff.target.wants/console-kit-log-system-stop.service
consolekit:/lib/systemd/system/halt.target.wants/console-kit-log-system-stop.service
consolekit:/lib/systemd/system/basic.target.wants/console-kit-log-system-start.service
cron:/lib/systemd/system/cron.service
devuan-baseconf:/etc/apt/preferences.d/avoid-systemd
dmeventd:/lib/systemd/system/dm-event.socket
dmeventd:/lib/systemd/system/dm-event.service
dnsmasq:/lib/systemd/system/dnsmasq.service
ifupdown:/lib/systemd/system/networking.service
ifupdown:/lib/systemd/system/ifup@.service
init-system-helpers:/usr/share/man/man1/deb-systemd-helper.1p.gz
init-system-helpers:/usr/share/man/man1/deb-systemd-invoke.1p.gz
init-system-helpers:/usr/bin/deb-systemd-invoke
init-system-helpers:/usr/bin/deb-systemd-helper
libsystemd0:amd64:/usr/share/doc/libsystemd0
libsystemd0:amd64:/usr/share/doc/libsystemd0/changelog.Debian.gz
libsystemd0:amd64:/usr/share/doc/libsystemd0/copyright
libsystemd0:amd64:/lib/x86_64-linux-gnu/libsystemd.so.0.15.0
libsystemd0:amd64:/lib/x86_64-linux-gnu/libsystemd.so.0
libsystemd0:i386:/lib/i386-linux-gnu/libsystemd.so.0.15.0
libsystemd0:i386:/usr/share/doc/libsystemd0
libsystemd0:i386:/usr/share/doc/libsystemd0/changelog.Debian.gz
libsystemd0:i386:/usr/share/doc/libsystemd0/copyright
libsystemd0:i386:/lib/i386-linux-gnu/libsystemd.so.0
lintian:/usr/share/lintian/checks/systemd.desc
lintian:/usr/share/lintian/checks/systemd.pm
lm-sensors:/lib/systemd/system/lm-sensors.service
lvm2:/lib/systemd/system/lvm2-pvscan@.service
lvm2:/lib/systemd/system/lvm2-monitor.service
lvm2:/lib/systemd/system/lvm2-lvmetad.socket
lvm2:/lib/systemd/system/lvm2-lvmetad.service
lvm2:/lib/systemd/system/lvm2-activation.service
lvm2:/lib/systemd/system/lvm2-activation-early.service
lvm2:/lib/systemd/system/lvm2.service
openssh-server:/lib/systemd/system/ssh.service
openssh-server:/lib/systemd/system/ssh.socket
openssh-server:/lib/systemd/system/ssh@.service
pulseaudio:/usr/lib/systemd/user/pulseaudio.socket
pulseaudio:/usr/lib/systemd/user/pulseaudio.service
pulseaudio:/usr/lib/pulse-7.1/modules/module-systemd-login.so
rsync:/lib/systemd/system/rsync.service
screen:/lib/systemd/system/screen-cleanup.service
slim:/lib/systemd/system/slim.service
sudo:/lib/systemd/system/sudo.service
system-config-printer-udev:/lib/systemd/system/configure-printer@.service
udev:/usr/share/man/man8/systemd-udevd.service.8.gz
udev:/usr/share/man/man8/systemd-hwdb.8.gz
udev:/bin/systemd-hwdb
udev:/lib/systemd/systemd-udevd
udev:/lib/systemd/system/systemd-hwdb-update.service
udev:/lib/systemd/system/systemd-udevd.service
udev:/lib/systemd/system/systemd-udevd-kernel.socket
udev:/lib/systemd/system/systemd-udevd-control.socket
udev:/lib/systemd/system/systemd-udev-trigger.service
udev:/lib/systemd/system/systemd-udev-settle.service
udev:/lib/systemd/network/99-default.link
udev:/usr/share/man/man8/systemd-udevd-control.socket.8.gz
udev:/usr/share/man/man8/systemd-udevd.8.gz
udev:/usr/share/man/man8/systemd-udevd-kernel.socket.8.gz
udev:/lib/systemd/system/udev.service
udev:/lib/systemd/system/sysinit.target.wants/systemd-hwdb-update.service
udev:/lib/systemd/system/sysinit.target.wants/systemd-udevd.service
udev:/lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service
udev:/lib/systemd/system/sockets.target.wants/systemd-udevd-kernel.socket
udev:/lib/systemd/system/sockets.target.wants/systemd-udevd-control.socket
usb-modeswitch:/lib/systemd/system/usb_modeswitch@.service
wpasupplicant:/lib/systemd/system/wpa_supplicant.service
xserver-xorg-input-wacom:/lib/systemd/system/wacom-inputattach@.service
zsh-common:/usr/share/zsh/functions/Completion/Unix/_systemd
dev1galaxy only uses BBCode, which you can find documented following the BBCode link below the Quick reply box, where it says "BBCode: on". The "BBCode" text is a link, to
https://dev1galaxy.org/help.php#bbcode which documents the extent of available markup.
Also, there is a Profile tick box in the "privacy" section for opting-in on getting subscribed to your topics. It might be possible to have that as default, and rather "force" people to to opt-out instead.
Maybe I misunderstood; my
devuan_jessie_1.0.0-beta2_amd64_CD.iso (from files.devuan.org)
includes /pool/DEBIAN/main/w/wpa/wpasupplicant_2.3-1+deb8u4_amd64.deb
The newest addition to the dev1galaxy.org forum intends to make git.devuan.org (gdo) more directly accessible and understandable to Devuan users as well as to (hopefully) help solve outstanding project issues posted at gdo.
Every project and issue at gdo can now be found on dev1galaxy via the two special "Projects" and "Issues" forums in the new "git.devuan.org" section.
The Projects forum (https://dev1galaxy.org/viewforum.php?id=18) organizes Devuan projects into two categories - "devuan-packages / infrastructure" and "other projects". Both categories are presented as alphabetical and activity ordered lists. The project lists offer a short description (if available) and a convenient, single-click access to all projects at git.devuan.org.
The Issues forum (https://dev1galaxy.org/viewforum.php?id=19) holds threads that are automagically created by dev1galaxy's trusty "gdolink" bot, from all open issues at git.devuan.org. The bot will add newly opened issues (if any) to the Issue lists, every 30 minutes. Posting these issues on d1g will give greater exposure to issues that are currently buried in the gdo 'cave' (which is perceived as inaccessible by some). Opening parallel forum threads provides opportunity for discussion and collaborative problem solving that will accelerate Devuan's progress and usability.
Note that the posts in these issue threads are distinct from the comment discussion on gdo. However, when a post suggests a solution to an issue, or has information to advance it, a project team member will be able to capture the post as an original issue comment at gdo.
Finally, the "gdo Help Desk" is the place to ask questions about gdo and to post tips that will help familiarize users with how gdo works.
I saw on IRC that you've done many things trying to get it to work.
What does dmesg say now?