Re: Small Installation Image - Installed

[Jeremy Hendricks]

You’ll have to connect to the server directly and run: sudo apt install
openssh-server

On Wed, Mar 22, 2023 at 1:26 PM Macauley Clark 
wrote:

> Hello,
>
> I hope this email finds you well, I have installed Debian 11 on my HPE
> server and have tried to access it using SSH but found that SSH isn't an
> included package, from what I read.
>
> I don't particularly want to have to install Debian 11 again because the
> binaries had to be uploaded by the Datacenter who hosts my hardware.
>
> Anything you can suggest would be appreciated.
>
> Thanks,
>

Re: Debian Jessie on AWS EC2

[Jeremy Hendricks]

Are you able to download the snapshot locally? If so and it’s not encrypted
somehow, maybe it can be mounted up somehow. Otherwise, you’re probably at
the mercy of AWS.

On Wed, Mar 22, 2023 at 11:24 AM Janne Lauros 
wrote:

> Hi!
>
>  I have a really old snapshot in EC2 that I need to make it as volume and
> mount it to copy some files from it. Unfortunately it is based on Debian
> Jessie AMI (https://aws.amazon.com/marketplace/pp/prodview-5pgbnftzmrgec)
> that cannot be subscribed to anymore thus making it impossible to mount the
> volume. Are the some known workarounds to this, perhaps a way to activate
> the subscription after shedding some tears first?
>
>  BR Janne
>

Re: Problem installing LocalWP

[Jeremy Hendricks]

I can only recommend contacting LocalWP for assistance. It is their product
and not supported by Debian.

On Thu, Mar 16, 2023 at 4:29 PM Stephen P. Molnar 
wrote:

> I am running uptodate Bullseye and have been running the-Debian version of
> LocalWP
>
> I was uninstalling an update to v-6.7.0 when the installer threw an
> error(s) wile installing my domain:[image: Screenshot]
>
> I have no idea how to fix this and would greatly appreciate help.
>
> Thanks in advance
>
>
> --
> Stephen P. Molnar, Ph.D.https://insilicochemistry.net
> (614)312-7528 (c)
> Skype:  smolnar1
>
>
>

Re: Debian installer chooses the wrong NVidia driver

[Jeremy Hendricks]

I think I know why.
https://en.m.wikipedia.org/wiki/GeForce_600_series

They made Kepler and Fermi variants of the GT 630. The nvidia driver
probably wrongly assumes it’s Kepler.

On Wed, Feb 22, 2023 at 4:01 PM Van Snyder  wrote:

> On Wed, 2023-02-22 at 15:43 -0500, Jeremy Hendricks wrote:
>
> Van, what is the specific GPU you have? I know it’s GF108 but what is the
> actual model?
>
>
> # nvidia-detect
> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108
> [GeForce GT 630] [10de:0f00] (rev a1)
>
>
> On Wed, Feb 22, 2023 at 3:33 PM Van Snyder 
> wrote:
>
> On Tue, 2023-02-21 at 23:27 +0200, Georgi Naplatanov wrote:
>
> On 2/21/23 23:16, Van Snyder wrote:
>
> On Tue, 2023-02-21 at 22:41 +0200, Georgi Naplatanov wrote:
>
> On 2/21/23 22:13, Van Snyder wrote:
>
> I have an NVidia GF108 video card. It works just fine, so I don't see a
> reason to replace it.
>
> It needs the nvidia-legacy-390xx-driver.
>
> But when I installed Debian 11, it chose the 470 driver, which doesn't
> work with GF108.
>
> Maybe that was caused by selecting "install all the drivers" instead of
> "install only the relevant drivers." I thought that meant "download them
> all in case you install some new hardware."
>
> Shouldn't the installer install only the drivers for the relevant
> hardware, even if it downloads all of them?
>
> I'm not going to re-install just to do an experiment to see if the
> installer does it right if I tell it to install only the relevant
> drivers.
>
>
>
> Hi!
>
> It seems that nvidia-legacy-390xx-driver is available in Debian 11
> (bullseye). You have just to install it. If you have problems again,
> then try to use open source driver for NVidia's cards - Nouveau. it's
> installed by default and you have just to uninstall NVidia's proprietary
> drivers - nvidia-*.
>
>
> I did install it, but it took me a week to find that that was the
> problem. I had expected Debian's installer to choose to use the correct
> driver even if all the drivers it has in its entire achive are downloaded.
>
>
>
> There is a package nvidia-detect
>
> it tells you which driver is appropriate for your NVidia's video card.
>
>
> Yeah, I used that. Why didn't the installer use it, and choose the 390
> driver instead of installing the 470 driver?
>
>
> Kind regards
> Georgi
>
>
>
>

Re: Debian installer chooses the wrong NVidia driver

[Jeremy Hendricks]

Van, what is the specific GPU you have? I know it’s GF108 but what is the
actual model?

On Wed, Feb 22, 2023 at 3:33 PM Van Snyder  wrote:

> On Tue, 2023-02-21 at 23:27 +0200, Georgi Naplatanov wrote:
>
> On 2/21/23 23:16, Van Snyder wrote:
>
> On Tue, 2023-02-21 at 22:41 +0200, Georgi Naplatanov wrote:
>
> On 2/21/23 22:13, Van Snyder wrote:
>
> I have an NVidia GF108 video card. It works just fine, so I don't see a
> reason to replace it.
>
> It needs the nvidia-legacy-390xx-driver.
>
> But when I installed Debian 11, it chose the 470 driver, which doesn't
> work with GF108.
>
> Maybe that was caused by selecting "install all the drivers" instead of
> "install only the relevant drivers." I thought that meant "download them
> all in case you install some new hardware."
>
> Shouldn't the installer install only the drivers for the relevant
> hardware, even if it downloads all of them?
>
> I'm not going to re-install just to do an experiment to see if the
> installer does it right if I tell it to install only the relevant
> drivers.
>
>
>
> Hi!
>
> It seems that nvidia-legacy-390xx-driver is available in Debian 11
> (bullseye). You have just to install it. If you have problems again,
> then try to use open source driver for NVidia's cards - Nouveau. it's
> installed by default and you have just to uninstall NVidia's proprietary
> drivers - nvidia-*.
>
>
> I did install it, but it took me a week to find that that was the
> problem. I had expected Debian's installer to choose to use the correct
> driver even if all the drivers it has in its entire achive are downloaded.
>
>
>
> There is a package nvidia-detect
>
> it tells you which driver is appropriate for your NVidia's video card.
>
>
> Yeah, I used that. Why didn't the installer use it, and choose the 390
> driver instead of installing the 470 driver?
>
>
> Kind regards
> Georgi
>
>
>

Re: Possible bug in radeon driver

[Jeremy Hendricks]

I suspect you just need firmware-linux installed if it isn’t already.
That’s if that hardware requires the Radeon firmware.

On Mon, Feb 20, 2023 at 5:48 AM Felix Miata  wrote:

> Omoikane Omake composed on 2023-02-19 21:50 (UTC+0300):
>
> > Excuse me for my broken English.
> > I don't know what exactly is cause of problem.
> > Old notebook eMachines d620 with radeon x1200, rs960m.
> > Driver works but no hardware acceleration.
> > Because of that some programs do not work properly.
> > For example, geeqie segfault, vlc crashed when opening file,
> > firefox crashing tabs etc.
> > If i disable radeon, all that programs works correctly with vesa driver
> but
> > everything is slow.
> > I dunno how to fix that. Maybe solution is simple but i am out of
> options.
>
> There are multiple radeon drivers. The two main ones are a kernel module
> for the
> radeon hardware, and a display device driver for X. The X1200 requires the
> radeon
> kernel driver, but possibly not the radeon display device driver. The
> alternative
> is to remove xserver-xorg-video-radeon, which allows the newer technology
> default
> modesetting display driver to be used instead, if it supports the X1200.
> It does
> not support my X1100, but it does my X1300.
>
> # pinxi -GSaz --vs --zl --hostname
> pinxi 3.3.25-02 (2023-02-16)
> System:
>   Host: gx28b Kernel: 6.1.0-3-686 arch: i686 bits: 32 compiler: gcc v:
> 12.2.0
> parameters: root=LABEL= ipv6.disable=1 noresume
> mitigations=auto
> consoleblank=0 vga=791 video=1440x900@60 5
>   Desktop: Trinity info: kicker wm: Twin v: 3.0 vt: 7 dm: 1: TDM 2: XDM
> Distro: Debian GNU/Linux bookworm/sid
> Graphics:
>   Device-1: AMD RV516 [Radeon X1300/X1550 Series] vendor: Dell driver:
> radeon
> v: kernel alternate: amdgpu arch: Rage-7 code: R200 process: TSMC 150nm
> built: 2001-06 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
> active: DVI-I-1,VGA-1 empty: SVIDEO-1 bus-ID: 01:00.0 chip-ID:
> 1002:7183
> class-ID: 0300
>   Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
> dri: swrast gpu: radeon display-ID: :0 screens: 1
>   Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 761x253mm (29.96x9.96")
> s-diag: 802mm (31.57")
>   Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: 
> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
> size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
> max: 1920x1200 min: 640x480
>   Monitor-2: VGA-1 pos: right model: Dell P2213 serial:  built:
> 2012
> res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
> diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
>   API: OpenGL v: 4.5 Mesa 22.3.3 renderer: llvmpipe (LLVM 15.0.6 128 bits)
> direct-render: Yes
> # pinxi -GSaz --vs --zl --hostname
> pinxi 3.3.25-02 (2023-02-16)
> System:
>   Host: gx28b Kernel: 5.10.0-21-686 arch: i686 bits: 32 compiler: gcc
> v: 10.2.1 parameters: root=LABEL= ipv6.disable=1 noresume
> mitigations=auto consoleblank=0 vga=791 video=1440x900@60 5
>   Desktop: Trinity info: kicker wm: Twin v: 3.0 vt: 7 dm: 1: TDM 2: XDM
> Distro: Debian GNU/Linux 11 (bullseye)
> Graphics:
>   Device-1: AMD RV516 [Radeon X1300/X1550 Series] vendor: Dell driver:
> radeon
> v: kernel arch: Rage-7 code: R200 process: TSMC 150nm built: 2001-06
> pcie:
> gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-1,VGA-1
> empty: SVIDEO-1 bus-ID: 01:00.0 chip-ID: 1002:7183 class-ID: 0300
>   Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting
> dri: swrast gpu: radeon display-ID: :0 screens: 1
>   Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 761x253mm (29.96x9.96")
> s-diag: 802mm (31.57")
>   Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: 
> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
> size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
> max: 1920x1200 min: 640x480
>   Monitor-2: VGA-1 pos: right model: Dell P2213 serial:  built:
> 2012
> res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
> diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
>   API: OpenGL v: 4.5 Mesa 20.3.5 renderer: llvmpipe (LLVM 11.0.1 128 bits)
> compat-v: 3.1 direct-render: Yes
> # pinxi -GSaz --vs --zl --hostname
> pinxi 3.3.25-02 (2023-02-16)
> System:
>   Host: gx320 Kernel: 6.1.0-3-amd64 arch: x86_64 bits: 64 compiler: gcc
> v: 12.2.0 parameters: ro root=LABEL= ipv6.disable=1
> net.ifnames=0
> noresume mitigations=auto consoleblank=0 vga=791 video=1440x900@60 5
>   Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
> vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux bookworm/sid
> Graphics:
>   Device-1: AMD RC410 [Radeon Xpress 200/1100] vendor: Dell driver: radeon
> v: kernel alternate: amdgpu arch: Rage-8 code: R300 process: TSMC 130nm
> built: 2002-07 ports: active: VGA-1 empty: none bus-ID: 

Re: FSF is not really free software (?)

[Jeremy Hendricks]

I’d recommend contacting FSF for FSF questions, not Debian.

On Wed, Feb 8, 2023 at 7:08 AM philip pocock 
wrote:

> "While many groups and individuals have contributed to Linux, the largest
> single contributor is still the Free Software Foundation, which created not
> only most of the tools used in Linux, but also the philosophy and the
> community that made Linux possible."
> -- https://www.debian.org/releases/buster/amd64/ch01s02.en.html
>
> Is there a link to the FSF contributions? I am told that FSF is centered
> on promoting proprietary software packages and assuring million $ salaries
> for Mozilla top execs for example. And therefore FSF is a capitalist
> utility above all.
>
> Stallman seems desperate for attention as it was Europe not the USA that
> birthed Linux into our online world. It bothers me to read praise of
> FSFwhen it is not praiseworthy unless one reveres money over all.
>
>
> --
> prof philip pocock
>
>
>

Re: Odd Wine issue with nvidia-tesla-470-driver

[Jeremy Hendricks]

Disregard. I made a mistake and found the error in my ways.

Odd Wine issue with nvidia-tesla-470-driver

[Jeremy Hendricks]

I found an odd issue on Debian Bookworm with nvidia-tesla-470-driver
installed and the i386 arch installed as a secondary arch (dpkg
--add-architecture i386). When installing wine it tries to pull in
nvidia-390 packages and breaks. Has anyone seen this before or is there a
workaround? I suspect nvidia-tesla-470-driver doesn't have as many packages
in i386 as amd64 does -or- there is a dependency in wine that doesn't
expects the normal nvidia-driver and not nvidia-tesla.

Re: PowerBook G4 OS

[Jeremy Hendricks]

I second and recommend FreeBSD. I can’t guarantee it’ll just work but I had
a Sawtooth G4 years ago and it was great until the hardware died.

On Wed, Jan 11, 2023 at 1:18 PM Stefan Monnier 
wrote:

> > No, there is no release for this architecture. The architecture's state
> is
> > "unofficial" and the only branch is unstable/sid. This branch may or may
> not
> > work. If you want to use Debian unstable/sid just replace "jessie" with
> > "sid" in /etc/apt/sources.list and do:
>
> While Sven is right to point out that upgrading directly from Debian
> 8 to Sid is rather risky, and while it's important to clarify that Sid
> can indeed be broken, I believe this ends up sounding much more
> discouraging than it should: since there is still a `powerpc` ports
> being updated, you should expect that it *does* work.
>
> I think in your place, I would start  by trying to boot your current
> installation with Sid's kernel.  If that works, then I'd make a fresh
> install using `debootstrap` into a new partition (you can then try out
> the new install using `chroot` as well as using dual-boot).  Or maybe
> I'd start by cloning your current root partition, and then try my luck
> at a plain `apt full-upgrade`: in case of problem you can simply boot
> back into your original root partition.
>
>
> Stefan
>
>

Re: why some memory are missing

[Jeremy Hendricks]

No problem. It was very common “back in my day”

On Sat, Jan 7, 2023 at 7:10 PM lsg  wrote:

>
> On 1/8/23 07:30, Jeremy Hendricks wrote:
>
> I imagine it’s a bios limitation and it cannot address the full 4GB even
> though it’s a 64bit CPU. This was common with the Intel 925/945 chipsets
> even through they supported Intel 64bit CPUs of the time.
>
>
>
>>
> Thank Jeremy Hendricks!
>
> it seems to me that someone made foolish mistake
>
> hp seems to say  it's not my fault by reminding user in reference guide
> that "The memory available may be limited by the operating system."
>

Re: why some memory are missing

[Jeremy Hendricks]

I imagine it’s a bios limitation and it cannot address the full 4GB even
though it’s a 64bit CPU. This was common with the Intel 925/945 chipsets
even through they supported Intel 64bit CPUs of the time.

On Sat, Jan 7, 2023 at 6:08 PM lsg  wrote:

> Thank Greg Wooledge!
>
> i've tried bullseye for amd64, it doesn't help
>
> memtest86+ claims it can test all memory
>
>
>

Re: I have some errors

[Jeremy Hendricks]

I cannot unfortunately. I’d check where the wp-plugins folder is on a
bitnami install. Their support might be more useful than Debian since this
isn’t an issue with Debian.

On Sun, Jan 1, 2023 at 9:44 AM Samir Bajraktarevic <
samir.bajraktare...@protonmail.com> wrote:

> Oh well can you be more specific om about how to do that? What commands to
> use? I would like to try that.
> Thx for the reply much appreciated.
> Samir B
>
>
>
> Skickat från Proton Mail mobil
>
>
>
>  Originalmeddelande 
> Den 1 jan. 2023 15:41, Jeremy Hendricks < jwh1...@gmail.com> skrev:
>
>
> Samir,
>
> It’s most likely, based on your message, that the lightsail instance it’s
> too small ram wise. I’d manually remove the plug-in from the wp-plugins
> folder and start it again.
>
> Thank you
>
> On Sun, Jan 1, 2023 at 9:39 AM Samir Bajraktarevic <
> samir.bajraktare...@protonmail.com> wrote:
>
>> Hello guys I have website on Amazon Lightsail running on Linux Debian.
>> After installing EWWW WordPress Plugin the website went down.
>> This is what I got searching through SSH:
>>
>>
>>- Failed to start LSB: bitnami init script.
>>bitnami.service loaded failed failed LSB: bitnami init script
>>
>> Subject: A start job for unit bitnami.service has failed░░ Defined-By:
>> systemd░░ Support: https://www.debian.org/support░░ ░░ A start job for
>> unit bitnami.service has finished with a failure.░░ ░░ The job identifier
>> is 587 and the job result is failed.Jan 01 11:09:22 ip-172-26-5-253
>> systemd[1]: bitnami.service: Consumed 1.850s CPU time.░░ Subject: Resources
>> consumed by unit runtime░░ Defined-By: systemd░░ Support:
>> https://www.debian.org/support░░ ░░ The unit bitnami.service completed
>> and consumed the indicated resources.
>>
>> Job for bitnami.service failed because the control process exited with
>> error code.See "systemctl status bitnami.service" and "journalctl -xe" for
>> details.
>> Is there any way to fix the problem? I put many months into content of
>> the website. I can not lose it.
>> If you have some easy intructions to follow please send.
>> Thank you in advance.
>> Samir B.
>>
>> Sent with Proton Mail <https://proton.me/> secure email.
>>
>

Re: I have some errors

[Jeremy Hendricks]

Samir,

It’s most likely, based on your message, that the lightsail instance it’s
too small ram wise. I’d manually remove the plug-in from the wp-plugins
folder and start it again.

Thank you

On Sun, Jan 1, 2023 at 9:39 AM Samir Bajraktarevic <
samir.bajraktare...@protonmail.com> wrote:

> Hello guys I have website on Amazon Lightsail running on Linux Debian.
> After installing EWWW WordPress Plugin the website went down.
> This is what I got searching through SSH:
>
>
>- Failed to start LSB: bitnami init script.
>bitnami.service loaded failed failed LSB: bitnami init script
>
> Subject: A start job for unit bitnami.service has failed░░ Defined-By:
> systemd░░ Support: https://www.debian.org/support░░ ░░ A start job for
> unit bitnami.service has finished with a failure.░░ ░░ The job identifier
> is 587 and the job result is failed.Jan 01 11:09:22 ip-172-26-5-253
> systemd[1]: bitnami.service: Consumed 1.850s CPU time.░░ Subject: Resources
> consumed by unit runtime░░ Defined-By: systemd░░ Support:
> https://www.debian.org/support░░ ░░ The unit bitnami.service completed
> and consumed the indicated resources.
>
> Job for bitnami.service failed because the control process exited with
> error code.See "systemctl status bitnami.service" and "journalctl -xe" for
> details.
> Is there any way to fix the problem? I put many months into content of the
> website. I can not lose it.
> If you have some easy intructions to follow please send.
> Thank you in advance.
> Samir B.
>
> Sent with Proton Mail  secure email.
>

Re: stopping mass surveillance

[Jeremy Hendricks]

Please provide code examples, flow chart, or a white paper.

On Wed, Dec 14, 2022 at 5:06 PM 
wrote:

> On 1/9/84 19:84, Andy Smith wrote:
> > Hello,
> > Can't comment on something you haven't elaborated upon.
> > First step, explain why your idea is better than, say, Tor.
>
> It is about solving a problem that counts as technically unsolveable.
> The idea is about making any type of traffic correlation including
> timing attacks very hard up to impossible. It also would make
> statistical analyses of routed traffic, by user behaviour caused network
> traffic routing much more catchier. If the product is available it will
> be very hard even for government agencies and people with huge amounts
> of money and access to large parts of the internet infrastructure to
> reallocate traffic back to sender or destination.
> Imagine agencies could not distinguish a difference between all of your
> users. Does it not sound interesting?
>
> This solutions needs to be developed to reclaim our fundamental rights
> technically and enforce our right to privacy. It is right before 1984
> and we need a privacy revolution, an enforcement of privacy.
>
>

Re: Independent menu system

[Jeremy Hendricks]

Maybe try running just the XFCE 4 panel

On Tue, Dec 13, 2022 at 7:09 PM  wrote:

> Folks:
>
> I prefer to run i3wm, but it has no native menu system. Like Openbox,
> GNOME, Plasma, etc. Does anyone know of a menu system/program which
> reads *.desktop files, and can supply categorized menus, but doesn't
> insist on being run under a non-i3wm desktop environment?
>
> Paul
>
> --
> Paul M. Foster
> Personal Blog: http://noferblatz.com
> Company Site: http://quillandmouse.com
> Software Projects: https://gitlab.com/paulmfoster
>
>

Re: black screen in sid

[Jeremy Hendricks]

In my experience, it’s of unheard of for Sid to break from time to time.
I’d imagine updating in a day or a few might fix it.

On Thu, Dec 1, 2022 at 8:00 PM Michael Thompson 
wrote:

> Dear Debian ~
>
> Please forgive my neglecting to use the correct format for a bug report,
> but ~ let me explain.
> I am a 60 year old home Linux tinkerer, a Linux geek. I run Mint + Mate as
> my host and virtualbox, with a dozen guests. One guest is Debian sid.
> I just ran sudo apt update; sudo apt full-upgrade and got a black screen.
> I tried booting into fallback / recovery, and I got told the X-server had
> not started.
> Tried the old kernel, same deal.
> Small frustration ~ re-install.
> Chose the aarnet.edu.au mirror (I am in Brisbane) and booted, login as
> root, adduser mike sudo.
> Edit sources. Change the two lines that mention bullseye to read sid -
> delete everything else.
> Reboot.
> Black screen.
> Try the fallback - black screen.
> Try the recovery, ask for startx - same msg.
> I THINK your problem lays with the latest revision of the Xserver.
> If you would like a screenshot of the output in the tty when X wouldn't
> start, I have a screenshot I can send you. Reply to this email.
> I hope you find this helpful. Mike
> kneedragon1...@gmail.com
>

Re: Chroot and x32

[Jeremy Hendricks]

My new project is to make a bootable live iso of Debian x32 with XFCE :) I
forgot about this port

On Tue, Nov 29, 2022 at 2:56 PM Sven Joachim  wrote:

> On 2022-11-29 11:24 -0500, Jeffrey Walton wrote:
>
> > I'm running a Debian Unstable machine. I use it for Chroots. I noticed
> > x32 is not available when I attempted to setup a chroot with
> > debootstrap:
> >
> > $ debootstrap --arch=x32 --keyring
> > /usr/share/keyrings/debian-archive-keyring.gpg \
> >   --variant=buildd --exclude=debfoster unstable debian-x32
> > http://ftp.ports.debian.org/debian-ports
> >
> > E: Unable to execute target architecture
> >
> > In the past I seem to recall I had a x32 chroot for testing. And the
> > Debian Ports page shows x32 as a work in progress. Cf.,
> > https://www.debian.org/ports/ .
> >
> > Has x32 been dropped? Or am I doing something wrong?
>
> Debian kernels disable x32 support by default for security reasons.  You
> can enable it at boot time via the "syscall.x32=y" kernel parameter.
> Here is the patch that Debian applies to the upstream kernel sources:
>
>
> https://sources.debian.org/src/linux/6.0.10-1/debian/patches/features/x86/x86-make-x32-syscall-support-conditional.patch/
>
> Cheers,
>Sven
>
>

Re: just saying

[Jeremy Hendricks]

This is my point of view also.

On Thu, Nov 24, 2022 at 5:43 PM Peter von Kaehne  wrote:

>
> >
> > Even if you have it can be very hard to find carefully constructed back
> doors.
>
> Shrug.. as opposed to installing closed source programmes where you know
> you are spied upon ? Which may of course have back doors but thanks tk
> being closed you I’ll not even learn about?
>
>
>
>
>
>
> >
> > Some code has been carefully looked at but most has not.
> >
> >>> On Thu, Nov 24, 2022 at 4:03 PM mick.crane 
> wrote:
> >>>
> >>> I love open source, more than you might think, but I have a niggling
> >>> feeling it's been infiltrated to make user control difficult.
> >>> If I was a spook it's what I'd do.
> >>> Please prove me wrong.
> >>> mick
> >>>
> >>>
> >
> > --
> > Alain Williams
> > Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer,
> IT Lecturer.
> > +44 (0) 787 668 0256  https://www.phcomp.co.uk/
> > Parliament Hill Computers Ltd. Registration Information:
> https://www.phcomp.co.uk/Contact.html
> > #include 
> >
>
>

Re: just saying

[Jeremy Hendricks]

I have no idea what you mean. It’s open source and you can analyze the code
line by line.

On Thu, Nov 24, 2022 at 4:03 PM mick.crane  wrote:

> I love open source, more than you might think, but I have a niggling
> feeling it's been infiltrated to make user control difficult.
> If I was a spook it's what I'd do.
> Please prove me wrong.
> mick
>
>

Re: Just a test

[Jeremy Hendricks]

I’m Jeremy, how are you?

On Tue, Nov 8, 2022 at 7:27 PM Amn  wrote:

> Please disregard this email.
>
>

Re: Nvidia-legacy-470xx-driver

[Jeremy Hendricks]

Thank you. It appears there is an issue with Linux 6.x. However, its been
fixed in SID per:
https://metadata.ftp-master.debian.org/changelogs//non-free/n/nvidia-graphics-drivers-tesla-470/nvidia-graphics-drivers-tesla-470_470.141.03-3_changelog

I imagine it will make it to Bookworm within a few days or else I'll just
compile my own 5.19 kernel for now

On Sat, Oct 29, 2022 at 12:03 PM Pierre Tomon  wrote:

> Le Sat, 29 Oct 2022 11:31:57 -0400,
> Jeremy Hendricks  a écrit :
>
> > Hello! Since Debian testing/bookworm has moved to the nvidia 510
> > driver, does anyone know if there will be a
> > nvidia-legacy-470xx-driver?
>
> If you need the 470 series you can install the "nvidia-tesla-470-driver"
> package.
>
>

Nvidia-legacy-470xx-driver

[Jeremy Hendricks]

Hello! Since Debian testing/bookworm has moved to the nvidia 510 driver,
does anyone know if there will be a nvidia-legacy-470xx-driver?

Re: Buster (oldstable) install image

[Jeremy Hendricks]

Hello!

Is this what you’re looking for?
https://cdimage.debian.org/cdimage/archive/

On Thu, Nov 18, 2021 at 3:35 PM Polyna-Maude Racicot-Summerside <
deb...@polynamaude.com> wrote:

> Hi,
> Where can I get a "Buster" (10) install image.
> I can only find the 11 version on Debian Server.
> Thanks
> --
> Polyna-Maude R.-Summerside
> -Be smart, Be wise, Support opensource development
>
>

Re: Privacy and defamation of character on Debian public forums

[Jeremy Hendricks]

Chuck,

I’ve been following this email thread. I’m a nobody here but: you can’t
change the past but you control the future. People make mistakes in how
things are handled. But you can avoid them in the future.

I say this as an extrovert in a senior IT position and I've been known to
be “animated” in how I handle things sometimes.

Have a good weekend.

On Sat, Sep 25, 2021 at 12:59 PM Chuck Zmudzinski 
wrote:

> On 9/25/2021 10:02 AM, Andy Smith wrote:
> > Hello,
> >
> > On Sat, Sep 25, 2021 at 09:06:34AM -0400, rhkra...@gmail.com wrote:
> >> On Friday, September 24, 2021 05:31:47 PM The Wanderer wrote:
> >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994899 -
> specifically.
> >>> the first reply (comment 10).
> > […]
> >
> >> I've read over message #5, and without being a Debian developer or a
> user of
> >> Xen, aside from being a little longer / wordier than probably
> necessary, I
> >> don't see anything so objectionable about it.
> > [ I am not a member of the Debian Xen team and haven't contributed
> > anything to this particular bug, but I have followed it all as I
> > have an interest in the team's work. ]
> >
> > It's not outrageously objectionable, it's just not a very good bug
> > report with some *slightly* objectionable elements and background.
> >
> > This whole thing is pretty mundane and has been blown out of all
> > proportion by Chuck failing to handle reasonable advice given by
> > someone trying to help in good faith.
>
> I don't doubt at all that the advice in message #10 was given
> in good faith. I thought the author of #10's decision to rudely
> refuse to collaborate with me forever by saying "Bye" in a later
> message was also an overreaction to anything wrong I might
> have done.
> > Also what would have remained
> > with a very niche audience (people interested in Debian's Xen
> > packages) has now been shown to a much wider audience as a
> > consequence of Chuck bringing this to the attention of debian-user.
> >
> > To explain a bit more of the background, you'll see that Chuck
> > referred to another bug in that bug log and a lot of other
> > discussion took place there. Some of the things that are wrong with
> > Chuck's bug are that Chuck criticised the Debian Xen team for
> > including particular patches, and made some other factually
> > incorrect statements,
>
> For example?
> > and wrote in a style as if as if the situation
> > were fully known about by the Debian Xen team while valiant users
> > like Chuck are crushed underfoot.
>
> I admit the Debian Xen Team may not have been aware
> of the situation, and besides, I was more concerned that
> the Debian Release Team did not notice that patches from
> an unstable branch of the Xen upstream source made it
> into the Debian stable release. There is what I would call
> a "Debian patch" exploit attack surface exposed here to the
> authors of malware. THAT is a serious issue. The Xen Team's
> patches in question are perfectly acceptable in unstable and
> maybe in testing, but IMO, not in stable.
> >
> > In reality, the Debian Xen team didn't have good visibility of the
> > issue and it's not yet been proven where exactly the bug lies. Even
> > if it was shown to be in a patch that the team HAD taken on
> > questionable basis, so what, we are all volunteers here, there is no
> > need to berate people for their good faith efforts,
>
> I think its an overstatement to say I "berated" anyone in the
> bug report. You, however, judge me as "damned" and as a
> "laughingstock" in your first reply to my original post. That also
> is an overstatement of anything wrong I might have done,
> don't you think?
> > we should expect
> > bug reports to just focus on finding and fixing the bug not as
> > someone's platform to deal out a blame narrative.
>
> Agreed.
> >
> > Basically it's not a big deal and could have easily been turned
> > around; I felt #10 was a fairly gentle request to focus on the facts
> > and make progress but to say the criticism was not received well
> > would be an understatement!
>
> I am truly sorry, are there second chances in the Debian Community?
> >
> > For example, one of the "strongest" statements in #10 is
> >
> >  "It's good that you filed this bug against the Debian Xen
> >  package […] way you went about it ... not so good."
> >
> > Chuck's response to that seems to have been to go about complaining
> > in multiple unrelated locations of how he has been accused of being
> > "not good". Note that he's morphed a statement of "your bug report
> > was not done in a good way" into "someone in the Debian community
> > told me I was not a good person; remove their slander or risk being
> > sued". A dramatic misrepresentation of what actually happened. The
> > rest of it is full of things like that.
>
> Are you trying to say now I am not a good person? Seems so to me.
> >
> > It could be partially understandable if #10 had simply said, "your
> > bug report sucks," which believe me, I have seen and 

Re: A bug in Vim, in Mate Terminal or in Debian 11?

[Jeremy Hendricks]

I apologize for assuming you upgraded from 9 to 11 directly (skipping 10).
It’s a common misconception that is acceptable.

On Sat, Sep 18, 2021 at 9:46 PM Dedeco Balaco 
wrote:

> I did not leap any release. I did everything correctly, step by step.
>
> The issue is not being reprodutible. I do not find a clear condition to
> make it happen. Searching about your suggestion, I found that vim has a
> few very important arguments, where 2 of them interest me a lot, to
> isolate this issue (I guess):
>
> $ vim -u NORC # does not load any RC file, global or user's
>
> $ vim -u NONE # does not load any RC file, and also no plugin
>
> More information can be found in vim man page, and inside vim:
>
> :h initialization
>
>
> Em 18/09/2021 22:27, Jeremy Hendricks escreveu:
> > Generally it’s not recommended to leap frog over releases and you should
> > upgrade in order (Ex. From 9 to 10). I suspect you might need to delete
> > some of the config files in your home directory (rename them it .bak) as
> > the version of vim, etc might be considerable different from 9 to 11 and
> > might have odd results. I’d recommend first renaming .vimrc to
> > .vimrc.bak and see if that fixes it.
> >
> > The next step might be to rename the config files for the mate-terminal
> > and test to see if it’s fixed.
> >
> > On Sat, Sep 18, 2021 at 9:15 PM Dedeco Balaco  > <mailto:dedeco.bal...@yahoo.com>> wrote:
> >
> > Hello,
> >
> > I recently upgraded my Debian 9 to Debian 11. But there are strange
> > or wrong things happening right now, that did not exist before.
> >
> > My window manager is Mate Desktop. The terminal i most use is its
> > own. And i use vim a lot, and i basically never use gvim, i prefer
> > it through a terminal window.
> >
> > Each mate-terminal window can have several tabs in it. I use this
> > feature a lot too. Each tab has its own title, which works pretty
> > fine. There are several programs that change the title shown while
> > they run.
> >
> > Vim is one of these programs. While it is running, the terminal
> > title shows the name of the file currently being edited, and the
> > number of files that was opened with it, when it was launched.
> >
> > After the upgrade, when i quit vim, the terminal title becomes
> > empty, instead of returning to the default title "Terminal".
> >
> > Why is this happening? A bug in Vim? In mate-terminal? Or in Debian
> 11?
> >
>
>

Re: A bug in Vim, in Mate Terminal or in Debian 11?

[Jeremy Hendricks]

Generally it’s not recommended to leap frog over releases and you should
upgrade in order (Ex. From 9 to 10). I suspect you might need to delete
some of the config files in your home directory (rename them it .bak) as
the version of vim, etc might be considerable different from 9 to 11 and
might have odd results. I’d recommend first renaming .vimrc to .vimrc.bak
and see if that fixes it.

The next step might be to rename the config files for the mate-terminal and
test to see if it’s fixed.

On Sat, Sep 18, 2021 at 9:15 PM Dedeco Balaco 
wrote:

> Hello,
>
> I recently upgraded my Debian 9 to Debian 11. But there are strange or
> wrong things happening right now, that did not exist before.
>
> My window manager is Mate Desktop. The terminal i most use is its own. And
> i use vim a lot, and i basically never use gvim, i prefer it through a
> terminal window.
>
> Each mate-terminal window can have several tabs in it. I use this feature
> a lot too. Each tab has its own title, which works pretty fine. There are
> several programs that change the title shown while they run.
>
> Vim is one of these programs. While it is running, the terminal title
> shows the name of the file currently being edited, and the number of files
> that was opened with it, when it was launched.
>
> After the upgrade, when i quit vim, the terminal title becomes empty,
> instead of returning to the default title "Terminal".
>
> Why is this happening? A bug in Vim? In mate-terminal? Or in Debian 11?
>

Re: why 1G memory is missing?

[Jeremy Hendricks]

Yup. That too.

On Tue, Aug 3, 2021 at 7:42 PM IL Ka  wrote:

>
>> That cpu was normally paired with the Intel 945 chipset that can’t
>> support more than about 3.25GB whether or not it’s 32/64 OS
>>
>
> Yes, and even worse: this CPU doesn't support 64bit OS
>
>> model name   : Intel(R) Atom(TM) CPU N280   @ 1.66GHz
>>> address sizes   : 32 bits physical, 32 bits virtual
>>>
>>>
> https://ark.intel.com/content/www/us/en/ark/products/41411/intel-atom-processor-n280-512k-cache-1-66-ghz-667-mhz-fsb.html
>  Instruction Set: 32-bit
>
>

Re: why 1G memory is missing?

[Jeremy Hendricks]

That cpu was normally paired with the Intel 945 chipset that can’t support
more than about 3.25GB whether or not it’s 32/64 OS

On Tue, Aug 3, 2021 at 7:24 PM  wrote:

> Thank Andy! my cpu is 32bit
> i have thought pae can support more than 4G memory
> but in fact it can't use full 4G memory hardware
>
> $ cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family: 6
> model : 28
> model name: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
> stepping  : 2
> microcode : 0x218
> cpu MHz   : 1000.000
> cache size: 512 KB
> physical id   : 0
> siblings  : 2
> core id   : 0
> cpu cores : 1
> apicid: 0
> initial apicid: 0
> fdiv_bug  : no
> f00f_bug  : no
> coma_bug  : no
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 10
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc 
> arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr 
> pdcm movbe lahf_lm dtherm
> bugs  :
> bogomips  : 3325.02
> clflush size  : 64
> cache_alignment   : 64
> address sizes : 32 bits physical, 32 bits virtual
> power management:
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family: 6
> model : 28
> model name: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
> stepping  : 2
> microcode : 0x218
> cpu MHz   : 1667.000
> cache size: 512 KB
> physical id   : 0
> siblings  : 2
> core id   : 0
> cpu cores : 1
> apicid: 1
> initial apicid: 1
> fdiv_bug  : no
> f00f_bug  : no
> coma_bug  : no
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 10
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc 
> arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr 
> pdcm movbe lahf_lm dtherm
> bugs  :
> bogomips  : 3325.02
> clflush size  : 64
> cache_alignment   : 64
> address sizes : 32 bits physical, 32 bits virtual
> power management:
>
>
>
>

Re: why 1G memory is missing?

[Jeremy Hendricks]

It’s bios/chipset dependent. Example: the Intel 945 will not allow more
than 3.25GB or so regardless if PAE is used. However, the Intel 965 chipset
will provide the full 4GB if used with PAE enabled and the BIOS allows it
by default or has a ‘remap’ option.

On Mon, Aug 2, 2021 at 7:15 PM  wrote:

> Jeremy Hendricks:
> Are you booting an x86 or x86_64 install? Run: “uname -a” without quotes
> and post the results to us.
>
>
> Linux debian 4.9.0-13-686-pae #1 SMP Debian 4.9.228-1 (2020-07-05) i686
> GNU/Linux
>
> Thanks, i thought pae can bypass 4G limit of 32-bit OS
>
>

Re: why 1G memory is missing?

[Jeremy Hendricks]

Are you booting an x86 or x86_64 install? Run: “uname -a” without quotes
and post the results to us.

On Mon, Aug 2, 2021 at 6:12 PM  wrote:

> i have 2 memory slots
> memtest86+ shows each has 2G, but total is 3G
> after booting linux, top shows total is 3G
> why 1 G is missing? Thanks!
>

Re: dns failover a record

[Jeremy Hendricks]

The feature you need to look for is GSLB. I’d Google opensource and GSLB. I
saw a few projects that should give you the functionality you need.

On Mon, Jul 12, 2021 at 8:23 AM Dan Ritter  wrote:

> Gokan Atmaca wrote:
> > I want to do dns failover. There is no such feature in the bind
> > service. It has RR feature but no Failover. I have 2 services. I want
> > the A record to change automatically when one is inaccessible. Is
> > there a tool you can recommend for this ?
>
>
>
> The most obvious way to do this is dynamic DNS updates. Set up your
> servers to send a dynamic DNS update to your DNS server when they decide
> that they are the new primary.
>
> Note that DNS TTL records are advisory, not mandatory, so it is
> unlikely that all your traffic will switch over quickly to the
> new primary. Losing connectivity for 3 minutes to 24 hours is
> for various clients is more or less expected.
>
> -dsr-
>
>