[DNG] Keith Smith presents on Model View Controller best practices
Hi all, The Wednesday, September 7, 2022 GoLUG online meeting will start at the SPECIAL TIME of 6pm Eastern Daylight Time rather than the usual time. It will be at https://meet.jit.si/golug. Full information is at http://golug.info . PHP expert Keith Smith will outline the way he does the MVC (Model View Controller) web application methodology. This is important because there are many contradictory definitions of MVC out there, many of which lead to difficult to maintain volleyball code and inconsistent coding. Among other things, Keith will outline the following: * Main Benefits of MVC. * Philosophy of MVC. * The meaning and function of the Model, the View and the Controller. * Are there one or several Models? Views? Controllers? Web based MVC documentation differs on this point. * Which code to put in the Model, which to put in the View, and which to put in the Controller. * Tips on how to keep track of your classes, objects and methods, in order to code quick with a minimum of debugging. * Pitfalls to be careful of while coding MVC. If you're unfamiliar with MVC, or if you've gotten a bad impression of MVC due to careless web documentation, or if you use MVC but just want to gain more ideas and techniques, or if you create web applications or if you want to start creating web applications, this presentation is for you. SteveT Steve Litt GoLUG Publicity Coordinator ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] chimaera install problem
Sorry if this has been addressed before - I did look through the posts, but couldn't see anything relevant. Also sorry if I'm missing something obvious. I'm trying to install chimaera on a virtualbox VM, using the netinstall image (devuan_chimaera_4.0.0_amd64_netinstall.iso, dated Nov 18 2021) - I've done this many times before, without a problem. This time, when I get to "configure the packet manager", it comes back with "The installer failed to access the mirror". I used wireshark to check that it's talking to the network and the server - it appears to be doing so (accessing server at 95.216.15.86). I'm wondering if it could be another effect of the recent key expiry problem. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On 1/30/22 14:01, o1bigtenor via Dng wrote: On Sun, Jan 30, 2022 at 8:14 AM Simon wrote: Joel Roth via Dng wrote: My problem is connecting via dhcp over ethernet. On IRC I was advised to try ping ff02::1%eth1 which fails to get a response, indicating IPv6 is not enabled in my client. I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, then "ifup eth1". This fails with no link-local IPv6 address for eth1 References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" will trigger the kernel to assign an IPv6 address. Since this is not happening, I'm asking the wisdom of the list VUAs how to enable IPv6 for this port. You don’t actually need DHCP to configure IPv6. snip As an aside, and not specifically in response to either of the above emails, I recommend the certification scheme run by HE at https://ipv6.he.net/certification/, and if your ISP doesn’t yet offer IPv6, then their tunnel service will provide you with good IPv6 connectivity. It’s true that there is some learning you need to do for IPv6, but this course will take you through things in steps - start with the basics and work up to the more complicated stuff. The only bit I thought was a p.i.t.a. is a stage where you have to provide ping and traceroute results to 100 different IPv6 destinations over 100 days. The hardest part if finding 100 different destinations - at the time I did it, I did some grepping of DNS server logs at work to find them ;-) Not only do I want to echo mr Joel but for mr Simon. This gives great information - - - all together AND in a fashion that I think I may even be understanding this. Please would you fashion perhaps 2 or three more messages for intermediate and maybe even extend this into more of the 'advanced' networking country. I am not needing ipv6 at present but likely this spring fiber optics are happening (finally some decent speed options) and they are in the process of moving to ipv6 likely within a year or so. I would prefer to know at least some more before I 'need' it. I think this is all great right up until you need a fixed address for something like a mail server or a web server. So far, I've found IPV6 to be unreliable. -- Curtis https://curtis.maurand.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] meta: list
declassed art via Dng wrote: > I do have an unconfigured PTR for a couple of reasons, one of those is lack > of static IP for now. I figured out quite quickly that checking reverse DNS is a waste of time - too many systems, even those run by professional network/server engineers, are just badly configured. Gregory Nowak via Dng wrote: > I have toyed more than once with the question of what would happen if > a group of us running our own mail exchanges made the choice to > reject mail from gmail.com with a 550? If a few of us did it, we might > miss mail we maybe wanted to get. If a bunch of us did it, then a > bunch of gmail users would complain to google. My guess is google's > response would be "this is a free service; if it doesn't work for you, > then don't use it.” No, I’ll tell you what Google’s response will be : “Our system is working fine, the other system is broken”. Don’t forget that this is a company that is quite happy to simply change the rules on the basis that it’s big enough that the rest of the world will adapt. Look at the history of stuff they’ve “just changed” because it suits them. Sticking with email, they were one of the first to implement SPF fully knowing that it would break most mailing lists and mail forwarders around the world - and so most mailing lists around the world had to update software & change setups to suit Google’s* new set of “how email is to work” rules. I know, I had a customer facing mail server** and mailing list server. * OK, they weren’t the only ones, but they were one of the first. In the network world, Android devices don’t work on managed networks using DHCPv6 for address assignment. For idealogical reasons, they don’t support DHCPv6 and even actively block third party support (by pressuring chipset manufacturers to block the packets in the hardware). I could be flippant and suggest it’s because they see it as their job to snoop on people and using DHCP allows network admins to do that, but it’s mostly because they are interested only in mobile applications and refuse to consider the needs of any other environment (even where it’s a legal requirement). In the web world they are pushing for “SSL or it doesn’t exist” despite the fact that it does actually cost money** to add SSL and there are situations (such as supporting older hardware) where there is no SSL and never will be. And of course, there’s the shenanigans with QUIK and DoH ... So basically, Google’s attitude is that if some other system doesn’t work with their offering - then it’s the other system that’s broken. And they are big enough that they can get away with that, especially when they are able to tell users who complain that that’s the case. ** When SPF started getting applied, clients started seeing problems. Ideally we’d have them set up an account in their mail client to get mail from our server using IMAP, but many customers would refuse to do that - “I want my mail in my inbox”. Trying to explain why that’s not a good idea is an exercise in futility. So once their ISP is checking SFP, they no longer get any emails from sources setting SPF - and it’s our fault that the client insists on doing the broken way. Instead, they’d say it’s because out mail server is faulty - because that’s what their ISP (usually using an ISP mail account) told them and apparently the hell desks at the big ISPs are more honest that a small IT services company where they can be on first name terms with the staff. Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Invalid signatures on testing
Thanks, it worked. Sorry for not noticing the solution passing through. Il 05/09/22 14:42, Antony Stone ha scritto: On Monday 05 September 2022 at 13:35:00, Antonio Rendina via Dng wrote: Hi, I get invalid signatures from testing version. Should I just wait that they get updated or is there something that I should do to update it? See https://lists.dyne.org/lurker/message/20220903.172703.1050aabb.en.html and https://lists.dyne.org/lurker/message/20220903.173401.2043605d.en.html Antony. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Invalid signatures on testing
On Monday 05 September 2022 at 13:35:00, Antonio Rendina via Dng wrote: > Hi, > I get invalid signatures from testing version. Should I just wait that > they get updated or is there something that I should do to update it? See https://lists.dyne.org/lurker/message/20220903.172703.1050aabb.en.html and https://lists.dyne.org/lurker/message/20220903.173401.2043605d.en.html Antony. -- "Linux is going to be part of the future. It's going to be like Unix was." - Peter Moore, Asia-Pacific general manager, Microsoft Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Invalid signatures on testing
Hi, I get invalid signatures from testing version. Should I just wait that they get updated or is there something that I should do to update it? Here the error: $ sudo apt-get update Hit:1 https://packages.microsoft.com/repos/ms-teams stable InRelease Hit:2 http://download.virtualbox.org/virtualbox/debian bullseye InRelease Hit:3 https://download.docker.com/linux/debian bullseye InRelease Hit:4 https://apt.releases.hashicorp.com bullseye InRelease Get:5 http://deb.devuan.org/merged testing InRelease [33.4 kB] Err:5 http://deb.devuan.org/merged testing InRelease The following signatures were invalid: EXPKEYSIG BB23C00C61FC752C Devuan Repository (Amprolla3 on Nemesis) Fetched 33.4 kB in 2s (20.9 kB/s) Reading package lists... Done W: http://download.virtualbox.org/virtualbox/debian/dists/bullseye/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: https://apt.releases.hashicorp.com/dists/bullseye/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.devuan.org/merged testing InRelease: The following signatures were invalid: EXPKEYSIG BB23C00C61FC752C Devuan Repository (Amprolla3 on Nemesis) W: Failed to fetch http://deb.devuan.org/merged/dists/testing/InRelease The following signatures were invalid: EXPKEYSIG BB23C00C61FC752C Devuan Repository (Amprolla3 on Nemesis) W: Some index files failed to download. They have been ignored, or old ones used instead. Thanks --- Antonio ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Key is expired
Ludovic, thanks for that. Confirmed that the new key seems to work, and upgrade now in process. One point which I'm sure is obvious, but just thought I'd mention it: "dpkg " => "dpkg -i " On Sat, 2022-09-03 at 19:27 +0200, Ludovic Bellière via Dng wrote: > Hello list, > > In order to resolve the gpg key being outdated, the following steps > needs to be taken: > > wget > http://deb.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2022.09.04_all.deb > sudo dpkg devuan-keyring_2022.09.04_all.deb > sudo apt update > > Cheers, > Ludovic > > > On Sat, 03 Sep 2022, Elimar Riesebieter wrote: > > > > > Hi all, > > > > the signing key 'Devuan Repository (Amprolla3 on Nemesis)' is > > expired: > > > > W: GPG error: http://deb.devuan.org/merged stable InRelease: The > > following signatures were invalid: EXPKEYSIG BB23C00C61FC752C > > Devuan Repository (Amprolla3 on Nemesis) > > > > Elimar > > -- > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Not installing files to /boot Debian discussion
Hi! Not installing files to /boot https://lists.debian.org/debian-kernel/2022/09/msg00062.html I hope this will be rejected by Debian community. EFI has a partition already, why then use FAT filesystem for /boot is beyond me. Especially as EFI should be replaced by something sane anyway. Ciao, -- Martin ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
