Reputation
4,688
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
10 22
Newest
 Nice Answer
Impact
~82k people reached

Mar
30
awarded  Nice Answer
Mar
24
awarded  Yearling
Feb
4
awarded  Nice Answer
Dec
18
awarded  Enlightened
Dec
18
awarded  Nice Answer
Nov
10
reviewed Approve Having tmux load by default when a zsh terminal is launched
Oct
30
reviewed Approve What does echo $-1 display?
Oct
29
awarded  Good Answer
Oct
28
awarded  Enlightened
Oct
28
awarded  Nice Answer
Oct
28
answered Is it safe to move a file that's being appended to?
Oct
25
comment CentOS IPTABLES how to block requests from router
Only taking a brief look (it's late in the local time zone ;) this seems quiet good. I'd suggest adding multiple REJECT rules at the end, more precisely I'd have rules rejecting with meaningful results depending on protocol (i.e. in this order: -p tcp -j REJECT --reject-with tcp-rst, -p udp -j REJECT --reject-with icmp-port-unreachable, -j REJECT --reject-with icmp-proto-unreachable). I'd prefer making the remote peer believe there is no service running than telling him the service is actively blocked.
Oct
25
revised Why should you not edit the .config kernel configuration file?
added 4 characters in body
Oct
25
revised chromium-browser processes' cmdline not available in full form
fix markup
Oct
25
comment Why should you not edit the .config kernel configuration file?
That's a rather unsatisfying answer. What if I don't change those files? That's like saying »Don't write your sendmail config yourself, you don't want to do this! You should use m4!« Anyways it would be perfectly fine to write it on your own (there are some really weird guys out there ;) ). The usual case being autogenerating files is not a valid reason for HAVING to use those tools.
Oct
25
answered Why should you not edit the .config kernel configuration file?
Sep
30
awarded  Explainer
Jul
11
comment Check ping statistics without stopping
One slight addition: You can emit SIGQUIT from the terminal by hitting "Ctrl-\", no need to have a second terminal open and use kill.
Jul
2
comment Built the kernel with NFS support but not getting /dev/nfs
Why don't you skip the initrd-part and let the kernel do autoconfiguration? Configure your kernel to have everything needed for booting (network drivers, NFS support, …) built-in and enable CONFIG_IP_PNP_DHCP. Would be much easier than fiddling with an initrd.
Jul
1
revised Built the kernel with NFS support but not getting /dev/nfs
added 302 characters in body