Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Replaced, substituted

Name: Anonymous 2024-06-08 23:14

No better word for this
You are too fucking retarded
Disgusting
Self centered

Ultimately

It was right, it does not know a thing about you.
And whatever kept you for so long, and you are "much specially complicated"
Clearly that will also, kept me all the same.


And you

On a goddamn parole
And sympathies.

Pardon the slowness. You were just lucky to be, Goliath.

Name: Anonymous 2025-07-29 13:25

Name: Anonymous 2025-07-29 13:43

Name: Anonymous 2025-07-29 13:50

Name: Anonymous 2025-07-30 7:12

106078053

Name: Anonymous 2025-07-30 11:00

https://sourceforge.net/p/clonezilla/discussion/Open_discussion/thread/c61cede1c5/
first 5 options off
-q1
-rescue
-icds

proportional resize of partiton tables on next screen

Name: Anonymous 2025-07-30 11:28

Name: Anonymous 2025-07-30 12:41

Name: Anonymous 2025-07-30 16:19

Including results for macos rebuild partition table
Search only for mac osX rebuild partition table
AI Overview
3 Easy Ways to Recover Deleted Partition on Your Mac (Guide)
Rebuilding a partition table on a Mac OS X system can be necessary when the table becomes corrupted or damaged, potentially leading to data loss or boot issues. The process typically involves booting into macOS Recovery and using Disk Utility or command-line tools to repair or recreate the partition table.
1. Using Disk Utility in Recovery Mode:

Boot into Recovery: Restart your Mac and hold down Command + R until the Apple logo appears.
Open Disk Utility: Select "Disk Utility" from the macOS Utilities window and click "Continue".
Select the Disk: In the sidebar, choose your startup disk (usually named "Macintosh HD").
Run First Aid: Click the "First Aid" tab and then click "Run" to attempt to repair the partition table.
If First Aid fails: You may need to consider data recovery options (if needed) and then erase the drive and reinstall macOS.

2. Using Command Line Tools (gdisk/gpt):

Boot into Recovery: Same as above.
Open Terminal: Select "Utilities" from the menu bar and then "Terminal".
Identify the Disk: Use commands like diskutil list, diskutil cs list, sudo gpt -vv -r show /dev/disk0, or sudo fdisk /dev/disk0 to identify the correct disk device (e.g., /dev/disk0).
Repair with gdisk: If you have it installed (or install it with brew install gdisk), use gdisk /dev/sdX (replace X with the disk identifier) to edit the partition table.
Recreate Partitions: Follow the prompts within gdisk to rebuild the partition table, potentially using backup information if available. You can use b to restore the backup GUID partition table and w to write the changes.
Verify: Run v within gdisk to verify the changes before writing them to disk.
Reboot: After writing the changes, reboot your Mac.

3. Other Tools:

TestDisk:
.

Another command-line tool that can help recover partitions. It's a more advanced option.
rEFInd:
.
A boot manager that can sometimes help with partition table issues, particularly when dealing with UEFI-based Macs.

Important Considerations:

Data Backup:
It's crucial to have a recent backup of your data before attempting any partition table repair, as data loss is a possibility.

FileVault:
If you have FileVault enabled, decrypting the entire disk before attempting partition table repairs might be necessary.
Expertise:
Rebuilding partition tables can be complex. If you're not comfortable with command-line tools, consider seeking professional help.

Name: Anonymous 2025-07-30 17:28

Name: Anonymous 2025-07-30 20:31

Name: Anonymous 2025-07-30 20:33

Name: Anonymous 2025-07-30 20:33

Name: Anonymous 2025-07-30 20:45

