[02:28] ubottu: tell Cyd about enter [02:43] ubottu: tell Cyd about codeofconduct [02:43] Cyd is a really fast reader. [02:44] I think he is reading it now [02:44] maybe not [02:44] that's not what 'before' means, gpc >.> [02:44] I know what before means, rww 0.> [02:45] hehe [02:50] It's too bad COPPA doesn't require an apparent-age maturity test too :( [02:51] I think we need #ubuntu-offtopic-unregged. Not because of bots, but because I think the questions would screen out some of our users. [02:52] I'd be fine with that. The unregistered ones have a much higher incidence of annoyingness lately. [02:52] * rww files in the "bad ideas for #ubuntu-offtopic" folder [03:14] rww: Should require a Myers-Briggs test in -unregged too [03:15] Can't get in unless you pass [03:15] or sort people into different rooms depending on type compatibility! [03:31] That'd be fun. Just think of how quiet #ubuntu-offtopic-ISTP would be! [03:41] hey, Howard Stern. Just failed the maturity test right there. === Amaranth__ is now known as Amaranth [04:36] ubottu: tell abhijain about nickspam [04:36] Error: I haven't seen abhijain, I'll let you do the telling. [04:36] ha [04:36] thanks [04:36] ubottu just reinforced your point ;) [04:36] Error: I am only a bot, please don't think I'm intelligent :) [05:55] want me to PM? [05:55] sure [05:59] no response so far [05:59] well not in PM.. [06:02] * tonyyarusso sigh [06:03] he seemed to be deliberately provocative [06:04] Of course, such is the pattern lately. [07:52] FloodBot1 called the ops in #ubuntu-ops-monitor (tiox appears to be abusive - 4) [11:10] didn't think that screen shot was coming....the ident "snot" was familier from a few days ago [12:28] i need to complain with some official ubuntu people [12:29] lets see [12:47] support questions via PM from jungli [12:48] from where/what nick ? [12:48] just report it to freenode as he's known and been told to stop it [12:49] ahh spicemaster [14:17] * [DrummerBoy38] (~bearblack@pool-72-91-149-20.tampfl.fios.verizon.net): Burt durt smurt [14:18] judging by the commentary that's hoober et al [15:18] bazhang called the ops in #ubuntu-offtopic (eternal) [15:19] looking [15:19] he's abusing all and sundry [15:20] sorry, didn't have it all on screen [15:20] thanks. tried to PM him but he just kept escalating abuse [15:20] thank you [15:26] bazhang: the "bearblack" ident confirms your suspicions. [15:27] tonyyarusso, I'd thought 'Hoober' was banned in #ubuntu , perhaps a ban evasion [15:32] yup [15:43] now he is cursing in -il [15:43] eternal that is [15:43] I'd tried to ping an op from there [15:44] bazhang: אם אין כאן כוסיות אני הולך [15:45] thats not good [15:45] ok we need a ban on this troll [15:45] topyli, you around? he's really going overboard [15:52] bazhang: maybe we should give him the chan list, he can dig himself deeper and get banned from all of them [15:53] gpc, nah. mistake on the first one, did not know the extensive issues -il had with him [15:53] uh jussi [15:53] he just wants to disrupt them [15:53] jussi: has a plan I sense [16:01] plan to let him continue abusing people in -ot? [16:01] may as well contact freenode if the -ot ops can't step in [16:02] ? [16:02] what's up [16:02] eternal continually abusing ljl and others. [16:03] I thought the kick was enough of a warning [16:03] longtime issue in -il apparently [16:03] can't do anything with that [17:45] In ubottu, sss said: Where is the terminal? [18:46] what is the cheatcode to show my kernel? i received update through manager. i am expecting a .35 or so from a .34 [18:46] this was regular updates afaik. [18:49] is there an autocomplete feature? intellisense or w/e [18:49] i can barely recall how to list ubuntu version which lists kernel alongside [18:57] DrummerBoy38: you probably meant to ask that in #ubuntu, not here in #ubuntu-ops [18:57] @btlogin [18:57] ubuntu-ops or at bt logic [18:58] wait so ubuntu [18:58] i asked there [18:58] this is not a support channel [18:58] not even kernel changes? [18:58] it looks like ikonia banned you from #ubuntu [18:58] let me check [18:58] no i don't think i was [18:59] last ikonia experience was through this ip address [18:59] if ikonia did, then she unbanned already. i only recall being kicked as a warning of some sort [19:00] today's updates included a kernel versions ending in 35 rather than 34 i see in bootloader. i didn't checked the boot loader, again but is there a command to show the kernel through the console [19:00] again, this is not a support channel, you're better off asking elsewhere [19:01] ok [19:33] bazhang: One -ot op is back from church now if you still need me. [20:44] * tonyyarusso sighs [20:44] Apparently putting /boot on RAID is a bad idea. [20:46] depends on the type of raid [20:47] ikonia: md, level 1 [20:47] that's fine [20:47] I do it all the time [20:47] It *sometimes* works. [20:47] /dev/md0 243M 27M 205M 12% /boot [20:47] never had an issue with it [20:48] But it will randomly decide to not boot, and I have to use an install disk to reinstall grub, and then it works again. No idea why. [20:48] /dev/md0 485M 46M 414M 10% /boot [20:48] I can get to "Grub loading...", but it just hangs forever. [20:48] tonyyarusso: ahhh you've not learnt the lessons...... [20:48] which lessons are those? [20:48] My current theory is that it does this after kernel upgrades, but I haven't looked into it much yet. [20:49] grub, no matter the raid level needs to be applied to the boot sector if each disk pointing at /boot on the raw, non raid disk [20:49] I did that. In fact, the Ubuntu installer installs grub to all of them by default when you use RAID for /boot. [20:49] eg: the installer installs grub to sda pointing at hd0,0 you need to apply grub to sdb pointing at sdb hd1,0 [20:50] yes, it installs to both, but it still points to one [20:50] If by "it" you mean the BIOS, yes. [20:50] eg sda sdb both look at hd0 [20:51] Yes, they do that. [20:51] this only works if there is a total disk failure and removal [20:52] Again, I *did* install grub to the boot sector of all 4 drives. And it still periodically fails to boot, from any of the drives. (changing the boot order in the BIOS does not fix the problem) [20:54] ikonia: Any other bright ideas? [20:55] tonyyarusso: but when you installed it to your drives did you make it point at /boot on it's own disk, or on the master disk [20:55] ikonia: What do you mean by "it" and "point at"? [20:56] sorry, when you install grub did you point grub at /boot on it's own disk, or at the primary boot disk [20:57] I still don't know what you mean. [20:57] actually it's a little different with grub2 thinking about it [20:58] when you install grub it needs to know where grub.conf is [20:58] so grub gets pointed at the partition that contains it [21:00] That would be /dev/md0 [21:01] ok, so change that to point at the local disk [21:01] (local to the disk that grub is installed on) [21:01] What the heck do you mean by "point at"? [21:01] Not to mention "that". [21:01] point at -> tell grub where grub.conf is or menu.lst [21:04] Dude, what step / file are you talking about? It's not remotely clear. [21:04] how do you normally install grub ? [21:08] Well, first off from the installer. [21:08] Alternate CD. [21:08] ok, [21:08] how about if I said to you do it manually ? [21:08] grub-install /dev/sdb; grub-install /dev/sdc; grub-install /dev/sdd; grub-install /dev/sde [21:09] ok, so you'll have to cut me a little slack on grub2 as I've not got my head fully around it's internals [21:10] but with grub when you dropped to a grub shell, you had two core commands "setup" and "root", root told the grub binary that was going to be written to the MBR where to find menu.lst (and a few other files) and then setup told it which mbr to write the binary to [21:10] so in that situation grub on /dev/sda would look at /dev/sda1 (/boot) for the stage files and menu.lst [21:11] If it helps, my entries in /boot/grub/grub.cfg include lines like " set root='(md0)' " [21:12] tonyyarusso: that's fine as that's "post grub boot" references [21:12] it's the bit that happens before it tries to boot anything that's key [21:12] And I just successfully booted after restoring with the install CD, so like I said it sometimes works, but at some point in the future it will cease working. [21:13] and I don't see anything in /etc/default/grub defining where /boot should be, which I assume is what I would need to change. [21:14] tonyyarusso: it's not in a config file (for grub 1) it's set in the data written to the mbr [21:14] ikonia: No, I mean what sets what gets written to the MBR when a new kernel is installed? [21:15] nothing, as that's in grub.conf, that's dynamic [21:15] ikonia: Because, again, it's working right now, but will stop later, without me manually touching anything grub-related. [21:16] /dev/md0 485M 46M 414M 10% /boot [21:16] /dev/md0 457M 33M 400M 8% /boot [21:16] What's your point? [21:16] oops, didn't mean to paste that, sorry [21:17] mouse button stuck [21:17] ah :) [21:19] ikonia: So if it works right now, what could possibly change the MBR to not work later? [21:21] I guess it depends on what was breaking it, the situation you referenced earlier is often caused with grub not being able to see the menu.lst/grub.conf (disk slow to spin up, missing, corrupted etc) hence why I was saying make sure grub looks at it's own disk for that info [21:23] ikonia: One thing I've heard is that maybe the RAID array isn't available yet when grub goes looking for it - does that sound plausible? [21:25] Wait, are you saying the grub on /dev/sdb should be looking for /dev/sdb1/grub/grub.cnf rather that /dev/md0/grub/grub.cnf, just ignoring the RAID entirely? [21:25] tonyyarusso: yes and no, yes, you're right, it's not available as Linux hasn't booted to start it, however it won't look at md0 for the data it needs at that point, it looks at the local physical disk, hence why I'm saying grub at sda should look at sda1 for the info, and sdb look at sdb1 [21:25] tonyyarusso: it will never look at md0 [21:25] oh, hrm [21:25] How would I know whether it's doing that or not? [21:25] that's why /boot could never go on a raid0 partition [21:26] as /boot wouldn't exist until boot, so menu.lst would never be available [21:26] tonyyarusso: not sure how to check with grub2, not fully got my head around the internals [21:27] (did I explain it ok this time, it's hard to get across on irc) [21:27] I think I understand what you're getting at now at least, but not how to implement it. [21:28] grub1....I'm all over, grub2, not fully understood more so with the odd layout ubuntu uses it with [21:30] Well, I'll leave that to muddle over for a while and go deal with concrete hardware things for a while :P [21:30] I'll look into it, it's time I picked it up [21:35] ubottu: tell eXistZ|Away about away [21:57] happy pro bowl night! [22:02] have nice day [23:59] seems to be tag teaming. identical nonsense