Triple boot Fedora, XP, and Vista
by Thomas Paine
I did some googling earlier looking for info on triple booting Fedora,
XP and Vista. I found some good info where everything is contained all
on one drive, but I have 4 sata drives that I'll be using.
I have an 80G for XP, and 80G for Vista, a 160 for Fedora, and a 250
for data storage.
Has anyone else worked at triple booting in this way?
The one guide suggests using the windows bootloader to let you handle
xp and vista and grub can get you into fedora. Ideally I'l like to use
grub for all three.Should I make my fedora drive sda then in this
case?
Anyone else done this and have ideas?
Thanks.
--
-=/>Thom
17 years, 5 months
Bash problems?
by Tomas Larsson
Dear group.
How do I do to, within a scrip, check if a directory I empty or not.
Cant find a way to do this in a simple way.
With best regards
Tomas Larsson
Sweden
Verus Amicus Est Tamquam Alter Idem
17 years, 5 months
Feeling real grumpy !
by Bill Case
Hi;
I have a friend staying with me for a couple of weeks. He is moving
here from another city and waiting for his new house purchase to close
and for his furniture with his computer to arrive. A perfect captive
audience to sell Linux and Fedora to.
My Fedora Core 6 i386 doesn't work.
"Np problem" says I to my friend, "I am on one of the most friendly and
helpful mailing lists in the world. You won't find anything like it for
help on Windows."
I send off a post describing my problem. No reply.
I try to show him the new compiz. It doesn't work.
I send a post describing my problem. No reply
I dig around and find that my video card using r128 driver doesn't work.
I send a post asking when it might be fixed. No reply.
I go to my backed up FC5 /etc/X11/xorg.conf and copy some of the
elements to my FC6 xorg.conf. I am not sure this will work, so I send a
post to this list asking if I will break anything. No reply.
I search Red Hat bugzilla for Fedora. I find a bug that is similar to
mine and add appropriate comments. No reply
I run into other problems that may be window manager related. I send
off a post. No reply.
"Well" I say to my friend "in the meantime, lets get some other things
working." I try to set up Gnomeradio. It doesn't work. I send a post to
the Gnome mailing list, wait a few days, then post the same problem to
the Fedora mailing list. No reply.
Sessions manager doesn't work. Several other applications are wonky. I
send off a list of wonky applications. No reply.
This morning my friend says that he is going out to look for a new Mac
computer.
No reply from me. I have googled and searched and found all kinds of
stories and comments about the failure/disagreement over AIGLX on r128
type video cards. Most of the comments seem outdated.
Can someone tell me:
Is this being fixed?
Is there a workaround?
Do I need a new video card?
Have I in someway in the past offended everybody on this list?
If I prepare a list of things-no-longer-working correctly, can someone
tell which ones are video card related?
I understand this is an all volunteer list. I have tried to give advice
when I could. I understand that FC6 is cutting edge and could have
bugs. I have been through the growing pains for FC3, FC4 and FC5.
Luckily, I have some work that has to be done I M$ Excel for today. But
I would like to show my friend more than half a Linux system.
--
Regards Bill
17 years, 5 months
Cross compilation
by Fernando Apesteguía
Helo list,
I'm using FC6 for x86_64. I need to compile a program for linux 32
bits. I tried with the -m32 flag to gcc, but I got:
core_recv.c:(.text+0x130): undefined reference to `__umoddi3'
and tons of ld warnings:
/usr/bin/ld: warning: i386 architecture of input file `main.o' is
incompatible with i386:x86-64 output
I searched in Google, but couldn't find the solution. For the
undefinded references I suppose it is because some missing i386
libraries right?
And what about the other things? How can I compile a 32 bit
application under a 64 bit system?
Thanks in advance.
17 years, 5 months
Notebook
by Andrea Bencini
I would like to buy a notebook and to install FC6.
Which one of these is the best to install FC6?
HP
ASUS
ACER
Toshiba
Thank
Andrea
17 years, 5 months
Re: Directory Size problem
by David G. Miller (aka DaveAtFraud)
"Dan Track" <dan.track(a)gmail.com> wrote:
> I've got a directory /var/spool/mqueue that is at 3.6G. The problem is
> that I've deleted everything in the directory but the size reported
> from du -hs is still reported as 3.6G. I've shutdown all potential
> sevices that could possibly be using teh directory e.g sendmail,
> httpd, syslog but it hasn't helped if I run an lsof or fuser against
> the directory I get no connections listed.
>
> Could someone please help me figure this weird problem out.
Is it the directory itself that still shows 3.6G? That is, what does ls
-lh /var/spool show for the mqueue directory? Since you've already
disabled all of the services that may access the directory, why not nuke
it (rm -rf /var/spool/mqueue) and then re-create it? Just make sure you
get the ownership and permissions right.
If the directory contained a large number of small files, it's possible
that it's just taking the file system some time to "catch up." At a
previous job I had to wipe clean a very bushy directory structure with
several hundred thousand files between test runs. If we could, we would
put this directory structure on a separate file system since it was
faster to unmount it, format it and remount it than it was to rm -rf the
directory structure. Could something like this be going on?
Cheers,
Dave
--
Politics, n. Strife of interests masquerading as a contest of principles.
-- Ambrose Bierce
17 years, 5 months
FC6 SATA-install on MSI K9AGM
by Kenn Thyrsted
Hi list.
FC6 will not install on sataII due to unreckognized device ATI SB600.
Any hints, workarounds etc. would be appreciated ;-)
- please....
Regards
Kenn
17 years, 5 months
RE: How to encrypt and burn to dvdr my home dir?
by Christian Burger
>Robin Laing wrote:
>>
>> What about truecrypt?
>>
>> http://www.truecrypt.org/
>>
>> If I was making a backup, I would tar and encrypt as explained before
>> and then RAR the files to make the files sizes easier to deal with.
>>
>> Just a thought.
>
>After encryption, it isn't going to compress.
>
>Mike
Nope not much if any... but rar will chunk it into 650 meg or whatever size
chunks that are desired....
17 years, 5 months
udev device-persistence problem
by Terry Horsnell
FC6 - kernel 2.6.18-1.2798.fc6 - udev-095-14
I'm trying to develop some rules to give me device-name
persistence on my SCSI disks. I have a couple of test rules:
BUS=="scsi", PROGRAM="/sbin/scsi_id -g -u"
RESULT=="20004cffffe0e0976", NAME="dsk0_%n", OWNER="root", GROUP="root", MODE="0700"
RESULT=="SSEAGATE_ST336807LC_3KT0CTTM00007530YTR2", NAME="dsk1_%n", OWNER="root", GROUP="root", MODE="0700"
With these rules disabled, I get:
[root@dev1 ~]# ls -l /dev/dsk* /dev/sd* /dev/sg*
brwx------ 1 root disk 8, 0 Nov 28 11:48 /dev/sda
brwx------ 1 root disk 8, 1 Nov 28 11:48 /dev/sda1
brwx------ 1 root disk 8, 16 Nov 28 11:48 /dev/sdb
brwx------ 1 root disk 8, 17 Nov 28 11:48 /dev/sdb1
brwx------ 1 root disk 8, 18 Nov 28 11:48 /dev/sdb2
brwx------ 1 root disk 8, 19 Nov 28 11:48 /dev/sdb3
brwx------ 1 root disk 8, 20 Nov 28 11:48 /dev/sdb4
brwx------ 1 root disk 8, 21 Nov 28 11:48 /dev/sdb5
brwx------ 1 root disk 8, 22 Nov 28 11:48 /dev/sdb6
brwx------ 1 root disk 8, 23 Nov 28 11:48 /dev/sdb7
brwx------ 1 root disk 8, 24 Nov 28 11:48 /dev/sdb8
crw------- 1 root root 21, 0 Nov 28 11:48 /dev/sg0
crw------- 1 root root 21, 1 Nov 28 11:48 /dev/sg1
(Note the two sg generic entries).
If I now enable these rules and reboot, I get:
[root@dev1 ~]# ls -l /dev/dsk* /dev/sd* /dev/sg*
brwx------ 1 root disk 8, 0 Nov 28 12:05 /dev/dsk0_
crw------- 1 root root 21, 0 Nov 28 12:05 /dev/dsk0_0
brwx------ 1 root disk 8, 1 Nov 28 12:05 /dev/dsk0_1
brwx------ 1 root disk 8, 16 Nov 28 12:05 /dev/dsk1_
brwx------ 1 root disk 8, 17 Nov 28 12:05 /dev/dsk1_1
brwx------ 1 root disk 8, 18 Nov 28 12:05 /dev/dsk1_2
brwx------ 1 root disk 8, 19 Nov 28 12:05 /dev/dsk1_3
brwx------ 1 root disk 8, 20 Nov 28 12:05 /dev/dsk1_4
brwx------ 1 root disk 8, 21 Nov 28 12:05 /dev/dsk1_5
brwx------ 1 root disk 8, 22 Nov 28 12:05 /dev/dsk1_6
brwx------ 1 root disk 8, 23 Nov 28 12:05 /dev/dsk1_7
brwx------ 1 root disk 8, 24 Nov 28 12:05 /dev/dsk1_8
brwx------ 1 root root 8, 0 Nov 28 12:04 /dev/sda
brwx------ 1 root root 8, 1 Nov 28 12:04 /dev/sda1
brwx------ 1 root root 8, 16 Nov 28 12:04 /dev/sdb
brwx------ 1 root root 8, 17 Nov 28 12:04 /dev/sdb1
brwx------ 1 root root 8, 18 Nov 28 12:04 /dev/sdb2
brwx------ 1 root root 8, 19 Nov 28 12:04 /dev/sdb3
brwx------ 1 root root 8, 20 Nov 28 12:04 /dev/sdb4
brwx------ 1 root root 8, 21 Nov 28 12:04 /dev/sdb5
brwx------ 1 root root 8, 22 Nov 28 12:04 /dev/sdb6
brwx------ 1 root root 8, 23 Nov 28 12:04 /dev/sdb7
brwx------ 1 root root 8, 24 Nov 28 12:04 /dev/sdb8
Why have I got both sd devices and dsk devices?
And what is the second line?
Why have I got an entry:
crw------- 1 root root 21, 0 Nov 28 11:45 /dev/dsk0_0
This looks like a generic device, but if so, why only one?
And where are the normal sg devices?
If I change the order of the disks on the SCSI bus, the
'generic' entry changes to dsk1_0. It seems to be associated
with the first disk encountered in the bus scan.
My disks are in a SCSI shelf and dsk1 is now in a
lower-numbered slot than dsk0.
[root@dev1 ~]# ls -l /dev/dsk* /dev/sd* /dev/sg*
brwx------ 1 root root 8, 16 Nov 28 16:05 /dev/dsk0_
brwx------ 1 root root 8, 17 Nov 28 16:05 /dev/dsk0_1
brwx------ 1 root root 8, 0 Nov 28 16:05 /dev/dsk1_
crwx------ 1 root root 21, 0 Nov 28 16:05 /dev/dsk1_0
brwx------ 1 root root 8, 1 Nov 28 16:05 /dev/dsk1_1
brwx------ 1 root root 8, 2 Nov 28 16:05 /dev/dsk1_2
brwx------ 1 root root 8, 3 Nov 28 16:05 /dev/dsk1_3
brwx------ 1 root root 8, 4 Nov 28 16:05 /dev/dsk1_4
brwx------ 1 root root 8, 5 Nov 28 16:05 /dev/dsk1_5
brwx------ 1 root root 8, 6 Nov 28 16:05 /dev/dsk1_6
brwx------ 1 root root 8, 7 Nov 28 16:05 /dev/dsk1_7
brwx------ 1 root root 8, 8 Nov 28 16:05 /dev/dsk1_8
brwx------ 1 root root 8, 0 Nov 28 16:05 /dev/sda
brwx------ 1 root root 8, 1 Nov 28 16:05 /dev/sda1
brwx------ 1 root root 8, 2 Nov 28 16:05 /dev/sda2
brwx------ 1 root root 8, 3 Nov 28 16:05 /dev/sda3
brwx------ 1 root root 8, 4 Nov 28 16:05 /dev/sda4
brwx------ 1 root root 8, 5 Nov 28 16:05 /dev/sda5
brwx------ 1 root root 8, 6 Nov 28 16:05 /dev/sda6
brwx------ 1 root root 8, 7 Nov 28 16:05 /dev/sda7
brwx------ 1 root root 8, 8 Nov 28 16:05 /dev/sda8
brwx------ 1 root root 8, 16 Nov 28 16:05 /dev/sdb
brwx------ 1 root root 8, 17 Nov 28 16:05 /dev/sdb1
Is this all as expected?
Am I going to be screwed later on if I need to do something
that requires a generic SCSI device for a particular disk?
Why do I still get /dev/sd* entries?
Any clues anyone?
Cheers,
Terry.
17 years, 5 months
Dual Head with FC6 on Intel GMA 950
by Guido Leisker
Dear all.
I am trying to get my Intel GMA 950 - which is in a Thinkpad T60 - running under
Fedora Core 6.
The Thinkpad-Display worked out of the box. Even the Desktop Effects are running
well. But now I have wobbling windows and a Cube of workspaces, but dual head is
still not running.
Trying to tell Fedora to start with both screens (the TFT of the Thinkpad and a
extern Benq FP 767 plugged to the Docking) by using system-config-display does
not help. FC starts, like I didn't do anything, with only the LCD of the
notebook.
So I tried a mix of my humble xorg-conf-skills and some xorg-confs I found in
the net. (Thinkwiki, ...)
The result is, that FC starts fine at the first time, but I am not able to log
out and in again or restart X by typing CTRL+ALT+BACKSPACE. X won't start a sec
time. Here are some Errors of Xorg.0.log:
> I810(0): V_BIOS address 0x7d8e0 out of range
> I810(0): VBE initialization failed.
> [..]
> Backtrace: [...]
> Fatal server error: Caught signal 11. Server aborting
:q
There are some warnings in the logfile from the first start too:
> (WW) I810(0): Bad V_BIOS checksum
> (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
> (WW) I810(0): Unable to estimate virtual size
> (WW) I810(1): Detected stolen memory (7872 kB) doesn't match what the BIOS
reports (12288 kB)
> (WW) I810(1): Extended BIOS function 0x5f28 failed.
> (WW) I810(0): Extended BIOS function 0x5f64 failed.
> (WW) I810(0): Extended BIOS function 0x5f64 failed.
> (WW) I810(0): Failed to set display devices to 0x800.
> (WW) I810(0): Enabling LVDS directly. Pipe B.
> (WW) I810(0): Disabling ADPA directly.
> (WW) I810(0): Writing config directly to SWF0.
> (WW) I810(0): Successfully set original devices
> (WW) I810(0): Setting the original video mode instead of restoring
the saved state
> [..]
-> (WW) I810(0): Successfully set original devices (2)
Unfortunately I do not know what a V-Bios is, or what it does mean to Enabling
LVDS directly. Pipe B..
Has anyone any idea? May be some hints, a link to a good wiki, some working
xorg.confs?
Here is my xorg.conf:
http://nopaste.debianforum.de/4573
the logfile of the first start:
http://nopaste.debianforum.de/4574
the logfile of the second start:
http://nopaste.debianforum.de/4575
thanking for any help
Guido
17 years, 5 months