Discuss October 2007

discuss@lists.centos.org

268 participants
322 discussions

Re: [CentOS] How to export X displays
by techlists＠comcast.net 15 Oct '07

15 Oct '07

I think you probably went from Linux to Windows, not from Windows to Linux. There is an RDP *client* for Linux that works quite well with Windows Remote Desktop, but RDP/Terminal Services is completely a Microsoft thing. Paul -------------- Original message ---------------------- From: "umair shakil" <umairshakeel(a)gmail.com> > Salam, > > Well, i have only used RDP as windows to linux (desktop), there should be no > issue... > for linux to linux, well x11 forwrding through ssh seems to be issue with > that.... not used > if i try i will let u know > > There is also another way if u can try.... > > www.nomachine.com and go to download section. > > U can find all details here, how to install, it also has client for ubunto. > what u will > do is to install the server, install the client on ur ubunto, and then use > it... it really very amazing i have used this.... > > Regards, > > Umair Shakil > ETD > > On 10/10/07, John R Pierce <pierce(a)hogranch.com> wrote: > > > > umair shakil wrote: > > > Why dont u enable RDP on centOS (running GUI), and then using ubunto > > > with this path > > > > > > > > RDP is a Microsoft Windows Remote Desktop Protocol. what good would > > that be for linux to linux ??!? > > > > > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos > >

2 1

Howto reconfigure / rebuild CentOS 5 LiveCD
by Patrice Guay 15 Oct '07

15 Oct '07

Hi, the instructions for creating your own CentOS 5 LiveCD using livecd-tools are given here: http://lists.centos.org/pipermail/centos-devel/2007-July/003744.html Regards, -- Patrice Guay

1 0

zebra-0.95 rpm
by Indunil Jayasooriya 15 Oct '07

15 Oct '07

Hi, I want to run zebra on CentOS 4.5 box acting as a firewall and router. I 'd rather like to user RPM. So I am lokking for a proper RPM. I now googled. But I could not find any for EL4 for CentOS 4. YOUR IDEAS? -- Thank you Indunil Jayasooriya

3 2

disk partitioning thoughts
by Jerry Geis 15 Oct '07

15 Oct '07

In the past I basically used 3 partitions for hard drives. partition 1: was all centos (typically 20G) partition 2: was swap (typically 2*RAM - 2G) partition 3: was everything else I wanted, needed or carded about, database files etc... Now with really big drives coming along 750G and 1T partition 3 is getting big. Except for time to format is there a problem with that??? I'm not really to fond of trying to break up partition 3 but I am just wondering if there is a major reason why I should not be partitioning my systems this way? My systems are really just running my application (that runs on linux). It is not a huge email server, not a huge apache server. Just running linux with 100% uptime (sweet). Again just my application running an a stable platform. My application has databases that grow big. My database is not MySQL it is ISAM based. Thanks, Jerry

2 1

CentOS-announce Digest, Vol 32, Issue 10
by centos-announce-request＠centos.org 15 Oct '07

15 Oct '07

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2007:0912-01: Important CentOS 2 i386 libvorbis security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Mon, 15 Oct 2007 12:00:31 +1000 From: John Newbigin <jnewbigin(a)ict.swin.edu.au> Subject: [CentOS-announce] CESA-2007:0912-01: Important CentOS 2 i386 libvorbis security update To: centos-announce(a)centos.org Message-ID: <4712C9BF.5000204(a)ict.swin.edu.au> Content-Type: text/plain; charset=us-ascii; format=flowed The following errata for CentOS-2 have been built and uploaded to the centos mirror: RHSA-2007:0912-01 Important: libvorbis security update Files available: libvorbis-1.0rc2-7.el2.i386.rpm libvorbis-devel-1.0rc2-7.el2.i386.rpm More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html The easy way to make sure you are up to date with all the latest patches is to run: # yum update -- John Newbigin Computer Systems Officer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 32, Issue 10 ***********************************************

1 0

This is a fsck log,what's the problem?
by spasti 15 Oct '07

