have | Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ | 02:07 |
---|---|---|
nacelle | thats... lovely. | 02:32 |
nacelle | :( | 02:32 |
DocScrutinizer | and reverting back to moderated mode | 07:40 |
nacelle | ouch | 09:18 |
Joerg-Neo900 | ouch? | 10:18 |
DocScrutinizer | didn't show up on homepage | 13:43 |
DocScrutinizer | ? | 13:43 |
DocScrutinizer | hi! | 14:01 |
Wasp | Hi, can anybody tell me what is gid 4 by default? | 20:39 |
Wasp | I have /var/log/messages for example on gid 4 but no group in /etc/group under that id | 20:39 |
Wasp | is it adm? | 20:40 |
ik5pvx | on debian it is | 20:40 |
Wasp | for some reason adm is on 5 for me | 20:40 |
Wasp | thats nto good | 20:40 |
ik5pvx | isn't the number totally irrelevant, so long as it is consistent? | 20:41 |
Wasp | yeah probably it is but that means I accidently changed AND saved it | 20:41 |
ik5pvx | on a devuan beowulf it is adm=4 as well | 20:41 |
Wasp | yeah thank you | 20:42 |
ik5pvx | although this was cloned and upgraded from a stable release | 20:42 |
Wasp | put it on 4 again | 20:42 |
Wasp | 5 was adm and tty at the same time | 20:42 |
ik5pvx | ahh, ok | 20:42 |
Joerg-Neo900 | a system admin question: what's wrong with granting others (world) read access to /dev/rtc0 (chmod o+r /dev/rtc*) ? | 20:47 |
MinceR | perhaps timing attacks in association with side channels in cache (for speculative execution exploits and others)? | 20:54 |
Joerg-Neo900 | MinceR: hmm, thanks. Gathered as much as it being something very exotic | 20:56 |
Joerg-Neo900 | MinceR: though I can't see how particularly cmos clock is any useful for such attacks | 21:00 |
DocScrutinizer | my google fu sucks at this question | 21:09 |
Wasp | Is there any command to find out if my insert harddisk/sata got physical connected? | 21:13 |
Wasp | cannot see it on fdisk | 21:13 |
Wasp | `echo "- - -" > /sys/class/scsi_host/host13/scan` doesn't show it up as well | 21:14 |
Wasp | even though I'm not sure about host13 | 21:14 |
Wasp | the lead on the rack/drawer of the disk is on .. but besides that it has power I cannot tell me anything more | 21:17 |
Joerg-Neo900 | a quote I kept: <Pali> Joerg-Neo900: command for rescaning sata devices on bus <n>: echo \"- - -\" >/sys/class/scsi_host/host<n>/scan"' | 21:17 |
Wasp | Joerg-Neo900: okay, but that's exactly what I've done ;) | 21:18 |
Joerg-Neo900 | I don't know anything but listening to the drive then | 21:18 |
Wasp | first of all I don't know which bus it is but dispite that I ran already through all busses except for host4 where the current running linux is on | 21:18 |
Wasp | ehm .. there are more disks in the box than this one | 21:19 |
Joerg-Neo900 | maybe you're using a bus that got disabled in BIOS? | 21:19 |
Wasp | even thouch gives some vibrations but for real it could be also from any other disk just transported over the box | 21:19 |
Wasp | no, the bus should be fine. Used it regularly on freebsd | 21:20 |
Joerg-Neo900 | it's not unusual that esata and one internal sata bus share one interface and id | 21:20 |
Joerg-Neo900 | use another SATA cable. I seen those critters fail just so often | 21:21 |
Wasp | funny that kern.log tells me ata5 but dev is something sd.. what the hell .. which one is it now | 21:28 |
Wasp | I'll reboot and I tell you it will be fine | 21:41 |
Wasp | supprise supprise: after reboot it get recognized | 22:32 |
Wasp | and it was ata8, on bus/host 7 | 22:34 |
Wasp | I scanned it | 22:34 |
Wasp | before I mean, nothing happened | 22:34 |
Wasp | I'll check bios later. Read that on some boards there is an option to disable/enable hot plug | 22:41 |
Joerg-Neo900 | yep | 22:51 |
Joerg-Neo900 | and SATA isn't originaly designed to support hotpkug iirc. So it's not too unusual that only first device attached gets proper initialization, on some hw even only when attached during power-up | 22:53 |
Joerg-Neo900 | for sure hotplugging is one of SATA's least thoroughly tested features | 22:54 |
Wasp | Joerg-Neo900: it shouldn't be a hardware issue since I use it regular on freebsd. The only thing I can imagine since my bios resetet for random reason, that something got reset and I forgot to enable it again | 23:36 |
Wasp | However devuan/linux/kde I dont know for real runs pretty un-smooth .. that's also why bios reset after a freeze of linux | 23:37 |
Wasp | I mean "why" .. I don't know why but just happens during this incident | 23:38 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!