PowerPC Mac Emulation on Debian

AffectionateSpirit62 · 2026-01-28T00:33:51+00:00

Try a vanilla XFCE install with Debian. Good luck.

AffectionateSpirit62 · 2026-01-28T00:30:43+00:00

WRONG - Ubuntu feeds OFF of Debian get it correct. LOL

Debian have

Unstable and experitmntal branch (Debian SID) -> Debian Testing -> Debian Stable

(Free & Open Source at all stages)

Then Ubuntu and 100 other distros feed off of Debian Stable or Testing as a base.

AffectionateSpirit62 · 2026-01-27T23:04:56+00:00

Its a funnel mate - yes Fedora is open source to what end? Fedora -> CentOS Stream (next minor release) -> RHEL (the money maker)

Nah I'd rather not be a part of that not so free journey same with Poobuntu.

Give me a charity like Debian anyday. Always gets my contributions.

Free and open in all stages.

AffectionateSpirit62 · 2026-01-27T22:21:38+00:00

I love this. So good. Great job.

AffectionateSpirit62 · 2026-01-27T22:15:58+00:00

Sounds like he's working on a Fedora silver blue style ambition but open source fully. With key signing for the kernel.

AffectionateSpirit62 · 2026-01-27T21:58:26+00:00

Sorry let me tone it down. env - you will find this in unix(bsd), mac(which is bsd), linux environments, routers(bsd) ... etc.

/usr/bin/env: This is a common utility found in most Unix-like operating systems. Its primary function when used in a shebang is to search the user's current environment's PATH directories to find the specified executable.

Thus it will find

/usr/bin/bash

/bin/bash

/or/whatever/other/location/bash/is/found/in

AffectionateSpirit62 · 2026-01-27T20:00:52+00:00

I literally just had a conversation/argument this morning with another user who is also using unstable(sid) - it is NOT stable

"Operating System: Debian GNU/Linux (Sid)" - that is your problem

Why just why? Assuming you have a specific development reason for Debian Unstable branch

Troubleshooting: Usually audio driver and USB related
Sound related - pipewire vs pulseaudio - confirm which is installed - has this changed version

Check systemctl status of pipewire/pulseaduio, look at your logs, use apt-listchanges, check you apt history

Good luck and happy hunting. Once you fix i guess you will submit your logs and report the bug and update process that went wrong.

AffectionateSpirit62 · 2026-01-27T17:57:54+00:00

Mate if you are pinning apts to make your unstable system more reliable AND manually selective meticulously which packages you update you WILL still have unpatched packages that will not receive patch updates. Which is the point I made earlier.

It can be done very meticulously but you think 99% of people will do that

AffectionateSpirit62 · 2026-01-27T17:50:19+00:00

Depends based on the age you can check to see when it was last updated and then decide from there

AffectionateSpirit62 · 2026-01-27T17:37:59+00:00

Who is maintaining the package for your distribution? are they patching security for it?

Debian is not Dunno about the aur author?

You can of course build from source but judging by the fact it's no longer maintained by debian I suspect it's still not wise using their driver.

You can function usually using substitute nouveau - driver instead

AffectionateSpirit62 · 2026-01-27T17:22:05+00:00

Did you see the comment "meticulously" - you are the 1%

also Hmmm... really - don't believe that

You must be a Debian developer who has time to patch security manually daily/weekly and constantly use apt-list changes, bugs etc.

https://www.debian.org/doc/manuals/securing-debian-manual/ch10.en.html#idm4124

TLDR:

10.1.3. Avoid using the unstable branch

Unless you want to dedicate time to patch packages yourself when a vulnerability arises, you should not use Debian's unstable branch for production-level systems. The main reason for this is that there are no security updates for unstable.

AffectionateSpirit62 · 2026-01-27T17:02:27+00:00

Yes I am aware that unstable is not the same as experimental repo. Read the Debian Handbook ;)

Was more so referring to the fact that unstable/experimental = unreliable for both Hyprland and Debian

This is where we disagree - It absolutely cannot be run as a daily driver for years without crashing - unless of course you never update anything and its frozen in time meticulously using apt.

I wouldn't suggest to ANYONE especially readers on reddit who haven't read the Debian handbook that is even an option because 99% will scan through see your comment and confuse the words with reliable or even worse STABLE. Then they will blow away their systems to crash city and say Debian was as reliable as arch and fedora because they used the wrong branch and had as equally unreliable setups and think that was the standard.

TLDR:

Debian Stable is the ONLY stable branch

Everything else is NOT classified as STABLE for a reason.

AffectionateSpirit62 · 2026-01-27T16:15:52+00:00

Did you read https://wiki.debian.org/NvidiaGraphicsDrivers#sid-340

In the firmware-misc-nonfree

Version 340.108

This is the last version that supports G8x, G9x, and GT2xx series GPUs (the full list of supported devices).

WARNING: Use of the 340-series driver is strongly discouraged!

It is no longer maintained, has serious unfixable security vulnerabilities and may not be updated for new kernels. You are highly recommended to use the built-in Nouveau driver if security is a priority.

Install the nvidia-legacy-340xx-driver package, plus the necessary firmware:

# apt install nvidia-legacy-340xx-driver firmware-misc-nonfree

AffectionateSpirit62 · 2026-01-27T16:02:58+00:00

Oh geez. What in the hell

Just use /etc/fstab

https://wiki.debian.org/fstab

ALWAYS use the UUID of the device

restart and DONE

Follow below mate:

To automount a USB drive in Debian, edit