15 Oct '07

This is a fsck log of my computer ,everytime when boot the system show this things, what's the problem? And how can I cancel it when system boot? Log of fsck -C -R -A -a Sun Oct 14 21:00:34 2007 fsck 1.40.2 (12-Jul-2007) dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/hdb1: 18222 files, 425355/1053230 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/hdb10: 22 files, 571488/1248831 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN There are differences between boot sector and its backup. Differences: (offset:original/backup) 5:44/57, 6:4f/49, 7:53/4e, 8:35/34, 10:30/31, 28:3f/9c, 29:00/98, 30:00/03 , 31:00/07, 71:4b/d0, 72:20/3f, 73:20/3f, 74:20/cb, 75:20/a5, 76:20/dd , 77:20/00, 78:20/00, 79:20/00, 80:20/00, 81:20/00 Not automatically fixing this. /dev/hdb11: 20 files, 493909/1022134 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/hdb5: 2906 files, 642353/1022134 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN There are differences between boot sector and its backup. Differences: (offset:original/backup) 32:fe/02, 33:25/a3, 34:9c/1a, 35:00/01 Not automatically fixing this. /dev/hdb6: 26154 files, 291410/638452 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/hdb7: 4 files, 180078/1034160 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN There are differences between boot sector and its backup. Differences: (offset:original/backup) 1:3c/54, 2:90/57, 90:f6/44, 91:f6/80, 92:f6/00, 93:f6/ee, 94:f6/15, 95:f6/06 , 96:f6/10, 97:f6/80, 98:f6/49, 99:f6/01, 100:f6/40, 101:f6/c2, 102:f6/50 , 103:f6/4d, 104:f6/41, 105:f6/a9, 106:f6/06, 107:f6/0a, 108:f6/b2 , 109:f6/c8, 110:f6/50, 111:f6/fd, 112:f6/00, 113:f6/5d, 114:f6/bb , 115:f6/a4, 116:f6/d4, 117:f6/07, 118:f6/ee, 119:f6/8c, 120:f6/8f , 121:f6/70, 122:f6/5a, 123:f6/07, 124:f6/d8, 125:f6/23, 126:f6/e4 , 127:f6/48, 128:f6/22, 129:f6/6e, 130:f6/82, 131:f6/0c, 132:f6/d9 , 133:f6/05, 134:f6/8d, 135:f6/d7, 136:f6/cd, 137:f6/55, 138:f6/9e , 139:f6/fa, 140:f6/d4, 141:f6/cd, 142:f6/9e, 143:f6/64, 144:f6/cb , 145:f6/76, 146:f6/c5, 147:f6/e4, 148:f6/ae, 149:f6/2c, 150:f6/52 , 151:f6/49, 152:f6/88, 153:f6/d0, 154:f6/82, 155:f6/82, 156:f6/ea , 157:f6/15, 158:f6/69, 159:f6/28, 160:f6/08, 161:f6/24, 162:f6/90 , 163:f6/65, 164:f6/06, 165:f6/21, 166:f6/0b, 167:f6/1e, 168:f6/35 , 169:f6/b3, 170:f6/4d, 171:f6/66, 172:f6/d1, 173:f6/26, 174:f6/a9 , 175:f6/04, 176:f6/89, 177:f6/a4, 178:f6/95, 179:f6/3e, 180:f6/4d , 181:f6/79, 182:f6/90, 183:f6/02, 184:f6/9a, 185:f6/10, 186:f6/c8 , 187:f6/80, 188:f6/28, 189:f6/86, 190:f6/49, 191:f6/01, 192:f6/a1 , 193:f6/02, 194:f6/49, 195:f6/8b, 196:f6/c6, 197:f6/d7, 198:f6/95 , 199:f6/5b, 200:f6/72, 201:f6/9d, 202:f6/10, 203:f6/48, 204:f6/20 , 205:f6/c1, 206:f6/46, 207:f6/e3, 208:f6/eb, 209:f6/7a, 210:f6/fb , 211:f6/1e, 212:f6/c5, 213:f6/65, 214:f6/f4, 215:f6/58, 216:f6/f4 , 217:f6/38, 218:f6/fd, 219:f6/8c, 220:f6/4f, 221:f6/6b, 222:f6/55 , 223:f6/bf, 224:f6/ce, 225:f6/4c, 226:f6/63, 227:f6/50, 228:f6/fa , 229:f6/92, 230:f6/13, 231:f6/a3, 232:f6/80, 233:f6/4f, 234:f6/4c , 235:f6/13, 236:f6/f5, 237:f6/8f, 238:f6/c7, 239:f6/fa, 240:f6/6e , 241:f6/5e, 242:f6/ee, 243:f6/ae, 244:f6/6b, 245:f6/55, 246:f6/76 , 247:f6/cb, 248:f6/97, 249:f6/2f, 250:f6/9a, 251:f6/af, 252:f6/5f , 253:f6/d3, 254:f6/72, 255:f6/f7, 256:f6/75, 257:f6/73, 258:f6/5a , 259:f6/ab, 260:f6/b6, 261:f6/5c, 262:f6/b9, 263:f6/7c, 264:f6/d5 , 265:f6/7a, 266:f6/94, 267:f6/e0, 268:f6/38, 269:f6/47, 270:f6/18 , 271:f6/0f, 272:f6/df, 273:f6/53, 274:f6/43, 275:f6/a7, 276:f6/e5 , 277:f6/aa, 278:f6/68, 279:f6/4a, 280:f6/d0, 281:f6/e2, 282:f6/7e , 283:f6/5d, 284:f6/49, 285:f6/65, 286:f6/5a, 287:f6/0c, 288:f6/49 , 289:f6/01, 290:f6/0e, 291:f6/9f, 292:f6/f2, 293:f6/84, 294:f6/b0 , 295:f6/89, 296:f6/0c, 297:f6/04, 298:f6/8a, 299:f6/38, 300:f6/bf , 301:f6/2c, 302:f6/05, 303:f6/5c, 304:f6/34, 305:f6/10, 306:f6/c9 , 307:f6/d4, 308:f6/b1, 309:f6/14, 310:f6/3e, 311:f6/b7, 312:f6/26 , 313:f6/75, 314:f6/67, 315:f6/58, 316:f6/72, 317:f6/74, 318:f6/20 , 319:f6/32, 320:f6/18, 321:f6/d9, 322:f6/86, 323:f6/93, 324:f6/13 , 325:f6/3a, 326:f6/42, 327:f6/0d, 328:f6/3c, 329:f6/6b, 330:f6/69 , 331:f6/08, 332:f6/04, 333:f6/c4, 334:f6/b2, 335:f6/36, 336:f6/0a , 337:f6/94, 338:f6/95, 339:f6/37, 340:f6/0d, 341:f6/1b, 342:f6/84 , 343:f6/b6, 344:f6/1a, 345:f6/62, 346:f6/77, 347:f6/a0, 348:f6/04 , 349:f6/92, 350:f6/94, 351:f6/a4, 352:f6/84, 353:f6/55, 354:f6/04 , 355:f6/cf, 356:f6/c6, 357:f6/df, 358:f6/51, 359:f6/08, 360:f6/05 , 361:f6/29, 362:f6/4d, 363:f6/29, 364:f6/48, 365:f6/7c, 366:f6/b4 , 367:f6/e8, 368:f6/2b, 369:f6/0a, 370:f6/41, 371:f6/44, 372:f6/a6 , 373:f6/94, 374:f6/d2, 375:f6/4b, 376:f6/ac, 377:f6/84, 378:f6/4a , 379:f6/0b, 380:f6/e0, 381:f6/81, 382:f6/79, 383:f6/e6, 384:f6/c1 , 385:f6/dc, 386:f6/04, 387:f6/02, 388:f6/92, 389:f6/0b, 390:f6/36 , 391:f6/49, 392:f6/24, 393:f6/9b, 394:f6/e2, 395:f6/04, 396:f6/06 , 397:f6/9d, 398:f6/20, 399:f6/03, 400:f6/4a, 401:f6/c3, 402:f6/09 , 403:f6/5f, 404:f6/b0, 405:f6/cd, 406:f6/92, 407:f6/6e, 408:f6/86 , 409:f6/0a, 410:f6/87, 411:f6/ad, 412:f6/43, 413:f6/6a, 414:f6/03 , 415:f6/54, 416:f6/90, 417:f6/5a, 418:f6/92, 419:f6/49, 420:f6/01 , 421:f6/13, 422:f6/50, 423:f6/90, 424:f6/44, 425:f6/09, 426:f6/93 , 427:f6/a9, 428:f6/8a, 429:f6/a0, 430:f6/de, 431:f6/d3, 432:f6/a0 , 433:f6/52, 434:f6/01, 435:f6/0d, 436:f6/db, 437:f6/87, 438:f6/77 , 439:f6/7b, 440:f6/e6, 441:f6/b2, 442:f6/15, 443:f6/56, 444:f6/c3 , 445:f6/89, 447:f6/e3, 448:f6/bc, 449:f6/0d, 450:f6/e6, 451:f6/6c , 452:f6/66, 453:f6/8d, 454:f6/70, 455:f6/aa, 456:f6/0a, 457:f6/81 , 458:f6/90, 459:f6/eb, 460:f6/08, 461:f6/4d, 462:f6/14, 463:f6/d1 , 464:f6/48, 465:f6/4c, 466:f6/89, 467:f6/22, 468:f6/29, 469:f6/28 , 470:f6/a4, 471:f6/be, 472:f6/a5, 473:f6/01, 474:f6/b4, 475:f6/a4 , 476:f6/b5, 477:f6/27, 478:f6/0c, 479:f6/a0, 480:f6/10, 481:f6/98 , 482:f6/2d, 483:f6/1b, 484:f6/64, 485:f6/f4, 486:f6/ae, 487:f6/e5 , 488:f6/b1, 489:f6/d8, 490:f6/ef, 491:f6/69, 492:f6/82, 493:f6/04 , 494:f6/4a, 495:f6/0c, 496:f6/6c, 497:f6/35, 498:f6/22, 499:f6/84 , 500:f6/84, 501:f6/45, 502:f6/54, 503:f6/18, 504:f6/12, 505:f6/96 , 506:f6/04, 507:f6/94 Not automatically fixing this. /dev/hdb8: 2435 files, 856391/1049733 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN Wrong checksum for long file name ":7Kl.bmp". (Short name 000\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":9gU.bmp". (Short name 001\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":6-U.bmp". (Short name 003\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":6Gq.bmp". (Short name 004\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5zM.bmp". (Short name 005\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":7+y.bmp". (Short name 006\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5yf.bmp". (Short name 007\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":8am.bmp". (Short name 008\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":91O.bmp". (Short name 010\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":6Qv.bmp". (Short name 011\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5yj.bmp". (Short name 012\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":6+v.bmp". (Short name 013\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":8v7.bmp". (Short name 014\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":90B.bmp". (Short name 015\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":91H.bmp". (Short name 016\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":91z.bmp". (Short name 017\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5nc.bmp". (Short name 018\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":70Q.bmp". (Short name 019\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":70r.bmp". (Short name 020\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":71U.bmp". (Short name 021\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5cD.bmp". (Short name 022\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":6+d.bmp". (Short name 023\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":6-X.bmp". (Short name 024\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":928.bmp". (Short name 025\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":89q.bmp". (Short name 026\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":71F.bmp". (Short name 027\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":8-a.bmp". (Short name 028\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":90s.bmp". (Short name 029\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":91I.bmp". (Short name 030\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":91e.bmp". (Short name 031\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5c1.bmp". (Short name 032\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":922.bmp". (Short name 033\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5zO.bmp". (Short name 034\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5cf.bmp". (Short name 035\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5Ih.bmp". (Short name 036\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5cg.bmp". (Short name 037\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5cZ.bmp". (Short name 038\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. Wrong checksum for long file name ":5c3.bmp". (Short name 039\0000000.\000MP may have changed without updating the long name) Not auto-correcting this. /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:7Kl.bmp Bad file name. Auto-renaming it. Renamed to 000\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:9gU.bmp Bad file name. Auto-renaming it. Renamed to 001\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:8i7.bmp Bad file name. Auto-renaming it. Renamed to 002\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:6-U.bmp Bad file name. Auto-renaming it. Renamed to 003\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:6Gq.bmp Bad file name. Auto-renaming it. Renamed to 004\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5zM.bmp Bad file name. Auto-renaming it. Renamed to 005\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:7+y.bmp Bad file name. Auto-renaming it. Renamed to 006\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5yf.bmp Bad file name. Auto-renaming it. Renamed to 007\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:8am.bmp Bad file name. Auto-renaming it. Renamed to 008\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5lm.bmp Bad file name. Auto-renaming it. Renamed to 009\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:91O.bmp Bad file name. Auto-renaming it. Renamed to 010\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:6Qv.bmp Bad file name. Auto-renaming it. Renamed to 011\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5yj.bmp Bad file name. Auto-renaming it. Renamed to 012\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:6+v.bmp Bad file name. Auto-renaming it. Renamed to 013\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:8v7.bmp Bad file name. Auto-renaming it. Renamed to 014\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:90B.bmp Bad file name. Auto-renaming it. Renamed to 015\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:91H.bmp Bad file name. Auto-renaming it. Renamed to 016\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:91z.bmp Bad file name. Auto-renaming it. Renamed to 017\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5nc.bmp Bad file name. Auto-renaming it. Renamed to 018\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:70Q.bmp Bad file name. Auto-renaming it. Renamed to 019\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:70r.bmp Bad file name. Auto-renaming it. Renamed to 020\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:71U.bmp Bad file name. Auto-renaming it. Renamed to 021\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5cD.bmp Bad file name. Auto-renaming it. Renamed to 022\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:6+d.bmp Bad file name. Auto-renaming it. Renamed to 023\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:6-X.bmp Bad file name. Auto-renaming it. Renamed to 024\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:928.bmp Bad file name. Auto-renaming it. Renamed to 025\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:89q.bmp Bad file name. Auto-renaming it. Renamed to 026\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:71F.bmp Bad file name. Auto-renaming it. Renamed to 027\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:8-a.bmp Bad file name. Auto-renaming it. Renamed to 028\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:90s.bmp Bad file name. Auto-renaming it. Renamed to 029\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:91I.bmp Bad file name. Auto-renaming it. Renamed to 030\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:91e.bmp Bad file name. Auto-renaming it. Renamed to 031\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5c1.bmp Bad file name. Auto-renaming it. Renamed to 032\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:922.bmp Bad file name. Auto-renaming it. Renamed to 033\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5zO.bmp Bad file name. Auto-renaming it. Renamed to 034\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5cf.bmp Bad file name. Auto-renaming it. Renamed to 035\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5Ih.bmp Bad file name. Auto-renaming it. Renamed to 036\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5cg.bmp Bad file name. Auto-renaming it. Renamed to 037\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5cZ.bmp Bad file name. Auto-renaming it. Renamed to 038\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5c3.bmp Bad file name. Auto-renaming it. Renamed to 039\0000000.\000MP Performing changes. /dev/hdb9: 6680 files, 980009/1278924 clusters /dev/hdb13: recovering journal /dev/hdb13: clean, 37/26104 files, 36385/104388 blocks : recovering journal : clean, 1691/640640 files, 367103/640584 blocks fsck died with exit status 1 Sun Oct 14 21:00:54 2007 ---------------- -- wonderful !

