They are banking on the fallout 76 model. Trying to get people to buy lootboxes and whatever.
SK4nda1
joined 1 year ago
Very nice! Unionization is the only way to make employera care about workers rights.
Its sad but linux is still a second class citizen. Nvidea drivers have improved greatly over the years, but it can be still flaky especially newer ones.
Multi moniter support too, it has a history troubled with challenges. Its much much better than it used to be but sometimes there are setups and usecases which have problems. It used to be multiple monitors, just having them as a desktop, was impossible. Nowaday I can daily drive Linux and expect to have a good desktop experience across multiple monitors.
Mindyou, every windows update its a dieroll what breaks for my work surface labtop. Often my display or dock behaviour breaks or my bluetooth, or my networking. Not to excuse the bugs in linux, but to show that even MS on their own hardware have bugs like that. Pcs are hard and even MS can't do it flawlessly.
What you describe as simple multimonitor RDP might actually be a very complex task from a technology and display standpoint.
That being said, it totally sucks having a usecase and finding out that for you have problems getting there. I agree that Linux still has major hurdles for general adoption, (although again, it is so much better than it used to be). Look at it this way: if desktop linux had the same amount of money and development time thrown at it as Windows or MacOS, we'd have a very different experience.
As for tips. I recommend to dualboot. Use MS for your usecases that are not a good experience and use Linux for the other things. Keep checking in with the multiple RDP tech/workflow to see if it works. I did the same thing for years. The only reason I used windows was my games. For other things I used Linux and learned my way around the desktop while doing that. Eventually Proton came along and I could switch entirely.
Jeah. A bit ie meme if you ask me
Wtf. Was this just an IP takeover?
A group of Norwegian unions says it will act against Tesla in solidarity with its Swedish colleagues
Which aide are you on, boys, which side are you on.
God i wish Unions where this strong everywhere.
Telling your coworker "Shut the fuck up?" Is not acceptable. The way communication happens matters.
SteamOS: Alyx will be released before SteamOS 3
In that case yes ofcourse. Why even ask. Pirating is illegal. Vpns are cheap. I can recommend Proton or mullvad
Thats what they said avout VR
Hey all,
I want to start using btrfs on my san/nas and use that as a backend for my nextCloud. Before I had read up on btrfs I was thinking about using RAID1. I thought RAID1 would fulfill my two requirements:
- It would allow me to just pull out a disk and put in a usb dock and read its contents. (disaster recovery, or for my SO to just power down the server and get her data off if something happens to me).
- It would simply Mirror the data so a single drive can fail and everything is fine.
Now I read things on the documentation of btrfs and in some other places that the RAID1 implementation of btrfs is non-standard, in that is also has some striping functionality.
The image included is from the btrfs docs and it seems it also stripes, not just mirrors, when using 4 disks.
Now my question is: What is its behaviour when using 2 disks? Will this fullfill my two requirements? If not do you have any other recommendations? (I mean i could use zfs...)
A penny for your thoughs :-).
Edit: new cable fixed it. The otherone wasnt crossover.
I have a problem.
I have an (Intertech 2U 2412)[https://www.inter-tech.de/productdetails-144/2U-2412_EN.html]. I have some old desktop hardware in it to build a SAN. The OS I'm running is currently Proxmox 7.
Now I have the problem i'm having is that the drives I put in the hotswap bay are not showing up in the OS. The lights on the bays light up, I can hear the disks spinning so they seem to have power.
The connection splits from SAS to 4 times SATA to a PCIE expansion card. This card is confirmed to work: If I put my bootdrive in it, the pc boots normally and the bootdrive shows up in the OS. The splitter cable could be the problem, granted, but the manual of the case specified this type of cable and I triple checked that this is correct.
When I look in /var/log I see kern.log files with loads of these messages in them. This is where things get murky for me. In my linux journey I haven't yet been this deep into the OS/kernel before. Can anyone help me debug what is happening in my system? Or at least help me understand what is happening in these logs?
[1378464.033553] ata14.00: status: { DRDY }
[1378464.033555] ata14.00: failed command: WRITE FPDMA QUEUED
[1378464.033556] ata14.00: cmd 61/08:a8:b0:ed:a0/00:00:0e:00:00/40 tag 21 ncq dma 4096 out
[1378464.033556] res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
EDIT: New cable fixed it! Turns out the other one wasnt crossover.
view more: next ›
Ah my bad. I remember they having bad dlcs and cashgrabby content at launch. Perhaps i'm misremembering. :-)