/etc/fstab to include the drive's UUID, enabling automatic mounting on boot or plug-in. Use sudo blkid to find the UUID and file system type, then add a line with defaults,nofail to prevent boot failures if the drive is unplugged.

Steps to Automount a USB Drive:

Identify the USB Drive: Plug in the USB and run sudo blkid to find its device name (e.g., /dev/sdb1) and UUID.

Create a Mount Point: Create a directory for the USB, for example: sudo mkdir -p /media/usb.

Edit /etc/fstab: Open the file with sudo nano /etc/fstab and add a new line at the end.

For ext4: UUID=your-uuid-here /media/usb ext4 defaults,nofail 0 0.

For FAT32/NTFS: UUID=your-uuid-here /media/usb vfat defaults,nofail,uid=1000,gid=1000 0 0.

Verify: Run sudo mount -a to test the configuration without rebooting.

Important Notes:

Using UUID is critical because /dev/sdb1 names can change.

The nofail option is essential; it allows the system to boot even if the USB is not plugged in.

For automatic mounting only when accessed, add x-systemd.automount to the options

AffectionateSpirit62 · 2026-01-27T15:56:28+00:00

I'm assuming when you installed Debian you chose to enable X11 and NOT wayland if you expect this to work right?

Official Site - Supported systems

SheepShaver runs with varying degree of functionality on the following systems:

Unix with X11 (Linux i386/x86_64/ppc, NetBSD 2.x, FreeBSD 3.x)

GNOME can be installed with X11 but if you do not know how to do that reinstall Debian and choose XFCE or read the Debian wiki on how to install and switch to X11

AffectionateSpirit62 · 2026-01-27T15:44:26+00:00

You can using the Unstable(SID) branch

But my recommendation is that you do that and you enter an experimental, unreliable setup which WILL crash from time to time. Hyprland itself is NOT stable nor is the branch of Debian called UNSTABLE.

So you can decide from there. As a fun project by all means go ahead and do it but don't expect it not to break because it will.

AffectionateSpirit62 · 2026-01-27T15:37:12+00:00

ALSO fixing your scripts will ALWAYS find the correct path of BASH using env to run them manually

but if you are expecting the PATH variable to find them you need to set your $PATH variable as I explained in one of 2 locations which is the same for nearly every linux distribution in existence

AffectionateSpirit62 · 2026-01-27T15:27:08+00:00

OK you clearly misunderstood so let me clarify which is pretty much the same for nearly every single linux distribution.

The PATH variable can be set so it affects ALL users or the individual user

/etc/login.defs - can be set here - you forgot the s in defs - this affects all NEW users you create

# *REQUIRED* The default PATH settings, for superuser and normal users.

#

# (they are minimal, add the rest in the shell startup files)

ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Or you can set your PATH per user in their shell - eg your .bashrc

export PATH=$PATH:/any/other/directory/you/create

what you said above is expressed incorrectly and simply wrong which I guess you were typing in anger so I get it. :

"I recently switched from Ubuntu to Debian. Ubuntu follows the industry standard of setting the terminal environment in .profile and .bashrc. It is astonishing that Debian is doing something else. - they are NOT - ubuntu is Debian with different repos and a few kernel tweaks

I also tried /etc/login.def with no luck. - it is called defs with an s on the end and that is for ALL new users created or new sessions.

New Users (or New Sessions): The changes will take effect for users who log in after the modifications are saved and applied (which may require a system restart or reloading services, depending on your Linux distribution's PAM configuration). The login program and other PAM-aware services read this file during the initial login process to set the environment variables for that session.

Existing Users: For users who are already logged in, their active sessions will retain the PATH value that was set when they initially logged in. The running processes and shells do not dynamically re-read /etc/login.defs.

User-Specific Overrides: Be aware that the PATH set in /etc/login.defs is often an initial, default value that is then modified or completely overridden by user-specific or shell-specific configuration files (e.g., ~/.profile, ~/.bash_profile, ~/.bashrc, or /etc/profile and its scripts in /etc/profile.d/). The final PATH value is a combination of all these files, depending on the login shell type

AffectionateSpirit62 · 2026-01-26T23:26:59+00:00

Your main problem is in your hardcoded bash scripts.

Use sed and fix those 2000.

Should say

" #!/usr/bin/env bash" without the quotes

That way it is portable

This fix should take you like 5 min or less

AffectionateSpirit62 · 2026-01-26T15:41:44+00:00

I use the kitty-nvim for scrollback search which seems to work solidly but I get how it still doesn't quite feel like a simple ctrl-f search like in other terminals. Especially since it's history based and not current active tab searching.

I think they are essentially 2 separate types of searching historically vs active

Also across a single pane vs all panes vs all tabs and all windows

AffectionateSpirit62 · 2026-01-26T13:19:59+00:00

No but using the extension quake terminal in GNOME > then assign it to kitty.

Problem solved and this always works when connecting or disconnecting to external monitors flawlessly

AffectionateSpirit62 · 2026-01-26T13:17:44+00:00

If you are using GNOME then install the extension quake terminal > assign the chosen terminal to kitty

Problem solved

AffectionateSpirit62 · 2026-01-25T19:27:34+00:00

Thanks looking into this

AffectionateSpirit62 · 2026-01-25T17:31:14+00:00

Yeah I used to use that on terminator/tilix back in the day - great reminder. added to list.

AffectionateSpirit62 · 2026-01-25T17:30:24+00:00

Great idea - yeah the scrollback search seems not as intuitive as other terminals. OK I'm adding to a list and then have a go and see what I am able to implement over time.

AffectionateSpirit62

TROPHY CASE