2 1

CentOS 5 IA64
by James A. Peltier 15 Oct '07

15 Oct '07

I only have this machine until Monday. I understand that there is a beta version around somewhere? Perhaps a developer can create an ISO that I can try to boot onto this machine?

3 2

Perfomance tuning for NIS client
by joseph blase 15 Oct '07

15 Oct '07

Hi, I have both linux and solaris NIS client against a Solaris NIS Server, but my linux box are shamefully slow compare to solaris some sample: on Solaris 5.8: # ypwhich transporter02.domain.com # time id userid uid=36923(userid) gid=36923(u_036923) real 0.0 user 0.0 sys 0.0 on Linux: [root@linux]# ypwhich transporter02.domain.com [root@amsdc2-n-s04taw root]# time id userid uid=36923(userid) gid=36923(u_036923) groups=36923(u_036923) real 0m10.509s user 0m0.030s sys 0m0.090s ********** Route**************** [root@linux]# traceroute transporter02 traceroute to transporter02.domain.com (IP), 30 hops max, 46 byte packets 1 nlamsdc2mp078-hsrp.net-equip.domain.net (IP) 0.000 ms 0.000 ms 0.000ms 2 transporter02.domain.com (IP) 0.000 ms 0.000 ms 0.000 ms solaris# traceroute transporter02 traceroute to transporter02.domain.com (145.6.246.53), 30 hops max, 40 byte packets 1 transporter02.domain.com (145.6.246.53) 0.462 ms 0.279 ms 0.306 ms Although I considered that latency involved but still I'm not statisfied, is there any tunable parameter that I can set on linux box to somehow improve the performance? I also noticed things that I'm not sure if this is default on linux nis bindings: [root@linux]# pwd /var/yp/binding [root@linux]# ls NONAME.DOMAIN.COM.1 NONAME.DOMAIN.COM.2 ===> why there are two of this on linux? solaris# cd /var/yp/binding solaris# ls NONAME.DOMAIN.COM xprt.tcp.3 xprt.ticlts.3 xprt.ticotsord.2 xprt.udp.2 xprt.tcp.1 xprt.ticlts.1 xprt.ticots.3 xprt.ticotsord.3 xprt.udp.3 xprt.tcp.2 xprt.ticlts.2 xprt.ticotsord.1 xprt.udp.1 ypbind.pid Thanks in advance for any feedback. Things I've tried to tweak: * put NIS Server IP on /etc/yp.conf * put NIS Server IP on /etc/hosts no positive result. joseph

