I explained myself badly.

Git as GIT_DIR and --git-dir for specifying location of the ".git".

What would be nice if there was also something like --git-dir-alias or similar for specifying non-standard name for that directory.

Then I could along the lines of

git clone <project URL>
cd <project>
export GIT_DIR_ALIAS=".git-private"
git init && git remote -add origin <private data URL> && git fetch origin && git reset --hard origin/main
unset GIT_DIR_ALIAS

It's not uncommon to initialize Git repositories to populated directories. E.g. that is how I clone my home directory skeleton on a new system:

git clone https://codeberg.org/jarkko/skeleton
git reset --hard origin/main

This is just extension to it. Home directories are great example use case also because then you could have separate Git repositories, if you want to isolate settings of a particular program but still have means to deploy them under the same root where they are cloned.

Sometimes it would be useful if you could have multiple Git repositories in the same clone as long as they don't share files. E..g, for separating private data.

#git

There is an alternative for Rocksmith, which also plays its '.RS files: https://tonelib.net/jam-overview.html

This not only fixes the issue macOS but there is also a native Linux version. Further, it happened to be 60% discount :-)

this motivates to work on my zmodem2 crate again (it is still more than a useful protocol in the modern world e.g., with FPGAs). i think i expand the test programs as utilities having tuis.

https://codeberg.org/jarkko/zmodem2

Cool, my PR for rust-hex was merged:

https://github.com/KokaKiwi/rust-hex/pull/83

It adds decode_in_slice() function, which decodes the hex string within the input buffer overwriting the contents. It is with ugly but still useful for e.g., fast and constrained protocol implementations.

Just came as surprise because the PR was made almost two years ago...

#rust #rustlang

I enjoyed responding this:

https://lore.kernel.org/linux-integrity/aGffUrDSjNH6w6rB@kernel.org/

Enjoyment did come like e.g, for "winning the argument". Instead it s fun to do this type of comparisons for the cause and effect of choices to the resulting binary :-) I did honestly did not know the correct answer beforehand.

Reviewing random day-by day patches can be boring. If I have some extra bandwidth this how I usually spice it up just a bit.

#linux #kernel #arm

@lkundrak lol i immediately decided to drop it

The fact that the issue is so trivial makes me doubtful of myself in this one:

https://github.com/himmelblau-idm/himmelblau/pull/592

#systemd #himmelblau

Himmelblau is the "new Samba" really, but how fast the situation needs to be addressed is on the other hand more like in the metrics of "EFI secure boot", which was an edge case 10+ years ago.

https://www.youtube.com/watch?v=gHnG8KZpYg4

Intune is a technology where open source community needs to be clear on that "no, microsoft, edge + a shitty daemon running on a subset of linux distributions is not acceptable".

#microsoft #intune #himmelblau #samba

experienced this today on a machine running debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078608