---> Cleaning libgcc10
Warning: System headers do not appear to be installed. Ports may not build correctly due to Xcode 10 only providing a 10.14 SDK.
Warning: You can install them as part of the Xcode Command Line Tools package by running `xcode-select --install'.
---> Fetching archive for libgcc9

Name: Anonymous 2025-07-30 20:47

For what you asked (GCC, SDL, OpenSSL, GLX, ...), here's a single command to get almost everything you want.

sudo port install gcc11 libsdl2 openssl glfw libsdl2_gfx libsdl2_image libsdl2_mixer libsdl2_net libsdl2_ttf

Name: Anonymous 2025-07-30 20:54

Name: Anonymous 2025-07-30 21:36

PID COMMAND %CPU TIME #TH #WQ #PORT MEM PURG CMPRS PGRP
76017 cc1plus 95.3 00:01.07 1/1 0 10+ 13M+ 0B 0B 2077
76016 xg++ 0.0 00:00.21 1 0 10 508K 0B 0B 2077
76010 cc1plus 93.9 00:03.04 1/1 0 10 48M+ 0B 0B 2077
76009 xg++ 0.0 00:00.21 1 0 10 508K 0B 0B 2077
76003 top 5.2 00:01.05 1/1 0 27 2768K+ 0B 0B 76003
75999 bash 0.0 00:00.02 1 0 19 716K 0B 0B 75999
75994 sshd 0.0 00:00.00 1 0 17 712K 0B 0B 75978
75991 cc1plus 95.6 00:08.21 1/1 0 10 73M+ 0B 0B 2077
75990 xg++ 0.0 00:00.21 1 0 10 508K 0B 0B 2077
75978 sshd 0.0 00:00.13 2 1 28 1676K 0B 0B 75978
75970 cc1plus 93.3 00:18.78 1/1 0 10 89M+ 0B 0B 2077
75968 xg++ 0.0 00:00.20 1 0 10 512K 0B 0B 2077
75928 GSSCred 0.0 00:00.02 3 3 18 772K 0B 0B 75928
75795 useractivity 0.0 00:00.10 3 2 68+ 992K 0B 1904K 75795

Name: Anonymous 2025-07-30 21:37

t you might install:
1. Essential Command-Line Tools:

Git: For version control.
wget: For downloading files from the internet.
nmap: For network scanning.
tcpdump/Wireshark: For network traffic analysis.
ffmpeg: For working with multimedia files.
jq: For working with JSON data.

2. Development Tools and Libraries:

cmake: A cross-platform build system generator.
Xcode command-line tools: Required for many ports that need compilers.
Programming language packages: Python libraries (like matplotlib, NumPy, SciPy), Perl modules, etc.
Graphics libraries: FLTK, Graphviz.

3. Utilities and Other Software:

Figlet: For creating large banner-like text.
GnuPG: For encryption and signing.
Minicom: For serial communication.
Unrar: For extracting RAR archives.
W3m: A text-based web browser.

4. Specific Packages for Specific Needs:

kubectl: For interacting with Kubernetes clusters.

FFmpeg variants: Different builds of FFmpeg with specific codecs or features (e.g., GPL3, non-free).

You can view available variants for a package, like FFmpeg, using the port variants command:

Name: Anonymous 2025-07-30 22:08

https://desuarchive.org/g/thread/87666511/#q87666514
------
These are some backtraces and stuff we've done (Chris, my mac friend, came over the house to try to figure it out too; but he was unable to)

pastebin com/YYpjt71d GDB of Sig Abort once asked to load a
map from OSX kernel

pastebin com/z2Q3mKAd printfs to standard out were commented
out, but still sig abort from kernel
pastebin com/hPnkBFai
https://pastebin.com/1bxkY3x8
https://pastebin.com/YaxNT0ea
https://pastebin.com/naVBCMb6


=pastebin com/xjUEBfcb
https://pastebin.com/JZLN9GXC

https://pastebin.com/UJk8ufqz

https://pastebin.com/yN3NfQxx
https://pastebin.com/2Bb0RXnq


(lldb) print texture->name
(char [64]) $0 = "textures/common/caulk"
(lldb) print name
(const char *) $1 = 0x0000000107c770c8 "textures/common/caulk"
(lldb)

(That is correct: that's what is supposed to be in those variables; no error here)
------

Name: Anonymous 2025-07-30 22:10

This is all from model_shared.c in darkplaces.
If one "defeats" the first strlcpy (ie by putting a hack that avoids the copy if the contents of both are at that point allready the same): the error just migrates down the code to the conditional at like 3161 or so:

>else if (!(texture->backgroundskinframes[j] = R_SkinFrame_LoadExternal(backgroundlayer->texturename[j], (backgroundlayer->texflags & texflagsmask) | texflagsor, false)))
{
Con_Printf("^1%s:^7 could not load texture ^3\"%s\"^7 (background frame %i) for shader ^2\"%s\"\n", loadmodel->name, backgroundlayer->texturename[j], j, texture->name);
>texture->backgroundskinframes[j] = R_SkinFrame_LoadMissing();
}

Name: Anonymous 2025-07-30 22:13

strlncpy

Name: Anonymous 2025-07-30 22:20

other ideas gcc-m4

Name: Anonymous 2025-07-30 22:28

106086075

Name: Anonymous 2025-07-30 22:35

https://desuarchive.org/g/thread/87538372/#q87538442
>>384413911
>Look in your menu.c file for anything that references _volume or could be referencing _volume. Same thing for the rest of the errors. It's probably all from one package, my guess is either the engine or SDL.

The engine code is all there.
The engine doesn't use outside dependancies for the menu. It's a Quake engine that's been updated. For audio it uses ogg vorbis stuff I guess.

I don't know anything about compiling on OSX.
The thing is it did compile the c files: so doesn't that mean it found everything?

This stuff used to compile on OSX in 2012.
The makefile is here:
https://pastebin.com/GPkifHGn
https://pastebin.com/TP7rJCLP

It has lines for OSX, iPhone etc. I got a 2011 Mac Mini just so it would be the same thing.

I've never made my own make files tho.

I installed the libs via both brew and mac ports:
>brew install sdl2 libjpeg-turbo libpng libvorbis curl
>sudo port install gcc11 libsdl2 openssl glfw libsdl2_gfx libsdl2_image libsdl2_mixer libsdl2_net libsdl2_ttf

And then I added, to the make file, for SDL which made it atleast get through the compile (but doesn't link):
>CPUOPTIMIZATIONS?=-fcommon -fno-math-errno -ffinite-math-only -fno-rounding-math -fno-signaling-nans -fno-trapping-math -D_THREAD_SAFE -I/opt/local/include/SDL2 -L/opt/local/lib -lSDL2

IE: -D_THREAD_SAFE -I/opt/local/include/SDL2 -L/opt/local/lib -lSDL2

As I was told to by a nice mac user.
I don't know if that should be somewhere else but CPUOPTIMIZATIONS is used in all compiles so I figured to put it there.
>>384413911
>Look in your menu.c file for anything that references _volume or could be referencing _volume. Same thing for the rest of the errors. It's probably all from one package, my guess is either the engine or SDL.

The engine code is all there.
The engine doesn't use outside dependancies for the menu. It's a Quake engine that's been updated. For audio it uses ogg vorbis stuff I guess.

I don't know anything about compiling on OSX.
The thing is it did compile the c files: so doesn't that mean it found everything?

This stuff used to compile on OSX in 2012.
The makefile is here:
https://pastebin.com/GPkifHGn
https://pastebin.com/TP7rJCLP

It has lines for OSX, iPhone etc. I got a 2011 Mac Mini just so it would be the same thing.

I've never made my own make files tho.

I installed the libs via both brew and mac ports:
>brew install sdl2 libjpeg-turbo libpng libvorbis curl
>sudo port install gcc11 libsdl2 openssl glfw libsdl2_gfx libsdl2_image libsdl2_mixer libsdl2_net libsdl2_ttf

And then I added, to the make file, for SDL which made it atleast get through the compile (but doesn't link):
>CPUOPTIMIZATIONS?=-fcommon -fno-math-errno -ffinite-math-only -fno-rounding-math -fno-signaling-nans -fno-trapping-math -D_THREAD_SAFE -I/opt/local/include/SDL2 -L/opt/local/lib -lSDL2

IE: -D_THREAD_SAFE -I/opt/local/include/SDL2 -L/opt/local/lib -lSDL2

As I was told to by a nice mac user.
I don't know if that should be somewhere else but CPUOPTIMIZATIONS is used in all compiles so I figured to put it there.

I don't know if it needs more stuff other than SDL path there. Never compiled on OSX before. Never used OSX before. My friend Chris is the OSX guy (straight, and got me into longboards)

I don't know what to do at all.
I don't know if it needs more stuff other than SDL path there. Never compiled on OSX before. Never used OSX before. My friend Chris is the OSX guy (straight, and got me into longboards)

I don't know what to do at all.

Name: Anonymous 2025-07-30 22:54

https://desuarchive.org/g/thread/87604657/#q87604713

Anonymous Mon 04 Jul 2022 05:14:11 No.87604713 Report
Quoted By: >>87604728
>>87604657
>There is no fucking way I can actually "fix" this program to run, that I know of.
Can you make your own strlcpy_fix that works properly, and then #define strlcpy strlcpy_fix inside an #ifdef that detects OSX?

"strlcpy buffer overlap"

Name: Anonymous 2025-07-30 23:04

Name: Anonymous 2025-07-30 23:06

Name: Anonymous 2025-07-30 23:16

Name: Anonymous 2025-07-30 23:19

Name: Anonymous 2025-07-31 7:41

Name: Anonymous 2025-07-31 7:43

Name: Anonymous 2025-07-31 7:45

Name: Anonymous 2025-07-31 7:46

Name: Anonymous 2025-07-31 9:32

106090497

Name: Anonymous 2025-08-01 13:24

Jeremy Bicha is welcome in ChaosXAnthology.
Free Software progammers are welcome.
Richard Matthew Stallman is welcome.
Do nothings like Brian "we need censorship on the net" Lunduke are not, since he does not program Free Software. Same with other christian-feminists that do not program Free Software.

YHWH allows child brides.
Xlibre is nice.

Name: Anonymous 2025-08-01 16:18

To change the UUID of a LUKS-encrypted partition, you can use the cryptsetup luksUUID command in conjunction with a new UUID generated using uuidgen. First, identify the partition and its current LUKS UUID using blkid or lsblk -f. Then, generate a new UUID with uuidgen and use it with cryptsetup luksUUID to update the partition's UUID. Finally, update the /etc/crypttab file with the new UUID if you are using it for decryption.
Steps to Change LUKS UUID:

1. Identify the partition and its current UUID:
Use sudo blkid or sudo lsblk -f to find the partition and its LUKS UUID.

For example, the output of sudo blkid might show something like: /dev/sda1: UUID="1234-5678-abcd-ef01" TYPE="crypto_LUKS".

2. Generate a new UUID:

Use the uuidgen command to generate a new UUID.

For example: new_uuid=$(uuidgen).

3. Change the LUKS UUID:

Use the cryptsetup luksUUID command with the new UUID and the device path of the LUKS partition.

For example: sudo cryptsetup luksUUID --uuid="$new_uuid" /dev/sda1.

4. Update /etc/crypttab (if applicable):

If you are using /etc/crypttab to manage the decryption of the partition, update the UUID in that file with the new one.

For example, if your /etc/crypttab entry was luks-1234-5678-abcd-ef01 UUID=1234-5678-abcd-ef01 none change it to luks-1234-5678-abcd-ef01 UUID="$new_uuid" none.

5. Reboot (if necessary):

After making changes to /etc/crypttab, a reboot might be required for the changes to take effect, especially if it's a root partition.

Important Notes:

Backup:
Always back up your data before making changes to partitions, especially encrypted ones.

Device Paths:
Ensure you are using the correct device path (e.g., /dev/sda1) for the LUKS partition.
crypttab:
If you are using /etc/crypttab, make sure the UUID in the file matches the actual LUKS UUID after the change.
Root Partition:
Changing the UUID of the root partition can be more complex and require careful handling of initramfs and other boot parameters.

Name: Anonymous 2025-08-01 16:20

Name: Anonymous 2025-08-01 16:21

Name: Anonymous 2025-08-01 16:23

Name: Anonymous 2025-08-01 16:23

AI Overview
While it is generally recommended to use UUIDs in /etc/crypttab for persistent and reliable device identification, it is possible to use device names instead.
To use device names in /etc/crypttab:

Identify the device name:
.

Determine the full path to the encrypted block device, such as /dev/sdaX or /dev/nvme0n1pY, where X and Y represent the partition numbers. You can use tools like lsblk or fdisk -l to find the correct device name.
Edit /etc/crypttab:
.
Open the /etc/crypttab file with a text editor and modify the entry for your encrypted device. Instead of UUID=<luks_uuid>, replace it with the device name.

Example:
Code

# Original entry using UUID
# cryptroot UUID=b40f1abf-2a53-400a-889a-2eccc27eaa40 none luks

# Modified entry using device name
cryptroot /dev/sda2 none luks

In this example, cryptroot is the name of the decrypted volume, and /dev/sda2 is the device containing the encrypted data.

Update the initramfs (if necessary): If the encrypted device is your root partition or a critical system partition, you may need to regenerate your initramfs to ensure the changes are reflected during early boot. This is typically done with a command like update-initramfs -u on Debian/Ubuntu or dracut -f on Fedora/RHEL.

Considerations:

Device name volatility:
.

Device names like /dev/sdaX can change if hardware is added or removed, potentially leading to boot failures if the crypttab entry is not updated accordingly.
UUIDs for persistence:
.
UUIDs are globally unique identifiers assigned to filesystems and partitions, making them more resilient to device name changes and providing a more robust configuration.
System impact:
.
Modifying crypttab incorrectly can prevent your system from booting, especially if it involves the root filesystem. Exercise caution and consider creating a backup of the file before making changes.

Name: Anonymous 2025-08-01 17:34


Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List