Re: raw1394 Kernel modul
On Wed, Dec 20, 2023 at 12:23:56PM +0100, Jan van Hulzen wrote: > Bitte teilen Sie mir mit, wie ich das raw1394 Kernel Modul aktivieren kann. > Damit ich meine dv Kamera über das Kino Programm benutzen kann. Als > Betriebssystem benutze ich Ubuntu. Hallo Jan, this kernel module has not existed in a very long time: https://www.kernel.org/doc/Documentation/ABI/removed/raw1394 That file suggests the libraw1394 library may be able to help. Try: apt-cache search libraw1394 sudo apt install libraw1394-11 # or whatever version number was returned You might also need to install libraw1394-dev and rebuild your application. Good luck. Thanks signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Choice of the openssl version for 23.10 and 24.04
On Mon, Dec 04, 2023 at 10:28:02AM +0100, Adrien Nader wrote: > We talked about creating a new "openssl" package that is whatever the > most recent version is (in universe, and probably with no ESM-guarantee Would this hypothetical package be strictly upstream OpenSSL, or would we make it match our Opinionated View on OpenSSL? (Or, another way: Would it support ancient protocols like SSLv2 so that scanner tools could use it?) Or, another another way: What problem is this going to solve? Thanks signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Proposal: Let's drop i386
On Thu, May 10, 2018 at 11:05:09PM -0700, Steve Langasek wrote: > I do believe that the real question before us is that of dropping the > architectures from the archive. > > However, please note that as of 18.04, i386 and armhf are still supported > architectures by Canonical for Ubuntu Core. While there is as yet no I believe deleting i386 and armhf before 18.10 is the politest thing to do: - supporting these architectures in 2025 doesn't sound plausible - thus supporting them in 20.04 LTS doesn't sound plausible - thus we should not encourage our users to accidentally migrate off 18.04 LTS to 18.10, 19.04, or 19.10. *Maybe* if we modify do-release-ugprade to ask users to confirm typing "I know what I'm doing" it wouldn't be so bad to support both arches through 19.10. But 20.04 LTS ought not include these architectures and I don't want to strand anyone away from an LTS release. Thanks signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Installation Media and supportability of i386 in 18.04 LTS Re: Ubuntu Desktop on i386
On Tue, Jun 28, 2016 at 02:54:13PM +0100, Dimitri John Ledkov wrote: > Let me resurrect this thread. In the context of what we should be > doing in 18.04 and what to do between now and then. Thanks for raising this again; it'd be nice to have a plan in place before we wind up in a difficult situation. > Here is an example draft plan to bikeshed over: > > 16.10, 17.04, 17.10: > * continue to provide i386 port to run legacy applications on amd64 > * continue to build i386 d-i / netboot installer > * continue to build i386 kernel > * continue to build i386 cloud-images > * stop producing i386 ubuntu-desktop.iso > * stop producing i386 ubuntu-server.iso Note that at some point, we may need to stop supporting specific packages on 32 bit systems. Some of our larger packages require modifications to compile and link on 32 bit platforms and we're probably going to see one or more of Firefox, Thunderbird, Chromium browser, Libreoffice, etc., no longer buildable on small-memory platforms. We may need to abandon upstream packages along the way. (And some of these huge packages are not practical for us to backport security fixes.) (See also, precise's chromium-browser.) > 18.04 LTS: > * continue to provide i386 port to run legacy applications on amd64 > * stop producing i386 d-i / netboot installer > * stop producing i386 kernel > * stop producing i386 cloud-images > * stop producing i386 ubuntu-desktop.iso > * stop producing i386 ubuntu-server.iso > > 18.10+: > * Stop providing i386 port > * Run legacy i386 only application in snaps / containers / virtual machines I'm afraid this proposal may strand some current i386 users on a release with no lifetime to it. 16.04's 32 bit support has a five-year lifespan. We may not be able to support the whole thing for the full five years but it should mostly work. But if we release 16.10, 17.04, 17.10 i386, we're basically encouraging users to install them and upgrade them and then find out in mid-2018 that they've reached the end of their OS life and no way back to the safety of 16.04 LTS. I propose that 16.04 LTS should be the last release with i386 support. That way we don't leave anyone with a choice of (a) keep running known-insecure 17.10 in 2018 or (b) figure out how to do a downgrade back to 16.04 LTS. I'm not sure how we acheive this specific goal but I think we shouldn't encourage i386 (or armhf?) users off of 16.04 LTS. Thanks signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