fixed up by:
sudo rm -rv /var/lib/apt/lists/*

#debian

Linux Foundation should take Himmeblau under its Umbrella.

As of today, the project is based on reverse engineering Apple and Windows clients, as the Intune API for Linux that Edge uses in tandem with intune-portal service does not have machine authentication.

"Microsoft Intune App" is based on chain of Microsoft binaries scavenging requested data from a system (Edge and intune-portal).

This blocks essentially the management tools for organization Linux machines by large.

Himmelblau on the other hand is a piece of middleware that manages the computer through the power cycle system-wide for the whole system, and thus can provide both boot-time initialization (himmelblaud) and reoccuring updates needed to maintain the trust (himmelblaud-tasks), such as Kerberos ticket and that kind of stuff.

So... I think for Audio CrossOver is not a great idea. I came to this conclusion after trying out if it could re-enable Rocksmith in macOS.

It's much better idea to run it on an emulated VM for the sake of USB passthrough. Graphics is not high-end in that game and then it will work with audio with best possible quality of service.

https://www.codeweavers.com/compatibility/crossover/tips/rocksmith-2014-pc/how-to-run-rockmith-2014-with-crossover-linux

@spubby what there is to convince in insecure url? i don't understand what you are talking about. insecure URL is a fucking insecure url. that's it.

a checkpatch error that provides an insecure URL as guidance lol:

WARNING: unnecessary cast may hide bugs, see http://c-faq.com/malloc/mallocnocast.html

Tried to fix it but also https is broken. It's also quite common mistake, meaning that it pushes insecure in volumes to developers.

#linux #kernel

finnish electro classic from 25-26'ish years ago: https://www.youtube.com/watch?v=xZpZWm5GRXo

i.e. when the electroclash boom was ongoing with lots of stuff coming from i-f, parallax corporation, miss kittin and the hacker, dmx krew and others. stuff like that was playing a lot at venues. good times :-)

what a depressing situation really, and weekend is ruined as i cannot do things i like to do on free time but i'll get there!

I'm trying to figure out how to get this to used in the Steam version of Rocksmith 2014 running with CrossOver:

IOUSBHostDevice, id 0x100000$
| | +-o Rocksmith USB Guitar Adapter@00110000 <class

There is macOS version of the game at Steam but unfortunately macOS Sequoia broke it, and it goes without saying that Ubisoft will not fix it ;-)

It runs otherwise with zero tweaks required and zero glitches appearing with CrossOver. I'll definitely buy it, if the cable starts working too. There's bunch of free alternatives but I'll just want to get the fucking game working and get on with my life. Definitely worth of paying the discounted price of 51 euros and 80 cents at least (up until 11th of July) ;-)

for what it is worth this is how you “lsusb” in macOS:

$ ioreg -p IOUSB
+-o Root  <class IORegistryEntry, id 0x100000100, retain 36>
  +-o AppleT8112USBXHCI@01000000  <class AppleT8112USBXHCI, id 0x100000371, reg$
  | +-o Magic Keyboard@01100000  <class IOUSBHostDevice, id 0x100000d5a, regist$
  +-o AppleT8112USBXHCI@03000000  <class AppleT8112USBXHCI, id 0x1000003bb, reg$
  +-o AppleT8112USBXHCI@00000000  <class AppleT8112USBXHCI, id 0x1000003ca, reg$
  | +-o 4-Port USB 2.0 Hub@00100000  <class IOUSBHostDevice, id 0x100000a0e, re$
  | | +-o USB2.0 Hub             @00140000  <class IOUSBHostDevice, id 0x100000$
  | | +-o Rocksmith USB Guitar Adapter@00110000  <class IOUSBHostDevice, id 0x1$
  | +-o 4-Port USB 3.0 Hub@00200000  <class IOUSBHostDevice, id 0x100000a10, re$
  |   +-o RTL9210B-CG@00220000  <class IOUSBHostDevice, id 0x100000a43, registe$
  |   +-o USB3.0 Hub             @00240000  <class IOUSBHostDevice, id 0x100000$
  |     +-o USB3.0 Card Reader@00243000  <class IOUSBHostDevice, id 0x100000a71$
  +-o AppleT8112USBXHCI@02000000  <class AppleT8112USBXHCI, id 0x10000036e, reg$
  | +-o Scarlett 4i4 USB@02100000  <class IOUSBHostDevice, id 0x100000a56, regi$
  +-o AppleEmbeddedUSBXHCIASMedia3142@08000000  <class AppleEmbeddedUSBXHCIASMe$
    +-o USB Receiver@08300000  <class IOUSBHostDevice, id 0x100000a2f, register$
    +-o YubiKey FIDO+CCID@08400000  <class IOUSBHostDevice, id 0x100000a37, reg$

ioreg is a wrapper utility for doing queries from https://developer.apple.com/documentation/iokit

just learned this and now i’ll probably remember it too after writing this ;-)

submitted fish version of the mc-wrapper:

https://github.com/MidnightCommander/mc/pull/4726

i'm actually using zsh (and no immediate plans to switch), but i just wanted to see how fish feels like so did a little bit of scripting ...

#fish #shell #mc