After a recent hard drive crash on my laptop,
I've been trying to limp along by installing
f11 on a 8GB USB stick. After an installation
from a live USB stick to another USB stick,
I drove to a local hotspot to update and
yum install some stuff that wasn't on the
live USB. It took forever to update, not
even counting the download time. I'm sure
there is a reason, but I was surprised that
the original installation took about 7 minutes
and it took several hours to update that
installation AFTER downloading all of
the updated rpms.
Anyhoo, now that I've spent most of a
day getting the USB stick updated
and configured, I want to clone it to
another USB stick. I tried a few naive
things like copying directories to the
backup stick, but ran into boot errors
(I think due to different uuids on the
backup sticks partitions). What is the
right way to clone a fedora installation
on a USB stick to a second stick that
isn't exactly the same size (they are
both 8G, but different models so have
slightly different sizes).
Second try to find an answer...
I purchased a 1.5 TB HD, and I used gparted to create 4 partitions (GPT),
without knowing that winx XP (32) cannot access GPT. Among the
is a vfat partition which I mount under winxp - acts as a way to
share files on a dual boot system. However, windows cannot see
any partitions on this disk.
Now I would like to convert these partitions to MBR type of partitions
without losing the filesystems (data) in each partition.
I have no second disk to back up these partitions to.
Is it possible to make this conversion? How?
Microsoft brings you a new way to search the web. Try Bing™ now
I have installed Fedora 11 on HP Mini 5101 that has Broadcom 4353
It looks like that chip is currently unsupported under Fedora 11, does
anybody have a solution. I would like not to use windows drivers via
ndiswrapper if there is an alternative to it.
pratite me na twitteru - www.twitter.com/valentthttp://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic, msn: valent.turkovic(a)hotmail.com
I find myself in another nice catch 22.
Some time last week, I updated with yum (after several weeks of not
updating) and, for some reason, I was able to reboot that day, but
the next day attempting to boot Fedora resulted in a kernel panic.
Looking things up, I see I'm not the only one with a panicking kernel.
So, I got to work to clear the crudded kernel out of the way.
Took me a while of looking around the web to rediscover the
incantation to get to rescue mode with an install CD: "linux rescue"
at the second stage boot prompt.
Then I booted to rescue mode. I was thinking along the lines of, even
though I don't get a grub menu like on x86, I should be able to
change the configuration file to default to the previous kernel.
Is the usual approach to that to use ybin? (And it looks like, with
all the strange parameters, and the success rate I'm having today
with arcane command parameters, it would likely take several tries to
get it right.)
Isn't there an easier way to do this?
I tried passing the kernel name of the previous kernel in at the
second stage prompt, but, even though I figured out (again) the
arcane open firmware syntax to point to the kernel:
(Since the boot volume is separate, the path to the kernel is empty.)
it tells me that I should try passing in the init= parameter. I tried
several permutations of what I thought was the probable syntax,
boot: hd:3,/vmlinuz-220.127.116.11-191.fc11.ppc init=/
and such, but all of them failed to execute, suggested specifying
init= and left me at 180 seconds to reboot.
So I'm having a hard time with things today. Can someone put me out
of my misery?
On Sep 27, 2009, at 3:20 AM, a helpful person wrote me off-list:
(Leaving out the name in case the off-list was intentional. Or maybe
it was because it was a reply to my mis-post to the -test-list.)
> On Sat, Sep 26, 2009 at 07:19:45PM +0900, Joel Rees wrote:
>> it tells me that I should try passing in the init= parameter. I tried
>> several permutations of what I thought was the probable syntax,
>> boot: hd:3,/vmlinuz-18.104.22.168-191.fc11.ppc init=/
> Err..., init is a program you are running first. If everything
> else failed try 'init=/bin/bash'
Okay, [...] init=/bin/bash
VFS: mounted root [and something I missed as it rebooted.]
Freeing unused kernel memory: 332k init
Warning: unable to open an initial console.
Failed to execute /bin/bash. Attempting defaults. . .
Kernel panic. - not syncing: No init found. Try passing init= option
Rebooting in 180 seconds.
> Don't you have some earlier kernel which still boots? If that fails
> too then maybe indeed your /sbin/init is messed up but that would
> have nothing to do with kernels.
The previous kernel did work, as I mentioned in another post, but
only when I went in, renamed it (and the three other files) and so
forth, as I described in the other post. I've yum remove-d
kernel-22.214.171.124-43.fc11.ppc, and so it boots the old kernel and seems
to run okay.
So if the init= parameter is not supposed to be the initrd file, the
bug in yaboot (under this ibook's openfirmware) might be that it's
trying to pass an init= parameter when none is specified on the boot
I got a message back from the developers, from a comment I left where
someone else reported this bug. Getting a fixed kernel is going to
take a little time, they say.
In the meantime, I'm avoiding updating, to keep the kernel at the
previous level, and hoping the kernel/userland level mismatch will
not bomb me out of anything important.
i'm putting together a tutorial on network services, and i'm really
uninterested in investing any time in covering NIS. anyone out there
still using it? is it worth it?
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
For anyone, but particularly Les H.
I have been re-reading some notes I have made on how DRAM works. As a
result I have a couple of unanswered questions?
1) This question is for personal visualization purposes. I fully realize
it makes no real difference on how DRAM works.
What is the most common arrangement of memory cells (??) within a memory
stick. It seems to be proprietary information? I have seen schematics
of two possibilities; a) with each stored bit side-by-side for the
length of a 'word' or in my case a 'double word' (i.e. 64 bits), or, b)
in a 4 X 4 arrangement. Is there some place in the DRAM manufacturer's
specification I could be looking to determine this?
As I said, this question is for no technical reason. When I am thinking
about DRAM memory, I use a visualizations in my mind about what is
happening in memory. I would like my mental vision of the process to be
as close to physical reality as possible.
2) When referring to DRAM memory, what is a 'cell'; is it physically one
bit (capacitor, transistor, lines and all) or is a cell a group of them?
If it is a group, from what I have read it is a bit ambiguous whether
'cell' refers to one 4 X 4 ( or one 16 bit linear) arrangement, one
'word' or one 'double word'?
Fedora 11, Gnome 2.26.3
Evo.2.26.3, Emacs 23.1.1
For a quick and dirty web page edit, such as adding a single date to a club
calendar, I like seamonkey composer. At the moment I have to open the web
browser then change to composer, which seems silly. I've added the relevant
command to the manu. Can anyone tell me how to add composer to the krunner,
or will it appear when I've called it a few times? Thanks
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
Yup. it crashes - every time for me.
I have all the latest updates installed.
Open the Nautilus main browser, select Edit->Preferences
and bugtool pops up and crashes all open Nautilius browsers.
Not very nice.