[gentoo-amd64] Re: Re: Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
David Guerizec posted <[EMAIL PROTECTED]>, excerpted below, on Mon, 06 Feb 2006 01:12:16 +0100: > On Friday 03 February 2006 17:28, Duncan wrote: > >> PKGDIR="/pkg" >> PORTAGE_TMPDIR="/tmp" >> PORTDIR="/p" >> PORTDIR_OVERLAY="/l/p" >> >> Here you can see some of my path customization. > > Are these different partitions ? And if so, does that relate in any way to > filesystem fragmentation ? > > (waiting explanation on how to fight against fragmentation here ;)) Yes, different "partitions". Or, they /were/ different partitions on my old single hard drive. I'm now running md, the multi-disk kernel-RAID driver, with four Seagate 300 gig drives, partitioned and multi-RAIDed into RAID-1 (/boot), RAID-6 (most of the system) and RAID-0 (the stuff like /tmp and /p, $PORTDIR, as these are either temporary anyway, or easily replaced off the net, so the speed and additional capacity of RAID-0 is good, and the redundancy of real RAID unneeded). Fragmentation doesn't tend to be as much of an issue on Linux, with "real" filesystems, as on MSWormOS, particularly FAT/FAT32. I'm running all reiserfs here, FWIW. It doesn't have a compaction tool (defrag, on MSWormOS), but I've not noticed any issues as a result. That said, yes, the partitioning does help, as does the better separation of executables vs data on Linux, as compared to MSWormOS. There are other reasons to partition that I consider more important, but it does help fragmentation, as well. First, while it's possible to separate /, /usr, and /var, and I've separated them in the past, I've come to the conclusion that it's more trouble than benefit, altho I do put some subdirs on their own partitions. Keeping those three together means all the locations portage will normally place merged package components are on the same partition, along with portage's database of what's merged. I've had them get out of sync before (long story, suffice it to say it can happen, particularly if they are on separate partitions), and take it from me, it's /much/ simpler if the database is always synced with what's on your system. I /do/ however keep two copies (and I should have made three) of that / partition (with /var and /usr), a working copy and a backup, such that I ever fat-finger something, or if a package upgrade kills my ability to boot for some reason (possible, running ~arch), I can simply boot the backup copy. (That's actually how the de-syncing happened above, after something happened, I ended up with a /var from the working copy and a / and /usr from the backup, so portage thought everything was up to date, when it was all as old as the backup snapshot -- a difference large enough to complicate things.) If it's three, working, fallback, and second fallback, you'll have a working fallback at all times, even if something happens in the middle of your update of the first fallback, since you'll have the second, and wouldn't attempt an update to it until you've verified the first fallback works after you updated it. As I mentioned, some of the subdirs of the above are separate partitions. /var/log is on its own partition so a runaway logging incident can't ever use up all available space anywhere but the log partition. This is common Unix practice. /tmp is its own partition because it just makes sense to keep temporary files isolated from the rest of the system. (Here, /var/tmp is a symlink to /tmp, so it's the same partition. They do have slightly different uses, so that's not for everyone, but it was standard on Mandrake, which I switched to Gentoo from, and it suits my needs. Servers and true multi-human-user systems where not all human users are trusted will be most likely to wish to keep these separate.) /usr/local is its own partition, so I can keep the scripts and stuff I have there across main system reinstalls, if necessary. /home is of course one of the first partitions often split off, again, allowing system reinstall without killing the stuff in /home. Of course, note that these splits also tend to be useful in a multi-boot situation. It's likely that the same /tmp could be used for all *ix boots anyway, whether that's 32-bit and 64-bit Gentoo, or Red Hat and Gentoo, or even Solaris or one of the BSDs and Linux, provided you choose your partition type appropriately. Likewise with /home and possibly the stuff in /usr/local, altho some *ix use that for more than Gentoo does. You'd likely wish to keep separate log partitions, of course. The /l from my previous mail is /usr/local as well. Here, I use the /l in my paths and local settings, so it's the real mount-point and /usr/local is the symlink to it, but that's purely personal preference. Likewise with /h and /home, only /h is the symlink since there's more system stuff that's going to have /home in its default path. I've done that with most of the system dirs as well, so /u->/usr, /e->/etc, /usr/portage->/p, /mnt->/m... There are three dirs other than /tmp and /var/tmp that sto
[gentoo-amd64] Re: Re: network problem - at a loss
Thierry de Coulon posted <[EMAIL PROTECTED]>, excerpted below, on Sun, 05 Feb 2006 00:14:44 +: > On Saturday, 4 February 2006 19:07, Duncan wrote: >> Evidently, Tyan has at least two "k8w" boards. > > Thanks for your hint, I didn't know. My board is sold as S2875ANRF Not a problem now, but as you can probably imagine, it caused a bit of confusion the first time someone with the s2875, calling it the k8w, got in a discussion with me, with the s2885, also the k8w. =8^) What Tyan had in mind when they pulled that trick I don't know, but I can tell you I had in mind some choice words for them when we figured it out! =8^) (Still, I'll take Tyan's Linux support over MSI's, any day. I've been very impressed with Tyan, and conversely, not so impressed with the reports from MSI users, so I think we made the right choice, even if they /did/ decide to play games with duplicate board names.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] k3b error
On Monday 06 February 2006 15:51, Gavin Seddon wrote: > /usr/bin/cdrecord: Success. write_g1: scsi sendcmd: no error > CDB: 2A 00 00 00 4A 79 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 03 00 00 47 E8 0A 00 00 00 00 0C 00 00 00 > Sense Key: 0x3 Medium Error, Segment 0 > Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0 > Sense flags: Blk 18408 (not valid) > resid: 10240 > cmd finished after 22.523s timeout 40s > /usr/bin/cdrecord: A write error occured. > /usr/bin/cdrecord: Please properly read the error message above. > write track data: error after 39045120 bytes > Writing time: 75.969s > Average write speed 6.4x. looks like you have a defective blank. Try another one. If that fails too, try a different brand. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] k3b error
Which package contains cdrecord? > - > > check permission - k3bsetup ? > try to re-emerge cdrecord > > anyway - it should work, however - setting "burning group" makes it better > > Piotr -- Dr Gavin Seddon School of Pharmacy and Pharmaceutical Sciences University of Manchester Oxford Road, Manchester M13 9PL, U.K. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] k3b error
On 2/6/06, Gavin Seddon <[EMAIL PROTECTED]> wrote: > Track 01: 36 of 57 MB written (fifo 59%) [buf 5%] 9.1x. > Track 01: 37 of 57 MB written (fifo 45%) [buf 85%] 8.7x. > /usr/bin/cdrecord: Success. write_g1: scsi sendcmd: no error > CDB: 2A 00 00 00 4A 79 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 03 00 00 47 E8 0A 00 00 00 00 0C 00 00 00 > Sense Key: 0x3 Medium Error, Segment 0 > Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0 > /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdc speed=32 -tao > driveropts=burnfree -eject > -data /home/mbpssgms/install-x86-minimal-2005.1-r1.iso ' Well, one thing that bothers me is that your system is not able to keep the fifo or the drive buffer full, which considering that 32x is only 4.8MB/s, it should be able to. Possibly you have something misconfigured, but I don't know what. 1. Check your cabling and drive jumpers. (Is this the only device on the secondary channel?) 2. Check that DMA is enabled for your hard drive (hdparm /dev/hdX). 3. If by chance the drive you are reading from is hdd, use -immed with cdrecord. Also, try dropping to 16x or even 8x and see if the results improve. -Richard -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] k3b error
Gavin Seddon napisał(a): Hi, k3b stops. The log is 'System --- K3b Version: 0.12.8 KDE Version: 3.4.3 QT Version: 3.3.4 Kernel: 2.6.14-gentoo-r2 Devices --- _NEC DVD_RW ND-3520A 1.04 (/dev/hdc, ) at /mnt/cdrom [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R; DVD-RW; DVD+R; DVD+RW; DVD+R DL] [DVD-ROM; DVD-R Sequential; DVD-RW Restricted Overwrite; DVD-RW Sequential; DVD+RW; DVD +R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96R; RAW/R96R; Restricted Overwrite] Used versions --- cdrecord: 2.1 cdrecord --- /usr/bin/cdrecord: Warning: Running on Linux-2.6.14-gentoo-r2 /usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer. /usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris. /usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Warning: Open by 'devname' is unintentional and not supported. Linux sg driver version: 3.5.27 SCSI buffer size: 64512 /usr/bin/cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. /usr/bin/cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. /usr/bin/cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Cdrecord-Clone 2.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.8'. Driveropts: 'burnfree' atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-3520A ' Revision : '1.04' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0014 Profile: 0x0013 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A Profile: 0x0009 (current) Profile: 0x0008 (current) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 1343488 = 1312 KB FIFO size : 4194304 = 4096 KB /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). - check permission - k3bsetup ? try to re-emerge cdrecord anyway - it should work, however - setting "burning group" makes it better Piotr -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] k3b error
Hi, k3b stops. The log is 'System --- K3b Version: 0.12.8 KDE Version: 3.4.3 QT Version: 3.3.4 Kernel: 2.6.14-gentoo-r2 Devices --- _NEC DVD_RW ND-3520A 1.04 (/dev/hdc, ) at /mnt/cdrom [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R; DVD-RW; DVD+R; DVD+RW; DVD+R DL] [DVD-ROM; DVD-R Sequential; DVD-RW Restricted Overwrite; DVD-RW Sequential; DVD+RW; DVD +R; DVD+R Double Layer; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96R; RAW/R96R; Restricted Overwrite] Used versions --- cdrecord: 2.1 cdrecord --- /usr/bin/cdrecord: Warning: Running on Linux-2.6.14-gentoo-r2 /usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer. /usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris. /usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Warning: Open by 'devname' is unintentional and not supported. Linux sg driver version: 3.5.27 SCSI buffer size: 64512 /usr/bin/cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. /usr/bin/cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. /usr/bin/cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Cdrecord-Clone 2.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.8'. Driveropts: 'burnfree' atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-3520A ' Revision : '1.04' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0014 Profile: 0x0013 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A Profile: 0x0009 (current) Profile: 0x0008 (current) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 1343488 = 1312 KB FIFO size : 4194304 = 4096 KB /usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler /usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. Track 01: data57 MB Total size: 66 MB (06:33.73) = 29530 sectors Lout start: 66 MB (06:35/55) = 29530 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable ATIP start of lead in: -11674 (97:26/26) ATIP start of lead out: 359848 (79:59/73) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 23 Manufacturer: SKC Co., Ltd. Blocks total: 359848 Blocks current: 359848 Blocks remaining: 330318 Starting to write CD/DVD at speed 32 in real TAO mode for single session. Last chance to quit, starting real write in 2 seconds. 1 seconds. 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is OFF. Turning BURN-Free on Performing OPC... Starting new track at sector: 0 Track 01:0 of 57 MB written. Track 01:1 of 57 MB written (fifo 100%) [buf 80%] 10.2x. Track 01:2 of 57 MB written (fifo 100%) [buf 73%] 4.7x. Track 01:3 of 57 MB written (fifo 100%) [buf 34%] 12.6x. Track 01:4 of 57 MB written (fifo 100%) [buf 29%] 12.0x. Track 01:5 of 57 MB written (fifo 100%) [buf 100%] 6.0x. Track 01:6 of 57 MB written (fifo 100%) [buf 58%] 12.1x. Track 01:7 of 57 MB written (fifo 100%) [buf 16%] 12.5x. Track 01:8 of 57 MB written (fifo 100%) [buf 62%] 12.0x. Track 01:9 of 57 MB written (fifo 100%) [buf 83%] 6.0x. Track 01: 10 of 57 MB written (fifo 100%) [buf 39%] 12.2x. Track 01: 11 of 57 MB written (fifo 100%) [buf 19%] 12.2x. Track 01: 12 of 57 MB written (fifo 100%) [buf 100%] 11.7x. Track 01: 13 of 57 MB written (fifo 100%) [buf 62%] 6.2x. Track 01: 14 of 57 MB written (fifo 100%) [buf 16%] 12.1x. Track 01: 15 of 57 MB written (fifo 100%) [buf 62%] 12.3x. Track 01: 16 of 57 MB written (fifo 100%) [buf 80%] 6.1x. Track 01: 17 of 57 MB written (fifo 100%) [buf 34%] 12.3x. Track 01: 18 of 57 MB written (fifo 100%) [buf 33%] 11.8x. Track 01: 19 of 57 MB written (fifo 100%) [buf 98%] 6.1x. Track 01: 20 of 57 MB written (fifo 92%) [buf 47%] 11.8x. Track 01: 21 of 57 MB written (fifo 76%) [buf 43%] 9.6x. Track 01: 22 of
