cmeerw
cmeerw
About
- Username
- cmeerw
- Joined
- Visits
- 10,109
- Last Active
- Roles
- Member
- Thanked
- 453
Comments
-
(Quote) There we go: https://download.cmeerw.net/netbsd/netbsd-10.1-pr58693.qcow2 (@linveo maybe name that "NetBSD 10.1 Minimal for Intel (PR58693)")
-
(Quote) What's actually in "non-free" nowadays? Do we really need that? Maybe we should get rid of it as the rules say "Free, open source software only." We might still need non-free-firmware, though.
-
(Quote) No real plan, so just go ahead.
-
(Quote) So I guess the high-level overview is that it hooks into the grub boot menu to add an Alpine Linux netboot live CD and then uses that to download and write the Linux image to the hard disk.
-
(Quote) That's the thing with bugs that have security implications that you don't want the details to be public until everyone affected had a chance to update. I'll want to wait until I get confirmation that they are fine with making the details pub…
-
(Quote) What I actually find interesting is that you seem to be using mxroute, but with IPv6 - I didn't think mxroute had IPv6 support? (Quote)
-
(Quote) Well... it's a bit complicated. :) Found the bug and the fix works. However, turned out it's actually in a third-party component (with potential security implications as it's essentially use of uninitialised memory). So reported as a potent…
-
(Quote) I had the low-end option: a SupraFAX: (Image)
-
(Quote) jed does :)
-
(Quote) for a day, a week, a month, or a year?
-
(Quote) Maybe one of these: https://www.supermicro.com/en/jumpstart
-
(Quote) Want to change this to PM you instead to comply with no-spam rules?
-
(Quote) Well... btrfs has a lot of features, but I am unlikely to ever use every feature of it. The question then is how much should I pay for features I don't use? Ideally, copy-on-write should only affect performance if I actually use it for some …
-
Just created an XFS volume: lvcreate -L 64G -n xfs M247-X10E-9N-vgmkdir /mnt/xfsapt-get install xfsprogsmkfs.xfs /dev/mapper/M247--X10E--9N--vg-xfs and added it to /etc/fstab (mounted on /mnt/xfs)
-
(Quote) Is there a description somewhere how the YABS IOPS tests work? (in terms of files created, operations done on those files, ...) (Quote) I guess, and then read up on what fio actually does. (Quote) Maybe should also try with XFS then?
-
(Quote) BTW, quite a big difference between Vienna and Amsterdam.
-
@bin456789 is there somewhere a high-level description of how the script works?
-
Announcing NetBSD 10.1
-
(Quote) I have now already made a NetBSD 10.1 image (@linveo ) as 10.1 binaries started appearing this morning.
-
(Quote) I have no idea what that does (actually https://www.cheervision.co/ipinfo/tools/ ) - the IP address is completely wrong (wrong continent) and so is the latency info.
-
(Quote) It's not even in HEAD. Unfortunately, there doesn't appear to be much interest in this one (even tried pointing out on the mailing list that another VPS provider is also affected).
-
NetBSD 10.1 seems to be just around the corner
-
(Quote) Not all blacklists are only about SMTP (and email spam), but some of them also cover other undesirable behaviour from a particular IP.
-
(Quote) So, "Free VPS trial for 1 month" is not considered free, but "Free VPS for 1 month" is? Could this be clarified where the line between "free" and "not free" is? I don't think I am the only one confuse…
-
(Quote) Maybe the value could be that this fine server is not on any blacklist so far (Quote) There is even a Debian package, but why does the README not recommend using that?
-
(Quote) Presumably, wireshark can be built without the GUI (which is what the OpenWRT build does - so you only get TShark there).
-
(Quote) No, I am patching the resize_root script when building the NetBSD image: sed -i -e 's,\[ "$opt" = "log" \],[ "$( dumpfs -s / | fgrep "wapbl version " | cut -f1 )" != "wapbl version 0x0" ],' …
-
(Quote) Ahh no, you probably got that resize_root script from NetBSD HEAD when you updated NetBSD.
-
(Quote) Oh... that's not good. That version of the script is a bit older than I thought (I though you already had the version that did the check via dumpfs instead of the flag in /etc/fstab) That means you'll have to do the resize command in the sh…
-
(Quote) Some of the output from startup scripts might end up in /var/log/messages, but I don't think this one does (that particular script uses # KEYWORD: interactive, so the output doesn't get redirected to the syslog processor). (Quote) The kerne…
-
I think I am actually already done with my changes. Here is what I did: * Log into the serverforge portal - this has some rescue options, but I couldn't really figure out what those would do * From the serverforge portal then log into the Console (…
-
(Quote) Alternative approach: * reboot into single user mode * tunefs -l 0 /dev/dk2 * reboot, again into single user mode * mount -u /dev/dk2 / * mount -ru /dev/dk2 / * exit
-
(Quote) Ok... while it seemed to work with NetBSD 10.0 for me, it actually left the old journal unconnected on the filesystem, so that's not too good. You might want to do a fsck_ffs -f /dev/dk2 in single user mode now.
-
@Not_Oles those kernel messages don't look like they should be expected (maybe that's a change with NetBSD HEAD?) BTW, Not resizing $rootmp: logging unsupported should be the message you are seeing (and the tunefs, re-mount was supposed to disable …
-
(Quote) And now that I have figured out the exact commands of how to do it, I could probably even integrate that into the resize_root script.
-
(Quote) This should work: * reboot into single user mode * tunefs -l 0 /dev/dk2 * mount -ruo reload /dev/dk2 / * reboot (this should then resize the filesystem, and trigger another reboot) in between these commands you can check with dumpfs -s / t…
-
(Quote) So the main issue is that resize_ffs doesn't really handle the filesystem log, so resizing such a filesystem is disabled in my boot scripts. In some cases you could run into data corruption (although that would be with an out-of-filesystem l…
-
(Quote) Thanks, I'll try to mainly work on it from around 16:00 UTC on Saturday to 23:00 UTC (but will hopefully be a lot shorter).
-
(Quote) well... (Quote) sounds a bit like there will always be some reason to kick users out. What if I feel offended by your repeated questions about CPU usage policies?