Fedora-Live-Workstation-x86_64-21-5 on Alienware laptop
by don fisher
I have an Alienware 17-1 laptop that I would like to run Fedora linux
on. The laptop has 2TB of disk, 32GB of ram and NVIDIA GeForce GTX 880M
graphics, so I thought it would make a great development platform. I
inserted the Fedora live DVD and booted. It asked If I wanted to check
the disk, which I did. Next I started Fedora. It got to the point where
the fedora logo is on the screen, and then disappeared. The fans came
on, so I assumed it was doing something, but after about 5 minutes the
system appeared to be still in the same state.
In the past there has been an install image that is about 4.3GB large
that guides the installation. I cannot find an similar image for F21. I
have been away for awhile, so if this is well known please forgive me. I
looked at the documentation and did not see any mention.
Will Fedora work on an Alienware laptop? I though the since it was Dell
it should. If so, what is the best way to load Fedora onto it? Is the
fact that the live DVD failed telling me I am out of luck?
Thanks,
Don
--
-----------------------------------------------------------------
| Don Fisher hdf3(a)comcast.net |
| 865 W. Cresta Loma Dr. VOICE: (520)888-7613 |
| Tucson, AZ. 85704-3705 |
-----------------------------------------------------------------
9 years, 2 months
despirate help needed - Samba and security = share
by Gary Stainburn
Many years ago I built a server on Fedora 8 which became my core network
server running all the network servers (DNS etc) as well as a host of custom
services over inetd, However it's main purpose was to service Samba shares.
That server is now failing so I've just spent a week building a new F20 server
and converting everything from F8 to F20 - amazing number of changes needed
but also an amazing number of things are still the same.
Last of the things to move because the old server is still live and serving is
SAMBA. This is where I need the help.
All of my servers run the same type of setup and it's all based
around "security = share". Why is this so universally declared as bad??
I know when I built some F16 servers it said that "security = share" was
depreciated but it still let me use it. Now with F20 it just refuses.
The problem is that security = share did *exactly* what I wanted and now I
can't seem to achieve the same effect any other way.
Very simply, I use the [homes] section and have about 10 users defined on the
server - service, parts, admin etc.
Then for each user PC (approx 120 - 150) I then map a network drive to each
service that is required. Many only have one or two but some people such as
admin have access to sales, accounts, wages and admin.
All very simple and faultless for 8 years.
Now, when I try some of the examples found online, client PCs seem to be able
to connect to the first share ok but then whenever I try to connect a second
share it complains about having to log out of the first share first.
Can anyone please help me here. If I can't get it working I'll have to scrap
my week's work and install F16 on this box.
Fingers crossed
9 years, 2 months
initscripts
by poma
Lukáš 'Allo 'Allo
I see that some people are trying to "modernize" Fedora.
But what about RHEL relictum - initscripts, particularly now that we have NetworkManager/ModemManager and systemd-networkd,
when will this package "fall off"?
poma
9 years, 2 months
libreport crashing
by SternData
Every time I use abrt to try to report a problem, it crashes with an
error in libreport. Unfortunately, I can't report that because
attempting to do so crashes abrt.
Is it just me or are others seeing this problem?
--
-- Steve
9 years, 2 months
Corrupted Hard Drive
by Mickey
Fedora 15 Hard drive. ext4
# e2fsck -b 8193 /dev/sdb
e2fsck 1.42.8 (20-Jun-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
What command should I use to overcome this ?
I'm using Fedora 20 to check the hard drive.
9 years, 2 months
Wireless can't ping wireless
by Jim Lewis
I just realized that my wireless computers can't ping each other.
Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
are all on the same subnet. If I switch to wired the computer can then
ping a wired or wireless. The computers can all access the Internet at
any time (either wired or wireless). I did some research and have
determined the problem might be my router.
I use a LinkSys E3000 which I have had for a very long time. I checked
their site and looked at the Release Notes for firmware upgrades. No
mention of this issue and so I am hesitant to perform it (I did however
download the latest file). I got into their Live Chat and the guy said
since the unit is no longer in warranty I would have to pay to get
assistance. I thought about doing this, but he could not guarantee
success and the payment is not refundable. I thought that sucked and
told him so.
So, does anyone have any ideas about how I might solve this? I am going
to be rather surprised if the problem is not the router. If it matters
here is my hardware:
Fedora 14 - wired desktop
Fedora 20 - wireless laptop
Fedora 21 - wireless laptop (or wired)
Fedora 21 - wireless laptop (or wired)
Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3)
Jim Lewis
9 years, 2 months
rsyslogd is stuck in D state
by Neal Becker
/usr/sbin/rsyslogd is stuck in D state, seems to be hogging my disk I/O
what is it doing??
I don't see anything interesting in /var/log/messages
--
-- Those who don't understand recursion are doomed to repeat it
9 years, 2 months
Anaconda illegal address
by CLOSE Dave
When anaconda complains about an "illegal IP address string passed to
inet_aton", how can I discover what the bad string contains? So far as I
can see, all the configured addresses are perfectly valid. Here's a copy
of the traceback: <http://ur1.ca/jkjvw>.
--
Dave Close, Thales Avionics, Irvine California USA.
cell +1 949 394 2124, dave.close(a)us.thalesgroup.com
"If a cluttered desk is a sign of a cluttered mind,
of what then is an empty desk?" --Albert Einstein
9 years, 2 months
Re: users Digest, Vol 131, Issue 86
by William W. Austin
On 2015-01-28 15:45:36, users-request(a)lists.fedoraproject.org wrote:
======quoted message from Gordon Messmer <gordon.messmer(a)gmail.com>, subject "Re: Suddenly can't get nameserver resolution on FC21 after ..."======
> On 01/28/2015 07:02 AM, William W. Austin wrote:
> > I have checked my ifcfg-* files under/etc/sysconfig/ (all 3 links
> of
> > each of the 2 nics) and they are unchanged. My /etc/hosts file is
> > unchanged
>
> DNS is configured in /etc/resolv.conf. Look there.
>
> Attempt to ping your DNS servers to verify they are reachable.
>
> Use "dig" to query them directly:
> dig @<dns IP address> <hostname>
Apologies - I neglected to include:
A) I can ping my gateway (route/cablemodem) just as before
B) I can ping all 3 of my nameservers with no trouble
D) Using dig (as you suggest) works correctly and resolves properly/
C) My /erc/resolv.conf is unchanged (and identical those on 2 other machines which work correctly).
D) IF I have the ip-address of a website (I can get that using another machine on my network), I can use the address in a browser and actually bring up the site.
Nevertheless I cannot ping, ssh or telnet to, or sftp/ftp to ANY site (even those on my internal network) unless I have the ip address of the machine.
So to me these are a clear indication that for some reason this system is refusing to use the nameservers as such.
The reason WHY this is the case still escapes me, and any help with the matter would be greatly appreciated.
Thanks,
- wwa
--
william w. austin airedad(a)att.net
"life is just another phase i'm going through. this time, anyway ..."
9 years, 2 months
End of 32-bit support?
by William Oliver
I recently read an interesting article recently that suggested that
Fedora 23 might be 64-bit only:
See:
http://www.phoronix.com/scan.php?page=news_item&px=Fedora-23-64-bit-Proposal
It's not a big deal to me -- all of my boxes are fairly modern.
However, I thought one of the big selling points of linux in general is
that you could run it on just about anything, including old, obsolete
boxes.
I've never been involved in doing packaging, etc., and I started
thinking...
How hard is it to make a 32-bit distro if you are making a 64-bit one
anyway? I guess in the back of my mind I sorta assumed it was scripted
and automatic, so it just meant running some script twice rather than
once.
Is it a tremendous hassle to make a 32-bit distro if you are making a
64-bit one anyway?
billo
9 years, 2 months
