Back to Home / #uml / 2007 / 08 / Prev Day | Next Day
#uml IRC Logs for 2007-08-19

---Logopened Sun Aug 19 00:00:25 2007
00:08|-|darious12 [~darius@athedsl-304874.home.otenet.gr] has joined #uml
01:53|-|aroscha [~aroscha@212.154.128.222] has joined #uml
01:56|-|darious12 [~darius@athedsl-304874.home.otenet.gr] has quit [Remote host closed the connection]
02:22|-|aroscha [~aroscha@212.154.128.222] has quit [Ping timeout: 480 seconds]
02:59|-|hfb [~hfb@75.80.37.175] has quit [Quit: Leaving]
07:17|-|horst [~horst@a89-182-66-128.net-htp.de] has joined #uml
08:33|-|jjkola [~jjkola@dsl-olubrasgw1-fe56fb00-241.dhcp.inet.fi] has joined #uml
08:34<jjkola>hello
08:40<jjkola>is there an easy way to modify cowed filesystem when you have borked /etc/fstab file?
08:41<jjkola>other than using uml_moo to remove cow
08:43<jjkola>I already tried using single mode but that didn't help
09:08<caker>jjkola: boot with init=/bin/bash?
09:08<caker>it'll dump you to a command line, then remount root read-write: mount -o remount,rw /
09:13<jjkola>ok, I'll try that as soon as I reboot my server
09:16<jjkola>hmm, I didn't need to reboot my server as I found out that there was still one process which was keeping uml image file open and after killing that process I could boot with that uml image
09:17<jjkola>I got this: [42949492.790000] EXT3-fs: cannot change data mode on remount
09:26<jjkola>I could correct my fstab file by mounting it when running some other uml in single mode (those others also have borked fstab)
09:28<jjkola>by the way I found out that if I try to remove one of the ubd devices when the ubd device points to non-existent file that it will panic the uml
09:36<jjkola>wohoo, I could get my umls back up and running
09:37<jjkola>now if only I could rectify the network problem which has forced me to make umls reboot every half an hour to keep network connections from stalling...
11:10|-|Blissex [~Blissex@82-69-39-138.dsl.in-addr.zen.co.uk] has joined #uml
12:14|-|besonen_mobile [~besonen_m@71-220-238-128.eugn.qwest.net] has joined #uml
12:21|-|ram [~ram@pool-71-245-102-10.ptldor.fios.verizon.net] has quit [Ping timeout: 480 seconds]
12:26|-|ram [~ram@pool-71-245-102-10.ptldor.fios.verizon.net] has joined #uml
12:59|-|Blissex [~Blissex@82-69-39-138.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer]
13:10|-|horst [~horst@a89-182-66-128.net-htp.de] has quit [Remote host closed the connection]
14:09|-|horst [~horst@a89-182-66-128.net-htp.de] has joined #uml
15:35|-|mgross [~mgross@pool-71-245-102-239.ptldor.fios.verizon.net] has joined #uml
15:52|-|richardw [~richardw@M247P022.adsl.highway.telekom.at] has joined #uml
16:36|-|richardw_ [~richardw@M385P000.adsl.highway.telekom.at] has joined #uml
16:43|-|richardw [~richardw@M247P022.adsl.highway.telekom.at] has quit [Ping timeout: 480 seconds]
16:59|-|richardw_ [~richardw@M385P000.adsl.highway.telekom.at] has quit [Quit: Leaving]
17:36|-|krau_ [~cktakahas@189.12.70.196] has joined #uml
17:42|-|krau [~cktakahas@201.32.148.171] has quit [Ping timeout: 480 seconds]
18:02|-|cktakahasi [~cktakahas@201.32.145.54] has joined #uml
18:09|-|krau_ [~cktakahas@189.12.70.196] has quit [Ping timeout: 480 seconds]
18:45|-|aroscha [~aroscha@213.211.74.10] has joined #uml
18:47|-|horst [~horst@a89-182-66-128.net-htp.de] has quit [Remote host closed the connection]
19:17|-|jjkola [~jjkola@dsl-olubrasgw1-fe56fb00-241.dhcp.inet.fi] has quit [Quit: *pop*]
19:18|-|aroscha [~aroscha@213.211.74.10] has quit [Ping timeout: 480 seconds]
22:59|-|VS_ChanLog [~stats@ns.theshore.net] has left #uml [Rotating Logs]
22:59|-|VS_ChanLog [~stats@ns.theshore.net] has joined #uml
23:07|-|aroscha [~aroscha@xgw.network.kz] has joined #uml
23:10|-|mgross [~mgross@pool-71-245-102-239.ptldor.fios.verizon.net] has quit [Quit: Leaving]
---Logclosed Mon Aug 20 00:00:59 2007