• 0 Posts
  • 46 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle

  • rsync was written by one of the original Samba developers. I wonder if Tridge and co have any idea about how to shuffle data from A to B safely?

    CIFS/SMB will only indicate received and not received and written. This is unlikely to be an issue.

    I would start by proving that my network works properly, especially that dodgy cable with only wires 1,2,3,7 connected - because that’s all 100Mb/s needs, or the solid core cable that runs for 150m with plugs at each end instead of sockets and drop leads.


  • “Is this a common issue with samba” - no.

    Samba shuffles rather a lot of data, quite happily. You have not given us an exhaustive description of the shoddy wiring, dodgy switches and wonky configuration that makes up your network. If it was perfect, you would not be posting here.

    There is one snag with CIFS (Samba follows MS’s standards and ironically, I think that CIFS is now renamed back to SMB) that I am aware of, so SMB … snag: SMB will indicate that a chunk of data has been received successfully but not that it has been written to disc successfully. NFS will notify that a chunk of data has been written to disc.

    The difference is subtle but if there is not a battery backed RAID involved then SMB/CIFS can lose data if the system restarts part way through a write.

    Your issue is probably hardware related. Test your network with say iperf3. Have a look at network stats. Don’t rely on cargo cult bollocks - do some investigations. Nowadays we have nearly all the tools as open source to do the entire job - we did not have that 30 years ago. Grab wireshark, nmap, mtr and the rest and get nerdy (or hire me to do it - don’t do that please!)


  • If I give you a free beer, you have one beer. If I give you the recipe, you can make your own beer. You do have to make your own open source beer or you can hire someone to do it for you or perhaps take you through the steps a few times until you’ve got it. With luck there will be a community of open source beer brewers with whom you can interact and improve those recipes.

    Free software is free until it isn’t! The illicit drugs industry works in a similar way (the first hit is for free).




  • I doubt it. They make a hell of a noise and print at a rate of characters per second not pages per second. The ribbons suffered from similar issues as cassette tapes (the other ribbons that we had to deal with). The ribbon would dry out if not used for a few days and you’d waste paper and a lot of time.

    DM printers were ideal in the guise of “line printers” - the big old IBM jobbies that munched through A3 landscape fan fold at ridiculous speeds. Home printers like the Epson FX80 or RX80 were at least affordable. I still remember the manual of our RX80 congratulating us on buying it and exhorting me to hug the printer on unpacking it. I suspect the Japanese to English translation might not have been the best.

    We had to get a Centronics interface board stuffed into our C64 and get it working (sacrifice a chicken on a waxing gibbous moon night, etc)

    It worked better on my 80286 box, some years later. I had to set it up in each application - Harvard Graphics, Word Perfect, Super Calc.

    In around 1991 I was able to buy a 80486 based beastie, thanks to gift from granddad. In around 1993 I was given a HP LJ 4P so I could print out proofs for a Plymouth (Devon) tourist tat thing.

    Nowadays I have a fairly elderly HPE MFP five toner humming away at home. Its on a VLAN that doesn’t get to see the internet. It just works. I won’t be “upgrading” it for the foreseeable future.


  • My Epson RX80’s ribbon is somewhere in landfill. The Commodore 64 however is all good and now sports a USB interface with more storage than the poor thing can possibly ever use. The Quickshot II joystick still works too.

    1984ish was when the C64 was bought by my dad, from the NAAFI in Rheindahlen (West Germany, as was).

    Picture the scene:

    Me and brother fly home from UK to probably Dusseldorf at the end of the winter term. Its December in the mid '80s. Every now and then, Russia sends a Tupolev Bear or Badger to chug along overhead. The US sends a YR-71 over the USSR at multiples of the speed of sound. The Cold War was quite unpleasant to live through. Its quite chilly, snow tyres on the car, chains in the boot. The autobahn has the usual psychotic bunch of lane two and three drivers. Lane one generally runs at around 90mph (yes, even back in the '80s)

    We get to home at the time (we move every two years or so - it is the way of things). Dad shows off the new gadget. He plugs the power lead into the video port.

    Some weeks after we have gone back to school for the spring term, the C64 is returned from the menders. We get to use it in the Easter hols. It travelled to the UK and back to DE several times and also to Cyprus (WSBA). The QS II took a serious battering thanks to Daley Thompson’s decathalon.

    I got it re-capped in 2019, which was all that needed doing. They were rather well made …




  • gerdesj@lemmy.mltoLinux@lemmy.mlProblems with Arch upgrade
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 months ago

    What on earth went wrong?

    Arch is just as safe as any other distro, sometimes more so. Being a rolling jobbie, smaller bits tend to break at a time. If you want to live life on the edge then Gentoo is your man but even Gentoo is becoming pretty safe. You might lose your windowing system for a while but you still have links2 to get to a search engine.



  • gerdesj@lemmy.mltoLinux@lemmy.mlRust for Linux revisited (by Drew DeVault)
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    7
    ·
    3 months ago

    “Every subsystem is a private fiefdom, subject to the whims of each one of Linux’s 1,700+ maintainers, almost all of whom have a dog in this race. It’s herding cats”

    There are three similes in that quote. When your considerations are that disorganized, you have not finished thinking everything through. Fiefdoms, dogs and cats … oh my! That’s on top of wild west and other trite, well worn and rather silly similes.

    Make your argument without recourse to inflammatory terminology and similes and you slighten the risk of pissing people off.

    Clarity is in the eye of the beholder or as someone once said: “You do you”.


  • I like to use my enterprise number and a UUID (all in lower case, for legibility). Here’s an example:

    .1.3.6.1.4.1.33230.0d456e46-67e6-11ef-9c92-7b175b3ab1f1
    
    

    Now you might say that the UUID is already globally unique or at least pretty unlikely to turn up anywhere else, so why bother prefixing it with more stuff? To that I say: “I need to be absolutely or at least reasonably sure … OK nearly sure”.

    Anyway, you maintain a database of these things and then attach documentation and meaning to them. An editor could abstract and hide that away.

    I started this post as a joke. Not sure anymore. Why get your knickers in a twist with naming conventions for variables and constants. Programming is already a whopping layer of abstraction from what the logic gates are up to, another one wont hurt!



  • Windows GPOs are a right old mess. I’ve been managing them for over two decades. The first fuck up is the word “Group”. You cannot assign Group Policy Objects to AD groups unless you use something like ZENworks or some funky WMI filters!

    Settings are applied to computers or users. Many settings are available to be set for both but only make sense or even work for one or the other. MS bought out some solution providers and that’s why you get the Control Panel and other handy stuff, rather roughly bolted on.

    AD with GPOs with the extension to “local machines” is a great idea but dreadful in execution. MS didn’t want to nobble third party apps in the past so that’s why we have this nonsense. Now its all about Azure/whatevs ie MS’s cloud and subscriptions.

    Now you belong us!

    Linux being a Unix has NIS(+) for a directory or LDAP or AD or anything else you fancy. Ansible works for all mainstream OSs, including Windows.

    So often I see people confusing and conflating authentication and authorisation, machine and session state configuration databases.


  • There are so many options it is almost impossible to know where to start!

    Which distro is the VM running (is it even Linux)?

    If you want the VM to use the host’s VPN then you will need some routing and perhaps NAT/masquerade. This is non trivial to sort out. Can the VM have its own VPN connection to your supplier?

    You are starting to reach the point where VLANs/subnets and separate routers (real or VM) may be required. Depending what you use as your ISP router, we might be able to get a solution together - so what model is it and do you have any switches?


  • Please do a little research before trying random stuff. After checking to see if you are actually using the iwlwifi module, why not find out a bit about whether the mentioned param. is available to you and what it does:

    Am I using the module. If the output from this is blank, then no:

    $ lsmod | grep iwlwifi
    iwlwifi               622592  1 iwlmvm
    cfg80211             1331200  3 iwlmvm,iwlwifi,mac80211
    
    

    Also verify with lspci -k as above:

    $ lspci -k | grep iwlwifi -A2 -B2
            DeviceName: WLAN
            Subsystem: Intel Corporation Raptor Lake PCH CNVi WiFi
            Kernel driver in use: iwlwifi
            Kernel modules: iwlwifi
    00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
            Subsystem: Hewlett-Packard Company Alder Lake PCH Serial IO I2C Controller
    
    
    # modinfo iwlwifi
       ...
    parm:           swcrypto:using crypto in software (default 0 [hardware]) (int)
    parm:           11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
    parm:           amsdu_size:amsdu size 0: 12K for multi Rx queue devices, 2K for AX210 devices, 4K for other devices 1:4K 2:8K 3:12K (16K buffers) 4: 2K (default 0) (int)
    parm:           fw_restart:restart firmware in case of error (default true) (bool)
    parm:           nvm_file:NVM file name (charp)
    parm:           uapsd_disable:disable U-APSD functionality bitmap 1: BSS 2: P2P Client (default: 3) (uint)
    parm:           enable_ini:0:disable, 1-15:FW_DBG_PRESET Values, 16:enabled without preset value defined,Debug INI TLV FW debug infrastructure (default: 16) (uint)
    parm:           bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
    parm:           led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
    parm:           power_save:enable WiFi power management (default: disable) (bool)
    parm:           power_level:default power save level (range from 1 - 5, default: 1) (int)
    parm:           disable_11ac:Disable VHT capabilities (default: false) (bool)
    parm:           remove_when_gone:Remove dev from PCIe bus if it is deemed inaccessible (default: false) (bool)
    parm:           disable_11ax:Disable HE capabilities (default: false) (bool)
    parm:           disable_11be:Disable EHT capabilities (default: false) (bool)
    
    

    sysfs is a pseudo filesystem with lots of info in it. cat the files here:

    $ ls -l /sys/module/iwlwifi/parameters/
    
    

    … to see what your current values are set at. You can install sysfstools and run this for a neat report:

    $ systool -vm iwlwifi
    Module = "iwlwifi"
    
      Attributes:
         ...
      Parameters:
        11n_disable         = "0"
        amsdu_size          = "0"
        bt_coex_active      = "Y"
        disable_11ac        = "N"
        disable_11ax        = "N"
        disable_11be        = "N"
        enable_ini          = "16"
        fw_restart          = "Y"
        led_mode            = "0"
        nvm_file            = "(null)"
        power_level         = "0"
        power_save          = "N"
        remove_when_gone    = "N"
        swcrypto            = "0"
        uapsd_disable       = "3"
    
    

  • xfs has reflinks. That means you can copy huge wodges of data nearly for free on one filesystem. For backup systems this is a killer feature. Veeam rolling up incremental backups into the last full happens in seconds because pointers to blocks are juggled around rather than the data blocks themselves.

    xfs has been around for a very, very long time. I use it for larger filesystems eg Nextcloud, Zoneminder and the like (and Veeam backup repos that are not object storage). I use ext4 by default.

    pfSense boxes - zfs because the alternative is ufs.

    RPi - OverlayFS (with ext4 and tmpfs) gets you a generally read only filesystem with changes held in RAM. Ideal for kiosks, appliances and keeping memory sticks alive.

    Windows - NTFS, it works well and has streams and there aren’t many other options (ReFS is a bit new but it does have reflinks)