00:08:58 <polarian> if you want to run multiple ifconfig commands in rc.conf say configure IP address then add members for a bridge
00:09:06 <polarian> can you do ifconfig_bridge0 twice?
00:09:14 <polarian> bridge0 being the interface you want to configure
00:09:45 <polarian> or do you chain it
00:10:20 <polarian> "inet 192.168.56.32 netmask 255.255.255.0 addm fxp0 addm fxp1"
00:10:23 <polarian> would that be valid?
00:34:36 <polarian> also according to the man pages... bridge and tap are both created through interface cloning... so if I do cloned_interface="bridge0 tap0"
00:34:44 <polarian> both a bridge and tap device will be created, correct?
05:26:08 <sixpiece> ok so I have node modules taking around 5 gb apache is around 15gb
05:27:14 <sixpiece> python, and other node modules 5 gb , usr/ports taking another 5 gb
05:28:14 <sixpiece> but the breakdown is /usr is 25 gb /var 12.7 gb /jails 3gb  /root 2.6gb
05:56:20 <sixpiece> hello anyone here?
05:56:31 <sixpiece> how do I check if firewall is on?
05:56:52 <sixpiece> ok ipfw is enabled
06:09:15 <sfox_> pfctl
06:13:29 <sixpiece> like what would be the command?
06:16:25 <vkarlsen> sixpiece: No, if you have ipfw enabled, ipfw list will show you your current rules
06:16:51 <sixpiece> both are enabled now
06:16:59 <sixpiece> but I don't know how to block someone
06:18:48 <vkarlsen> Don't enable both
06:21:14 <vkarlsen> The handbook explains how to use the firewalls: https://docs.freebsd.org/en/books/handbook/firewalls/
06:42:35 <sixpiece> i deleted some log files that were really huge to free up space and will it recreate those files or I need to remember their names?
07:12:54 <rennj> https://termbin.com/cvk8 fbsd 5.x days was easier
07:13:04 <rennj> # Stop RFC1918 nets on the outside interface
07:13:06 <rennj> haha
07:13:37 <rennj> not current
07:13:40 <rennj> haha
07:13:47 <rennj>     # Stop RFC1918 nets on the outside interface
07:21:33 <rennj> probably should use pf at this point.
07:23:56 <rennj> https://docs.freebsd.org/en/books/handbook/firewalls/
07:26:33 <rennj> PF is a complete, full-featured firewall that has optional support for ALTQ (Alternate Queuing), which provides Quality of Service (QoS).
07:28:43 <rennj> Dummynet & ipfw = QoS perhaps
07:31:14 <rennj>  dummynet is a flexible tool originally designed for testing networking protocols, and since then (mis)used for bandwidth management.
07:37:03 <rennj> https://termbin.com/4n3t generic vmware.vmx file w00t.. xhci vs echi. finally got. now i just need to lsi scsi to it. Saturday night one more beer.
07:37:30 <rennj> thats a good .vmx file
07:40:13 <angry_vincent> when /usr/obj is on tmpfs, it looks that META_MODE does not work?
07:51:21 <vkarlsen> sixpiece: I'm missing some context. Are you the person who was here the other day with a VPS that was fuller than it should?
08:45:24 <sixpiece> vkarlsen yes that's me
08:50:25 <vkarlsen> sixpiece: Thoser are some large numbers for a small server without much content, especially /var and /root. Are you storing a bunch of things in /root? Did you find out why /var/db takes up so much space?
08:52:09 <sixpiece> I cleared it up quite a bit
08:52:46 <sixpiece> now I have 20gb but they had a ssl error log and some people obviously trying to hack and I just deleted the file that was over many gb
08:53:29 <sixpiece> so I am hoping these deleted files will recreate themselves when they attempt to write to the file
08:57:08 <sixpiece> but I agree there's probably still quite a bit more that needs to be deleted
10:38:28 <polarian> Anyone can answer my questions in the backlog? (casually bumping my query) :P
10:41:33 <nimaje> polarian: you shouldn't write commands in rc.conf, as how often it get read (sourced) is unspecified, you should only have assignments there and later assignments to a variable override previous assignments to that variable
10:44:10 <polarian> nimaje: not commands
10:44:25 <polarian> but when doing ifconfig configurations... do you duplicate the variable or do you chain them
10:44:38 <polarian> for example, I need to set an IP for bridge0 and also assign interfaces to it
10:44:44 <polarian> can I mix the inet with addm?
10:44:59 <polarian> that was the question, sorry if I was not clear.
12:26:03 <polarian> anyone know the answer/
12:31:34 <ridcully> cloned_interface is correct.  i have added the ip here via alias - no clue, why i did that back then.  so maybe you can not mix it (assuming, you are asking, because you have tried and did not work)
13:00:47 <nimaje> […] and later assignments to a variable override previous assignments to that variable
13:01:52 <dvl> tsoome: That loader.conf.local issue - it is NOT a problem with the Azure templates - the file originated in the VM I was migrating from DigitalOcean to Azure. Looking at the original droplet, the file is dated 2017
13:49:07 <Soni> how hard would it be to replace the entire address space on a signal
13:49:28 <Soni> (or, at least the object code)
13:51:32 <Soni> see, we have this cursed proposal, let's call it "sigaltexec", which, given appropriate compiler support, lets you replace the object code with a signal-safe version when handling signals
13:52:05 <Soni> and by "signal safe" we mean the code would be compiled twice: once with access to everything normally, and once without access to things like malloc
13:53:01 <Soni> (then it's just a matter of replacing the object code when handling signals and even function pointers can be safely passed around between the two "worlds")
14:25:51 <polarian> nimaje: so how do you assign and add interfaces
14:26:09 <polarian> do you just compress it into a single ifconfig_bridge0 line
14:26:18 <polarian> addm and set inet/netmask on the same line
14:41:22 <nimaje> probably, I didn't need to look to deeply into configuring network stuff yet
15:03:40 <ridcully> i have `ifconfig_bridge0` just for the `addm ...` and then `ifconfig_bridge0_alias0` for an `inet ...` ipv4 on it
15:40:02 <mzar> that's sad story kwiat
15:40:12 <mzar> that's sad story ketas
15:43:09 <ketas> mzar: i can't recall any recent sad stories, only older ones
15:43:52 <mzar> your laptop BrindledCat
15:43:59 <mzar> your laptop broke
15:44:10 <ketas> oh
15:44:12 <mzar> I am sorry for tab abuse BrindledCat
15:44:15 <ketas> well
15:44:58 <ketas> it was n.o.s. t60 that worked over 10 years?
15:46:10 <mzar> you can install FreeBSD on more recent hardware
15:46:43 <mzar> ig4 touchpad works, touchscreen too
15:50:22 <ketas> ig4 is what?
15:50:38 <ketas> and yes i could
15:54:28 <polarian> nimaje: I will try this then, and if not I will do what ridcully has done... thanks for all the help <3
15:54:36 <rwp> polarian, In /etc/rc.conf you cannot have duplicate variables. Later assignments overwrite earlier assignments. Your previous cloned_interface="bridge0 tap0" is normal. Add ifconfig_bridge0="addm eth1 up" ifconfig_tap0="up" with whatever names your system needs.
15:55:35 <polarian> rwp: I am aware... that wasn't my question... my question was can you mix arguments kaa... ifconfig_bridge="inet 192.168.43.21 netmask 255.255.255.0 addm eth0 addm eth1"
15:55:45 <polarian> would that be valid or invalid
15:56:09 <polarian> I am unsure how freebsd would interpret it... as an ifconfig command it would be invalid, but what about in rc.conf?
15:56:36 <rwp> Any valid ifconfig command is valid there.  If you can run the command from the command line as an ifconfig command then it can be used in an ifconfig_bridge0 setting.
15:56:56 <rwp> ifconfig processes option arguments left to right across the argument list.
15:57:39 <rwp> The only thing you are missing is that ifconfig_bridge does not match the pattern ifconfig_${name} and name is bridge0 or bridge1 or tap0 some such.  So it needs to be ifconfig_bridge0 there.
15:57:54 <rwp> Or ifconfig_bridge1 or ifconfig_tap0 or whatever named interface you are configuring.
15:59:16 <rwp> Saying a different way for clarity, if you can successfully run "ifconfig bridge0 inet 192.168.43.21 netmask 255.255.255.0 addm eth0 addm up" from the command line and it works then the same is a valid setting in the ifconfig_bridge0= variable setting, without the "ifconfig bridge0" part because that's in the name.
16:00:05 <rwp> You probably want to add "up" as well to make sure the interface is marked up so it can pass packets.  Not bringing interfaces up is a typical snag I hit myself often.
16:00:43 <rwp> There is a sysctl setting for automatically marking tap interfaces up on open to avoid snags for tap devices too.  net.link.tap.up_on_open=1
16:01:50 <polarian> rwp: oh...
16:01:55 <polarian> it does work from ifconfig
16:02:05 <polarian> in the man pages and handbook it always is ran separately
16:02:20 <polarian> I assumed it didn't work... so ifconfig can do all configuration in a single line... if so then that solves ALL my issues :P
16:03:18 <rwp> I can't remember if the rc script parses the argument list itself and then runs the commands separately or not.  It might.  But the effect will be the same in either case.  So actually it doesn't matter to us.  We can put the list of commands all in that one variable for it and it is okay.
16:04:34 <rwp> Also, instead of the old-style 192.168.43.21 netmask 255.255.255.0 which is still and always will be okay it's more compact to use the CIDR style 192.168.43.21/24 and so I definitely prefer seeing the more compact style now.  Just less to read.  Lines are shorter.
16:05:46 <ketas> yeah use cidr
16:06:12 <ketas> while there, set IFCONFIG_FORMAT=inet:cidr,inet6:cidr
16:07:01 <rwp> Let me say again just for clarity that the rc scripts actually call the ifconfig command.  I always test out what I want to do on the command line first.  Then I put those settings in the rc.conf.  Then I clear everything out (ifconfig bridge0 destroy, and destroy everything else back to nothing) and test the settings by running the rc scripts.
16:07:18 <ketas> and uptime to env LC_TIME=de_DE.ISO8859-15 uptime or so
16:07:22 <ketas> oh well
16:07:48 <rwp> I always work on a system with console access.  Usually I do this from the console.  So I don't have fear that I will lock myself out of the system.
16:08:09 <ketas> why ifconfig can't do ether ... inet in one go?
16:08:25 <ketas> however if you run it twice...
16:09:17 <ketas> internally it can do whatever it wants in meaning of order
16:09:34 <rwp> ketas, Please say more?  I don't understand the point you are making.
16:09:55 <polarian> rwp: funny enough, I CIDR when it comes to IPv6
16:10:00 <polarian> but for some reason I like sticking netmask :32
16:10:18 <ketas> i mean i can't set mac and ip to if in one command
16:10:25 <ketas> just doesn't work
16:10:27 <polarian> then
16:10:29 <polarian> how would you do that
16:10:31 <polarian> in rc.conf
16:10:43 <ketas> supposedly families conflict
16:10:45 <polarian> on OpenBSD hostname.if(4) uses newlines to separate commands
16:10:55 <rwp> ketas, Can you give an example?  Because I mean ifconfig can process a very long list of things.  Like the example I posted above.
16:11:09 <polarian> but rc.conf(5) doesn't seem to support multiple commands
16:11:32 <polarian> so either it allows the entire interface config in a single line... or theres a limitation on what you can do on rc.conf
16:12:36 <rwp> Hmm...  Looking at "man rc.conf" I see at least one example of multiple commands ifconfig_wlan0="DHCP WPA mode 11b" but that's it.  It would be nice if it gave a more complicated example for em0 or something.
16:13:02 <rwp> But we only run into this usually with jails and bhyve and so I guess those examples get explained in more detail in that side of the documentation.  Maybe.
16:13:43 <polarian> rwp: agreed...
16:14:01 <polarian> the handbook separates them into commands, but does not talk about what to do in rc.conf either...
16:14:34 <rwp> polarian, I am not familiar with OpenBSD's details.  I have run it sparingly.  Mostly for a reference and not in actual use where I get a lot of experience with it.  So I don't know about hostname.if and am reading the man page for it now.
16:16:20 <ketas> rwp: go and literally run: ifconfig bridge30000 create ether aa:aa:aa:aa:aa:aa inet 1.1.1.1/32
16:16:37 <ketas> that doesn't work!
16:16:44 <rwp> So far if I want to do more than what can be done all at once then I do those other things in the jail.conf file where one can run multiple lines using exec.prestart and exec.poststop.
16:17:02 <ketas> when it didn't work in init, i went and look why
16:17:10 <ketas> and i was surprised
16:17:26 <ketas> without create it won't, either
16:17:31 <polarian> rwp: ketas what the fuck? why would you have 30,001 bridges!!!
16:17:55 <ketas> as namespace reasons
16:18:03 <rwp> polarian, That command doesn't work because it doesn't work though not because it is all on one line.
16:18:10 <ketas> but this was example
16:18:13 <polarian> rwp: I know but still
16:18:18 <polarian> why would you have 30,001 bridges
16:18:26 <rwp> Oops.  s/polarian/ketas/ there.
16:18:49 <ketas> no it should
16:19:01 <ketas> but it can't do l2 and l3 at same time
16:19:07 <ketas> funnily
16:19:46 <ketas> kernel happily accepts it all in both ways sequenced
16:19:58 <ketas> ifconfig is just nooope fu
16:20:53 <ketas> then you need to put one as _alias0=
16:21:25 <ketas> took for a while to realize
16:22:50 <rwp> ketas, That looks like either a bug in ifconfig or a limitation in ifconfig.  Something that could be improved in ifconfig.
16:22:58 <ketas> yeah
16:22:58 <rwp> Using alias0 is a nice hack for it.
16:23:33 <ketas> but yes i do have epair10000
16:23:36 <ketas> and 20000
16:23:57 <ketas> not 10000 of epairs
16:24:10 <ketas> unsure how much memory one took
16:26:30 <ketas> > ifconfig -l
16:26:31 <ketas> em0 lo0 bridge1 bridge3 bridge10000 bridge10001 bridge10002 bridge10003 tap4 tap5 tap6 tap10000 tap10001 tap10002 tun20 lagg0 epair3a epair3b epair10000a epair10001a epair10002a epair10003a epair10004a epair10005a epair10006a epair20007a vlan1 vlan3 vlan4 vlan7 vlan9 vlan40 vlan60 vlan61 vlan62 vlan63 vlan64 vlan65 pflog0
16:26:37 <tsoome> dvl :)
16:26:41 <ketas> in the end i have this
16:26:47 <ketas> not thousands
16:27:52 <ketas> epair is total legit reason for ether x inet y
16:30:35 <ketas> i didn't want to rename them either altho i could
16:31:10 <polarian> rwp: but this limitation is then a issue
16:31:14 <polarian> if rc.conf only accepts a single command
16:31:38 <polarian> either 1. rc.conf supports multiple ifconfig commands per interface or 2. ifconfig can configure an entire interface in a single command
16:31:42 <polarian> otherwise you run into limitations
16:33:35 <rwp> It's definitely a limitation with regards to ketas' ifconfig limitation of setting both the ethernet link address and the IP address.  That feels like a bug in ifconfig to me.
16:34:26 <rwp> So far I personally have not needed to control the MAC address of a bridge.  So I haven't run into that case yet myself.  Though I could see a VPS providing having MAC filtering and therefore it being a requirement in some environments.
16:34:31 <polarian> ketas: maybe report this as a bug then?
16:34:40 <ketas> it's known
16:35:04 <rwp> And as far as managing epairs I always do those things in jail.conf in exec.prestart and such and so for me it hasn't been a limitation.
16:35:07 <polarian> well according to if_bridge(4) the bridge mac address is assigned randomly within the local range, it should never conflict
16:35:22 <polarian> so the need for changing mac is low
16:35:39 <ketas> maybe i could move it to jail.conf but still
16:35:41 <polarian> which, if it is a bug, is likely why its unpatched then if its known
16:36:04 <rwp> I vaguely recall there is a setting that causes bridge ethernet link addresses to inherit from the first associated member but can't find the docs on it now.
16:36:12 <polarian> ketas: you could run it as a script
16:36:14 <polarian> https://docs.freebsd.org/en/articles/rc-scripting/
16:36:20 <polarian> this will run on startup then
16:36:40 <ketas> rc.conf was simpler for now
16:36:54 <rwp> That's what I would do too.  If I need something really custom then I put it in a script.
16:37:22 <polarian> hey its a good patch for someone who wanted to get into freebsd contributions
16:37:25 * polarian is too stupid
16:37:43 <ketas> http://ketas.si.pri.ee/ask-m-001/jail.conf
16:38:08 <ketas> probably could improve
16:39:03 <ketas> i can't really figure out how to patch ifconfig for that, properly
16:39:35 <ketas> i also wish uptime could do 24h clock, maybe on option, and uptime in secs with option too
16:40:11 <ketas> had to use separate util for that which i badly wrote in c
16:41:01 <ketas> some patches i could even submit
16:41:26 <ketas> like one which configures whatever wifi if is there, automatically on init
16:41:42 <ketas> iirc it's still not there
16:43:26 <ketas> there are no fallbacks like ifconfig_DEFAULT
16:46:11 <ketas> what used to work is in http://ketas.si.pri.ee/bbb/src-patches/rcng-wlan_autoconfig.diff
16:46:30 <ketas> i currently haven't place to test it anymore
16:46:57 <ketas> it allowed me to not known what driver the random usb wifi used
16:55:12 <ketas> likely noone else will submit it than me?
16:55:42 <ketas> however with ifconfig i'm unsure if i can do it
16:56:27 <ketas> init one is already a hack
17:17:57 <ketas> rwp: i wanted my macs to stay put, instead of changing every boot, as ll's come from them and therefore v6 ips, and if you dhcp it like my jails are, then v4 ones too, now you need fixes macs on host or jail
17:18:18 <ketas> on bridge and on epairs
17:19:16 <ketas> also less of a confusio where the hell is mac actually located at
17:20:47 <ketas> i also stole mac prefix from phys nic
17:21:05 <ketas> naughty
17:22:03 <ketas> so i know whatever participates in network comes from single machine
17:30:58 <archer72> Quick question.  I found a Pi with some sort of BSD on it.  Is there a command to tell which Pi version and which BSD it is?
17:32:50 <vkarlsen> archer72: If it is running, uname -a should tell you some things about the OS
17:34:10 <archer72> Ahh TY vkarlsen I forgot about that one
17:34:39 <archer72> FreeBSD PiBSD 13.1-RELEASE FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac2212 GENERIC arm
17:39:13 <archer72> I tried `pinout` but that didn't exist on my system to show the Pi version.  I suspect it is a version 2
17:43:19 <rwp> ketas, For my use I am always doing static IP assignment so they are not ever going to change regardless of dynamic ethernet address.
17:44:18 <rwp> archer72, On most systems of the various types BSD & other these days this will yield useful information: cat /etc/os-release
18:06:22 <archer72> I found my Pi 1.  Does FreeBSD run on this?
18:09:20 <archer72> rwp https://pastebin.com/nkf147mE
18:18:36 <nimaje> freebsd is removimg support for armv6 as it is an old legacy architecture
18:27:07 <ketas> nbsd works iirc
18:32:36 <rwp> archer72, Yep!
18:33:47 <rwp> I don't know the history but /etc/os-release is where all of the current operating systems that I interact with place information about the running release.
18:34:22 <rwp> Probably can't be counted upon in an absolute sense.  But across my collective that's the one place where every system puts interesting descriptive information about their release.
18:49:08 <hc> So how's the FreeBSD project doing these days? I love FreeBSD, I use it on almost all of my servers
18:49:37 <hc> Hope for the project to continue to exist for a long time :) It's the best OS out there right now imho
18:49:52 <hc> (Just a random thought)
18:50:16 <sfox_> it kernel panics constantly
18:50:30 <sfox_> from several year old kernel page fault bugs
18:50:39 <sfox_> still open due to lack of manapower
18:51:54 <hc> Hmm, is FreeBSD getting new hackers from the younger generations?
18:52:11 <hc> (while I use it daily I don't really keep track of the mailing lists, etc.)
18:52:16 <sfox_> idk
18:54:50 <hc> sfox_: Just curious, have you got a link to the bug you mentinoed?
18:55:31 <sfox_> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
18:55:34 <hc> Thanks
18:56:00 <sfox_> it's got several bug numbers from multiple people reporting it over the years, but this is one of the older ones
18:56:13 <hc> Fun fact: A long time ago I tried to do a freebsd project under the GSoC. I was in brief contact with a maintainer but they stopped responding altogether after a few emails, I found that a bit rude
18:56:27 <hc> Haven't tried to get active within the project since, but still like it very much as a user:)
18:56:36 <hc> I think that was around 2008 or so
18:56:52 <sfox_> i tried adding the workaround of exec.poststop = "sleep 2";
18:56:53 <sfox_> but unfortunately that no longer prevents crashing anymore in 14.1-R
18:57:55 <hc> That bug sounds to me like people are unsure as to the root cause?
18:59:56 <sfox_> it's related to VNET's networking code
19:00:07 <sfox_> it's been reproduced in both virtual machines and bare metal
19:04:34 <sfox_> i'm not sure how the root cause could still be unknown. I can provide core dumps to developers if need be
19:16:20 <bbrtj> I'm having a problem with acpi_video after upgrading to 14.1 from 14.0. All sysctl variables for brightness are there, but changing them don't do anything. hw.acpi.video.lcd0.active is 0 and cannot be changed to 1. acpi_video kernel module is loaded after drm. What am I missing?
19:17:02 <mzar> 4
19:17:04 <mzar> err
19:21:37 <bbrtj> Ah I see there's now a backlight program and it works. Neat, not sure if it existed before
20:08:32 <ant-x> Hello, all. The networkmgr utilty must be auto-started via sudo, but won't. .xsession-errors tells me I must use an askpass helper. What is the FreeBSD way to let a sudo command succeed during the X login, wihtout user interaction?
20:11:20 <ant-x> The solution to my problem here says I should add the user to the `wheel' group: <https://forums.freebsd.org/threads/networkmgr-in-applet-tray-not-appearing-after-login.92383/#post-645155>. Are there any alternatives?
20:12:00 <ant-x> (seems a bit dangerous just to let a GUI network manager autostart)
20:14:17 <skered> ant-x: You could set the sudo entry to run the command be password free.
20:15:04 <ant-x> skered, OK: via what mechanism?
20:16:30 <skered> Look at /usr/local/etc/sudoers for a NOPASSWD example.  The man page for sudoers as well.
20:18:08 <skered> er well that might not work if this is an X application?
20:19:27 <skered> If the user can run sudo `sudo ...` where ... is the path to the application run/appear in X?
20:19:53 <ant-x> Thanks, waity-minty.
20:20:51 <ant-x> Yeah, I am a sudoer in the `sudoers' file: <mylogin> ALL=(ALL:ALL) ALL
20:21:13 <ant-x> I can use sudo commands in the X terminal, but the first time I have to enter the root password.
20:21:27 <ant-x> Will look into NOPASSWD
20:22:17 <skered> Ok then maybe it will work.  Running X application as a different user than who is logged in can sometimes be a pain due to DISPLAY/XAUTHORITY unset/mismatch
20:22:57 <skered> There's also doas (sudo like) that can help here too.
20:23:14 <ant-x> I see: I can make the user a NOPASSED sudoer: too much for a single application.
20:25:27 <ant-x> Is there a way to enable a passwordless sudo invocation of /that one/ program for /that one/ user?
20:30:36 <skered> Yes.  You might want to also look at doas.  Its config is a bit simpler but less fearure rich as sudo.
20:31:52 <ant-x> skered, ... and shall I then replace `sudo` with the corresponding `duas` in my autostart .desktop file?
20:32:18 <skered> doas but yes.
20:34:25 <ant-x> That was a typo. Thanks. So, there are three optons: 1) make the user a NOPASSED sudoer; 2) same thing with `doas`, and 3) add the user to the wheel group.
20:37:19 <skered> I wouldn't be surprised if you still need to be in wheel for other things.
20:37:46 <skered> I would have maybe expected xfce to use polkit to allow this type of access.
20:40:58 <ant-x> skered, polkit is starge: it requires JavaScript programming!
20:41:03 <ant-x> * strange
20:41:31 <skered> Once you get it you get it.
20:41:57 <skered> and that's after all the security issues it has had.
21:00:59 <rwp> ant-x, BSD has this extra security layer that if you are not in the wheel group then you are blocked from root access.
21:01:16 <rwp> Use of the name "wheel" is a joke name because if you are in the wheel group then you are a "big wheel" https://idioms.thefreedictionary.com/a+big+wheel
21:01:46 <rwp> Without being in the wheel group so that one can su or sudo to root then one can only login as root from the console.
21:01:57 <ant-x> "I wanna roll like big wheel, across a Georgeia cottonfield!" -- I love Joe Turner.
21:02:38 <ant-x> How I have inserted a USB stick. How do I find out which device it is?
21:02:53 <rwp> The default sshd_config is PermitRootLogin=no so one can't ssh in as root either unless that is changed.
21:03:23 <ant-x> rwp, Thanks, there is a lot of mechanisms. I am not on SSH, though.
21:03:32 <rwp> ant-x, I "tail /var/log/messages" and see what device it just created.  Probably /dev/da0
21:04:15 <ant-x> rwp, Ouch! "logfile turned over due to size > 1000K (-:
21:04:29 <ant-x> (tail won't show anything)
21:04:35 <rwp> Then look at the previous file.
21:05:15 <rwp> zless /var/log/messages.0.bz2 would be my choice and then G to get to the end of the file.
21:05:34 <ant-x> You guessed right: it was /dev/da0. Hmmm! there should a transparent way of examing the last log records that took care of the log rotation.
21:05:57 <rwp> On SATA based systems the disks will be /dev/ada0 ada1 ada2... but on SAS/SCSI based systems they will be /dev/da0 da1 da2... so on SAS systems one must be super careful not to get the wrong device!
21:06:22 <rwp> But on SATA systems it is safer because only USB will be using the da0 type naming.
21:07:25 <rwp> On my SATA desktop I add this following /etc/devfs.rules files entries.  https://paste.debian.net/plain/1322626
21:08:08 <rwp> That changes the permissions on USB devices to be 0660 writable by group wheel.
21:08:31 <rwp> And then I can write to inserted USB devices as me without needing su or sudo.  Seems a lot safer.  I can't wipe out my disk when working as me.
21:09:08 <rwp> Don't do that on a SAS system though as that would be too risky there as it would also affect the system disk drives on those systems.
21:09:29 <ant-x> Thanks for the tip. I have not yet tried to write to USB stick as normal user.
21:10:10 <ant-x> rwp, then one could intercept an automount event and set the permissions there. Ingternal HDDs do not automount.
21:10:49 <rwp> Cool!  If you write it up please send me the instructions for it!
21:12:39 <ant-x> Indeed, I can't write to USB sticks as normal user.
21:13:34 <ant-x> rwp, This time, I am preparing this laptop for a colleague, so not sure... I have written up a script for exponential brightness control, which was non-trivial!
21:22:54 <ketas> hmm why exp?
21:25:26 <ketas> transparent way to look rotated logs?
21:25:33 <ant-x> ketas, because the starndard ACPI interface, at each Fn keypress changed the brightness level by 1 point of 100, so that it took ages to adjust it.
21:26:08 <ant-x> ketas, Yes: to access the last n entries even if part of them are in in rotated an archived log file.
21:26:22 <ketas> like zfgrep boo /var/log/messages* ?
21:26:56 <ketas> oh
21:27:50 <ant-x> Yes, I think so.
21:29:14 <rwp> zfgrep boo /var/log/messages* will list them in an inopportune order for my taste.  Reversing the file order would grep entries in time order.
21:29:43 <ketas> ( zcat /var/log/messages.?.* ; cat /var/log/messages ) | tail
21:30:34 <ketas> assuming they aren't large
21:33:08 <ketas> that's still wrong
21:33:14 <rwp> zgrep foo $(ls -t1 /var/log/messages*)
21:33:41 <rwp> Sorry, reverse that.  zgrep foo $(ls -rt /var/log/messages*)
21:34:21 <ant-x> Guys -- I am trying those now, have to learn some basic shell scripting first.
21:34:36 <rwp> That will list entries in a more intuitive time order.  But I don't like using the output of ls -t there as it feels icky since it isn't really an explicit command and might be wrong.
21:35:08 <ant-x> Perhaps a decidcated script/program?
21:35:22 <rwp> I would like to use "tac" (which prints lines in reverse) but it is not in base.
21:36:51 <la_mettrie> tail -r works like tac
21:37:57 <ant-x> ...Has anybody got Wine working on their FreeBSD machine? A freshly insalled Wine on mine complains that i386-wine-pkg/user/local/bin/wine does not exists and asks me to install 32-bit Wine with: /usr/local/share/wine/pkg32.sh . This is not right for my amd64 laptop...
21:38:57 <ketas> find /var/log -depth 1 -name 'messages*' | sort -r | xargs fgrep dhcp
21:39:23 <ketas> from shell to ls isn'y ideal indeed
21:39:47 <ketas> shell expands *, then ls sorts it
21:39:50 <ketas> it works
21:41:43 <ketas> (z)
21:41:55 <rwp> The find case is fun.  Though I would do it this way: find /var/log/messages* -name 'messages*'
21:42:40 <rwp> I hadn't thought about sort -r.  With that I might do: echo /var/log/messages* | tr ' ' '\n' | sort -r
21:42:50 <ketas> shell expands * again
21:42:53 <ketas> here
21:42:56 <ketas> it's fine
21:43:08 <ketas> yeah echo * is fine too
21:43:09 <rwp> What's wrong with having the shell expand the *?
21:45:20 <ketas> echo /var/log/messages* | xargs -n 1 | sort -r | xargs zfgrep boo
21:45:22 <ketas> nothing
21:45:45 <ketas> but ls * is like double task
21:45:58 <ketas> fine for oneliner you do once
21:46:24 <ketas> tr eh
21:46:30 <ketas> works
21:46:36 <rwp> I think "tr ' ' '\n'" is lighter weight than "xargs -n 1".
21:46:54 <ketas> yes
21:47:10 <rwp> I would prefer not "ls /var/log | grep messages" as that might produce significant character I/O that is not needed.
21:47:10 <ketas> i have xargsy habits
21:48:20 <ketas> oh text manip tools are fub
21:48:21 <rwp> I do often do things like this when searching through crontabs and not knowing where something was located: find /etc/cron* /usr/local/etc/cron* -type f -exec grep foo {} +
21:48:25 <ketas> fun
21:48:37 <ketas> like tr ' ' + | xargs bc
21:48:48 <ketas> for number adding
21:49:15 * rwp must run off, TTFN!
22:00:41 <jbo> cracauer
22:04:58 <polarian> bsdconfig(8) seems interesting
22:05:07 <polarian> not my cup of tea using a tui but its still cool
22:18:50 <cracauer> ?
22:23:00 <jbo> we're having so much fun, aren't we?
22:34:58 <cracauer> Well, it is a legitimate regression on 14.1 (probably) and I don't want to deal with Windows, so there I go. I just wish he would start running `make world`s already instead of fiddling with the commit list.
22:36:07 <jbo> many (and I really mean many) of us have tried to help that guy over the years. It's tedious.
22:43:30 <cracauer> Well, it better be today. I have work-work tomorrow :-)
22:45:36 <jbo> heh :p
22:45:43 <jbo> better don't F5 then
23:16:09 <archer72> I had help on the Raspberry pi front.  `sysctl hw` gave me what I was looking for.
23:17:25 <archer72> hw.fdt.model: Raspberry Pi 2 Model B Rev 1.1
23:18:42 <archer72> ATM, I'm git cloning NanoBSD for Pi 1.
23:32:52 <jbo> use --depth 1 if you git clone and don't need the full history
23:32:58 <jbo> greatly improves perf