5 6

help with mdadm/mount
by Craig White 14 Oct '07

14 Oct '07

Just upgraded from CentOS-3 to 5 (yeah - probably not the best idea) I am using software raid In order to ensure that I had enough space on /usr (which was a bit tight), I had an extra partition that I changed to /usr/share from /etc/fstab... /dev/md5 /usr/share ext3 defaults 1 2 but it won't mount up at boot. It will mount after boot if I issue the command 'mount -a' (obviously because of the fstab entry). Is there something like an mdadm label that I need to change? Craig

1 1

Problem creating volgroups with kickstart installations (on xen)
by Kai Schaetzl 14 Oct '07

14 Oct '07

I'm testing doing kickstart installations on Xen VMs. This is the first time I'm trying out kickstart at all, so I rather think I'm doing something wrong in the kickstart configuration than it is a Xen issue. I use a modified kickstart file from an earlier manual installation with a very basic filesystem setup. It fails with "SystemError: vgcreate failed for VolGroup00". The Xen VM file is allowed to grow up to 2GB. The kickstart commands for partioning are: clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 pv.2 --pesize=32768 pv.2 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=416 --grow --maxsize=832 This is taken exactly from the "template" kickstart file, I just added the --initlabel after reading the kickstart tips on the wiki. I read the kickstart part of the RH Installation and Deployment Guide, but it didn't help in this respect. Apparently --pesize=32768 is a maximum for volgroup extent sizes and is harmless. When I change to creating a partition for / it works just fine. Can someone help? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 3

← Newer
1
...
17
18
19
20
21
22
23
...
33
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2007