=== mbiebl [n=michael@e180126205.adsl.alicedsl.de] has joined #upstart === hunger_ [n=tobias@p54A71F89.dip0.t-ipconnect.de] has joined #upstart === mbiebl [n=michael@e180126205.adsl.alicedsl.de] has joined #upstart === joh6nn [n=joh6nn@24-177-251-138.dhcp.nwtn.ct.charter.com] has joined #upstart [06:21] i'm trying to add a script to my boot process to turn off dma on one of my hdds (long story), and i'm very clearly going about it the wrong way, but i'm not sure where i'm falling down [06:21] i've looked through the wiki and the getting-started page, but i'm guessing that's only taught me enough to be dangerous, not enough to get this working [06:41] /etc/rc.local =) [06:43] just stuff it in there and it should work? [06:44] uh huh [06:44] thanks, i'll give that a shot [06:45] alternatively, is there a better way to disable dma for a drive at boot? [07:12] er. wasabi__, i must be missing something. rc.local is a basically no-op script. were you just suggesting i shove my one line in there, since it's there anyway? [07:12] uh huh [07:13] it's run during boot. it's for local stuff... to run during boot [07:13] this has nothing to do with upstart, btw. =) [07:14] yeah, normally, that'd be a fair enough answer to the question. unfortunately, i'm needing to set /dev/hdd to dma = off round about the time that the init-top scripts start getting run (possibly sooner; i may be mis-remembering at that point) [07:15] that would be in the initramfs [07:16] yeah, that was where i tried to add it first. i stuffed my own little script in there in init-top, but there's seemingly more to it than just adding new scripts to the directory; it didn't appear to run [07:17] have to rebuild hte initramfs [07:17] dpkg-reconfigure the kernel package [07:18] also, i dont think your drives will exists in init-top [07:18] maybe. ;) [07:18] that can't be right; i need to reconfigure the kernel package just to add a new boot script? [07:20] uh huh [07:20] that's hte initramfs [07:20] initramfs != boot scripts exactly. [07:22] ok, well, then i'm clearly going about this the wrong way. there's gotta be a better way of changing this setting then [07:23] i'd like to know why you have to change it [07:24] if it i don't, it hangs and doesn't finish booting. at a guess, the BIOS in the box isn't very good, and isn't properly handling the dma settings for the drive [07:24] hmm. [07:25] well, how far does the boot get? [07:25] gets to scanning to see what IDE devices are connected, and hangs at /dev/hdd [07:26] i've tried setting it in /etc/hdparm.conf, too, but that doesn't have any visible effect [07:26] It's going to be a bit hard to tell the kernel not to use dma on a device before the kernel hsa discovered hte device. [07:29] yeah, i'm grasping at straws, really [07:29] also, im not sure if the kernel even enables dma automatically in the initramfs or before [07:29] i've tried setting it with hdparm, and then rebooting, but that doesn't work. i'm guessing it's not working because the BIOS sees that the drive supports DMA, and turns it back on [07:30] hdparm affects transient kernel settings. [07:30] it doesn't save [07:30] ah [07:31] would be nice if the man made that clearer, eh? ; ) [07:33] well, anything that "saved" in linux would have to have someplace to 'save it' [07:33] hdparm.conf is that [07:35] off to bed. sorry i can't help ya much [07:35] night === j_ack [n=rudi@p508DBB33.dip0.t-ipconnect.de] has joined #upstart === joh6nn [n=joh6nn@24-177-251-138.dhcp.nwtn.ct.charter.com] has left #upstart [] === juergbi [n=juerg@80-219-19-246.dclient.hispeed.ch] has joined #upstart === jonib1 [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === Amaranth_ [n=travis@ip72-198-200-109.om.om.cox.net] has joined #upstart === Keybuk [n=scott@wing-commander.netsplit.com] has joined #upstart [12:34] random thought [12:34] the job definition parser currently "ignores" parser errors and just outputs warnings [12:34] should it abort parsing instead? [12:34] I would think so [12:35] because if there is an error, it could cause the rest of it to parse incorrectly and could cause problems [12:35] yeah, especially the unknown stanza bit ... [12:35] ned script [12:35] exec foo [12:35] end block [12:35] will give you [12:35] foo:1: ignored unknown stanza: ned [12:35] foo:2: ignored unknown stanza: end [12:36] but set the job's exec to be "foo" because exec is a valid stanza [12:36] yep === hunger_ [n=tobias@p54A71F89.dip0.t-ipconnect.de] has joined #upstart === j_ack [n=rudi@p508DBC6D.dip0.t-ipconnect.de] has joined #upstart === rwall [n=richard@82-69-197-190.dsl.in-addr.zen.co.uk] has joined #upstart === rwall [n=richard@82-69-197-190.dsl.in-addr.zen.co.uk] has left #upstart [] === wasabi__ [n=wasabi@cpe-76-184-96-5.tx.res.rr.com] has joined #upstart === theCore [n=alex@ubuntu/member/theCore] has joined #upstart === j_ack [n=rudi@p508DBC6D.dip0.t-ipconnect.de] has joined #upstart === Keybuk [n=scott@wing-commander.netsplit.com] has joined #upstart === theCore [n=alex@ubuntu/member/theCore] has joined #upstart === mbiebl [n=michael@e180124027.adsl.alicedsl.de] has joined #upstart