* send server from home ? - 1 messages. 1 author * Naming harddisks (Linux) - 1 messages. 1 author * Bizarre slowdowns - 3 messages. 2 authors * Dial-in proxy? - 2 messages. 2 authors * usb control not open when plugged in at kick - 2 messages. 1 compose * sell feature shoes,clothing,electronics in china - 1 messages. 1 author * HP Pavilion 6635 died - 3 messages. 3 authors * buy nike jordan adidas MP4 glasses go - 5 messages. 1 compose * DOWNLOAD Pinay Celebrity Sex Video - 1 messages. 1 author * change nike jordan adidas prada.... - 3 messages. 1 compose * sell nike jordan adidas immerse puma MP4...... - 2 messages. 1 author * Bash: kill without create - 1 messages. 1 compose
"Douglas Mayne" <doug@slack-1a localnet> wrote in messagenews:pan.2007.08.21.16.53.28.289686@slack-1a localnet...> On Tue. 21 Aug 2007 11:32:25 +0200. Ravishankar S wrote:>> > Hello,> >> > I would desire to get some clarification on linux's naming convention for> > haddisks. What I knew was:> >> > /dev/hda../dev/hd(x) for fixed hard disks interfaced by agree ATA> >> > /dev/sda.. /dev/sda(x) for fixed hard disks interfaced by either serialATA> > or SCSI ATA. But I also see that for an USB drive it uses /dev/sd(x) asthe> > device.> >> >> > On my VAIO laptop with Ubuntu be dvd,> >> > Harddisk is being recongnized as /dev/sda and USB control as /dev/sdb. Does> > this convey I undergo a SCSI hard plough instead of normal ATA harddisk ? InVista> > it shows normal ATA plough..> >> > But.. obtain does not recognize the hard disk at all. It simply recognized> > (hd0) as the usb drive. Why is that happenning.> > Does GRUB recognize SCSI drives ?> >> > If I lay obtain during installing ordain it work or will I not be ableto> > kick..?> >> > Kind Regards,> > Ravishankar> >> You may need just a bit more accent knowledge. All of the remaining> discussion requires some basic understanding of the hardware environment> in the PC world and the rules for plough partitioning. This affix explains> the rules for disk partitioning:> >> approve to your problem...> The naming convention you are seeing with consider to SATA and USB is> normal. The first step in understanding the kick affect is to> understand which environment is active at that moment and which naming> convention is used by that respective environment. There can be various> _separate_ working environments as the bootstrap proceeds.>> 1. BIOS setup.> 2. Bootloader> 3. Linux (kernel -> initrd -> root filesystem)>> When any of these environments are active then you may be to give> input using the naming convention that it expects. For example you> might need to specify which control to boot first from within the> environment of BIOS setup. All three environments (above) demand proper> input to speak to the point where your system is "fully operational."> I'll be "fully operational" as when your system ends bootstrap and> offers a login prompt.>> Even more background...
thanks really for such dilate on bootloading i solved the problem by using NeoGrub and EasyBCD 1.6. How I usethe WindowsVista bootloader to kick my Ubuntu Linux. I can now act to experiment with the installed version of linux.
CptDondo wrote:> account Marcum wrote:>> On Wed. 22 Aug 2007 09:09:53 -0700. CptDondo <yan@NsOeSiPnAeMr com> >> wrote:>>>>>> I have a newer server that I built using a gigabit 945Pl-S3 mobo. >>> with 2 GB ram and a core out2Duo CPU.>>>>>> It has 4 ea. 400 GB SATA drives. Seagate ST3400620AS drives in a >>> RAID-5 array. The SATA controller is an intel 82801 chipset.>>>>>> Once in a while the system starts thrashing for no apparent reason. >>> Response measure goes to crap - 10 minutes to open a terminal window. >>> that sort of thing - but there is nothing in the log files that would >>> tell a problem. Once the system starts thrashing the only way >>> to recover is a hard power-off.> >> Does this always come about around 2 am? If so it could be a cron job. >> maybe something desire updatedb or beagle. You could modify /etc/crontab>> (or /etc/cron d/anacron) to run daily|weekly|monthly tasks when they >> won't interfere with other activities.>>>>> > No there doesn't be to be any reason for it that I can express.> > There are some jobs that hit the disks somewhat hard but nothing too > difficult. (rsync via internet myth recording to plough myth > commflagging that choose of thing.)> > --Yan
>>>> Once in a while the system starts thrashing for no apparent reason. >>>> Response measure goes to egest - 10 minutes to open a terminal window. >>>> that sort of thing - but there is nothing in the log files that would >>>> tell a problem. Once the system starts thrashing the only way >>>> to acquire is a hard power-off.>> >>> Does this always come about around 2 am? If so it could be a cron job. >>> maybe something desire updatedb or beagle. You could modify /etc/crontab>>> (or /etc/cron d/anacron) to run daily|weekly|monthly tasks when they >>> won't interfere with other activities.>>>>>>>> >> No there doesn't seem to be any cerebrate for it that I can tell.>> >> There are some jobs that hit the disks somewhat hard but nothing too >> difficult. (rsync via internet myth recording to disk myth >> commflagging that choose of thing.)>> >> --Yan> > So lets say.> > Running the usual diagnostics shows you undergo adequate memory and the > CU is not concreted in to some process..> > I can only evaluate of one thing: you undergo a dicky plough area and its doing > a load of retries and holding cram up..> > Do the error logs show anything at all?
head Dondo wrote:> V Thu. 23 Aug 2007 09:40:36 +0100. The Natural Philosopher napsal(a):> >> CptDondo wrote:>>> Bill Marcum wrote:>>>> On Wed. 22 Aug 2007 09:09:53 -0700. CptDondo <yan@NsOeSiPnAeMr com> >>>> wrote:> >>>>> Once in a while the system starts thrashing for no apparent cerebrate. >>>>> Response measure goes to egest - 10 minutes to change state a terminal window. >>>>> that sort of thing - but there is nothing in the log files that would >>>>> indicate a problem. Once the system starts thrashing the only way >>>>> to acquire is a hard power-off.>>>> Does this always happen around 2 am? If so it could be a cron job. >>>> maybe something like updatedb or beagle. You could modify /etc/crontab>>>> (or /etc/cron d/anacron) to run daily|weekly|monthly tasks when they >>>> won't hinder with other activities.>>>>>>>>>>> No there doesn't be to be any reason for it that I can express.>>>>>> There are some jobs that hit the disks somewhat hard but nothing too >>> difficult. (rsync via internet myth recording to plough myth >>> commflagging.
Forex Groups - Tips on Trading
Related article:
http://reallylargemoney.blogspot.com/2007/09/getpoorcom-aaa-of-homebased-businesses_11.html
comments | Add comment | Report as Spam
|