[ale] These times are a changing ... (at least Slackware is)

[Benjie]

Did you look at the boot messages ( Is there any reference to
/dev/sda?)  Try dmesg | less, and look for a reference to /dev/sda
being found.  Also, what scsi card are you using?  The upgraded distro
may not be loading the kernel module for it.

On 8/25/07, Bob Kruger <bkruger at mindspring.com> wrote:
> All;
>
> I just upgraded a faithful and trusty server that had been running
> Slackware v9.0 to Slackware v12.0.  This machine has two IDE drives (hda
> and hdb) and one SCSI drive (sda).
>
> Upgrade went flawlessly until I tried to mount the SCSI drive.  I
> usually use a line like so (until I update my /etc/fstab file)
>
> mount -t ext3 /dev/sda1 /pub/sda
>
> (Note - mount point, e.g. directory, /pub/sda exists.)
>
> Much to my surprise, I got the message:   mount: special device
> /dev/sda1 does not exist
>
> A quick check of the /dev directory shows no device sda1, which I had
> always seen in past Slackware versions.
>
> Has something drastically changed, or is there a simple way that I can
> create the device /dev/sda and /dev/sda1 in the /dev directory and keep
> driving on?
>
>  From another older slackware server, doing ls -la /dev/sda* results in:
>
> brw-rw----  1 root disk 8,  0 1995-04-29 06:33 sda
> brw-rw----  1 root disk 8,  1 1995-04-29 06:33 sda1
>
> Hopefully there is a simple way for me to create these in the /dev
> directory and not have to bother with massive changes.
>
> Thanks in advance for any assistance.
>
> V/r
>
> Bob
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>


-- 
"The most important thing to remember about drunks is that drunks are
far more intelligent than non-drunks. They spend a lot of time talking
in pubs, unlike workaholics who concentrate on their careers and
ambitions, who never develop their higher spiritual values, who never
explore the insides of their head like a drunk does."  -- Shane
McGowan